15
Quote:
anderssk wrote:
But the 4 language files in ../install/language/yourlanguage has to be encoded in UTF-8
In my release, there weren't any other language files present except for English. I don't think that would be a problem, while these files are only temporary used with the installation, which generates utf-8 html. Or does the setting of the database encoding to something else, also change the encoding of the html?
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:
And the I ask, what sense is there in having lang files in utf-8. I would need to buy an special editor just to make small changes in language files. Utf-8 sucks big for me. Why can I just use my old and pretty simple notepad? This will soon become the faq most readed.
Are you talking about Windows Notepad? Because there you can select the encoding when doing file - save as. It has ANSI, UTF-8, Unicode little and big endian.
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.