Eike,
Pavel,
> No, not to the list, please create a new issue, assign it to me ('er')
> and attach the locale data file to the issue. Please don't forget to
> state your real name in the issue so I can look it up in the list of
> copyright approvals after your JCA arrived. Be sure the locale data
> fulfills the requirements lined out in
> i18npool/source/localedata/data/locale.dtd HEAD revision, is validated,
> verified to work, best in SRC680_m121 or later, and passes the tests
> mentioned.
OK, I'll do this asap,
> Because somewhen we have to freeze UI strings and addition of new
> locales for a release. We now seem to have arrived at this somewhen.
> Also bear in mind that adding a completely new locale involves work to
> be done by several people, developers, release engineers, QA. It is also
> quite normal that new localizations are added after the first major
> release, OOo2.0.1 will not be very far away in the future.
I can understand that... in fact as I said it earlier we can wait for October
or November,
but what is too bad to our eyes is really to miss the press annoucement that
will be
obviously more important for 2.0 than for 2.0.1...
Another point for us is to know if there is a way to test our translation in
the meantime,
inside the OO2.0beta framework, I mean for example by squatting another
language entry or
may be by using a "user defined language" entry ? This would definitely help us
to validate,
our translation, and correct it if necessary,
Thanks,
Philippe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
