Bugzilla – Full Text Bug Listing
| Summary: | TVT3.2:TCT725: DA: English or incorret Danish entries in Msg Locale details list | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | CDE Administration <cdeadmin> | ||||
| Component: | TPTP.monitoring | Assignee: | Eugene Chan <ewchan> | ||||
| Status: | CLOSED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P1 | CC: | camle, kitlo, umarkova | ||||
| Version: | unspecified | Keywords: | plan | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux-GTK | ||||||
| URL: | 725 | ||||||
| Whiteboard: | closed460 | ||||||
| Attachments: |
|
||||||
|
Description
CDE Administration
Created attachment 43146 [details]
27.001340.jpg
[Added by CDE: Rejected by the CDE Bridge] [Added by CDE: Completed by the CDE Bridge] <cde:tctdetail> Testcase: 27.001350 TPTP Project: WSW32 Component: CDE - TPTP/Monitor UI Priority: 3 Subject: DA: English or incorret Danish entries in Msg Locale details list Article ID: 725 Originator: mette@djoerup.dk </cde:tctdetail> Reopening... I load the list of locales and their translations directly from the Java API Locale.getAvailableLocales(), so I use whatever locale description the JDK is providing, locale.getDisplayName(). If the JDK translation are not sufficient then we need to externalize all the locale description strings in our own resource bundle. Please confirm that other countries have the same problem! There is also a slight performance problem with the API Locale.getAvailableLocales(), another good reason to move the locales to a resource bundle. I think that getting the locale names from the JDK is the correct way to handle this, rather than moving the names to an eclipse resource bundle. If we (and everybody else) were to do our own translations, we would duplicate effort and invariably introduce differences. If everybody uses the JDK, we can ensure that our users see consistent translations. So I would recommend that the translation issues noted in this problem report be opened as a defect against the JDK. It looks to me as if the translations used for getDisplayName() are specific to the IBM JDK (at least for Danish). If I run against the Sun JDK (1.5), I get translations only for the Danish locale name, while if I run the same test against the IBM JDK (1.5), I get the full, translated list. So it would seem that additional translations for certain languages are one of the enhancements in the IBM version. I assume this should make it slightly easier to get changes made (Sun bugs sometimes seem to move at a glacial pace). The CLDR reflects these differences: http://www.unicode.org/cldr/data/diff/main/da_DK.html (the comparison chart shows that Sun has all English names, while the entries for the IBM JDK reflect what is listed in this problem report). Moving to 4.4. Target to future. Cannot be contained in 4.4 due to limitation of resource. Move target back to 4.4. Monitor defects are mistakenly targeted in bulk move. Targetting to address this in iteration 2. The recommendation is to open a bug against the Sun JDK to provide the required translations and not to make any modifications to TPTP code. Deferring to iteration 3. This is a JDK bug on a particular JDK version (Sun JDK 1.5). It is not a bug in the TPTP code. Please track this problem with the JDK product. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |