On Sun, Feb 22, 2009 at 04:45:51PM +0900, Osamu Aoki wrote: > Oops, reformating line made wrong text.. > > On Sun, Feb 22, 2009 at 12:31:10PM +0900, Osamu Aoki wrote: > > Package: po4a > > Version: 0.35-1 > > Severity: normal > ... > > It seems to me that > > * <authorgroup> section is correctly split into strings down to > > * <surname> <firstname> <holder> tag is correctly treated as inline > > * within <authorgroup> commented line with --previous option has funny > > "# type: ...." line with wrong tag with respect to the latest > > original file while line number is correct. > > this should have been: > > It seems to me that > * <authorgroup> section is correctly split into strings down to > <surname> <firstname> > * <holder> tag is correctly treated as inline > * within <authorgroup>, commented line with --previous option has funny > "# type: ...." line with wrong tag with respect to the latest > original file while line number is correct. > > This may be issue with backend getttext / msgmerge tool chain though...
Yes, this is msgmerge, which formats the "previous" strings. It will not be possible (and non standard) to introduce "#| type:" or "#|: " lines. # type: Content of: <book><bookinfo><authorgroup><author><firstname> #: ../en/debian-reference.en.xml:23 #, fuzzy #| type: Content of: <book><bookinfo><copyright><holder> #|: ../en/debian-reference.en.xml:35 #| msgid "Osamu Aoki" msgid "Osamu" msgstr "青木 修 (Osamu Aoki)" I will check if using a msgctxt would fix this without drawbacks (I fear It could break string reuse) Using an EXTRACTED-COMMENTS instead of TRANSLATOR-COMMENTS could be better (this will fix the last point, about outdated tag) Best Regards, -- Nekral -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
