Issue 53550 - changes in Dzongkha locale
Summary: changes in Dzongkha locale
Status: CLOSED FIXED
Alias: None
Product: Internationalization
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: oc
QA Contact: issues@l10n
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-19 14:39 UTC by pema.geyleg
Modified: 2013-08-07 15:00 UTC (History)
2 users (show)

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

Attachments
patch to dz_BT locale (23.19 KB, patch)
2005-08-19 14:40 UTC, pema.geyleg 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description pema.geyleg 2005-08-19 14:39:40 UTC 
Eike,

   Please find attached a patch for the dz_BT.xml locale that is much closer to
Dzngkha language and Bhutanese culture.
   The locale has been validated before making the patch. The Language id is not
altered by this patch.
Comment 1 pema.geyleg 2005-08-19 14:40:39 UTC 
Created attachment 28929 [details]
patch to dz_BT locale
Comment 2 ooo 2005-08-22 14:38:12 UTC 
Are the changes otherwise identical to those of issue 53497? I'm asking because
I'll integrate that one, which would make this issue here superfluous and it
could be closed then.
Comment 3 ooo 2005-08-22 15:59:37 UTC 
Decided differently. For issue 53497 I applied only the simple change of LCID,
other changes will be done with this patch.
Comment 4 ooo 2005-08-22 17:51:39 UTC 
On branch cws_src680_localedata6:
i18npool/source/localedata/data/dz_BT.xml 1.2.4.1
unotools/source/i18n/localedatawrapper.cxx 1.30.26.1

Note that FormatCode of formatindex="13" contained a typo,
[NatNum1]CURRENCY] instead of [NatNum1][CURRENCY]. This was detected
during runtime in a non-product version, or in a product version if the
environment variable OOO_ENABLE_LOCALE_DATA_CHECKS was set to Yes, see
i18npool/source/localedata/data/locale.dtd for a description.

Note also that if a format code contains separate subformats, for
example for positive and negative formats, a [NatNum1] must be applied
to all subformats if all should be displayed using native numbering. Did
that for the currency format codes.

However, having a currency [NatNum#] format as default format currently
doesn't work, this will be addressed in a later CWS.

Furthermore, the combination of [NatNum1]-[$Nu-...] created some almost
duplicated format entries in the dialog's list, with different minus
sign position, this is what the fix in localedatawrapper.cxx is for.
Comment 5 ooo 2005-08-23 12:44:18 UTC 
Reassign to QA.

re-open issue and reassign to oc@openoffice.org
Comment 6 ooo 2005-08-23 12:44:23 UTC 
reassign to oc@openoffice.org
Comment 7 ooo 2005-08-23 12:44:27 UTC 
reset resolution to FIXED
Comment 8 oc 2005-08-24 15:11:24 UTC 
verified in internal build cws_localedata6
Comment 9 oc 2005-09-29 10:56:03 UTC 
closed because fix available in OOo1.9m131