You can't have it both ways. Either shell() only characters of the broadest character set, Unicode, or it returns binary. If it returns characters, then it will not work for binary responses; that will have to be documented as excluded.
If Unicode is returned then textDecode is not needed and even should not be used. > On Aug 22, 2019, at 2:08 PM, Richard Gaskin via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Dar Scott wrote: > > > If the result of shell() is run through textDecode, should then > > shell() return binary data? This puts it outside the scope of > > "everywhere". I like the idea, as long as simple ASCII characters > > work transparently. > > Isn't that the goal of UTF-8, which is why so many programming languages uses > it as the default? > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > ____________________________________________________________________ > ambassa...@fourthworld.com http://www.FourthWorld.com > > _______________________________________________ > 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 _______________________________________________ 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
