Issue 69289 - Enable checking for missing string resources
Summary: Enable checking for missing string resources
Status: CONFIRMED
Alias: None
Product: Internationalization
Classification: Code
Component: code (show other issues)
Version: OOo 2.0.3
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-05 15:55 UTC by epost
Modified: 2017-05-20 11:13 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description epost 2006-09-05 15:55:43 UTC
It often happened that we had a Release Candidate ready and then found out that
some strings were still missing that should have been translated for the RC.

As the extractor and merge tools "know" which strings to extract and merge, they
could also be modified to check whether a translatable string has really been
translated for a given language. What should be possible is to create a tool
which checks if all strings which are due for translation are actually
translated for a given language / set of languages. This could also be
implemented as a build option which enables a build with strict checking for
translation.

Such a feature would enable us to better check whether the translation of a
version is complete before doing manual checks.
Comment 1 epost 2006-09-06 08:13:53 UTC
added gh to CC
Comment 2 gregor.hartmann 2006-09-07 06:36:25 UTC
the problem with a build option would be that eather the build breaks -> Prio 1
which cannot be fixed if there is really no translation
or nobody notices anything (warning or whatever is ignored by buildserver)

another way to chack could be to extract the strings (source + all desired
targets) and have an extra tool check whats missing. Such a tool should be
fairly easy to implement.

As jörg mentioned in discussion a list of exclusions would also be needed (e.g.:
we do not translate the testtool (basich/source/app))
Comment 3 epost 2006-09-11 12:59:31 UTC
What _could_ also be done is to additionally check for incorrectly encoded
strings inside the localize.sdf files. This could as well be done on the side of
gsicheck or a switch could be used to call gsicheck.
Comment 4 Martin Hollmichel 2008-01-28 02:38:17 UTC
set target 3.x
Comment 5 Marcus 2017-05-20 11:13:45 UTC
Reset assigne to the default "issues@openoffice.apache.org".