Replies: 3 comments 3 replies
-
Can we just have a simple mapping (I guess per locale) for these hardcoded strings?
Do we need to hardcode a solution for Germany? EG if the Intl API doesnt handle it, then is it fair to say that most people would not notice the specialism?
Sounds reasonable to me - we don't expose CLDR directly, we just use it so IMHO these are internal identifiers |
Beta Was this translation helpful? Give feedback.
-
I think I found a solution of it. |
Beta Was this translation helpful? Give feedback.
-
Sadly there are no |
Beta Was this translation helpful? Give feedback.
-
I try to implement
qx.locale
classes with Intl API and get rid ofnode-cldr
andcldr-data
. Now I've encountered the next issues:getPercentFormat
method ofqx.locale.Number
- just still not done. There are no tests for this method.getAmMarker
andgetPmMarker
always returns AM and PM but actually for other locales there are other values too. Intl implementation fixes the problem.qx.locale
methods which are started with cldr_ prefix. If I get rid of cldr should I rename this prefix on something else?getTimeFormat
ids are ["short", "medium", "long", "full"] or ["HHmm", "HHmm", "HHmmss", "HHmmsszz"]You can see here what I've done so far.
Any suggestions, advices and help will be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions