Monte Goulding wrote:

>> On 13 Feb 2018, at 11:56 am, Richard Gaskin wrote:
>> something more sensible
> We already have:
> open file for “utf-8” text
> There was some discussion of implementing “file+<encoding>:/path
> /to/file” style urls to avoid having to use binfile and textDecode
> and manual line ending wrangling.
> Also if there is a BOM then the unicode encoding can and is worked
> for file: urls and open file for text. It’s when there’s no BOM and
> no explicit encoding specified that the engine defaults to legacy
> native encodings.

More reasonable indeed. With all the complicated examples floating around I'd forgotten about the "open file" addition. Nice.

 Richard Gaskin
 Fourth World Systems
 Software Design and Development for the Desktop, Mobile, and the Web

use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription 

Reply via email to