Pamela,
I rechecked my code again and I can now get the asian chars to show up but since I use Lines (with cr's) and also ":" as my item delimiter I am noticing that sometimes my code ignores the : and puts the rest of the items on the line. I am also noticing that ome of the whole lines are not available hinting to me that you are probably right on track about the CRs. I copy pasted a few itemdelimiters ":" to replace the ones in between the asian items and now the items show up. I have yet to figure out the line endings - I don't know how to copy paste a line ending????
I am assuming that either the itemdelimiters are in unicode and won't work with the "put item 2" stuff or they are not in unicode and the code can't see them. I am copying what I think are non-unicode delimiters in between the items and now they show up correctly. HHMMMMM
I will write when I figure out the line endings. I hope.
Tom
On May 9, 2005, at 10:44 PM, pkc wrote:
One thing I discovered in experimentation was that if I moved a Chinese file line by line into a new field I could get the same junk that Windows users are getting (the boxes --light or dark-- and random character elements in a meaningless string). (this was not a paste, which reproduces the textFont perfectly, as previously noted). It seemed to me that I was transferring not only the characters but also carriage-returns (is this possible??). When I manually removed the spaces between characters, everything straightened up. The problem was that I was left with a field that the computer thinks has one character in it. That won't work with my strategy --all the characters will go into the marker for the first character.
I think that could have been a blind alley, and now I am interested in the idea that Mac and Windows systems reverse the placement of the null character when dealing with UTF-16. That could be why Windows users are picking up the carriage returns and Mac users are not. The problem is I don't see a way in Revolution to tell the computer to put the null characters where WIndows expects it to be. Oh, one thing I just thought of experimenting with... I have so far been making the editing software remove all empty spaces (they produce those weird cross things in Unicode). But maybe it would be healthier to make sure the empty spaces are there, in order to keep the character returns out of the WIndows character renderings? No idea, will experiment and see if the results are any better.
Anyway, Tom, I sympathize.
Pamela Crossley _______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541
_______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
