Closed Swiftyhu closed 12 years ago
can you please update it and replace all \u00E9
characters with normal UTF-8 chars? If you look at all other translations they are made in pure UTF-8 and all works file
I can do that... :D But I do not see why I should do that?
This is an 7 bit version (escaped) UTF-8 language file.... I understand that it is harder to edit, but it is always the same both under linux and under windows too...
Why do not you like it? P.s.: It is not yet finised... :D
Because UTF-8 is a must for correct work of elFinder, that is why you do not need to fallback for compatibility. All other translations are in UTF-8.
P.S.: and what the difference can be between windows and linux editing the same UTF-8 file?
Well, some Windows programs write BOM characters at the begin of the file... And for example those "windows" PHP files can introduce errors on linux... :D
And while not every program can read/write UTF-8 files, every can do it with ASCII... And the other question who will edit the language files again? Most of the users will never do that...
So is it a "design rule" or there is something more behind this "UTF-8 needed" scenario?
Anyway... I can convert the chars to UTF-8 if you definetly need it...
Just a line: I am currently under linux.... And my console is set up to ISO8859-2...
Translations is made by humans for humans, so there is really no need in some "codes", just keep it simple. Maybe someone would like to improve your translation and will not be able to do the same way as you.
Some other facts: I never heard of BOM problem in elRTE or elFinder Your translation will be the only one "ugly" Imagine https://github.com/Studio-42/elFinder/blob/2.x/js/i18n/elfinder.zh_CN.js this translation with encoded strings - it would be useless for normal human Many other products use normal utf-8 encoded translations without any problems
So there is really no need to encode it, believe me =)