I lost track of this and it came up again this morning.   I'm not having a
lot of luck researching what should be done.

I see in
http://cldr.unicode.org/cldr-features#TOC-Locale-specific-patterns-for-formatting-and-parsingthere's
a heading "Translation of Names" where there's a list item "timezones,
timezone cities" but no link.

But, perhaps a more on point and useful question is:

I need to always show times with a timezone, and in a way that is localized
for the user.    What is the best way to do that currently with DateTime?


Should "EST" be translated?   What about "UTC"? (e.g. if using UTC +
offset)   I suspect UTC + offset isn't a very friendly timezone for many
people.


Locale "ar-sa" shows the following.  Is America/New_York and EST not
translated on purpose?

using format: full    : الأحد، 26 يناير، 2014 America/New_York 10:37:42 ص
using format: long    : 26 يناير، 2014 EST 10:37:42 ص
using format: medium  : 26‏/01‏/2014 10:37:42 ص
using format: short   : 26‏/1‏/2014 10:37 ص




On Thu, Jan 16, 2014 at 2:29 PM, Bill Moseley <mose...@hank.org> wrote:

> I would like to simplify our localization of dates and, if possible, just
> use this format for timestamps:
>
> $dt->strftime( '%x %X' );
>
>
> First question, is there any difference between the above and this?
>
>            join ' ' , $dt->format_cldr( $locale->date_format_default,
> $locale->time_format_default )
>
> Second, do timezones get localized?   For example, here's the default
> formats for "ko":
>
> using format: full    : 2014년 1월 16일 목요일 오후 05시 10분 28초 America/New_York
> using format: long    : 2014년 1월 16일 오후 05시 10분 28초 EST
> using format: medium  : 2014. 1. 16. 오후 5:10:28
> using format: short   : 14. 1. 16. 오후 5:10
>
> Won't be using the "full" format, but showing a timezone is needed.   Can
> (or does?) EST get localized?
>
> Thanks,
>
>
>
>
>
>
>
> --
> Bill Moseley
> mose...@hank.org
>



-- 
Bill Moseley
mose...@hank.org

Reply via email to