Alberto Escudero Pascual wrote:
Hi Stephan,
What it might seem "trivial" it can create a big overhead tracking those
-small changes-. Will it be possible for you to send out what strings
are affected? How many are we talking about? It will great to have a GSI
with those strings only.
See the below URL for a list of all the potentially affected strings.
In principle, each of those strings should have been without final
punctuation in every language (and thus would have to be changed). In
practice, however, quite a number of those strings already contained
final punctuation in de and/or en_US (the two languages I changed
myself), so this might be similar for other languages.
Sorry, I have no idea what a GSI file is. Maybe someone in the know
from the Hamburg I18N infrastructure can jump in here---Ivo, Frank?
-Stephan
Alberto
On Mon, 2006-04-03 at 18:59 +0700, Javier SOLA wrote:
This will produce a lot of untranslated strings when PO files are
updated to 162. This can be solved by using Translation Memory, but
still, all the messages will be labeled as fuzzy, as they are not an
exact match.
Javier
Stephan Bergmann wrote:
Hi all,
I would like to inform those of you who are involved in translating
OOo's strings into various languages of one specific change:
On CWS sb48, integrated into SRC680m162, I changed a lot of error
resource strings to consistently end in punctuation (full stops or
question marks, which used to be added programatically at runtime).
No other changes have been made to these string resources on sb48, so
reflecting the changes for any given language should be trivial
(although maybe a little bit tedious).
See <http://www.openoffice.org/servlets/ReadMsg?list=dev&msgNo=16341>
for a list of all the relevant strings.
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
