| Re: How do I change charset=UTF-8 |
| by anderssk on 2008/8/10 7:55:40 #18 Give notepad++ a try. It's also show witch encoding the file have, and you can change it with one click
|
| Re: How do I change charset=UTF-8 |
| by ghia on 2008/8/10 0:24:49 Quote: trabis wrote: If an UTF-8 file is incorrect marked as a text file you see weird characters mostly a kind of a and more than one character in the place of one accented character. In that case copy  or type alt 0239 alt 0187 alt 0191 to the beginning of the file. Save, close notepad and reopen then the file. Now the inserted characters are no longer displayed and used as BOM, which forces the file to read as UTF-8. If you see all alike weird characters such as blocks and your file is correctly interpreted as UTF-8, that means that your fonts characterset is insufficient. Do select all and set with format - font the font to lucida sans unicode, dejavu sans mono or download FreeFont and set it to FreeMono. You should now be able to view most of the characters. Then save as with encoding Ansi. |
| Re: How do I change charset=UTF-8 |
| by anderssk on 2008/8/9 7:48:26 The Notepad++ can also convert from UTF-8 to ANSI as well from ANSI to UTF-8 Open Your language-files and select Format -> convert to UTF-8 (without BOM) og Format -> conbert to ANSI Save the file again. |
| Re: How do I change charset=UTF-8 |
| by trabis on 2008/8/8 23:07:30 Quote:
Yes, but, if you have a utf-8 file and you edit in notepad, it will show weird characteres, it will not converte them. You can not use notepad to convert utf-8 to Iso. Well, I have not figured how to do it yet. :( |
| Re: How do I change charset=UTF-8 |
| by ghia on 2008/8/8 22:52:49 Quote: anderssk wrote: There is also an SQL file for the standard XOOPS smilies and ranks. Will that work out allright for any chosen encoding of the database? Maybe the language files of the install should contain a definition for the default character set encoding for the database. I for myself would opt for latin1 for our national languages Dutch, French and German. Quote: trabis wrote: For the moment most modules are ISO encoded for their language and sql files. There will be a lot of problems when going to utf-8. And if there was to take a unicode characterset I would prefer UTF-16. This makes it easier to reserve dataspace for strings: it's simply the double of the required string length. Unfortunate MySQL isn't yet complete on that. |