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.
Tim > On Mar 3, 2016, at 2:37 PM, Monte Goulding <mo...@appisle.net> wrote: > > I know I have discussed this with Mark Waddingham before. I believe he was > originally thinking of allowing other encodings at some point but was not > averse to my suggestion of only supporting UTF8 with or without BOM. > > Sent from my iPhone > >> On 4 Mar 2016, at 6:17 AM, Tim Bleiler <blei...@buffalo.edu >> <mailto:blei...@buffalo.edu>> wrote: >> >> I guess that leaves the question of whether this should remain a requirement >> of script only stacks or if the engine can be modified to accept without BOM > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
