Converted between ISO-Latin-1, UTF8, and Java (ASCII with \uXXXX unicode escapes) encoding using GNU Recode version 3.6 on Linux with these commands:
recode l1..JAVA < calendar-es-latin1.js > calendar-es.js recode l1..JAVA < calendar-fr-latin1.js > calendar-fr.js recode u8..JAVA < calendar-ko-utf8.js > calendar-ko.js recode u8..JAVA < calendar-it-BEFORE.js > calendar-it.js recode u8..JAVA < calendar-pl-BEFORE.js > calendar-pl.js
I suggest you use the code with the \uXXXX encoding everywhere. Unlike UTF8 or ISO-Latin-1 they can be edited with any ASCII text editor and should be the safest for any server setting. You'll notice the Korean version is about 25% bigger but it doesn't affect latin based languages much. I tested on IE 6.0 and FireFox 1.0 and 1.5 but not other browsers.
Also I substituted \u2039 for "String.fromCharCode(0x2039)" in the "ABOUT" string and that works and is easier to read.
Disclaimer: I don't speak French, Spanish, German, Italian, Polish or Korean. I got the files from the 1.0 release or the forums and did fix-ups and character-encoding using GNU recode.
Note: The UTF8 files may not display right in your browser (or editor) if it hasn't been properly told that the file is UTF8. That is why I am doing these conversions. You might just want to grab the zip file.
The highlighted files are the ones you want to use. The others are just provided so you can easily see what I changed from the 1.0 release.
calendar-en.js | English, ASCII with non-ASCII characters such as « » encoded as \uXXXX |
calendar-es-latin1.js | Spanish, ISO-Latin-1 encoding. This is closest to the file called "calendar-es.js" released in version 1.0. Added <BR> to Calendar._TT["TIME_PART"] because it was too long. |
calendar-es.js | Spanish, ASCII with non-ASCII characters encoded as \uXXXX. Converted from calendar-es-latin1.js, so the same comments apply. |
calendar-fr-latin1.js | French, ISO-Latin-1 encoding. This is a merge between "calendar-fr.js" released in version 1.0 and a French file I got from the forums; I did this because I thought the one from the forums was more accurate (but I don't speak French). I added <BR> to Calendar._TT["TIME_PART"] because it was too long. Also I added Calendar._FD because it was missing. |
calendar-fr.js | French, ASCII with non-ASCII characters encoded as \uXXXX. Converted from calendar-fr-latin1.js, so the same comments apply. |
calendar-de.js | German, ASCII with non-ASCII characters encoded as \uXXXX. No Character conversion was needed because it was already encoded that way in the 1.0 release. I added Calendar._FD because it was missing. I added explicit <BR>s to 5 of the Calendar._TT strings because they were too long and causing the calendar to expand sideways - so now it expands down instead, which is much better. I use the calendar with "weekNumbers : false" so it is a bit narrower than the demo calendars. |
calendar-it-BEFORE.js | Italian, UTF8. Called "calendar-it.js" in the 1.0 release. I added Calendar._FD setting and I also modified the ABOUT tooltip to use \u2039 instead of "String.fromCharCode(0x2039)" and similar changes for \u203a, etc. |
calendar-it.js | Italian, ASCII with non-ASCII characters encoded as \uXXXX. Converted from calendar-it-BEFORE.js, so the same comments apply. |
calendar-pl-BEFORE.js | Polish, UTF8. Called "calendar-pl.js" (not "calendar-pl-utf8.js") in the 1.0 release.
I added these settings because they were missing:
|
calendar-pl.js | Polish, ASCII with non-ASCII characters encoded as \uXXXX. Converted from calendar-pl-BEFORE.js, so the same comments apply. |
calendar-ko-utf8.js | Korean, UTF8. I added these settings because they were missing:
|
calendar-ko.js | Korean, ASCII with non-ASCII characters encoded as \uXXXX. Converted from calendar-ko-utf8.js, so the same comments apply. |
language.zip (21 kB) | Zip file with all of the above |
.calendar table td { font: normal 11px tahoma,verdana,sans-serif; }Get calendar-win2k-1.css