| Re: utf-8 and portuguese |
| by ghia on 2009/4/24 14:28:35 The encoding is a big problem for legacy sites in European languages (eg French, German, ...), which uses a lot of accented characters (128 - 255 in ascii). At the time being users with such sites are adviced to leave their site and database in the original encoding. Conversion is not straight forward, because the many ISO variants used. And on top of that, the database tables are often also cluttered by windows character sets. For the language files, there is a need to have two encodings for the same language. The conversion (from ansi to utf without bom) can easily be done with eg Notepad++. This is needed for all language definitions and templates. There is no need to rename the language directories itself as Trabis suggests, but the archives should contain two extra directories in the root: iso and utf, which will then contain the normal directory tree with all the language files. A partial example for the mrbs module and french could be: le="color: #000000"><?php |_modules | |_mrbs | |_index.php | |_xoops_version.php | |_lang.fr | |_admin | |_language | |_french | |_main.php | |_iso | |_modules | |_mrbs | |_lang.fr | |_language | |_french | |_main.php |_utf |_modules |_mrbs |_lang.fr |_language |_french |_main.php The module itself contains by preference default the utf language files. When the other encoding is needed, a simple copy or upload can easily be used to overwrite all relevant files.
|
| Re: utf-8 and portuguese |
| by trabis on 2009/4/24 13:05:34 Oh, big issue is the encoding. I know we are supposed to move to uft8, but I(and I believe all users from latin derivated languages) am feeling reluctant to change. Changing or not changing, we should have the encoding appended to the folder name. utf8_portuguese_pt, portugues_pt-utf8, whatever. |
| Re: utf-8 and portuguese |
| by trabis on 2009/4/24 12:59:16 First I like to say "Hello!" to Mikhail. He was my first xoopser contact in msn messenger and I'm sorry that we have talk only 2 or 3 times, because you have discussed some many interesting things, among some, the issue that this thread is covering. In portugues pt 'register'=>registar In portuguese br 'register'=>registrar or cadastrar In PT we use "cadastrar"(cadastrados) to define people who have been convicted for some crime. Some of this differences can become very annoying. A solution is to adopt neutral translations(mikhail ideia) having brazilian and portuguese working togheter in some kind of translation standards that would fit both interests. I can't complain about pt_utf8 translations however, has said above, there is no real community for PT support so, the job made by brazilian team is more than welcome. When I have some issue it is easy for me to make change. There are not so many changes to be done, really. Also, as I believe Mamba said, this is something for the communities to decide. They can make their own locale translations and submit them to SVN. We just have to decide the name to give for this folders. My opinion is to have portuguese(neutral) portuguese_pt and portuguese_br. In case some translation does not exist, the user can allways rename the folder(as I allways did!) |
| Re: utf-8 and portuguese |
| by ghia on 2009/4/24 6:04:29 I think we can stick with the full name (in english) for language files, eg (english, french, dutch). For the variants, we can add the two letter iso code as eg englishUK. If a variant is needed it can be created as such on SourceForge. Which foldernames should be used for this variant? - The same as the original (eg english): In that case the files can easy be overwritten. - As the variant (eg englishUK): this allows to operate the site in multilanguage mode. For you to think about it and to choose. I think second option may be preffered. Quote: My 20 Euros. 
|
| Re: utf-8 and portuguese |
| by Catzwolf on 2009/4/24 0:03:02 As some one who is actually Scottish (Considered British to many of you), I do not consider US English and UK English the same thing. That is why we have two different dictionaries and no, they are not the same to me. So if I can say that US and UK English are not the same and I do get annoyed that I am forced into using the US spellings on websites and with Xoops. I can say, I understand why others feel the same with their languages. I am not sure about others, but the case of US and UK English, this could be easily sorted with changing the structure and the way XOOPS deals with languages. For example, we could use en-US and en-GB. That way, we Brits don't have to put up with the silly US spelling of color etc. So how could this be fixed in your own language and the way XOOPS deals with your language? Is there a browser compliant way of dealing with it? Nice to see you here again Mikhail :) Catz |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|