On 11/3/15, 9:43 AM, "Marcus Fritze" <[email protected]> wrote:
>Thanks for the advice. It’s maybe the quickest fix to create a >ActionScript function that fixes the file name of any selected file >before I upload a file to the server. > >But seems to be a lot of work, to fix all the allowed UFT-8 characters >which are allowed in file names. I only did enough digging to find the two links. I don’t know if it is better to fix the file names before upload, or ask the server for a corrected file name before displaying it to the user. There might be existing code that will fix the UTF-8 in browsers or in JavaScript that you could call via ExternalInterface. There might be an ActionScript conversion. Or you might be able to get away with a simple test for the 776 character and have a table of replacements. > >Please, correct me if I am wrong, but this is a Google Chrome issue, >right? Should I file a issue for Chrome? There might be more than one issue here. IMO, Flash should properly display the string with the 776 character. I’d be surprised if there isn’t already an issue filed against Chrome, but I would expect their answer to be that they are doing the “right” thing. I’m not an expert in this stuff, but it isn’t clear to me that it is “wrong” to not use 228 in a UTF-8 app, especially if there are algorithms out there that do sorting/collation based on breaking out the diacritics, or for making valid URLs. Good luck, -Alex
