comment on

My thinking is that could could modify your code to something like (untested):

#  assumes $filename is set from Tk 

my $fh;
Win32::LongPath::openL (\$fh, '<', $filename) 
  or die "Unable to open $filename";

my $parser   = Spreadsheet::ParseXLSX->new();
my $workbook = $parser->parse($fh);

#  do stuff
[download]

openL is documented at https://metacpan.org/pod/Win32::LongPath#openL-FILEHANDLEREF,MODE,PATH

You could also check the filename can be found using testL. https://metacpan.org/pod/Win32::LongPath#testL-TYPE,PATH

This all comes with the caveat that I have not used these functions, although if it does work then it will help solve one of my own longstanding headaches with a Gtk2 application.

In reply to Re^3: Spreadsheet::ParseXLSX filename non Latin Tk getOpenFile by swl
in thread Spreadsheet::ParseXLSX filename non Latin Tk getOpenFile by IB2017

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks