Unicode is not "everywhere"...

Paul Dupuis paul at researchware.com
Thu Aug 22 11:37:53 EDT 2019


I have filed two bug reports that are in LC905rc1 and go back to 7.0 
where LC functions that should deal with Unicode properly do not.

These are:
https://quality.livecode.com/show_bug.cgi?id=22213 -- The "detailed 
files" function fails for any files with Unicode in the name, returning 
the filename with %3F (?) instead of the Unicode characters properly URL 
encoded (they should be UFT8 encoded and then URL encoded)
and
https://quality.livecode.com/show_bug.cgi?id=22334 -- the shell command 
is not Unicode aware in returning it's results. On OSX, the results are 
UTF8 encoded (discovered by accident) and so an extra step is needed to 
text decode them, but on Windows it is a complete failure and any 
Unicode results of the command line - SHOWN 100% correctly is executed 
in the command line - are returned NATIVE encoded, causing all Unicode 
characters to become question marks.

I have written work-around for both of these bugs that can be found in 
the bug reports. My work-around for the "details files" is slow, due to 
repeated calls to shell to fetch file properties one at a time.

If anyone else out there has run into these bugs in your own code and 
developed a faster work-around for the "detailed files" and would care 
to share, I would welcome a faster fix.

Of course, I'd welcome a fix from LiveCode, Ltd. to these bugs even more!




More information about the Use-livecode mailing list