Re: [l10n-dev] NEW Locale Data Audit - please participate!

2006-01-25 Thread Samphan Raruenrom

What should be used for CurrencyID?
http://l10n.openoffice.org/nonav/i18n_framework/cldr/LocaleDataAudit_OOo202.html#219
I see inconsistencies between locales.
- bank symbol
- currency symbol
- translated currency name
- currency name in English
I see all cases in the OOo locale. Should we have a standard?

Eike Rathke wrote:

I created a new locale data audit document, 320kb
http://l10n.openoffice.org/nonav/i18n_framework/cldr/LocaleDataAudit_OOo202.html

that does a comparison between locale data as of OOo m151 and CLDR 1.3.
For details and description please see the document.

Again, I would like to ask as many people as possible to take a look at
his/her locale whether s/he can spot and name a difference and tell
which one is right. Please use the [EMAIL PROTECTED] mailing list to discuss 
your
findings, or if you have any questions regarding the document.

--
_/|\_ Samphan Raruenrom. Open Source Development Co., Ltd.
Tel: +66 38 311816, Fax: +66 38 773128, http://www.osdev.co.th/



smime.p7s
Description: S/MIME Cryptographic Signature


Re: [l10n-dev] NEW Locale Data Audit - please participate!

2006-01-25 Thread Dwayne Bailey
Hi Eike,

Out of curiosity do you have a list of locales that are in Microsoft but
not in OOo?

On Wed, 2006-01-25 at 21:22 +0100, Eike Rathke wrote:
> Hi,
> 
> I created a new locale data audit document, 320kb
> http://l10n.openoffice.org/nonav/i18n_framework/cldr/LocaleDataAudit_OOo202.html
> 
> that does a comparison between locale data as of OOo m151 and CLDR 1.3.
> For details and description please see the document.
> 
> Again, I would like to ask as many people as possible to take a look at
> his/her locale whether s/he can spot and name a difference and tell
> which one is right. Please use the [EMAIL PROTECTED] mailing list to discuss 
> your
> findings, or if you have any questions regarding the document.
> 
> Thanks
>   Eike
> 
-- 
Dwayne Bailey
Translate.org.za

+27-12-460-1095 (w)
+27-83-443-7114 (cell)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [l10n-dev] NEW Locale Data Audit - please participate!

2006-01-25 Thread Dwayne Bailey
Hi Eike,

1413: This was reported under #645 to CLDR
1414: align to CLDR.  LC_CURRENCY is inherited from en_ZA.  en_ZA should
also be corrected to have CurrencyName=Rand.  So CurrencyName in both
CLDR and OOo for en_ZA is incorrect.

The other South African languages I assume are listed because there is
no CLDR data?

On Wed, 2006-01-25 at 21:22 +0100, Eike Rathke wrote:
> Hi,
> 
> I created a new locale data audit document, 320kb
> http://l10n.openoffice.org/nonav/i18n_framework/cldr/LocaleDataAudit_OOo202.html
> 
> that does a comparison between locale data as of OOo m151 and CLDR 1.3.
> For details and description please see the document.
> 
> Again, I would like to ask as many people as possible to take a look at
> his/her locale whether s/he can spot and name a difference and tell
> which one is right. Please use the [EMAIL PROTECTED] mailing list to discuss 
> your
> findings, or if you have any questions regarding the document.
> 
> Thanks
>   Eike
> 
-- 
Dwayne Bailey
Translate.org.za

+27-12-460-1095 (w)
+27-83-443-7114 (cell)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[l10n-dev] NEW Locale Data Audit - please participate!

2006-01-25 Thread Eike Rathke
Hi,

I created a new locale data audit document, 320kb
http://l10n.openoffice.org/nonav/i18n_framework/cldr/LocaleDataAudit_OOo202.html

that does a comparison between locale data as of OOo m151 and CLDR 1.3.
For details and description please see the document.

Again, I would like to ask as many people as possible to take a look at
his/her locale whether s/he can spot and name a difference and tell
which one is right. Please use the [EMAIL PROTECTED] mailing list to discuss 
your
findings, or if you have any questions regarding the document.

Thanks
  Eike

-- 
 OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer.
 GnuPG key 0x293C05FD:  997A 4C60 CE41 0149 0DB3  9E96 2F1A D073 293C 05FD

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[l10n-dev] Right-to-left localization

2006-01-25 Thread Farzaneh Sarafraz
Dear Arabic/Hebrew localizers,
I have a simple, straight-forward, yet very important question. How do
you change the direction of the items such as menus from LTR ro RTL?
I appreciate your help.
fa


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [l10n-dev] Problem merging po between versions

2006-01-25 Thread Farzaneh Sarafraz
Hi,
You haven't described your problem clearly. However, please notice that
in order to migrate from your old po files (older than m147) to the new
ones, you should follow the guideline in the message thread "m148" on
this list. I hope this helps you with your problem.
fa


On چهارشنبه, 2006-01-25 at 07:46 +0700, Samphan Raruenrom wrote:
> Hi,
> 
> The Thai OOo translator team has done OOo translation since
> 2.0, integrated in 2.0.1 (but not in time for 2.0.2).
> 
> We have a serious problem. We use po for translation to
> leverage already available tools.
> We convert SDF to po, then translate them, then convert them
> back. I guess this is the normal process for many locale. (?)
> 
> However, when finish 2.0, and try to merge po (from SDF)
> update from 2.0.1, we have a problem. When we finish 2.0.1
> po and try to merge from m150, we have the same problem.
> I'm not the one who did the process so I may not describe
> the problem correctly.
> 
> The problem is something like some entres in the SDF
> are moved to other source files (result in bad po merge),
> some entries have the same msg id in po.
> We're trying to hack the tool to make it workable.
> 
> I guess many of you should have found the same problem
> if you use po. How do you solve them?
> 
> Thanks.
> 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [l10n-dev] [Fwd: Re: TCM QA for l10n builds is planed from Feb 2nd]

2006-01-25 Thread Rafaella Braconi

Hi David,

what we intend to do during this TCM testing cycle is to perform 
collaboration testing on special builds localized in the 
StarOffice/StarSuite relevant languages. I am afraid en-GB is not one of 
those list.


For a en-GB build please wait for the milestone builds.

Thanks,
Rafaella

dwb wrote On 01/23/06 20:14,:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rafaella,

Thanks for forwarding this. Why is en-GB not included amongst the
languages? GSIs and all information was submitted in time as requested. I
trust this is a simple omission.

Thanks
David.

Rafaella Braconi wrote:
 


FYI: in case you have missed Naoyuki's announcement on the
dev@qa.openoffice.org list.

We plan to do l10n QA with TCM against latest l10n builds
from Feb 2nd for 2 weeks.
The builds will be from the CWS localization05 which is on the SRC680
codeline.
This means that builds will not be normal milstone builds
but they will have newly added translations (both UI and OLH) for 2.0.2
release.
So the purpose of this QA will be for finding l10n problems not
for giving Go/NoGo.
The languages which will be abailable :
'de', 'fr', 'it', 'es', 'sv', 'pt_BR', 'nl', 'hu', 'ru', pl,'zh_CN',
'zh_TW', 'ko', and 'ja'

The platforms :
Windows and Linux

Vladimir Glazounov will place the builds at:
http://oootranslation.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization05/

   


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFD1SsXgH46HTEjeiURAgiTAKCH5KTjyqafNd7cYK+79zMgUTvOEwCbBuZt
tr1+rALV+WvbFYX4noKrSu4=
=/UvE
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

 



--
Rafaella Braconi
Software Program Manager
EMEA G11n Center
Sun Microsystems GmbH
Sachsenfeld 4
D - 20097 Hamburg
Tel:   +49 40 23646 781
Email: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]