# DateString and localization, $Language ignored I have a DateString calculated in English. Now I would like to change the output according to localization. I have read that localization is possible for Menu, Messages and Cells. A simple $Language = "French" before calling DateString is ignored.

Since this should be a basic feature for localization, I am wondering if my keywords for Google and SX are just plain wrong? Or is this feature not present?

-
It uses your operating system's language settings, not \$Language. Try to change the regional settings of your OS. This did change the date formatting for me on WIndows –  Szabolcs Mar 19 '13 at 16:06
I actually had a similar problem, which I could work around once known but never got a solution. Here is my question in mathgroup. There were no answers for that question there, as far as I can see and remember... –  Albert Retey Mar 19 '13 at 17:24
Actually, my OS regional settings are not English. I only installed Mathematica with English interface to be sure to have the same "wording" when discussing with colleagues. Strange. Every high-level language nowadays has this feature (incl. Java). Thus it is just not implemented in pure MM. Ok, there's still the possibility to make a Java call... –  Frank Mar 19 '13 at 18:38
What OS do you have? –  Szabolcs Mar 19 '13 at 19:08
Win7 64bit with MM9 –  Frank Mar 19 '13 at 19:59

Ok, There seems to be some agreement, that the function is not natively implemented in MM. Thus, I will try to answer my question with a workaround. My answer is based on a java question over at SX

In[1]:= Needs["JLink"]
InstallJava[];
In[2]:= date = JavaNew["java.util.Date"];

In[3]:= df = DateFormatgetDateInstance[DateFormatLONG, LocaleGERMANY];
df@format[date]

Out[3]= "19. März 2013"

In[4]:= df = DateFormatgetDateInstance[DateFormatLONG, LocaleFRANCE];
df@format[date]
Out[4]= "19 mars 2013"

In[5]:= df = DateFormatgetDateInstance[DateFormatLONG, LocaleITALY];
df@format[date]
Out[5]= "19 marzo 2013"


Maybe someone can come up with a better solution. Since then, I stay with my opinion that this feature is basic and should be implemented in MM before any (ugly) tachometer or so onis added to the UI - At least I don't want a Labview like MM...

-