Opened 15 years ago
Closed 14 years ago
#5223 closed bug (fixed)
Locale preflet "Country" tab doesn't do anything
Reported by: | damoklas | Owned by: | pulkomandy |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Kits/Locale Kit | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Translations in preferences not work or incorect.
- not traslating strings
– in CPU frequency: Open Speedstep preferences... Install Replicant into Deskbar – in Bluetooth: Connections & channels...
- different strings on not different things:
– Media setting: "Defaults" in Audio setting and "Default nodes" in Video setting
- in Locale:
– Numbers, Currency changen not work, not saves; saple nor work – in "Date" place missing string for translating: Month
Change History (9)
comment:2 by , 15 years ago
Component: | Preferences → Kits/Locale Kit |
---|---|
Owner: | changed from | to
comment:3 by , 15 years ago
Status: | new → in-progress |
---|
Bluetooth : fixed Cpufrequency : known bug, I have a fix in mind 2 : will look into it. 3 : a) known bug. The API is not written yet.
b) will look.
comment:4 by , 15 years ago
Summary: | Translations in preferences incorect work → Locale preflet "Country" tab doesn't do anything |
---|
in hrev34984 and hrev34985 I fixed the missing translations in cpufrequency and locale. As for Media, apparently the "node" is there on purpose, so I'm not changing that. As for Locale preflet country tab not working, I'll work on that later. Note that none of the translated app are trying to use this part of the Locale API yet, so it is quite useless anyway.
comment:5 by , 15 years ago
for hrev34985, still need to put the "Month" strings in locale catkeyses, and translate later it.
comment:6 by , 15 years ago
In my opinion, it would be better if at all should not be any compilation and locale to be simple text files. And could be added to the already collected system. And I think, would be good to have, translation program, as is done in Splocale (on BeOS). The current localekit is too complicated. What happens next? When the increase in translations.
comment:7 by , 15 years ago
damoklas, you are just not aware of all the features of Haiku's Locale Kit. Plain text files which are added later are not a problem and are already supported. It's just not how we handle the translation "shipped" with Haiku. These are being pre-compiled to maximize efficiency of starting up applications. Fast program loading times are not something we want to sacrifice because of internationalization.
The workflow of translating can be made more comfortable, and as far as I know, there are some efforts under way to make this happen. But the way it was done in ZETA was not efficient, I know that because I got a glimpse of that at the time.
comment:8 by , 15 years ago
Just realizing that SpLocale is something different from the ZETA translation process... just ignore that comment. :-)
comment:9 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | in-progress → closed |
The country tab now does things.