mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-10-05 21:29:20 +02:00
glib/gutf8.c (g_get_charset) glib/gconvert.c (g_locale_from_utf8) Clarify
2008-02-21 Tor Lillqvist <tml@novell.com> * glib/gutf8.c (g_get_charset) * glib/gconvert.c (g_locale_from_utf8) * docs/reference/glib/running.sgml: Clarify character set issues on Windows. svn path=/branches/glib-2-14/; revision=6552
This commit is contained in:
committed by
Tor Lillqvist
parent
540d41ec4b
commit
0976f73d27
@@ -1,3 +1,7 @@
|
||||
2008-02-21 Tor Lillqvist <tml@novell.com>
|
||||
|
||||
* glib/running.sgml: Clarify character set issues on Windows.
|
||||
|
||||
2008-02-06 Matthias Clasen <mclasen@redhat.com>
|
||||
|
||||
* === Released 2.14.6 ===
|
||||
|
@@ -214,6 +214,22 @@ call <function>setlocale (LC_ALL, "")</function> to set up the current
|
||||
locale.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
On Windows, in a C program there are several locale concepts
|
||||
that not necessarily are synchronized. On one hand, there is the
|
||||
system default ANSI code-page, which determines what encoding is used
|
||||
for file names handled by the C library's functions and the Win32
|
||||
API. (We are talking about the "narrow" functions here that take
|
||||
character pointers, not the "wide" ones.)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
On the other hand, there is the C library's current locale. The
|
||||
character set (code-page) used by that is not necessarily the same as
|
||||
the system default ANSI code-page. Strings in this character set are
|
||||
returned by functions like <function>strftime</function>.
|
||||
</para>
|
||||
|
||||
</refsect2>
|
||||
|
||||
<refsect2>
|
||||
|
Reference in New Issue
Block a user