On Thursday, September 18, 2003, at 03:37 PM, Tuviah Snyder wrote:
Okay, but how do I determine what to do at runtime? On my system I
have three different file names that I am testing with:
1) All english characters
2) All japanese characters
3) Uses european characeters (é)
If I use uniEncode
> Hi,
>
> I am trying to implement double-byte support for an application I am
> updating for a customer. I have some things working with Unicode but
> the majority I have not been able to figure out yet. I'm hoping
> someone can shed some light on this for me.
>
> Setup:
> Mac OS X.2.6
> In
> So how do I determine which encoding to use on a string so it displays
> correctly?
Well I think we need to support unicode or UTF8 paths names, using the
useunicode property, which I plan to do in the near future. Current there is
no way to know:-( because to be compatible with the previous beha
On Thursday, September 18, 2003, at 12:53 PM, Tuviah Snyder wrote:
Problem here is that one of your unicode characters may contain the
newline
character and therefore Rev is returning the wrong line offsets
(because the
chunk stuff is still working in ASCII mode). Support for unicode
chunks is
> The following code will display a path which looks like
> "/Users/tdevore/desktop/JAPANESE_CHARACTERS" on the first line of the
> field but will not work for multiple lines. It places everything on
> the first line or causes Rev to hang. The code works fine without
> unicode text. tNextLine is
