On 19 March 2013 02:36, Enrico Tröger enrico.troeger@uvena.de wrote:
On 18/03/13 01:27, Lex Trotman wrote:
On 18 March 2013 10:31, Colomban Wendling lists.ban@herbesfolles.org wrote:
Le 17/03/2013 19:51, Colomban Wendling a écrit :
Le 17/03/2013 17:42, Colomban Wendling a écrit :
Le 17/03/2013 17:17, Christian Dywan a écrit :
Branch: refs/heads/master Author: Christian Dywan christian@twotoasts.de Committer: Enrico Tröger enrico.troeger@uvena.de Date: Sun, 17 Mar 2013 16:17:09 UTC Commit: d270e6c69082d114901af23b756a3375a5b5ce23 https://github.com/geany/geany/commit/d270e6c69082d114901af23b756a3375a5b5ce...
Log Message:
Parse compiler provided build date to use the translatable date format string
I have a system with LANG=fr_FR.UTF-8.
Opening the about dialog with LANG=C results in:
(geany:23003): GLib-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gdate.c:2523Error converting results of strftime to UTF-8: Invalid byte sequence in conversion input
(geany:23003): GLib-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gdate.c:2523Error converting results of strftime to UTF-8: Invalid byte sequence in conversion input
(geany:23003): GLib-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gdate.c:2523Error converting results of strftime to UTF-8: Invalid byte sequence in conversion input
(geany:23003): GLib-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gdate.c:2523Error converting results of strftime to UTF-8: Invalid byte sequence in conversion input
(geany:23003): GLib-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gdate.c:2523Error converting results of strftime to UTF-8: Invalid byte sequence in conversion input
(geany:23003): GLib-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/gdate.c:2523Error converting results of strftime to UTF-8: Invalid byte sequence in conversion input
OK apparently if the LANG doesn't have encoding information g_locale_to_utf8() assumes something not UTF-8 (I guess ASCII), and since I didn't change LC_TIME, strftime() did output something the GLib code couldn't handle (with UTF-8 I guess). Setting LC_TIME=C fixes the issue.
Not sure if we can to do something about it.
Sigh, if I knew what problems this can cause, I probably didn't do it... However I wonder if this only happens if someone manually fiddles with LANG and LC_* settings or if it may also happen on "normally" configured system?
From comments on IRC, there are a number of users who like to run
their applications in lang=C whilst keeping their desktop using their local locale. So while not very common, it isn't rare.
Cheers Lex