Þ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 ***