Your text file has been UTF8 encoded, and starts with a "byte order mark"
(BOM) {0xEF 0xBB 0xBF}, which then is rejected by [route].see https://en.wikipedia.org/wiki/Byte_order_mark#UTF-8 : The UTF-8 <https://en.wikipedia.org/wiki/UTF-8> representation of the BOM > is the byte sequence 0xEF,0xBB,0xBF. A text editor or web browser > misinterpreting the text as ISO-8859-1 > <https://en.wikipedia.org/wiki/ISO-8859-1> or CP1252 > <https://en.wikipedia.org/wiki/CP1252> will display the characters  > for this. Antoine Rousseau http://www.metalu.net <http://metalu.net> __ http://www.metaluachahuter.com/ <http://www.metaluachahuter.com/compagnies/al1-ant1/> 2017-02-07 8:34 GMT+01:00 Liam Goodacre <[email protected]>: > I'm getting some strange behavior when reading a .txt file with [text > define], where the output from [text get] isn't routeable like a normal > list. See the attached file for an example. Do other users experience the > same thing? > > > [text fromsymbol] reveals that there are some extended ASCII characters > junking around in front of the problematic term. Is PD accidentally reading > some meta-data from the text file? > > Currently, it only seems to be happening on the first line of the file. I > think I remember having the same problems throughout a textfile, although I > can't replicate this now. > > > Any suggestions? > > _______________________________________________ > [email protected] mailing list > UNSUBSCRIBE and account-management -> https://lists.puredata.info/ > listinfo/pd-list > >
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
