Date: Wed, 15 Dec 2004 15:32:34 -0800 From: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> To: pav@FreeBSD.org Cc: freebsd-bluetooth@FreeBSD.org Subject: Re: obexapp-1.4 Message-ID: <41C0C992.2050605@savvis.net> In-Reply-To: <1102731873.60420.21.camel@hood.oook.cz> References: <41B8D6D5.6090801@savvis.net> <1102634931.90683.9.camel@hood.oook.cz> <41B8E56C.6050409@savvis.net> <1102668370.34937.7.camel@pav.hide.vol.cz> <41B9E211.8050005@savvis.net> <1102709951.60420.9.camel@hood.oook.cz> <41BA2816.9000908@savvis.net> <1102721530.60420.15.camel@hood.oook.cz> <41BA5490.3000708@savvis.net> <1102731873.60420.21.camel@hood.oook.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Pav, >>>> so i guess obexapp(1) should use encoding header from xml and >>>> translate values from xml into locale one is using >>> >>> Would be very nice, yes. >> >> how about setting you locate to utf-8, i.e. >> >> % LANG=<whatever>.UTF-8 xterm (for Russian language >> LANG=ru_RU.UTF-8) >> >> and then in new xterm window try to run obexapp and do ls. does cd >> command work? do you see any difference in ls output? > > ls output is now readable, but I can't cd to directories. ok, thanks. just as i expected :( this whole thing is a train wreck :( OBEX_CharToUnicode and OBEX_UnicodeToChar just plain broken in openobex library :( the quick hack is to use something like iconv(3) to convert between current locate and unicode/utf-8. i do not like it very much, because its another port to install, but i'm not sure there is a standard freebsd-way to do the same thing. also, it seems, libbsdxml(3) always feeds utf-8 characters to all callbacks. it worked before only because no one tried obexapp(1) on "localized" phone :( btw, what locale are you using? max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41C0C992.2050605>