The thing is importing using file mode changes the line endings which is
perfectly fine in UTF8. It's still UTF8 afterwards which is why textDecode
still works. You could just textDecode then script the replacement of the line
endings but it's probably easier for the engine to do it.
Sent from
Thanks for the link. I need to “grow up” and move some stacks to 7. I will need
to re-re-learn about unicode before it bites me.
.Jerry Jensen
> On Aug 18, 2015, at 1:50 PM, Brahmanathaswami wrote:
>
> i would highly recommend a "deep read" of the read me docs for 7.05 where
> there is super d
On 8/18/2015 3:50 PM, Brahmanathaswami wrote:
So I extracted this for my own ref
http://dev.himalayanacademy.com/stacks/705-Release-Unicode-Notes.pdf
Thanks for that. As Monte said, it turns out "file" works, but I didn't
expect it because the entry for textDecode talks about binary files. I
i would highly recommend a "deep read" of the read me docs for 7.05
where there is super detail info on all the unicode changes
so much changed, mission critical stuff, a lot easier, but you need to
do it right.
OH! the release notes for 7.1 don't have any of the unicode business...
I don't
I don't think it would hurt to use file for utf-8
Sent from my iPhone
> On 19 Aug 2015, at 5:41 am, J. Landman Gay wrote:
>
> Should I be using "file" or "binfile" to retrieve unicode text from a UTF-8
> text file? I thought I should be using binfile, but after textDecoding the
> data, text c
Should I be using "file" or "binfile" to retrieve unicode text from a
UTF-8 text file? I thought I should be using binfile, but after
textDecoding the data, text chunking and delimiters break when I do that.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software
