Re: problem with german umlauts and gtk apps (maybe unicode issue)
On Wed, 8 Jun 2011 19:57:05 +, Alexander Best arun...@freebsd.org wrote: otaku% ls|grep html|hd c3 84 c3 96 c3 9c c3 a4 c3 b6 c3 bc c3 9f 2e 68 |Ã.Ã.Ã.ÀöÌÃ..h| 0010 74 6d 6c 0a |tml.| 0014 [...] is gtk maybe switching to unicode when saving non-asciichars, instead to ISO8859-15? Yes, it looks that way. You _could_ try to use the traditional (non-european) settings: setenv LC_ALL en_US.ISO8859-1 setenv LC_MESSAGES en_US.ISO8859-1 setenv LC_COLLATE de_DE.ISO8859-1 setenv LC_CTYPEde_DE.ISO8859-1 setenv LC_MONETARY de_DE.ISO8859-1 setenv LC_NUMERIC de_DE.ISO8859-1 setenv LC_TIME de_DE.ISO8859-1 (I set them per /ect/csh.cshrc systemwide, and don't set $LANG). The downside is that there is no Euro symbol with this setting, but nobody needs that. :-) however when it accesses a filename it can understand unicode as well as ISO8859-15? I would assume that as ISO-Umlauts and UTF-Umlauts have different byte representation, (iso)öäü.html and (utf)öäü.html would be different file names, so files with the same file name would be possible. can i instruct gtk to always use ISO8859-15 when saving filenames? As I'm not a Gnome user, I can't be specific on that question. Maybe there is a setting available through the gconf tool? A workaround, of course NOT a solution, is to NOT use non-standard characters in file names. I have trained my kids... erm users. Users! :-) to exactly do that, so there won't be problems in file name representation. And only lowercase. And no spaces. If you use, for example, das_uebel_vom_fasz.html instead of Das Übel vom Faß.html, you don't need to care for character representation (as everything will always be ASCII). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem with german umlauts and gtk apps (maybe unicode issue)
On Wed, 08 Jun 2011 13:18:34 -0700, Chuck Swiger cswi...@mac.com wrote: Fortunately, ISO 8859-15 can be stored on FreeBSD's UFS filesystem without lossage-- other character sets can't since UFS doesn't do Unicode per se, just UTF-8. Storing is one thing, correct displaying is the other. As Alexander mentioned, display for 8851-1 and -15 even work in text mode console (using cons25l1) in terms of Umlauts and Eszett. The speciality of -15, the Euro symbol, won't be displayed if I remember correctly. Maybe the currency symbol (squished bug) will be used instead? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem with german umlauts and gtk apps (maybe unicode issue)
2011-06-08 21:57, Alexander Best skrev: hi there, Hallo for me the output of `locale -a` looks like this: LANG=en_GB.ISO8859-15 LC_CTYPE=de_DE.ISO8859-15 LC_COLLATE=en_GB.ISO8859-15 LC_TIME=de_DE.ISO8859-15 LC_NUMERIC=de_DE.ISO8859-15 LC_MONETARY=de_DE.ISO8859-15 LC_MESSAGES=en_GB.ISO8859-15 LC_ALL= What is the reason for setting that? I only set this in the .login_conf; me:\ :charset=iso-8859-1:\ :lang=sv_SE.ISO8859-1: And all is fine and dandy, except gqview only understands utf-8 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem with german umlauts and gtk apps (maybe unicode issue)
On Thu, 09 Jun 2011 13:16:18 +0200, Bernt Hansson be...@bah.homeip.net wrote: 2011-06-08 21:57, Alexander Best skrev: hi there, Hallo for me the output of `locale -a` looks like this: LANG=en_GB.ISO8859-15 LC_CTYPE=de_DE.ISO8859-15 LC_COLLATE=en_GB.ISO8859-15 LC_TIME=de_DE.ISO8859-15 LC_NUMERIC=de_DE.ISO8859-15 LC_MONETARY=de_DE.ISO8859-15 LC_MESSAGES=en_GB.ISO8859-15 LC_ALL= What is the reason for setting that? The reason is to have finer control over certain language aspects. For example, if one wants to have collation and date specific settings for the german language, but english program messages, LC_* can be used to address things individually. LC_ALL sets _one_ definition for all aspects, and LANG... I think LANG will be used if LC_* aren't present... not fully sure. I only set this in the .login_conf; me:\ :charset=iso-8859-1:\ :lang=sv_SE.ISO8859-1: And all is fine and dandy, except gqview only understands utf-8 I assume this does define LC_* / LANG variables? I know this setting is present in the system, but I never really used login.conf. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem with german umlauts and gtk apps (maybe unicode issue)
2011-06-09 13:21, Polytropon skrev: On Thu, 09 Jun 2011 13:16:18 +0200, Bernt Hanssonbe...@bah.homeip.net wrote: 2011-06-08 21:57, Alexander Best skrev: hi there, Hallo for me the output of `locale -a` looks like this: LANG=en_GB.ISO8859-15 LC_CTYPE=de_DE.ISO8859-15 LC_COLLATE=en_GB.ISO8859-15 LC_TIME=de_DE.ISO8859-15 LC_NUMERIC=de_DE.ISO8859-15 LC_MONETARY=de_DE.ISO8859-15 LC_MESSAGES=en_GB.ISO8859-15 LC_ALL= What is the reason for setting that? The reason is to have finer control over certain language aspects. For example, if one wants to have collation and date specific settings for the german language, but english program messages, LC_* can be used to address things individually. LC_ALL sets _one_ definition for all aspects, and LANG... I think LANG will be used if LC_* aren't present... not fully sure. I only set this in the .login_conf; me:\ :charset=iso-8859-1:\ :lang=sv_SE.ISO8859-1: And all is fine and dandy, except gqview only understands utf-8 I assume this does define LC_* / LANG variables? It defines LANG=sv_SE.ISO8859-1 no LC* I know this setting is present in the system, but I never really used login.conf. :-) login.conf is system wide. .login_conf is not. Example from xterm %cal Juni 2011 Sö Må Ti On To Fr Lö 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 åäö ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem with german umlauts and gtk apps (maybe unicode issue)
On Thu Jun 9 11, Polytropon wrote:
On Wed, 8 Jun 2011 19:57:05 +, Alexander Best arun...@freebsd.org wrote:
otaku% ls|grep html|hd
c3 84 c3 96 c3 9c c3 a4 c3 b6 c3 bc c3 9f 2e 68
|Ã.Ã.Ã.ÀöÌÃ..h|
0010 74 6d 6c 0a |tml.|
0014
[...]
is gtk maybe switching to unicode when saving non-asciichars, instead to
ISO8859-15?
Yes, it looks that way.
You _could_ try to use the traditional (non-european) settings:
setenv LC_ALL en_US.ISO8859-1
setenv LC_MESSAGES en_US.ISO8859-1
setenv LC_COLLATE de_DE.ISO8859-1
setenv LC_CTYPEde_DE.ISO8859-1
setenv LC_MONETARY de_DE.ISO8859-1
setenv LC_NUMERIC de_DE.ISO8859-1
setenv LC_TIME de_DE.ISO8859-1
(I set them per /ect/csh.cshrc systemwide, and don't set $LANG).
The downside is that there is no Euro symbol with this setting,
but nobody needs that. :-)
however when it accesses a filename it can understand unicode as
well as ISO8859-15?
I would assume that as ISO-Umlauts and UTF-Umlauts have
different byte representation, (iso)öäü.html and (utf)öäü.html
would be different file names, so files with the same
file name would be possible.
can i instruct gtk to always use ISO8859-15 when saving filenames?
As I'm not a Gnome user, I can't be specific on that
question. Maybe there is a setting available through
the gconf tool?
A workaround, of course NOT a solution, is to NOT use
non-standard characters in file names. I have trained
my kids... erm users. Users! :-) to exactly do that, so
there won't be problems in file name representation.
And only lowercase. And no spaces. If you use, for
example, das_uebel_vom_fasz.html instead of Das Übel
vom Faß.html, you don't need to care for character
representation (as everything will always be ASCII).
i think the problem is gtk. when i set LC_ALL=ISO8859-15, gimp complaints
about it:
(gimp:56139): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
when i set it to lets say LC_ALL=de_DE.ISO8859-15 or LC_ALL=de_DE.ISO8859-1, it
doesn't complain. so it recognises that locale. however for some reason it
switches to UTF-8 when using chars like ö or ä, although they are perfectly
valid chars for the locale i defined.
this seems like a gtk bug imho.
cheers.
alex
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
--
a13x
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
problem with german umlauts and gtk apps (maybe unicode issue)
hi there, for me the output of `locale -a` looks like this: LANG=en_GB.ISO8859-15 LC_CTYPE=de_DE.ISO8859-15 LC_COLLATE=en_GB.ISO8859-15 LC_TIME=de_DE.ISO8859-15 LC_NUMERIC=de_DE.ISO8859-15 LC_MONETARY=de_DE.ISO8859-15 LC_MESSAGES=en_GB.ISO8859-15 LC_ALL= when i do `touch ÄÖÜäöüß` this works great. i can see the correct characters under the console, X term and in gtk file dialogs. *however* when i save a file via the gtk save dialog (lets say from within chromium), the filename only gets displayed correctly in the gtk open dialog. saving a file ÄÖÜäöüß.html from chromium's gtk dialog returns the following under the console or an X term: otaku% ls|grep html|hd c3 84 c3 96 c3 9c c3 a4 c3 b6 c3 bc c3 9f 2e 68 |Ã.Ã.Ã.ÀöÌÃ..h| 0010 74 6d 6c 0a |tml.| 0014 when i start gnome and use the open dialog both the `touch`ed ÄÖÜäöüß file as well as the ÄÖÜäöüß.html saved by chromium looks fine. is gtk maybe switching to unicode when saving non-asciichars, instead to ISO8859-15? however when it accesses a filename it can understand unicode as well as ISO8859-15? can i instruct gtk to always use ISO8859-15 when saving filenames? cheers. alex -- a13x ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem with german umlauts and gtk apps (maybe unicode issue)
On Jun 8, 2011, at 12:57 PM, Alexander Best wrote: *however* when i save a file via the gtk save dialog (lets say from within chromium), the filename only gets displayed correctly in the gtk open dialog. saving a file ÄÖÜäöüß.html from chromium's gtk dialog returns the following under the console or an X term: otaku% ls|grep html|hd c3 84 c3 96 c3 9c c3 a4 c3 b6 c3 bc c3 9f 2e 68 |Ã.Ã.Ã.ÀöÌÃ..h| 0010 74 6d 6c 0a |tml.| 0014 That's a UTF-8 representation; c3 84 is Unicode U+00C4 aka LATIN CAPITAL LETTER A WITH DIAERESIS. when i start gnome and use the open dialog both the `touch`ed ÄÖÜäöüß file as well as the ÄÖÜäöüß.html saved by chromium looks fine. is gtk maybe switching to unicode when saving non-asciichars, instead to ISO8859-15? however when it accesses a filename it can understand unicode as well as ISO8859-15? Yes, that appears to be the case. can i instruct gtk to always use ISO8859-15 when saving filenames? Dunno. Fortunately, ISO 8859-15 can be stored on FreeBSD's UFS filesystem without lossage-- other character sets can't since UFS doesn't do Unicode per se, just UTF-8. Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
