Hi!
I had a look at Asciidoc documentation, your change looks fine; I
committed a fix.
Thanks, your fix looks great. Good to get some structure in there.
> Example:
>
> #. type: Plain text
> #: target/original/src/introduction/what-is-a-graphdb.asciidoc:20
> msgid "[\"dot\", \"graphdb-GVE.svg\",
\"meta\"]"
> msgstr "[\"dot\", \"graphdb-GVE.svg\",
\"meta\"]"
>
> I do think this message should get translated (as there may be
> attributes in there that you wish to alter in a translation), but it's
> not plain text.
I still do not fully understand Asciidoc syntax, but I guess that we
need to allow customization as is done in other po4a modules (for
instance LaTeX or Xml).
The question for me is how this holds up for really long lines?
If such lines get wrapped into multiple lines in the generated translation,
it's not AsciiDoc any more.
I'll have to check how that works.
And set up a test case for another thing i saw (and worked around) today.
Anyhow, I'm happy with the progress we're making.
This will be awesome :-)
My plan is to keep migrating translated documents over to use po4a,
and report problems I encounter. We use a lot of the features in
AsciiDoc, which might be a good thing here.
/anders