SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Midnight Commander needs a patch to display utf8 characters, and it also needs a utf8-patched slang2.
Further I had some problems with kmail authenticating to a iso-8859-15 server, with utf8 enabled locally.
But I don't know, if that problem was caused by kmail or the server.
I've switched to UTF8 now myself and take back my comment on Midnight Commander. I don't know what all this complaints about missing UTF8 support in mc are about, but it works good enough to work with, at least under a X terminal. Mc seems to have some issues with col-width calculation when displaying filenames with unicode-characters. But that's more a design-issue than a functionality issue.
I'm in an UTF8 system now for 2 days. So far, no problems at all.
I did edit the /etc/profile.d/lang.sh.
I wanted to switch a while ago, but had to switch back as too many files had iso-content. Also some files had iso-characters in their filenames.
I had to correct these things for the final switch, which happened just days ago.
You raise an interesting point - what to do with all the files that have troublesome filenames... I've noticed a plethora of utf8-conversion scripts out there - do you have anyone in particular to recommend?
(While I do have backups, I'd rather not find out in retrospect that the particular script I choose is garbling all filenames beyond recognition)
Nope. I've written one myself but I won't recommend anyone to use it...
And I still have not converted everything. OOo-files, notes etc do still have some weird chars.
I basically relied on iconv and uconv.
Apart from the already mentioned mc vs utf8 issue, i can't saying anything to keep you from switching either. Configure your apps properly and you'll be happy ever after
Unfortunately it is not so. Sorry. Partly it is so. If you use US or British English or you don't use console at all then it will be so. But many issues are around, for examble those I mentioned above and plus those those packages that were updated in current, speaking of wget and oggenc they have the same problem: they span new lines while refreshing the lines.
Basic utils still seem to lack UTF-8 support. For example
find dir -ls
will give just escape sequences for UTF-8 symbols.
You're right - Having searched savannah for info on findutils, I cannot find any open bugs on find not being utf8-compliant. Any ideas or pointers where to search for the root cause to this?
I mean - for groff/man, it's easy: lot's of useful patches sitting in cvs, but no release for ages (groff:4 years, man: 1 year) - but for findutils everything appears to be OK as per the bug database and changelogs...
Then again, I'm a novice at tracking these things down - hence the question :-)