Portuguese/Brazil translation. May be it needs some ajust in date format...

jack.slocum

7 Apr 2007, 9:19 PM

schmidetzki:

You don't have to include {1}, you can put whatever you want in there.

tyama

7 Apr 2007, 9:49 PM

Japanese (utf-8) translation. :)

genius551v

7 Apr 2007, 9:58 PM

Spanish translation :D

schmidetzki

8 Apr 2007, 12:00 AM

schmidetzki:

You don't have to include {1}, you can put whatever you want in there.

That's wright. My Fault. It was simply too late last night.

Arikon

8 Apr 2007, 1:06 PM

Here is updated Russian translation in UTF-8.

hata1234

8 Apr 2007, 8:17 PM

Hi Jack..
It's Traditional Chinese (utf-8) translation.

justheatingup

8 Apr 2007, 8:21 PM

someone should sticky this thread.

DavidHu

8 Apr 2007, 9:02 PM

Hi Jack,
It's Simplifid Chinese Tanslations(utf-8).

I test it in Ext beat 1 examples.
I seems ok except the date chooser and date format.
1.the DatePickker can't show correct month when I click to change the month.
2.Althtough I changed the date format to y年m月d日, the date string still like m/d/y.

Shou I get the source form SVN?

JohnF

8 Apr 2007, 9:28 PM

Hi Jack!

It's danish (da) in utf-8.

eric_void

10 Apr 2007, 3:25 AM

Italian translation

koto

10 Apr 2007, 5:58 AM

Polish translation

Ylodi

10 Apr 2007, 12:32 PM

Croatian translation (hr), utf-8.

62

I have the same problem like DavidHu (month names).
Beta 1 examples.

jack.slocum

11 Apr 2007, 1:19 AM

I just wanted to say thanks to everyone who has posted a translation so far! We will be getting these into the next build. :)

Skeleton

11 Apr 2007, 1:52 AM

Here comes Turkish (in UTF-8):

65

vbert

11 Apr 2007, 11:49 AM

Polish translation (utf-8) - alternative version ;)

Version corrected

bpmtri

12 Apr 2007, 8:06 AM

Here is my Vietnamese translation.

trbs

12 Apr 2007, 3:03 PM

Polish translation (utf-8) - alternative version ;)

vbert could u please upload your translation again with normal line breaks in the file ?
if i open the file it looks minimized with all line endings and blank lines removed.

thanks guys for providing all these translations :)

vbert

12 Apr 2007, 3:40 PM

vbert could u please upload your translation again with normal line breaks in the file ?
if i open the file it looks minimized with all line endings and blank lines removed.

Yes sir ! ;)

Already corrected!

trbs

12 Apr 2007, 4:40 PM

Yes sir ! ;)

Already corrected!

Thanks vbert !

KimH

12 Apr 2007, 11:39 PM

Hi Jack!

It's danish (da) in utf-8.

I've updated JohnF's source on line 64 to include startDay : 1 ;)

trbs

13 Apr 2007, 2:17 PM

I seems ok except the date chooser and date format.
1.the DatePickker can't show correct month when I click to change the month.

Thanks DavidHu
I fixed the translation of month display in the datepicker in svn.

amon

14 Apr 2007, 6:47 AM

Here is the Hungarian, UTF-8 translation.

freakishmisko

14 Apr 2007, 8:07 AM

My 5 cents ;-)

Slovak translation (Slovak Republic) for the minority of slovak users (i hope there i'm not the only one ;)

Jack - everithing has been said so many times here - but again from me - one big THANK YOU for all this!

Misko

mdelanno

15 Apr 2007, 12:48 AM

Here is a french version.
Find an error on line :

Ext.grid.Grid.prototype.ddText = "%0 selected row(s)";

should be

Ext.grid.Grid.prototype.ddText = "{0} selected row(s)";

I've added Ext.LoadMask.msg (new functionality) and monthNames and dayNames in Ext.DatePicker. You have to override it because you redefine Date.monthNames and Date.dayNames after there've been affected in Jack's code.

Thanks Jack, Animal and all other people who makes & cares with Ext!
Great work men and if any folowing language versions or if you have something to do for me feel free to contact me B)

In translation there are 4 files (2 language identifiers + their min versions), i extract lang info from HTTP_ACCEPT_LANGUAGE, so it's similar to browser. Will be nice feature if u can include automatic detection by browsers ACCEPT_LANGUAGE info in any of folowing version.

Tested and works :)

trbs

2 May 2007, 3:44 PM

Thanks a lot for all the translations. Ext 1.0.1 contains more then 20 different languages ! :D

Please submit further translations as UTF-8 from now on; as the default character encoding for ExtJS translation files is set to UTF-8.

Condor

3 May 2007, 2:49 AM

There are some errors in the dutch translation (I checked ext-lang-nl.js version 1.0.1a):

There are some errors in the dutch translation (I checked ext-lang-nl.js version 1.0.1a) [...] Could somebody fix these ?

Condor:

I suggest you correct the latest version of the file, and post the corrected file here. (That's what I did when I found some problems with the Spanish file.)

Also, remember to use UTF-8, as requested in a previous message.

Regards

trbs

3 May 2007, 3:18 PM

There are some errors in the dutch translation (I checked ext-lang-nl.js version 1.0.1a):
Could somebody fix these ?

I did :)

thanks for the report ! helps bring the best translations possible to ExtJS \:D/
Changes are in svn and will make there way into the next ExtJS release. In the mean time here's the updated dutch translation file.

thesilentman

6 May 2007, 11:03 AM

Greek translation \:D/

solle

7 May 2007, 2:21 AM

Finally I got around doing what I've promised - translating the strings into Swedish. The file is encoded in utf-8.

Hi mrgekko,

Thank you for this! I found a few minor errors that probably should be considered included in the next release. Below is a list of changes I made, and new js is attached.

* Changed 'V

Ylodi

8 May 2007, 5:07 AM

Croatian translation (UTF-8).

Fixed:
- day names
- valid date format
- one missed translation

More user friendly translation (error messages).

pwfraley

10 May 2007, 1:23 AM

there is a bug in the german translation,

the translation for loading messages should be:

Micha

10 May 2007, 1:49 AM

its better to use the Ext Translation thread (http://extjs.com/forum/showthread.php?t=4323) for that.

neongrau

10 May 2007, 2:14 AM

and beside that, the text shows up correctly.

check if the encoding matches with the one your app is using, the file was recently converted to UTF-8 in SVN (not sure if you already have that version) but even in the initial commited file the string was correct.

iMax

11 May 2007, 3:05 AM

I noticed there are some errors in the german translation included in the official ext-1.0.1a download. Maybe they are already corrected in the SVN version? If not here is a corrected version. (The js file is UTF-8 encoded)

Find attached a greek translation. I have used extjs\source\locale\ext-lang-en.js to do it.

Best regards

Vagelis

trbs

3 Jun 2007, 10:17 AM

Hi,

Find attached a greek translation. I have used extjs\source\locale\ext-lang-en.js to do it.

Best regards

Vagelis

Thanks vagelis, i'll import it into svn.
One question though; any special reason for using Latin-1/ISO-8869-1 as character encoding for the Greek translations ?
It seems to work fine when i convert it to UTF-8 encoding.

thesilentman

3 Jun 2007, 10:29 AM

Thanks vagelis, i'll import it into svn.
One question though; any special reason for using Latin-1/ISO-8869-1 as character encoding for the Greek translations ?
It seems to work fine when i convert it to UTF-8 encoding.

Hi Trbs,
I had submitted a fine greek translation and it's already in SVN. If there are errors we should take a look and merge...
Vagelis, do you see errors in the existing translation?

trbs

3 Jun 2007, 10:53 AM

Hi Trbs,
I had submitted a fine greek translation and it's already in SVN. If there are errors we should take a look and merge...
Vagelis, do you see errors in the existing translation?

yeah your right... same as with the alternative polish translations then.
weird that i didn't see this from the country codes.

Silentman that's the meaning of 'el' in 'el_GR' ? otherwise i'll rename it too only 'gr'.
Hopefully saves the confusion next time :)

thesilentman

3 Jun 2007, 11:15 AM

Hi Trbs,
Thanks for the response,
Better leave el_GR as is. it stands for greek (Greece)...

The greek language is also spoken in Cyprus, where the locale would be el_CY

Just like en_US, en_UK, en_AU,...,...,...

So I guess the confusion stays? :D

Greetings,
Frank

trbs

3 Jun 2007, 11:31 AM

only in my mind :D

if i see Jack, i'll ask what he thinks... cause i think it would be nice to have at least some standard.. may that be en_US, nl_NL, etc or plain en, nl...

in the mean time, there is a file in examples/locale called languages.js which contains an array of all translation files with there locale name and character encoding. (it's used in the multi-lang.html example) Could come in handy if u don't remember all the country codes or get confused like me :)

In general (OS, Web servers, Server software, etc...), go with the long version. It makes some sense.
Just a quick example for en_US and en_UK, doesn't apply to ext, but some words in other languages could apply to ext.... ;)

en_US = Theater
en_UK = Theatre

Greetings,
Frank

vagelis

4 Jun 2007, 9:36 PM

Thanks vagelis, i'll import it into svn.
One question though; any special reason for using Latin-1/ISO-8869-1 as character encoding for the Greek translations ?
It seems to work fine when i convert it to UTF-8 encoding.

Hi trbs,

For Greek language valid encoding is ISO-8869-7 or windows-1253 but you can use also UTF-8 I didn't found encoding in the file so I forgot to mention it.

thanks for the report, i fixed the startDay for german translations in svn.

netnoise

21 Jun 2007, 10:26 AM

Please add the following changes to the German langfile:

Ext.apply(Ext.form.DateField.prototype, {
format : "d.m.Y"
});

(Current version breaks date validation.)

Thanks!
Timon

trbs

21 Jun 2007, 1:24 PM

Please add the following changes to the German langfile:

Ext.apply(Ext.form.DateField.prototype, {
format : "d.m.Y"
});

(Current version breaks date validation.)

Thanks!
Timon
done, thanks for the report.

rb

22 Jun 2007, 5:03 AM

I don't know if someone already mentioned it...
It would be nice to have month short names in locale files too : it's not always the first 3 letters of the full name. e.g. in french: Juillet->Jul, Juin->Jun (Jui is ambiguous and not used).

wolverine4277

11 Jul 2007, 2:12 PM

Can be missing this piece of code in the file locale/ext-lang-sp.js???
I don't check in the rest of files of locale...

Adding this in spanish language the message in grids for loading, changes from Loading... to Cargando...

ext-1.1-rc1

trbs

14 Jul 2007, 2:20 PM

:D:D:D

Thanks for the info trbs.

Just my two cents.

In general (OS, Web servers, Server software, etc...), go with the long version. It makes some sense.
Just a quick example for en_US and en_UK, doesn't apply to ext, but some words in other languages could apply to ext.... ;)

en_US = Theater
en_UK = Theatre

Greetings,
Frank

Ok, i've been thinking about this for the upcoming 1.1 release.
Instead of renaming all the files to there complete locale name (aka: en_EN / nl_NL) I've only renamed files which are not in the same location as there language originated from.

So to give an example, it's:

ext-lang-en.js, ext-lang-nl.js and ext-lang-fr.js

For English (US), Dutch and France.

But for Canadian France it's: ext-lang-fr_CA.js
So if anybody would like to contribute an UK English translation file it should be called: ext-lang-en_UK.js :)

So only if there is a difference in the same language depending on location the filename gets an extra code.
This looks to me as the nicest solution for the file structure and from what I've seen many other projects use the same kind of structure.

KimH

18 Jul 2007, 12:56 AM

I second that!

thys

22 Jul 2007, 2:10 PM

:-)

craneleeon

25 Jul 2007, 12:41 AM

I checked the last 'ext-1.1-rc1' some translates of 'ext-lang-zh_CN.js' are definitely wrong. So I corrected them, BTW I think use 'Y-m-d' prefer than 'Y-M-d' in chinese, cause some chinese words such like 'Month' 'Day' will cause parsing issue on the serverside for some lang.

trbs

26 Jul 2007, 12:03 PM

cool guys :)

I'll add Afrikaans and update the Chinese translation.

trbs

28 Jul 2007, 2:33 PM

I checked the last 'ext-1.1-rc1' some translates of 'ext-lang-zh_CN.js' are definitely wrong. So I corrected them, BTW I think use 'Y-m-d' prefer than 'Y-M-d' in chinese, cause some chinese words such like 'Month' 'Day' will cause parsing issue on the serverside for some lang.

While adding Afrikaans (cool language btw \:D/ ) i noticed that the updated Chinese translation is not in UTF-8 format.

Craneleeon: Could you submit the updated translation file with UTF-8 encoding ? Thanks.

Filetype is read on my system as: Non-ISO extended-ASCII text, with CRLF, NEL line terminators

cariad

29 Jul 2007, 7:15 AM

I've made some further changes to the swedish translation originally by mrgekko (with changes by solle).
I hope everyone will agree with these changes. :)

St

NBRed5

30 Jul 2007, 1:56 AM

Please find attached a UK English translation, which only has adjustments to the date format to d.m.Y etc as this is standard UK date formate of day month year.

trbs

30 Jul 2007, 11:47 AM

i added ext-lang-en_UK.js to svn.

I've made some further changes to the swedish translation originally by mrgekko (with changes by solle).
I hope everyone will agree with these changes.
Cariad, i love to update the swedisch translation. only one question :)
i see that the names of weekdays and months are all spelled without a capitol as the first letter.

Is that correct that way ? or should they start with capitols.

with kind regards,
trbs

cariad

31 Jul 2007, 3:53 PM

trbs:
Yes, months and weekdays are always written in lowercase in Swedish, unless they are at the beginning of a sentence. However, when not in a sentence it's also written without capitols.

Most of the updates and changes I've made are done with Microsoft's translations in mind, which i guess is what most people recognize and expect.

trbs

1 Aug 2007, 11:28 AM

trbs:
Yes, months and weekdays are always written in lowercase in Swedish, unless they are at the beginning of a sentence. However, when not in a sentence it's also written without capitols.

Most of the updates and changes I've made are done with Microsoft's translations in mind, which i guess is what most people recognize and expect.

ok clear, it's committed in svn :)
thanks for the update and explanation.

I updated the English and Dutch translations with the HtmlEditor and DatePicker translations. For everybody wanting to use a localized HtmlEditor and/or the 3 new DatePicker localization text please look at the sniplet below.

Thanks! I'm actually interested in russian translation ^^. The UTF-8 version, that was posted here never worked for me. Shows some really wierd sumbols, nevertheless the page's encoding is set to UTF-8. Any suggestions?

trbs

29 Aug 2007, 2:30 PM

Thanks! I'm actually interested in russian translation ^^. The UTF-8 version, that was posted here never worked for me. Shows some really wierd sumbols, nevertheless the page's encoding is set to UTF-8. Any suggestions?

Does http://extjs.com/deploy/ext/examples/locale/multi-lang.html with the Russian translation work for you ?

Although i don't read Russian the characters look fine to me, that is what i would expect from a Russian site. In that example i explicitly use:

If the characters in the multi-lang.html example look good to you try the charset line in your (java)script tags. Hope this helps.

ZooKeeper

30 Aug 2007, 1:14 AM

Thanks for a piece of advice. The format of the ext-lang-ru.js, located in the source folder and the one in the build (ext-lang-ru-min.js) are totally different.

Using ext-lang-ru.js is fine, but minified version has Unicode characters like

trbs

30 Aug 2007, 8:19 AM

FYI:

I only maintain the locale's package/part of Extjs. I wish i could speak and write all those languages so i could update them all :)

The ext-lang-en.js should (normally) always be the most up-to-date translation file. You can use meld or another differences program to see if there new entries in the English file which does not exist in your locale and update it accordingly. (and please please post them here so i can update them in svn)

So the translations and locales are mostly a community effort, people using the Ext locales should check once in a while for updates to the English file and update accordingly. Regrettably this most often happens after a new release. Hopefully in the future we can develop a system where we have more or less fixed locale maintainers and notify them a couple of days/weeks in advance of a new release, so they can update there language files.

CSS Minifications
I think this is part of the new YUI-Compressor, and i could very well be a bug with that. I'll look further into this.

ZooKeeper

30 Aug 2007, 11:56 AM

Here you go. Updated non-minified version of Russian translation.
UTF-8. UNIX endlines. Hope it's fine.
I'll keep it up to date, since looks like there's almost no Russians here :(

trbs

30 Aug 2007, 12:37 PM

Great, thanks for your support ZooKeeper !!

It's committed into svn :)

UNIX Endlines: I prefer Unix style EOL, any other way is IMHO just wrong :)
I'll keep it up to date: Great thanks, keep your eye on this thread for any big news.

trbs

31 Aug 2007, 4:40 PM

FYI:

I looked into the minified translations problem that ZooKeeper reported.
This is a bug in the build script that is used to compress extjs with yui-compressor.

Yui-Compressor does not automatically (and correctly) detect character encoding on files. This means that our utf-8 encoded translations are mangled into ASCII minified files. Like ZooKeeper reported this results in all non-ascii characters being converted to dummy characters. Specially bad for translations like Russian which contains almost nothing else then full utf-8 characters.

I reported this bug in the JSBuilder forums.

ZooKeeper

2 Sep 2007, 8:26 AM

Thanks for looking into this problem. I'm pretty sure they'll fix it or probably there's a reason to take a look at some other minifier out there.
Hope this'll be fixed till the time next version is gona see the light of day.

Sorry fangzhouxing i cannot read this. Also i think that the characters got mangled by the forum post.
Please attach a patch created with diff -uh oldfile.js newfile.js to this thread as a zip file. (so it would be ext-lang-zh_CN.js.path.zip) (or otherwise the full file)

nicetip

4 Sep 2007, 6:09 PM

here is korean translation file.
I hope I could find this file in next version. :)

There's a missed translation in the italian one.
Add this line inside the Ext.DatePicker translation:

if(Ext.DatePicker){
Ext.apply(Ext.DatePicker.prototype, {

...

cancelText : 'Annulla'

});
}

Bye

trbs

10 Sep 2007, 3:21 PM

Hi everybody, first post for me here!

There's a missed translation in the italian one.
Add this line inside the Ext.DatePicker translation:

if(Ext.DatePicker){
Ext.apply(Ext.DatePicker.prototype, {

...

cancelText : 'Annulla'

});
}

added to svn, thanks keeper :)

deltaiworks

11 Sep 2007, 4:29 AM

I found mistakes in a file ext-lang-ru-min.js. Mistakes in source/locale/ext-lang-ru.js are not present, i.e. probably mistakes have arisen at a stage of assembly of the module.

Also it is necessary to add in class Ext. DatePicker additional arrays for the reduced names of months and days of week. As reductions in Russian are not the first letters from the name.

becomcs

13 Sep 2007, 7:39 AM

Here is the french canadian translation. :)

It's also a french french translation :) excepte for é cars. Is it due to UTF format?

haattila

14 Sep 2007, 2:35 AM

Serbian-Latin translation.

trbs

14 Sep 2007, 8:08 AM

It's also a french french translation :) excepte for é cars. Is it due to UTF format?

Please check the examples/locale/multi-lang.html ( http://extjs.com/deploy/ext/examples/locale/multi-lang.html?lang=fr_CA&charset=UTF-8 ) and select the France (Canadian) language. Does it still show strange characters there ?

trbs

14 Sep 2007, 8:14 AM

Serbian-Latin translation.

added to svn, Ext now boosts 32 different translation files \:D/

r2k

18 Sep 2007, 5:44 AM

Change Log:

* Added All Messages for HTMLEditor
* Fixed the rendering for some non-standart characters like

Hi , is there an spanish lang file (locale) for version 2.0 alpha1 ??
if not can you provide me with an english base to start working on the translation for 2.0
Thanks..!

:D

mystix

9 Oct 2007, 8:37 PM

all locale files are stored in the source/locale directory (check there to see if there's already a spanish locale file).

for the base locale file in english, grab the latest 2.0 SVN and look for the source/locale/ext-lang-en.js file.

cmendez21

9 Oct 2007, 9:41 PM

its cause i didnt notice the latest SVN version and theres no place where you can see an updated log about this (well at least for me i didn't find any in the site) (:|

thanks and sorry for the trouble..!

mystix

9 Oct 2007, 10:29 PM

its cause i didnt notice the latest SVN version and theres no place where you can see an updated log about this (well at least for me i didn't find any in the site) (:|

thanks and sorry for the trouble..!

no worries. what's the code for spanish anyway?

ext-lang-??.js

cmendez21

9 Oct 2007, 10:36 PM

its ext-lang-sp.js
:D

trbs

10 Oct 2007, 11:01 AM

Dear Translators and Ext Community,

I would like to ask everybody who wrote a language file to take a look at there file and the differences it has with ext-lang-en.js and update it accordingly.

Most recent and notably additions are Date.monthNumbers and Ext.form.HtmlEditor section.

I will make sure the updated language files make there way into Ext2.0, so hopefully we can have an extensive and up-to-date translation set for Ext 2.0 Final.

If you have any questions or like to update a translation originally written by somebody else feel free to post to this thread. Please refer to the original post #0 of this thread on instruction how to translate and submit the file.

Regards,
Trbs

(P.S. Mystix if you have some additional pointers for translators please feel free to reply or add to this post)

ZooKeeper

11 Oct 2007, 3:44 AM

I'm a little confused about current alpha locale files.
It appears that they are pretty much the same files, that we can see in the 1.1 release.
I can tell about russian file, it's sligtly changed 1.1 version with no HTMLEditor support. The one I uploaded here well before 2.0alpha made it to the public had it. My guess will be it was commited to the 1.1 branch, but not in the 2.0.
So, speaking of 2.0 changes to the lngs, can you please upload an english example, because, as i said before, the 2.0 ext-lang-en.js is identical to the 1.1 version.
Thanks

@Amon / @gkk1969 sorry this came late, here's the latest ext-lang-en.js file for 1.1.1 (SVN rev 1187) correct at the time of this post.
this will be used as the base for the 2.0 english locale file, so pls help improve it by reporting new additions to 2.0 which are missing from this file. thanks!

I'm a little confused about current alpha locale files.
It appears that they are pretty much the same files, that we can see in the 1.1 release.
I can tell about russian file, it's sligtly changed 1.1 version with no HTMLEditor support. The one I uploaded here well before 2.0alpha made it to the public had it. My guess will be it was commited to the 1.1 branch, but not in the 2.0.
So, speaking of 2.0 changes to the lngs, can you please upload an english example, because, as i said before, the 2.0 ext-lang-en.js is identical to the 1.1 version.
Thanks

Sorry i should have explained this more clearly in the POST. Thanks to Mystix for replying.

At the time of writing the Ext 1.x SVN (and thus Ext 1.1.1) have the most up-to-date translation files. All other files then ext-lang-en.js got synced once every few months from the Ext 1.x SVN to the EXT 2 SVN.

Where now moving toward improving Ext translation files so they all will be complete for the next Ext 2.0 release.

Please use the Ext 1.1.1 for a reference if that release already got a translation file for your language and not Ext 2 Alpha1 or Ext 2 Beta1, then check it against the file Mystix posted (or Ext2.0/src/locale/ext-lang-en.js if you got SVN access) to find which translations are missing from your language file.

Within the next couple of days as new translation files get posted (Thanks to all you guys/girls!!!) the locale files in Ext 2 SVN will be updated to the latest versions.

P.S. The translations/locales have not changed between Ext1 and Ext2 so the files will just-work in both versions.

Persian (Farsi) language for ver.2 Beta 1
It's based on English translation and all strings are translated. :)

brian.moeskau

22 Oct 2007, 4:07 AM

DateField.altFormats was recently added to the default English locale in 1.1 and 2.0. Please reply if you can provide the appropriate string for other locales:

if(Ext.form.DateField){
Ext.apply(Ext.form.DateField.prototype, {
disabledDaysText : "Disabled",
disabledDatesText : "Disabled",
minText : "The date in this field must be after {0}",
maxText : "The date in this field must be before {0}",
invalidText : "{0} is not a valid date - it must be in the format {1}",
format : "m/d/y",
altFormats : "m/d/Y|m-d-y|m-d-Y|m/d|m-d|md|mdy|mdY|d|Y-m-d"
});
}

It has also been added to the Italian translation (ext-lang-it) per user request like so, which I imagine may be what others will want as well:

altFormats : "d/m/Y|d-m-y|d-m-Y|d/m|d-m|dm|dmy|dmY|d|Y-m-d"

trbs

23 Oct 2007, 11:09 AM

Persian (Farsi) language for ver.2 Beta 1
Added to Ext 1 and 2 svn :)

DateField.altFormats was recently added to the default English locale in 1.1 and 2.0. Please reply if you can provide the appropriate string for other locales:

......

It has also been added to the Italian translation (ext-lang-it) per user request like so, which I imagine may be what others will want as well:

altFormats : "d/m/Y|d-m-y|d-m-Y|d/m|d-m|dm|dmy|dmY|d|Y-m-d"

Thanks Brian !

I'd imagine that most other languages than English-US will use Day-Month-Year notation and not Month-Day-Year.
Added the altFormats with the d-m-Y specifications to the following locales:

Here is the updated translation for the latest Ext2.0, the file is UTF-8 encoded.

ktl

24 Oct 2007, 12:56 PM

This is a summary of the following post http://extjs.com/forum/showthread.php?t=15476

I had a problem with the French locale file in the 2.0b1 release; all accented characters were looking weird.

Mystix had a look and provided files which were encoded differently and this solved the problem.

This implies that the used encoding has a major impact on portability. I have tried to replace special characters with html entity numbers and it still works fine (at least for me). Maybe this is a solution to make the locale files independent of encoding problems. The French file with html entities is attached so that others can test and give feedback.

trbs

25 Oct 2007, 4:38 AM

This is a summary of the following post http://extjs.com/forum/showthread.php?t=15476

I had a problem with the French locale file in the 2.0b1 release; all accented characters were looking weird.

Mystix had a look and provided files which were encoded differently and this solved the problem.

This implies that the used encoding has a major impact on portability. I have tried to replace special characters with html entity numbers and it still works fine (at least for me). Maybe this is a solution to make the locale files independent of encoding problems. The French file with html entities is attached so that others can test and give feedback.

Did you look at examples/locale/multi-lang.js ? (And there are some form posts about it too)

When i explicitly set the encoding type in the script tag i can get every locale to work fine. Normal European systems will most likely have there default encoding in latin-1 while the locale files are in UTF-8, so you'll have to set the character encoding. Either in the response headers or in enctype parameter of the script tag.

There are some other locale's which have opted for using html entities in there locale file. This has some added advantages; like it will work in <title></title> tags where non-ascii characters will not.

If you have a case where you did provide the character encoding to the locale file and it still did not render the characters correctly then i would like to see a live example of that.

Hope this helps.

trbs

25 Oct 2007, 4:49 AM

Btw, i would like to add the french locale with html entities if;
- Please provide the locale file with UNIX line endings. (there now using DOS endings)
- Add missing translations (see svn version of ext-lang-en.js)

Thanks!

mystix

25 Oct 2007, 5:04 AM

- Please provide the locale file with UNIX line endings. (there now using DOS endings)

:-? i just checked the SVN copy of all locale files for both 1.1.1 and 2.0 -- all of them are using UNIX line endings.

p.s. i posted some windows tools for converting line endings in case anyone needs them:
71337

wm003

26 Oct 2007, 2:32 AM

The localization of the context-menu entries "Group by this Field" and "Shown in Groups" isn't supported by any localization-File so they stay spelled in english.

btw: excellent widget!!B)

nedkopenev

26 Oct 2007, 4:32 AM

Bulgarian version

mystix

26 Oct 2007, 9:37 AM

The localization of the context-menu entries "Group by this Field" and "Shown in Groups" isn't supported by any localization-File so they stay spelled in english.

btw: excellent widget!!B)
thanks for reporting this.

the following L10n code has been added to the 2.0 ext-lang-en.js file in SVN:

Is it specific for 2.0? Will it be ok to place this locale file into 1.1.1 proj?
Will post russian version here shortly.

mystix

27 Oct 2007, 6:01 AM

Is it specific for 2.0? Will it be ok to place this locale file into 1.1.1 proj?
Will post russian version here shortly.

sorry bout that. added the version numbers above for clarity. GroupingView is unique to 2.0, while the methods added for the Date class are identical for both 1.1.1/2.0.

HTH

trbs

29 Oct 2007, 11:15 AM

For everybody without svn access, here is the most recent version of ext-lang-en.js ( Ext2 svn of 29 October 2007 20:00 CET )

Note for users/developers using both Ext1 and Ext2: The only diversion at this moment from Ext1 in Ext2 is Ext.layout.BorderLayout.SplitRegion which used to be called Ext.SplitLayoutRegion. Because of the if() {} statements around the locale definitions you should be able to safely use translations files between versions. However when name/refactoring changes are made you might lose some translations. Also it's not a problem to have both the definitions in the same file, so the same file will work on both Ext2 and Ext1, as long as the surrounding if () {} statements are there.

wm003

31 Oct 2007, 5:19 AM

find attached the current german locale file based on mystix / trbs svn posting.

I added string-translation of splitbar aswell as grouping grid and the html editor

There are two versions: The original one just added with the new Strings and a new one where the "umlauts" were replaced by html-entities.

Why two versions? Well, as for the splitbar tooltip, this one isn't done with html but the title attribute which does not support htmlentities (i already started a thread asking for support of quicktips in the splitbar here) (http://extjs.com/forum/showthread.php?t=15889)

ktl

4 Nov 2007, 6:06 AM

Find attached a new version of the fench locale files.

ext-lang-fr_htmlentities.js: ASCII text
ext-lang-fr.js: ISO-8859 text

ZooKeeper

6 Nov 2007, 4:07 AM

Russian UTF-8

Thylia

9 Nov 2007, 6:31 AM

French UTF-8

madrabaz

9 Nov 2007, 1:57 PM

Turkish UTF-8
- Added new translations
- Fixed typos

trbs

13 Nov 2007, 10:49 AM

13-November-2007: updated svn of ext2 with the lastest files attached to translation thread

<Thinking Out Loud>
Maybe we should start a part on the wiki/learn section of the Ext site for Translations.
So that translation maintainers (somebody who maintains a particular language translation) can be listed
there with there work in progress locale file for credits and glory. Also the community could discus details on language specific translations there. As for example i see a lot of (subtle?) differences in different translators for the France locale. Then we could also use the forums again for discussions about translations like; RTL and htmlentities etc.

Please append to this thread if you have ideas, comments or other thoughts on how to structure the translated part of Ext better.
</Thinking Out Loud>

mmar

16 Nov 2007, 1:30 AM

Polish UTF-8 translation:
- based on Ext 2.0 rc1
- based on vbert version + some improvments for Ext 2.0

Vladas

18 Nov 2007, 9:13 AM

Here are Lithuanian translations.

A zip archive consists of two files:
ext-lang-lt_LT - is for ISO-8859-13 aka WIN-1257 aka Latin-7,
ext-lang-lt_UTF8 - for UTF-8.

Vladas

hb562100

21 Nov 2007, 5:27 PM

good work thank you!

she

28 Nov 2007, 1:40 PM

Bulgarian translation...
I hope I did not make something wrong:">

edit: I just saw that there is already bulgarian translation.. I don't want to say that it's bad, i just saw it too late (like always).

People, I'm so confused...
I changed hundread times my translation and I still see a mistakes.
(It seems I did not speak bulgarian for long enough).

trbs,
i hope you used the other translation - its much better than mine...

trbs

8 Dec 2007, 5:06 PM

trbs,
i hope you used the other translation - its much better than mine...

Yes, i used the other one, actually i only fixed one error that jslint reported in the file, it's also why i asked for comments on the translation.

But while double checking i found a small error and fixed it, thanks :)

she

8 Dec 2007, 11:59 PM

:)
Actually the main difference between the two versions (except my mistakes, of course :">) is that my translation is in official form and the other one not, but I guess its better if its not official..
And one more thing : in the other translation for the disabledDaysText and disabledDatesText is written word by word "inaccessible"; in my translation is written "inactive"... I think enabled means more active, than accessible.

Ah, yeah, and I think that I found more correct words to translate sortAscText and sortDescText :">

But you can also let the other translation like it is - its very good. I, as a bulgarian, find it very well and I know that its not easy to translate PC terms on our language, cause very often we just use the english ones. :)
Oops, I shall not speak so much.

Greets~o)
Viva la ExtJS :D

hh2007

11 Dec 2007, 12:22 AM

hello,
Thanks extjs.com to give me the Ext2.0 final to use.
but I have a question about this file "ext-lang-zh_CN.js".
In the source:
ext-2.0/source/locale/ext-lang-zh_CN.js
In this function
Before：

I have updated Catalonian translation file. You can see the last version at http://extjs.com/forum/showthread.php?p=95911#post95911

krukow

11 Dec 2007, 11:44 AM

Hello,

I have a some corrections to the translations in ext-lang-da.js. Obviously it is hard for the core team to judge whether this is really a "bug" or not, but these are my suggestions.

[code]Ext.form.Field.prototype.invalidText = "V

trbs

11 Dec 2007, 12:28 PM

Hi all

I have updated Catalonian translation file. You can see the last version at http://extjs.com/forum/showthread.php?p=95911#post95911

updated in svn, thanks a lot ! :)

trbs

11 Dec 2007, 12:33 PM

hello,
Thanks extjs.com to give me the Ext2.0 final to use.
but I have a question about this file "ext-lang-zh_CN.js".
In the source:
ext-2.0/source/locale/ext-lang-zh_CN.js
In this function

hh2007

I'm regrettably not a Chinese speaker but i hope some other speakers can help you with this... when there's a new consensus please upload an updated translation file here and i will make sure it gets into the next release.

I was seeing a "Please Wait..." on my message boxes, so I started to look into the code ;)

What should we do with those pieces of code?

krukow

13 Dec 2007, 11:02 PM

http://extjs.com/forum/showthread.php?p=97799#post97799

ext-lang-da.zip attached.

trbs

14 Dec 2007, 5:00 AM

http://extjs.com/forum/showthread.php?p=97799#post97799

ext-lang-da.zip attached.

Thanks a lot ! committed to svn

DServe

14 Dec 2007, 8:03 AM

French UTF-8 translation :

Correction de minText et maxText dans les DateField et TimeField.

New revision :

Line 14
[HTML]Ext.grid.Grid.prototype.ddText = "{0} ligne(s) s

trbs

14 Dec 2007, 12:12 PM

New revision :

Committed to SVN, thanks !

DServe

18 Dec 2007, 1:06 AM

Thanks to Thylia here's a corrected version.
Changes :

Line 154
[HTML]minText : "La date de ce champ ne peut

fgrilli

21 Dec 2007, 6:23 AM

Completed translation of missing parts. Used UTF-8 encoding for special characters. Set Monday as first day of week.

killernay

22 Dec 2007, 12:26 PM

Thailand Translate support

trbs

24 Dec 2007, 4:50 AM

Committed fr, it and th languages. Thanks guys !!

killernay your file was not in UTF-8 and not valid Javascript (missing quotes).

Translators in general, please check and validate your files before uploading and read the first post of this thread carefully ! :)

Thanks in advance !
And thanks for all the hard work on maintaining Ext locale files, we now have 41 language files in Ext2.0 SVN ! ;)

Marry-XMass and a Great New Year !!

AntonioCS

25 Dec 2007, 7:33 AM

Portuguese translation (took the translation from webersouza and made some adjustments)

trbs

29 Dec 2007, 7:16 AM

Portuguese translation (took the translation from webersouza and made some adjustments)

i converted ext-lang-pt.js from ISO-8859 to UTF-8 and uploaded to svn :)

Condor

4 Jan 2008, 2:54 AM

There are no translations for Ext.form.TimeField in the 2.0 build.

Have they already been added to SVN (I can't check) or is this on the to-do list?

haattila

18 Jan 2008, 6:12 AM

Hi!

In this version of Serbina Latin translation I corrected some mistakes.

tore.kjorsvik

21 Jan 2008, 2:58 PM

Attached is a zip file with two translations, Norwegian bokm

alperyazgan

24 Jan 2008, 1:33 AM

New Turkish Translation

Alper YAZGAN

alperyazgan

24 Jan 2008, 2:04 AM

Sorry a double quote was missing :-)

New Turkish Translation

Alper YAZGAN

wolverine4277

24 Jan 2008, 4:09 AM

Corrections to Spanish/Latin American Translation

The changes that i made are:

Line 175:

createLinkText : "Por favor proporcione el URL para el enlace:",

to

createLinkText : "Por favor proporcione la URL para el enlace:",

Line 188:

title: 'Italica (Ctrl+I)',

to
[code]
title: 'It

wm003

24 Jan 2008, 11:30 PM

There are no translations for Ext.form.TimeField in the 2.0 build.

Have they already been added to SVN (I can't check) or is this on the to-do list?

Find attached the updated german locale including the mentioned TimeField translations and a missing translation for the justifyright parameter of the editor as well as correction of DateField translations according to the english original.

For the Timefield translation i added the following base-code at the end of the locale. (still in english here, translated in the attached file)

Use this for your own translations as source (and translate the strings of course..:)

if(Ext.form.TimeField){
Ext.apply(Ext.form.TimeField.prototype, {
minText : "The time in this field must be equal to or after {0}",
maxText : "The time in this field must be equal to or before {0}",
invalidText : "{0} is not a valid time",
format : "g:i A"
});
}

[Edit]
I also changed the "startDay" option to 1 in the german locale to have the Datepicker start with Monday.

tof

25 Jan 2008, 6:38 AM

Hi,

There is a translation problem with the "short" month names, at least for the french version :

- months "june" and "july" are translated "juin" and "juillet", which is truncated as "jui" for both; the uses are to shorten them as "jun" and "jui" to prevent confusion.
- depends on encoding, but for "f

mystix

25 Jan 2008, 8:17 AM

[QUOTE=tof;114838]
There is a translation problem with the "short" month names, at least for the french version :

- months "june" and "july" are translated "juin" and "juillet", which is truncated as "jui" for both; the uses are to shorten them as "jun" and "jui" to prevent confusion.
- depends on encoding, but for "f

tof

25 Jan 2008, 9:05 AM

yay! someone finally made use of that function! (and yes, that's exactly why i put it in...

Thanks :D

well you could simply override stuff for now

Of course I can... but this is way beyond translation ;)

Should I file a bug for this ?

mystix

25 Jan 2008, 9:16 AM

Of course I can... but this is way beyond translation ;)

true...

Should I file a bug for this ?

i think you should. just quote the previous posts. there might be some other unnoticed spots where i10n may be difficult / impossible without overriding.

This occurs in Ext 2.0.x: when trying to parse a date with format "l, d \de F \de Y" it will fail and return some date in year 1969.

I've found it occurs cos the parser fails to correctly find the month related javascript number.

I've attached a patch to this.

72

8 Feb 2008, 9:09 AM

Czech localization for 2.0 (suitable for 1.0.1 too)
Česk

amon

9 Feb 2008, 3:06 AM

Hungarian localization for 2.0 (based on the latest ext-lang-en.js in the 2.0.1)
Encoding: UTF-8

quartex

11 Feb 2008, 12:38 AM

Hi,
In Ext.FormPanel in submit action when using

waitMsg: 'Attendere ...'

the windows title "Please wait" is in english.
I included
<script type="text/javascript" src="/dnshst/libjs/ext20/build/locale/ext-lang-it.js"></script>
but this "internal" message is the unique not translated.

trbs

11 Feb 2008, 11:19 AM

Hi,
In Ext.FormPanel in submit action when using

waitMsg: 'Attendere ...'

the windows title "Please wait" is in english.
I included
<script type="text/javascript" src="/dnshst/libjs/ext20/build/locale/ext-lang-it.js"></script>
but this "internal" message is the unique not translated.

That message declared in BasicForm.js as waitTitle.
It can be put in the translation as: Ext.form.BasicForm.waitTitle = "Please Wait..."
or as: Ext.form.Action.Submit.waitTitle = "Please Wait..."

And yes, these ones should be added to the ext-lang-en.js translation file as a reference to people... but I'm currently too busy to try and find most of these and put them in the english reference file.

If somebody else is willing to take a go at this (shouldn't take more then a couple of hours) and check the if everything works fine I'll be happpy to commit it to svn. (and thus promoting it to the next release)

t34

26 Feb 2008, 10:49 AM

Hello,

i build my own ext.js and use the translations.

My project did not need the section "Layout" but i must include this section, because of that code in the translations.

if(Ext.layout.BorderLayout.SplitRegion){

I save 20k by change that to:

if(Ext.layout.BorderLayout && Ext.layout.BorderLayout.SplitRegion){

Please put this into the official release.

Greetings from germany, thomas

keypoint

26 Feb 2008, 11:37 AM

Hey, I find myself replacing the Romanian locale with the attached one all the time. I don't know if it's better but it seems more natural. It uses "." as the date separator and also adds some alternate date formats, useful for entering just the day of the month, for example - trivial stuff, but useful.
Other Romanian users - your input would be appreciated. Maybe it will make it into the next build.

techbug

27 Feb 2008, 12:28 AM

Korean translation
Suitable for ext 2.0.2

wm003

5 Mar 2008, 2:02 AM

i was wondering, why the text when dragging rows from a grid always displays

"1 row selected", no matter which locale file i included.

The solution lies in the locale-files:

The Object to change this text was accidently called "Ext.grid.Grid" instead of "Ext.grid.GridPanel"

I needed use Currency Format, so I added brMoney to the translation file!

yanick

18 Mar 2008, 3:23 AM

Hi,
some strings in ext-lang-sk.js has incorrect codepage (not UTF8) and date format has a incorrect format. Corrected file is in attachment.

kayegil.hauan

25 Mar 2008, 3:40 PM

The norwegian translations of the altFormats property of Ext.form.DateField.prototype
seems to lack the 'Y-m-d' format.
Even though this format is never used in norwegian it should be included in order to make forms able to read dates from e.g. a MySQL database.

gwinyam

18 Apr 2008, 6:25 AM

Hi!

Thanks for all your translations! But I have a problem with that. When you have download the package which interests you and put it in the good folder.

I don't want to make a new translation pack, I just want to use it. And I don't understand how to do it...

Thanks for all!
Gwinyam

Condor

18 Apr 2008, 7:48 AM

- Months and days are not written with captials in dutch.
- The short name for March is mrt and not maa.
- Changed date format from d-m-y to j-m-y.
- Removed unneeded capitals.
- Corrected some errors.
- Added translation for Ext.form.TimeField.

wm003

18 Apr 2008, 7:59 AM

Guys, you should take care of my post above (http://extjs.com/forum/showthread.php?p=133543#post133543).

There is accidently "grid" instead of "gridpanel" specified in all language-files by default.
you should change this too.:)

mystix

21 Apr 2008, 10:14 AM

Guys, you should take care of my post above (http://extjs.com/forum/showthread.php?p=133543#post133543).

There is accidently "grid" instead of "gridpanel" specified in all language-files by default.
you should change this too.:)

just fixed in SVN.

mystix

21 Apr 2008, 10:14 AM

Hello,

i build my own ext.js and use the translations.

My project did not need the section "Layout" but i must include this section, because of that code in the translations.

if(Ext.layout.BorderLayout.SplitRegion){

I save 20k by change that to:

if(Ext.layout.BorderLayout && Ext.layout.BorderLayout.SplitRegion){

Please put this into the official release.

Greetings from germany, thomas
fixed in SVN. thanks.

mystix

21 Apr 2008, 10:20 AM

Hi,
some strings in ext-lang-sk.js has incorrect codepage (not UTF8) and date format has a incorrect format. Corrected file is in attachment.

added to SVN. thanks.

mystix

21 Apr 2008, 10:21 AM

- Months and days are not written with captials in dutch.
- The short name for March is mrt and not maa.
- Changed date format from d-m-y to j-m-y.
- Removed unneeded capitals.
- Corrected some errors.
- Added translation for Ext.form.TimeField.

added to SVN. thanks.

mystix

21 Apr 2008, 10:27 AM

Korean translation
Suitable for ext 2.0.2

added to SVN. thanks.

mystix

21 Apr 2008, 10:28 AM

I needed use Currency Format, so I added brMoney to the translation file!

added to SVN. thanks.

mystix

21 Apr 2008, 10:31 AM

The norwegian translations of the altFormats property of Ext.form.DateField.prototype
seems to lack the 'Y-m-d' format.
Even though this format is never used in norwegian it should be included in order to make forms able to read dates from e.g. a MySQL database.

added to SVN. thanks.

jtarini

22 Apr 2008, 8:43 AM

Locale ext-lang-pt_br.js da vers

Jineb

24 Apr 2008, 3:46 AM

[quote=tof;114838]Hi,

There is a translation problem with the "short" month names, at least for the french version :

- months "june" and "july" are translated "juin" and "juillet", which is truncated as "jui" for both; the uses are to shorten them as "jun" and "jui" to prevent confusion.
- depends on encoding, but for "f

mystix

24 Apr 2008, 5:36 AM

Hello,

I use this code, my fields are corrects ("23 Jun 2008" for example), but not the calendar :

http://images3.hiboox.com/vignettes/1708/bbg95cjw.png

Maybe the calendar use his own getShortMonthName function, so in which file is the calendar created?

your image looks correct... what's wrong?

wm003

24 Apr 2008, 5:43 AM

your image looks correct... what's wrong?

The screenshots both shows "Jui" for June and July, but he defined it with "Jun" and "Jui"...

mystix

24 Apr 2008, 5:45 AM

The screenshots both shows "Jui" for June and July, but he defined it with "Jun" and "Jui"...

ooh... sharp :)
and i'm B)

did you experience / notice this in your DatePickerPlus plugin?

wm003

24 Apr 2008, 6:00 AM

ooh... sharp :)
and i'm B)

did you experience / notice this in your DatePickerPlus plugin?

yep, it's the same, because i'm using the same monthpicker from the original datepicker. monthpicker really seems to have his own getShortMonthName function somewhere