From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041016
Description of problem:
Korean directory name display to "???????" in Locale UTF-8.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Execute mc in directory with Korean name.
Actual Results: Display to "??????"
Korea directory name is encoded to UTF-8/
Created attachment 105365 [details]
mc in Korean directory name.
Known issue. The fixes to the UTF-8 patch should fix this.
Jindrich, you should use the original (but fixed against CVS) utf8
patch, plus Vladimir's utf8-fix, utf8-hints and utf8-input patches.
Together these should fix most utf8 issues, and issues with other locales.
Sangu, please also tell which terminal you use as that might also make
a difference. And make sure you set input to 8 bits.
Jindrich, wrt this you might want to use SuSE's 8bit patch. Take from
one of their srpms, or from
please try out the newest version I have built today: mc-4.6.1-0.8. We
have there all the recommended UTF8 patches so I think this should be
fixed in this release. I cannot test it as I don't understand Korean.
Please let me know if that helped.
This problem still happen in mc-4.6.1-0.8,
and current mc package not view and not edit Korean unicode document.
Sorry, my mistaken posting.
mc-4.6.1-0.8 can edit and view unicode document.
But the problem still happenes in directory with Korean name.
Ok, I have to test it somehow in order to do some fixup for this.
Could you please post here (as an attachment) a simple bash script
that only creates a Korean named directory in an actual path? It will
help me much to investigate the whole thing and help you get rid of
Created attachment 105590 [details]
Request bash script by Jindrich
Test in en_US.UTF-8 or ko_KR.UTF-8
(My first script for all my linux life)
Sangu, congratulations for the first bash script! Thanks for it, now
I'm able to reproduce the bug. I'll try to fix it today.
The error was in the second part of uglydir patch. The is_printable()
function returns that the Korean characters are not printable, so
question marks are displayed instead of them. Since a case noticed in
bug 127164 does not occur when UTF8 is enabled, I dropped the second
part of the uglydir patch and it is displayed correctly now.
Jindrich, can you please submit the (fixed) uglydir patch upstream? TIA.
*** Bug 137435 has been marked as a duplicate of this bug. ***
Fixed in mc-4.6.1-0.9.