Hi list
To reignite this discussion now that I've finished my exams...
I posted this on Simos' blog a while back, but the discussion there
had died off it seems, so I'll repost here.
UTF-8 is designed so that subsequences are unambiguous. You won't get
a byte less than 0x80 in any part of a
Some people are worried about string functions breaking. I really
don't see how this is the case, seeing as we're doing g_some_function
(_(Some ASCII string)) which is replaced with a UTF-8 string at
runtime anyway.
Does anyone have any actual proof of UTF-8 in our translatable strings
2008-06-13 klockan 16:44 skrev Alan Cox:
If your string is untranslated then _(foo) - foo. If your locale is
not unicode then this places utf8 symbols into non-utf8 locales.
Since you don't know whether the result of _(foo) will be strict ASCII,
you must always treat it as if it were not.
Since you don't know whether the result of _(foo) will be strict ASCII,
you must always treat it as if it were not. GLib/GTK+ *requires* UTF-8
strings for all (most?) of its string handling functions...
GTK/Glib are not the biggest problem here. You also use C library
functions in Gnome
On Fri, Jun 13, 2008 at 4:12 PM, Alan Cox [EMAIL PROTECTED] wrote:
What about printing to files ? An nm also rather suggests that gnome
apps do use printf and fprintf somewhat and many of the other functions
mentioned. syslog() is another that is used.
I don't know what your use cases are,
On Fri, 13 Jun 2008 19:41:15 +0100
Iain * [EMAIL PROTECTED] wrote:
On Fri, Jun 13, 2008 at 4:12 PM, Alan Cox [EMAIL PROTECTED] wrote:
What about printing to files ? An nm also rather suggests that gnome
apps do use printf and fprintf somewhat and many of the other functions
mentioned.
Alan Cox wrote:
GTK/Glib are not the biggest problem here. You also use C library
functions in Gnome applications. Glib/Gtk+ works with the C library in C
locale simply because ASCII is a subset of UTF-8. That ceases to work the
moment you introduce UTF-8 bytesequences into non utf-8 locales.
2008/6/12 Xavier Claessens [EMAIL PROTECTED]:
I hope this will help the adoption of Empathy for GNOME 2.24.
-1
(I haven't said anything during the 2.24 release cycle. I just reviewed the
application as it stands at version 0.23.1 and I believe that it simply is
not ready to be included.
Hello,
Jason D. Clinton wrote:
I hope this will help the adoption of Empathy for GNOME 2.24.
-1
(I haven't said anything during the 2.24 release cycle. I just reviewed the
application as it stands at version 0.23.1 and I believe that it simply is
not ready to be included. Perhaps in
On Fri, 2008-06-13 at 17:35 -0500, Jason D. Clinton wrote:
(I haven't said anything during the 2.24 release cycle. I just
reviewed the application as it stands at version 0.23.1 and I believe
that it simply is not ready to be included. Perhaps in 2.26.)
Not to be picky but you are already 2
Alan, you seem to be missing the point. The only places where I am
suggesting replacing with are in existing gettext calls, which
*are* UTF-8 whether they need to be or not, and are always used with
UTF-8 string functions.
The issue is whether the compiler will bork when it sees bytes with
MSB
So how do we go about coming up with an official position for this? If
I start cooking patches here and there I don't want to have to make
the same argument with every maintainer... :)
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
12 matches
Mail list logo
