Unicode is not "everywhere"...

[Monte Goulding]

Both of these are anomalies we could only resolve with new syntax I think… at lease the urlEncode one is. I’m not sure if the expectation of shell is it returns text or binary data… The workaround there would be to open process for UTF8 text read instead of using shell... not sure if UTF8 would be right on windows… possibly UTF16 there.

Regarding url encoding the anomaly bug is https://quality.livecode.com/show_bug.cgi?id=14015 <https://quality.livecode.com/show_bug.cgi?id=14015> so your report should be closed as a duplicate of it I suspect.

Probably the simplest way to resolve the detailed files/folders issue is to have a new parameter for the files and folders function to return an array. Anyone want to suggest a name for the parameter?

Cheers

Monte


> On 23 Aug 2019, at 1:37 am, Paul Dupuis via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> 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!
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode