Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Locale::Po4a::AsciiDoc is pot_in: supported #401

Open
benoitrolland opened this issue Mar 26, 2023 · 2 comments · Fixed by #402
Open

Locale::Po4a::AsciiDoc is pot_in: supported #401

benoitrolland opened this issue Mar 26, 2023 · 2 comments · Fixed by #402

Comments

@benoitrolland
Copy link

benoitrolland commented Mar 26, 2023

First, thank you so much for the great job of including assciidoc into po4, allowing translation from asciidoc files.

Willing to exclude some elements from translation, I am trying to use the pot_in feature as described in the doc
When specifying the path to a copy of the originaly generated pot file as value to pot_in: in the po4a.cfg file,
a new pot file is generated on next run and is different from the first.
More of that it seems corrupted and as such is not usable within Poedit,
since the elements to be translated are full of # followed by what should be the comments .
msgid "" seems duplicated and its first occurence included within the normally preceeding comments:

#. type: Plain text
#: po4a/book-I.adoc.pp.filtered.pot:149
#: po4a/book-II.adoc.pp.filtered.pot:139
#: po4a/book-III.adoc.pp.filtered.pot:139
msgid ""
"#. type: Plain text #: book-I.adoc.pp:174 Book-"
"II.adoc.pp:164 #: book-III.adoc.pp:164 #, no-"
"wrap msgid \"\" \"This is a text to not show the real one"
"but technically this is, \\\"the_same_\\\", I hope you"
"do not mind."

@benoitrolland benoitrolland changed the title Locale::Po4a::AsciiDoc is pot_in: suported Locale::Po4a::AsciiDoc is pot_in: supported Mar 26, 2023
@mquinson
Copy link
Owner

Hello @benoitrolland,

as for your other issue, I need some documents to reproduce the error, please. It may be a branch in an existing project where you try to use the pot_in feature, or an archive file, or even a brand new little project created for the sole purpose of providing this minimal working example.

Thanks for your interest,

jnavila added a commit to jnavila/po4a that referenced this issue Apr 2, 2023
This partly fixes mquinson#401 but not completely. The problem is that po
format does not support inline markup, so we cannot hide formatting
marks away from translators. We could use a different format for the
translation (for instance xml), but this would require a lot of
changes in AsciiDoc.pm.

Signed-off-by: Jean-Noël Avila <[email protected]>
mquinson pushed a commit that referenced this issue Apr 13, 2023
This partly fixes #401 but not completely. The problem is that po
format does not support inline markup, so we cannot hide formatting
marks away from translators. We could use a different format for the
translation (for instance xml), but this would require a lot of
changes in AsciiDoc.pm.

Signed-off-by: Jean-Noël Avila <[email protected]>
@mquinson mquinson reopened this Apr 14, 2023
@mquinson
Copy link
Owner

@benoitrolland could you please provide more info? If not, I'll have to close the issue as I fail to understand the problem for now.

Thanks in advance,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants