Christian Hujer wrote:
Hello dear co-devs.
We have a common problem with the text encodings of data files.
Examples:
* Daimonin used (until a few minutes ago) the ISO paragraph character 0xA7
for
separating a map's sound spec from its name.
* Daimonin uses the ISO degree character
En l'instant précis du 02/06/07 09:03, Mark Wedel s'exprimait en ces termes:
(OT: Did not post for a long time, hello to everyone)
#3 probably makes the most sense, and at least for the gtk2 client, looks
like
it would actually be handled properly (as the message generated on the wine
Hello.
My favorite solution would be 3. UTF-8, followed by 1. US-ASCII. I dislike
2. ISO-8859-15 very much.
Favorite solution is 3, UTF-8 :)
It works nicely even with non utf8-aware functions (strlen such), and is
international so we'll not have any more issues with that :)
Nicolas
--
Nicolas Weeger (Laposte) wrote:
My favorite solution would be 3. UTF-8, followed by 1. US-ASCII. I dislike
2. ISO-8859-15 very much.
Favorite solution is 3, UTF-8 :)
It works nicely even with non utf8-aware functions (strlen such), and is
international so we'll not have any more
Hello dear co-devs.
We have a common problem with the text encodings of data files.
Examples:
* Daimonin used (until a few minutes ago) the ISO paragraph character 0xA7 for
separating a map's sound spec from its name.
* Daimonin uses the ISO degree character 0xB0 for highlights in messages.
*
5 matches
Mail list logo
