Re: glib2/gnome weirdness
maybe this can be of some help: http://www.mail-archive.com/openpkg-cvs@openpkg.org/msg07951.html --- Lars Hansson
Re: glib2/gnome weirdness
On Sat, Nov 26, 2005 at 04:08:47PM +0100, Marc Espie wrote:
Looks like the charset.alias file from libiconv needs to be completed
with info about what to do with 646...
netbsd does not have the issue because it does not use gnu libiconv...
Just adding a line like:
646 ISO-8859-1
to /usr/local/lib/charset.alias should fix things (even though it's
slightly incorrect)
changing charset.aliases is not really a complete fix.
for example, iconv(1) does not work if you use 646 as an encoding.
code that is busted because it is using nl_langinfo(CODESET)
to get the charset can be fixed by using locale_charset() from
libiconv (or libcharset but it seems nothing uses libcharset)
instead.
locale_charset() takes the output of nl_langinfo(CODESET) and does
the canonicalization (the lookup in charset.aliases).
--
[EMAIL PROTECTED]
as an example:
#include stdlib.h
#include stdio.h
#include nl_types.h
#include langinfo.h
#ifdef USE_LIBICONV
#include localcharset.h
#endif
int
main(int argc, char *argv[])
{
const char *codeset;
const char *codeset_iconv;
codeset = NULL;
codeset_iconv = NULL;
codeset = nl_langinfo(CODESET);
#ifdef USE_LIBICONV
codeset_iconv = locale_charset();
#endif
if (codeset == NULL)
codeset = ;
if (codeset_iconv == NULL)
codeset_iconv = ;
printf(codeset = %s\n, codeset);
printf(codeset_iconv = %s\n, codeset_iconv);
exit(0);
}
Re: glib2/gnome weirdness
Bernd Ahlers [Wed, Nov 30, 2005 at 07:09:54PM +0100] wrote:
However, I'd rather not touch it. I think that just writing an alias that
says 646 is ASCII in charset.alias will fix everything for now.
Like this? Works for me. Verified with gqview.
ok, comments?
No one? I think it's a simple fix and I want to get it in.
Bernd
Index: Makefile
===
RCS file: /cvs/ports/converters/libiconv/Makefile,v
retrieving revision 1.21
diff -u -r1.21 Makefile
--- Makefile 23 Apr 2005 14:40:42 - 1.21
+++ Makefile 30 Nov 2005 18:07:28 -
@@ -3,7 +3,7 @@
COMMENT= character set conversion library
DISTNAME= libiconv-1.9.2
-PKGNAME= ${DISTNAME}p1
+PKGNAME= ${DISTNAME}p2
CATEGORIES= converters devel
MASTER_SITES= ${MASTER_SITE_GNU:=libiconv/}
Index: patches/patch-libcharset_lib_config_charset
===
RCS file:
/cvs/ports/converters/libiconv/patches/patch-libcharset_lib_config_charset,v
retrieving revision 1.5
diff -u -r1.5 patch-libcharset_lib_config_charset
--- patches/patch-libcharset_lib_config_charset16 Apr 2005 21:10:22
- 1.5
+++ patches/patch-libcharset_lib_config_charset30 Nov 2005 18:07:28
-
@@ -1,7 +1,7 @@
$OpenBSD: patch-libcharset_lib_config_charset,v 1.5 2005/04/16 21:10:22 espie
Exp $
--- libcharset/lib/config.charset.origWed Jan 21 19:53:20 2004
-+++ libcharset/lib/config.charset Sun Apr 10 17:20:33 2005
-@@ -345,7 +345,7 @@ case $os in
libcharset/lib/config.charset Wed Nov 30 17:52:14 2005
+@@ -345,13 +345,14 @@ case $os in
#echo sun_eu_greek ? # what is this?
echo UTF-8 UTF-8
;;
@@ -10,3 +10,10 @@
# FreeBSD 4.2 doesn't have nl_langinfo(CODESET); therefore
# localcharset.c falls back to using the full locale name
# from the environment variables.
+ # Likewise for OS/2. OS/2 has XFree86 just like FreeBSD. Just
+ # reuse FreeBSD's locale data for OS/2.
+ echo C ASCII
++ echo 646 ASCII
+ echo US-ASCII ASCII
+ for l in la_LN lt_LN; do
+echo $l.ASCII ASCII
Re: glib2/gnome weirdness
Committed. Bernd
Re: glib2/gnome weirdness
Marc Espie [EMAIL PROTECTED] wrote: GLib: Cannot convert message: Conversion from character set 'UTF-8' to '646' is not supported Looks like the charset.alias file from libiconv needs to be completed with info about what to do with 646... 646 as a designation is a bit weird. This should really be ISO-646 aka ASCII. I guess I should take a look how glib arrives at 646. -- Christian naddy Weisgerber [EMAIL PROTECTED]
Re: glib2/gnome weirdness
On Wed, Nov 30, 2005 at 03:27:14PM +, Christian Weisgerber wrote: Marc Espie [EMAIL PROTECTED] wrote: GLib: Cannot convert message: Conversion from character set 'UTF-8' to '646' is not supported Looks like the charset.alias file from libiconv needs to be completed with info about what to do with 646... 646 as a designation is a bit weird. This should really be ISO-646 aka ASCII. I guess I should take a look how glib arrives at 646. You don't have to look. It's the default runelocale, in libc/locale. If you want it to be ASCII, just so be it. However, I'd rather not touch it. I think that just writing an alias that says 646 is ASCII in charset.alias will fix everything for now.
Re: glib2/gnome weirdness
Marc Espie dixit: 646ISO-8859-1 646 ASCII to /usr/local/lib/charset.alias should fix things (even though it's slightly incorrect) That looks better to me. //mirabile -- I believe no one can invent an algorithm. One just happens to hit upon it when God enlightens him. Or only God invents algorithms, we merely copy them. If you don't believe in God, just consider God as Nature if you won't deny existence. -- Coywolf Qi Hunt
Re: glib2/gnome weirdness
Actually they are fatal - gnome-terminal crashes at start and it is impossible to manually run Xterm from the run application menu item, it gives the same Conversion from character set... error as below. Forgot to mention - I am on i386. On Sat, 26 Nov 2005, Damien Miller wrote: Hi, I am installing a fresh machine with the Nov 24 os + ports snapshot and I am seeing these warnings as I install gnome-session: GLib: Cannot convert message: Conversion from character set 'UTF-8' to '646' is not supported GLib: Cannot convert message: Conversion from character set 'UTF-8' to '646' is not supported WARNING: Failed to parse default value `([binary gibberish[)' for schema (/schemas/apps/gnome-terminal/global/active_encodings) gnome-session-2.10.0p0:gnome-terminal-2.10.0p0: complete Any ideas? They look non-fatal so far... -d
Re: glib2/gnome weirdness
On Saturday 26 November 2005 10:24, Damien Miller wrote: GLib: Cannot convert message: Conversion from character set 'UTF-8' to '646' is not supported GLib: Cannot convert message: Conversion from character set 'UTF-8' to '646' is not supported I get this too for pretty much all apps that uses Gtk2 but i havent any had fatal problems due to it yet, only lots of spewing to stderr (especially with Sylpheed). --- Lars Hansson
