[Blog] Script Only Stacks

Tim Bleiler bleiler at buffalo.edu
Fri Mar 4 10:12:15 EST 2016


Thanks Mark,

I submitted the file in bug report 17067.

Tim


> On Mar 4, 2016, at 5:38 AM, Mark Waddingham <mark at livecode.com> wrote:
> 
> On 2016-03-03 20:45, Tim Bleiler wrote:
>> It probably doesn’t matter much as long as it’s made clear what
>> encodings are allowed. I would guess most users taking advantage of
>> this feature could live with that. Casual users may be confused
>> however, because most of us don’t give much thought to such details; a
>> text file is a text file. Mark’s blog post doesn’t make any
>> distinction either and implies any text file should work.
> 
> The current implementation in the engine uses the BOM to determine what the encoding is - if there is no BOM then it assumes the native encoding (e.g. MacRoman on Mac).
> 
> In terms of line endings, the engine converts all line endings to ASCII 10 (the universal LiveCode line ending). For reference these are:
>   CR LF (ascii 13 then ascii 10 - default windows line endings)
>   CR (ascii 13 - old-style Mac line endings)
>   LF (ascii 10 - unix line endings)
> 
> So, it shouldn't matter what line endings the input file has, and whether they are mixed or not.
> 
> I'm surprised lack of BOM in a simple script only stack would cause it to fail to load... Tim, could you attach the script only stack files you tried to create which fail to load to a bug report so we can take a look?
> 
> Warmest Regards,
> 
> Mark.
> 
> -- 
> Mark Waddingham ~ mark at livecode.com ~ http://www.livecode.com/
> LiveCode: Everyone can create apps
> 
> _______________________________________________
> 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





More information about the use-livecode mailing list