Shaun McDonald wrote:
How about generating these files that testtool uses, from the
original localisation file that people like Clytie actually do the
translation in? This would be instead of doing it from the Windows
version of ooo.
one way to do this would be to only have an identifier of the string in
the testtool and then fetch the corresponding string at runtime from en
excerpt of the translations.
The problems would be
a) how to generate a unique identifier for each string which *never*
changes (well at least almost never)
b) keep the scripts readable
solutions might be
a) there are so called KeyID Builds provided by SUN, but of course only
for some languages. In these builds each string is preceded by its ID
From the database, which is unique and does not change. The problem is
that these IDs are not available to the Community. There are KeyID
Builds by the community, namely Pavel also, but their numbers change
from build to build and thus are not suitable in this case. This issue
however might help if reopened.
http://qa.openoffice.org/issues/show_bug.cgi?id=36162
If the IDs are not available to the Community sun could still provide
the IDs and would also have to provide the files with the translations.
The problem wold be that the translation has first to go through the
whole process before it will be available to test scripts, but OTOH the
Office is not available before that either.
b) to keep it readable the IDs could be provided along with their
wording in the scripts.
Gregor
On 13/01/2007, at 1:46 AM, André Schnabel wrote:
[..]
When we talk about localizing the testtool scripts, it would be a
huge help if we didn't have to take on yet another scattered group
of strings. Already, we have the templates, samples, formats and
autotext strings which don't exist in the interface file. Anything
not included in the interface file is going to fall off the priority
list for projects with few resources (like mine), or simply be
unknown. When I submitted our complete translation for
OpenOffice.org 2.1, I didn't know about the templates, samples,
formats and autotext needing translation: AFAIK there is no
information specifying this in our l10n docs.
See above.
If it's viable, I would suggest recommending any further strings be
integrated in the interface file. Yes, it makes it larger yet again,
but at least we have direct access to the strings, they get updated
with the main file, and they can't easily be missed.
AFAIK no other strings are really needed, they are already there.
They are just taken from the app, rather than the original file.
[..]
ShaunSend instant messages to your online friends
http://uk.messenger.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
