obexapp-1.4

[Pav Lucistnik]

Maksim Yevmenkin píše v st 15. 12. 2004 v 15:32 -0800:

> >>>> 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, 

That would be not a big paint, libiconv is present on almost every
system, and certainly on every desktop system. It's dependency on common
packages like gettext, gmake, ...

> 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?

LANG=cs_CZ.ISO8859-2

-- 
Pav Lucistnik <pav at oook.cz>
              <pav at FreeBSD.org>

Autumn changed into Winter ... Winter changed into Spring ...  Spring
changed back into Autumn and Autumn gave Winter and Spring a miss and went
straight on into Summer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: Toto je =?iso-8859-2?Q?digit=E1ln=EC?=
	=?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?=
	=?ISO-8859-1?Q?_zpr=E1vy?=
Url : http://lists.freebsd.org/pipermail/freebsd-bluetooth/attachments/20041216/a3cdeabc/attachment.bin