Looking at the export of strings from 2.2.0, I see many
strings exported as
having a translation while it actually is untranslated.
Example:
basic/source/app/basic.src
basic/source/app/localize.sdf
RID_CALLDLG isn't translated for it, ja, pt-BR, sw-TZ,
zh-CN, zh-TW. The sv
translation as well, but has an upper/lowercase typo.
Exporting one of these translations using 'localize -e -l
<id> -f <file>'
exports the "untranslated" string as well. Using
the exported file for further
translations is ugly, because you start with 100% translated
messages unless you
assume that for languages != en-*, all messages with
msgid=msgstr are actually
untranslated.
- Is there a better way to do that?
- Why are the untranslated messages imported in the sources
in the first
place? Is OOo unable to handle untranslated messages, or
should these
no-translations just be removed?
Matthias
_______________________________________________
Openoffice mailing list
Openoffice lists.ximian.com
h
ttp://lists.ximian.com/mailman/listinfo/openoffice
|
