On 23 February 2013 12:38, Andrea Pescetti <pesce...@apache.org> wrote:
> On 22/02/2013 janI wrote: > >> so to cut it short, I would like to provide the most information posssible >> to translators but comments is not supported by the .po file structure. >> > > Am I missing something? PO files do support comments, and PO editors, like > POEdit, support displaying comments. So (even though I have no idea if the > current x-comments have meaningful information or not, so I surely won't > complain if x-comments are dropped) supporting PO files won't get in the > way of supporting comments. > > The documentation at > http://www.gnu.org/savannah-**checkouts/gnu/gettext/manual/** > html_node/PO-Files.html<http://www.gnu.org/savannah-checkouts/gnu/gettext/manual/html_node/PO-Files.html> > shows support for both translator's comments and extracted (programmer's) > comments. > > Regards, > Andrea. > Hi. No offence, but that is what I call the easy answer without considering the field we work in. I know that the format of .po files are: white-space # translator-comments #. extracted-comments #: reference... #, flag... #| msgid previous-untranslated-string msgid untranslated-string msgstr translated-string However I have not managed to utilize all of this information, and make sure it works across pootle, our own source files and editors like poedit, not forgetting that some of our translators use "normal" editors. But I stand corrected, and hereby reformulate my reply to tj: I am not skilled enough to use the comments in .po files, consistent with the way x-comment (and x-translate) are used in our source files. I am currently trying to make sure the .po files are generated consistent, which is more than enough of a challenge. We have so many things in the current translation that is not working correctly, like I just found a string with the text: "Note: After a password has been set, the document will only open with the password. Should you lose the password, there will be no way to recover the document. Please also note that this password is case-sensitive." Our current solution only detects (and translates): "Note: After a password has been set, the document will only open with" Which to me missed significant information, therefore I concentrate on getting a solution that works and are robust instead of utilizing every possibility (that are not used in 98% of the messages, at this moment I have removed 11 x-comment). If anybody feel they can do a better job or help me make a better solution, please come forward, I would be more than happy to get help. Sorry about the not fullfilling answer before, I hope the corrected answer clarifies the problems and explains why I focus as I do. Jan I.