>If the visible display of the value of the Last-Modified header (which may or may not reflect the actual last modification time) is regarded as useful, it should of course be in the same language as the rest of the page.
I completely disagree. There may be many applications and web pages that are not translated into my preferred language, but I still want to be able to use my regional preferences. Especially common for US English apps and sites - I am entirely happy to use the English language UI, but I am very unhappy if I cannot see sensible dates with a dd/mm/yyyy order, a calendar where Monday is the first day of the week, and numbers where the decimal separator is a comma, just to mention the most common issues. Elsebeth >________________________________ > Fra: Jukka K. Korpela <jkorp...@cs.tut.fi> >Til: unicode@unicode.org >Sendt: 9:27 tirsdag den 3. april 2012 >Emne: Re: Klingon on Unicode site? > >2012-04-03 19:03, Shawn Steele wrote: > >> I was amused to see Klingon on the >> http://www.unicode.org/versions/Unicode6.1.0/ page ;-) >> >> Yes, I realize it’s primarily me and maybe a few other geeks, but I >> still smiled. > >On the other hand, it sets a bad example: an illogical mix of language, with >all the rest in English, including the label “Last updated:”. It would not be >that serious if it were not so common: unlocalized content (or content >localized server-side) and content localized client-side. > >If the visible display of the value of the Last-Modified header (which may or >may not reflect the actual last modification time) is regarded as useful, it >should of course be in the same language as the rest of the page. And if it >contains a time of the day part, it should indicate the time zone. > >Yucca > > > > >
