Issue 81914 - untranslated message strings cannot be identified
Summary: untranslated message strings cannot be identified
Status: CONFIRMED
Alias: None
Product: Internationalization
Classification: Code
Component: ui (show other issues)
Version: OOo 2.3
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks: 81913
  Show dependency tree
 
Reported: 2007-09-24 20:42 UTC by doko
Modified: 2017-05-20 11:13 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description doko 2007-09-24 20:42:24 UTC
this was raised at
http://l10n.openoffice.org/servlets/ReadMsg?list=dev&msgNo=7656

talking with Rafaella at OOoCon I learned that the inclusion of untranslated
messages is needed by the code, and the information, if a message is translated,
is only available in an internal database. This makes it currently impossible to
offer users translation of messages like it's done for ubuntu:
https://translations.edge.launchpad.net/ubuntu/gutsy/+source/openoffice.org

so either don't export untranslated strings ore mark them correctly
Comment 1 ooo 2007-10-12 19:30:46 UTC
I'm not involved with this, not i18npool, transferring to Ivo.
Comment 2 pavel 2007-11-02 11:43:17 UTC
.
Comment 3 gregor.hartmann 2008-01-22 11:42:41 UTC
from reading the message I now understand the issue.

Let me first state that it is unnexessary and thus an error to have untranslated
strings in the localize.sdf file. It just enlarges it unnecessarily.

As of localize. Does it extract the untranslated strings from localize.sdf or
does it generate them also for strings not contained in localize.sdf?
The latter should be foxed by Ivo.

As of Rafaella. Her concerns are handled at another place, so untranslated
strings are not needed in localize.sdf!

Comment 4 gregor.hartmann 2008-01-22 11:44:16 UTC
what I am talking about are onlky completely untranslated strings, not old
translations which might be outdated.
Comment 5 epost 2008-04-17 10:12:17 UTC
Hi Ivo, I set the target milestone to 3.x as IMO we should soon fix this issue.
I would ask you to check for which version of OOo 3 the issue can best be
resolved. Thanks
Comment 6 Marcus 2017-05-20 11:13:09 UTC
Reset assigne to the default "issues@openoffice.apache.org".