Follow-up Comment #9, task #2614 (project savane):
Hm, I don't agree with you here.
> We we certainly not waste time to manage every possible locale
> on earth while date() already do that.
We would not have to support every locale on earth, but only the few locales
we already support (seven). All other locales are not supported by Savane
anyway.
On top of that, the date() localization is not sufficient for our purposes.
First of all, it does not solve the ambiguity mentioned in bug #4542
(06/11/05 vs. 11/06/05).
Second, it cannot be used when we want to specify additional information. For
example, the string '%a %x, %R' is not localized. For German, I need to use
'%a, %x, %R' instead. It's the same with '%A %x '._("at").' %R %Z', which
would need to be _('%A %x at %R %Z').
My thinking is that if we support l10n, we should do it with no exception.
The difference between using "%x" and e.g. "%d %B %Y" is only to provide the
translator with a more fine-grained control of how the date is going to be
displayed. While it might be fine to write "Monday 21 November 2005" in one
language, another language might require "21 November Monday 2005". This
would not be possible by using "%x".
Note that I'm not arguing in favour of using "%s" in a simple sprintf and
manually translating all weekday and month names. We already take advantage
of the localization done in the C library -- we only take over more control
of how things are done.
In conclusion, if we want to provide additional information such as weekdays
and times to "%x", we need to go for the fine-grained control approach.
_______________________________________________________
Reply to this item at:
<http://gna.org/task/?func=detailitem&item_id=2614>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev
