|
Bugzilla – Full Text Bug Listing |
| Summary: | Use of "Mio." in english translations | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Roger Whittaker <roger> |
| Component: | Translations | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED WONTFIX | QA Contact: | Karl Eichwalder <ke> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | ke |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Roger Whittaker
2005-08-18 12:58:23 UTC
The string "Mio." does not appear in any yast POT file? Is it hardcoded or is it part of another project (sax2?). Marcus, can you please help with this issue? It's hardcoded since years :-) nobody complained. The string is "16.7 Mio. [ 24 Bit ]" I would prefere an "international" version which doesn't need to be translated I think an "international" version for big numbers does not exist. Maybe, you can play with LC_NUMERIC or mark it for translation. Another posibility would be, to avoid these numbers complete and use something descriptive like "truecolor" or "realistic color display". IIRC, that's the way how it is called on MacOS. On MacOS they have:
Colors: ( ) 256 Colors
( ) Thousands
(x) Millions
Either use this literally or "16 Million".
Thanks for information, for 10.0 this is too late because of the text freeze mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy) Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;( |