11:08 a.m.
It seems that the asciidoc filter of po4a does not "understand" include::
macros.
That would be a veeery nice addition and will put po4a + asciidoc on-par
with sphinx that handle translation of included file perfecty well....
(a little antagonism is well put here... ;-)
With multi-chapters documents you have to create apposite scripts to
handle this, see this ugly hack for instance:
https://github.com/ciampix/kicad-doc/blob/master/src/Makefile#L107
My humble opinion is that this is a bug.
May I file a bug report?
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
+------------------------+
| GNU/Linux User #78271 |
| FSFE fellow #364 |
+------------------------+
1:57 p.m.
New subject: [Po4a-devel] before filing a bug report...
Quoting Marco Ciampa (2015-05-25 18:08:44)
My humble opinion is that this is a bug.
May I file a bug report?
You may always file a bugreport in Debian.
If not a bug then it can easily be demoted to "severity wishlist", or
closed outright if judged unsuitable treating even as proposed
improvement.
Regards,
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
6:42 p.m.
New subject: [Po4a-devel] before filing a bug report...
On Mon, May 25, 2015 at 08:57:39PM +0200, Jonas Smedegaard wrote:
Quoting Marco Ciampa (2015-05-25 18:08:44)
> My humble opinion is that this is a bug.
>
> May I file a bug report?
You may always file a bugreport in Debian.
If not a bug then it can easily be demoted to "severity wishlist", or
closed outright if judged unsuitable treating even as proposed
improvement.
The same applies for the alioth bug tracker if you prefer that tool to
the debian bug tracker. I use both, don't worry.
Bye, Mt.
PS: my answer to the actual question will come in another mail, when
time permits
--
This message has been made up using recycled ideas and language constructs.
No tree has been cut nor animal harmed in process of making it.
7:02 p.m.
New subject: [Po4a-devel] before filing a bug report...
Hello
I do agree. That's a bug that you should fill. But I need more
information here, like a pointer to the specification of asciidoc and
a document using that feature.
It would be really really cool if you could provide a test case for
the feature that you would like to see implemented (check in the t/
directory in the archive for the filenames to use and the kind of code
to write if you know some perl). Even only the asciidoc and po files
with no Perl would be really helpful.
Naturally, a patch for the feature would be the best, but the test is
already really helpful if you want to see that feature implemented.
Thanks, Mt.
On Mon, May 25, 2015 at 06:08:44PM +0200, Marco Ciampa wrote:
It seems that the asciidoc filter of po4a does not
"understand" include::
macros.
That would be a veeery nice addition and will put po4a + asciidoc on-par
with sphinx that handle translation of included file perfecty well....
(a little antagonism is well put here... ;-)
With multi-chapters documents you have to create apposite scripts to
handle this, see this ugly hack for instance:
https://github.com/ciampix/kicad-doc/blob/master/src/Makefile#L107
My humble opinion is that this is a bug.
May I file a bug report?
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
+------------------------+
| GNU/Linux User #78271 |
| FSFE fellow #364 |
+------------------------+
--
Computers are useless. They can only give you answers. -- Pablo Picasso
2:53 a.m.
New subject: [Po4a-devel] before filing a bug report...
On Thu, May 28, 2015 at 02:02:31AM +0200, Martin Quinson wrote:
Hello
I do agree. That's a bug that you should fill. But I need more
information here, like a pointer to the specification(1) of asciidoc and
a document using that feature.(2)
1) http://www.methods.co.nz/asciidoc/chunked/ch21.html
2) https://github.com/ciampix/kicad-doc/blob/master/src/Eeschema/Eeschema.adoc
bear in mind that due a bug similar to this for images:
https://alioth.debian.org/tracker/index.php?func=detail&aid=314919&am...
(by the way: was the bug report attached patch applied to the new 0.46
version? I mean, is this bug still present in 0.46? I am sorry but I am
not acquainted with that bug report system. It seems to me that this bug
report/patch is still unnoticed)
include should have a bogus text inside like
include::chapt1.txt[foo]
since
include::chapter1.txt[]
raise an error in po4a:
po4a::asciidoc: Unable to parse attribute list: []
this with po4a version 0.45
Is this a different bug?
Is this still present in the 0.46 version?
Can someone check please?
----------------
You just have to create a couple of test asciidoc files like these:
test.adoc:
= Hello
Here is some text
include::test-inc.adoc[]
Then other text
1) hello
2) hi
3) bye
test-inc.adoc:
This is included text
* item
* item
* item
then run:
po4a-gettextize -f asciidoc -m test.adoc -p test.pot
----------------
Should I file another, I mean separated, bug report for this?
TIA
Regards,
--
Marco Ciampa
I know a joke about UDP, but you might not get it.
+------------------------+
| GNU/Linux User #78271 |
| FSFE fellow #364 |
+------------------------+
3468
days inactive
3471
days old
4 comments
3 participants
participants (3)
-
Jonas Smedegaard -
Marco Ciampa -
Martin Quinson