Re: encoding chars problems in Xterm
 

Out of curiosity, is there a listing of power features? We all might be missing on something. Good job, hope you keep it up.

Re: encoding chars problems in Xterm
 

There isn't a complete listing of all power features provided by busybox-power; the bulk of it is introduced by over three years of upstream BusyBox development. I can give you a global summary of busybox-power's features over those of the stock BusyBox though.

[shameless self-plug]
There are roughly four areas of improvement:

• Utilities - A lot more utilities are provided (e.g. iostat, wget, ip, httpd, crond, unix2dos, telnet, and ~180 more)
• Features - More features in most provided utilities (e.g. swapon with priority support and colored ls output) and more features in the default shell (e.g. much improved Unicode support, Ctrl-R reverse history search and proper shell history handling)
• Upstream fixes - Over 3 years of fixes (bug fixes, security fixes, ..) from upstream BusyBox. Also see upstream BusyBox' git log.
• Maemo fixes - Providing Maemo-specific bugfixes, e.g. bug #700, #5317, #4174, #4175, #7014

[/shameless self-plug]

Further busybox-power specific discussion (if any) should probably continue over at its own thread, since we're getting kind of off topic now.

Re: encoding chars problems in Xterm
 

Thanks for it iDont :-)

No more problem in terminal but with my application (smssend), have the same problems I used to before... (example: instead of "é", I get "é", and latin-1 chars)

Re: encoding chars problems in Xterm
 

You're welcome :)

I'm not sure if this is related to the terminal itself. Setting a locale enables your applications to know what language/charset you want to use, but this only works if the application respects it and handles the charset properly. While the shell itself might support Unicode perfectly fine, applications launched from it might not.

This post supports that smssend might be at fault, although the author hasn't responded yet at the moment. I'll keep an eye on the smssend thread.