Date: Wed, 08 Jun 2011 13:18:34 -0700 From: Chuck Swiger <cswiger@mac.com> To: Alexander Best <arundel@freebsd.org> Cc: freebsd-questions@freebsd.org Subject: Re: problem with german umlauts and gtk apps (maybe unicode issue) Message-ID: <C7306FBF-4C14-4CF5-A7B3-D08B854DF66B@mac.com> In-Reply-To: <20110608195705.GA60747@freebsd.org> References: <20110608195705.GA60747@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. >=20 > saving a file "=C4=D6=DC=E4=F6=FC=DF.html" from chromium's gtk dialog = returns the following > under the console or an X term: >=20 > otaku% ls|grep html|hd=20 > 00000000 c3 84 c3 96 c3 9c c3 a4 c3 b6 c3 bc c3 9f 2e 68 = |=C3.=C3.=C3.=C3=80=C3=B6=C3=8C=C3..h| > 00000010 74 6d 6c 0a |tml.| > 00000014 That's a UTF-8 representation; c3 84 is Unicode U+00C4 aka "LATIN = CAPITAL LETTER A WITH DIAERESIS". =20 > when i start gnome and use the open dialog both the `touch`ed = "=C4=D6=DC=E4=F6=FC=DF" file as > well as the "=C4=D6=DC=E4=F6=FC=DF.html" saved by chromium looks fine. >=20 > 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, --=20 -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C7306FBF-4C14-4CF5-A7B3-D08B854DF66B>