Yep, actually I have tried getOpenFile, Tk::FBox and Tk::FileSelect, and only Tk::FileSelect could find out the exact path without transcoding to UTF-8. It shows up a Tk-style selection dialog but can't display CJK characters correctly. Worse in the case of Tk::FBox, which also shows up Tk-style dialogs but appears to be unable to handle CJK characters in the path (error message comes out when you select one). Only getOpenFile can open OS's native file selection dialog and show non-latin1 characters out.

In my opinion, a generic way to get the OS's current character encoding would be very helpful not only in pathname transcoding but also for many I18N applications. :)

In reply to Re^2: How to detect the OS's current encoding? by chaoslawful
in thread How to detect the OS's current encoding? by chaoslawful

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.