Re: [libreoffice-l10n] Capturing and sharing translator feedback using x-comment language
On 2011-03-02 09:45, Andras Timar wrote: 2011/3/2 Dwayne Baileydwa...@translate.org.za: I few years ago I worked on some changes to oo2po that allowed the 'x-comment' language to be extracted to translator comments. Similarly the 'translations' of x-comment could be pushed back into the source. This puts translator comments in the hands of people who understand what needs commenting. Comments would be useful in place where: 1. Variables are not clearly defined 2. Blank entries 3. Verb/noun disambiguation I haven't used the x-comment feature since I wrote it. But I assume it will still work. It works quite simply. The 'translations' are placed in x-comment entries. When running oo2po the 'x-comments' are placed in the PO files translator comments section. Then on Pootle any translator can make a suggestion to the x-comment language, an English review team would go through those comments, make fixes in the source string or accept the comment. Each release would need to be 'translated' by the team to review any new texts. Hi Dwayne, This sound very interesting. How can you extract x-comments that it is not present in the SDF template? Can you please give us the commands to use? This is the bit that is outside of my expertise. How is the EN/DE .sdf created in the first place. From my understanding it would then be a matter of adding x-comment. -- Dwayne -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/l10n/ *** All posts to this list are publicly archived for eternity ***
Re: [libreoffice-l10n] Capturing and sharing translator feedback using x-comment language
2011/3/2 Dwayne Bailey dwa...@translate.org.za: On 2011-03-02 09:45, Andras Timar wrote: 2011/3/2 Dwayne Baileydwa...@translate.org.za: I few years ago I worked on some changes to oo2po that allowed the 'x-comment' language to be extracted to translator comments. Similarly the 'translations' of x-comment could be pushed back into the source. This puts translator comments in the hands of people who understand what needs commenting. Comments would be useful in place where: 1. Variables are not clearly defined 2. Blank entries 3. Verb/noun disambiguation I haven't used the x-comment feature since I wrote it. But I assume it will still work. It works quite simply. The 'translations' are placed in x-comment entries. When running oo2po the 'x-comments' are placed in the PO files translator comments section. Then on Pootle any translator can make a suggestion to the x-comment language, an English review team would go through those comments, make fixes in the source string or accept the comment. Each release would need to be 'translated' by the team to review any new texts. Hi Dwayne, This sound very interesting. How can you extract x-comments that it is not present in the SDF template? Can you please give us the commands to use? This is the bit that is outside of my expertise. How is the EN/DE .sdf created in the first place. From my understanding it would then be a matter of adding x-comment. It needs further investigation then. .sdf file does not contain x-comment by default. Caolan has added a new easy hack to address this issue: http://wiki.documentfoundation.org/Development/Easy_Hacks#Export.2FImport_.src_comments_to_.sdf.2F.po_format Andras -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/l10n/ *** All posts to this list are publicly archived for eternity ***
Re: [libreoffice-l10n] Capturing and sharing translator feedback using x-comment language
On 2011-03-02 14:32, Andras Timar wrote: 2011/3/2 Dwayne Baileydwa...@translate.org.za: On 2011-03-02 09:45, Andras Timar wrote: 2011/3/2 Dwayne Baileydwa...@translate.org.za: I few years ago I worked on some changes to oo2po that allowed the 'x-comment' language to be extracted to translator comments. Similarly the 'translations' of x-comment could be pushed back into the source. This puts translator comments in the hands of people who understand what needs commenting. Comments would be useful in place where: 1. Variables are not clearly defined 2. Blank entries 3. Verb/noun disambiguation I haven't used the x-comment feature since I wrote it. But I assume it will still work. It works quite simply. The 'translations' are placed in x-comment entries. When running oo2po the 'x-comments' are placed in the PO files translator comments section. Then on Pootle any translator can make a suggestion to the x-comment language, an English review team would go through those comments, make fixes in the source string or accept the comment. Each release would need to be 'translated' by the team to review any new texts. Hi Dwayne, This sound very interesting. How can you extract x-comments that it is not present in the SDF template? Can you please give us the commands to use? This is the bit that is outside of my expertise. How is the EN/DE .sdf created in the first place. From my understanding it would then be a matter of adding x-comment. It needs further investigation then. .sdf file does not contain x-comment by default. Caolan has added a new easy hack to address this issue: http://wiki.documentfoundation.org/Development/Easy_Hacks#Export.2FImport_.src_comments_to_.sdf.2F.po_format Further investigation of the command line options for localize.pl is probably the right way to do it. The oo2po and po2oo parts should work without any changes. I looked through my old emails and can't find anything about x-comments extraction, was probably discussed on IRC. I've forward you the email I wrote about how it should work with oo2po and po2oo. Rimas: don't worry seems Andras is on this -- regards Dwayne -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/l10n/ *** All posts to this list are publicly archived for eternity ***
[libreoffice-l10n] Capturing and sharing translator feedback using x-comment language
I few years ago I worked on some changes to oo2po that allowed the 'x-comment' language to be extracted to translator comments. Similarly the 'translations' of x-comment could be pushed back into the source. This puts translator comments in the hands of people who understand what needs commenting. Comments would be useful in place where: 1. Variables are not clearly defined 2. Blank entries 3. Verb/noun disambiguation I haven't used the x-comment feature since I wrote it. But I assume it will still work. It works quite simply. The 'translations' are placed in x-comment entries. When running oo2po the 'x-comments' are placed in the PO files translator comments section. Then on Pootle any translator can make a suggestion to the x-comment language, an English review team would go through those comments, make fixes in the source string or accept the comment. Each release would need to be 'translated' by the team to review any new texts. Rimas, is this something that you would be able to look at? -- regards Dwayne -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/l10n/ *** All posts to this list are publicly archived for eternity ***
Re: [libreoffice-l10n] Capturing and sharing translator feedback using x-comment language
2011/3/2 Dwayne Bailey dwa...@translate.org.za: I few years ago I worked on some changes to oo2po that allowed the 'x-comment' language to be extracted to translator comments. Similarly the 'translations' of x-comment could be pushed back into the source. This puts translator comments in the hands of people who understand what needs commenting. Comments would be useful in place where: 1. Variables are not clearly defined 2. Blank entries 3. Verb/noun disambiguation I haven't used the x-comment feature since I wrote it. But I assume it will still work. It works quite simply. The 'translations' are placed in x-comment entries. When running oo2po the 'x-comments' are placed in the PO files translator comments section. Then on Pootle any translator can make a suggestion to the x-comment language, an English review team would go through those comments, make fixes in the source string or accept the comment. Each release would need to be 'translated' by the team to review any new texts. Hi Dwayne, This sound very interesting. How can you extract x-comments that it is not present in the SDF template? Can you please give us the commands to use? Thanks, Andras -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/l10n/ *** All posts to this list are publicly archived for eternity ***
Re: [libreoffice-l10n] Capturing and sharing translator feedback using x-comment language
Þann mið 2.mar 2011 07:23, skrifaði Dwayne Bailey: I few years ago I worked on some changes to oo2po that allowed the 'x-comment' language to be extracted to translator comments. Similarly the 'translations' of x-comment could be pushed back into the source. This puts translator comments in the hands of people who understand what needs commenting. Comments would be useful in place where: 1. Variables are not clearly defined 2. Blank entries 3. Verb/noun disambiguation BTW, anyone interested in good l10n support on behalf of devs should take a look at orca.master.pot (GNOME) which is commented to death :-) Example: #. Translators: this announces that a bookmark has been entered. #. Orca allows users to tell it to remember a particular spot in an #. application window and provides keystrokes for the user to jump to #. those spots. These spots are known as 'bookmarks'. #. #: ../src/orca/bookmarks.py:79 msgid bookmark entered msgstr This case may be a bit over the top, but then one has to understand the uses of the software itself (accessibility). They never take anything for granted... Even when using KID to locate messages in the UI (do we have this for LibreOffice ?) a translator/localizer can have difficulties on defining relations between a string and its function (such as Verb/noun disambiguation). Wanted just to say that the LibreOffice devs could do a bit more for the l10n community, they don't like uncommented code either... Regards Sveinn í Felli -- Unsubscribe instructions: E-mail to l10n+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/l10n/ *** All posts to this list are publicly archived for eternity ***
