Opened 12 years ago
Closed 12 years ago
#9230 closed bug (fixed)
[AboutSystem] localize kernel_build_date
| Reported by: | anakincho | Owned by: | siarzhuk |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Applications/AboutSystem | Version: | R1/alpha4.1 |
| Keywords: | Cc: | przemub@… | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
In Russian language in "system/apps/AboutSystem" you can see at the left side of the menu that not everything is translated like in the right side. Screenshot name: bug2.png
Attachments (1)
Change History (9)
by , 12 years ago
comment:1 by , 12 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 12 years ago
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
Seems like a valid bug to me:
The code is here: http://haiku.it.su.se:8180/source/search?q=systemInfo.kernel_build_date
comment:3 by , 12 years ago
| Summary: | Not full translation in Russian language → [AboutSystem] localize kernel_build_date |
|---|
comment:4 by , 12 years ago
As far as I can see this comes from expanding compilers' DATE macro so it can be counted as always fixed in English. May be some routine to parse string Date in English and reconstructing localized representation could be added into Locale kit? May be it is already exists in ICU?
comment:5 by , 12 years ago
There's already the locale agnostic parsedate() which could be used for the parsing.
comment:6 by , 12 years ago
| Owner: | changed from to |
|---|---|
| Status: | reopened → assigned |
This issue was published as GCI 2012 task: http://www.google-melange.com/gci/task/view/google/gci2012/7973237
comment:7 by , 12 years ago
| Cc: | added |
|---|
comment:8 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
fixed in hrev44944 during completing GCI task. Thanks.
Thank you for your check. Most of localization related tickets you posted this evening have no sense here. Localization is never ending process - developers are changing sources, translators are trying to follow them step by step. So it is no wonder that some strings are not localized ATM. It is obvious and have no sense to have such endless tickets in the Trac.