PO set custom comments?

l10n
#1

Would it be possible to maintain a custom comments in PO files of the template set? Sort of what translate-toolkit utils add, "# (pofilter)"?

The use I have in mind for that right now is keeping meta-information, e.g., hints for translators. Sort of: "the term XYZ in this record relates to record ID4 (e.g., namedlg.src#RID_SCDLG_NAMES.STR_HEADER_RANGE.string.text)" or "translate in line with ID1, ID2, ID3" or "option name, not command".

Yury

#2

Could also the plural/singular(/dual) be used within po files?

Lp, m.

#3

Hi,

Would it be possible to maintain a custom comments in PO files of the
template set? Sort of what translate-toolkit utils add, "# (pofilter)"?

Yes, there were discussions on this mailing list about extracting the
x-comment strings from the source. Currenty we don't have many
x-comments. It is not enough to have the tools that extract them, but
we need to write those comments. It's kind of a chicken and egg
problem, why work on extracting the comments when we have only a few,
and why write comments when nobody sees them. :slight_smile: If someone sends a
patch for either extraction or for making things clear in the source,
then we can make progress. Let me know, if I should send code
pointers.

Thanks,
Andras

#4

No, because po is only a container for the translations, LibreOffice
does not use gettext internally. Could you please assign any bugs to
me which are related to wrong plural handling in LibreOffice. I think
there are not many, and we can fix them one by one.

Best regards,
Andras

#5

I was rather referring to the possibility of 'just' having extra comments associated with certain 'strings' and kept there.
Would this be equivalent to the introduction of extra source code? What serves as a master-copy of (en-US) templates then, actually, a Pootle or PO set?

Yury

#6

...
Just after sending, saw Andras' answer to Martin. Scratch my questions, as the problem is of another scale than I thought.

Yury