> as far as I know, text files from the "text" object are encoded in
> macRoman (XP and OSX), and this object may only accept macRoman
> encoded characters.
> That’s why probably you run into problems when using neooffice or
> other text editors that may output UTF-8 encoded characters by
But then still Open office and simpletext should create the same result
and if you do it in Textwrangler you can choose the format and it still
If I double click the text object it shows all lines correctly, if I
send the line command, it will put out only a single "set". The same
with the max created works fine…
There must be a bug, I tried all variants on coding and line breaks.
But if I create a new file it will read correct. With Simpletext or with
Maybe the files created on windows are fine for windows, and the one on
Mac are fine for the Mac…
Falk Grieffenhagen wrote:
> Now I found out I have to be a bit more precise asking for
Not about the format, just tell them to use simple text which is on
every Mac. It works with its default setting. But a little smart parser
in Max which would be able to make intelligent assumptions, could be
helpful as well.
Of course in Max 5 I expect externals which do understand meta data of
text files… (for the record of the feature collection department of