On Sat, Nov 26, 2005 at 08:30:58AM -0600, Jolan Luff wrote: > On Sat, Nov 26, 2005 at 01:33:02PM +1100, Damien Miller wrote: > > > > 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. > > this is fallout from the CODESET stuff espie did. dvdauthor is also > broken, gqview spews warnings, etc. > > do we have to go through fixing ports or is this a src problem? > > > 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
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)
