[Po4a-devel] before filing a bug report...

[Marco Ciampa]

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&group_id=30267&atid=410622

(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 |
+------------------------+