I feel like I am reading a foreign language (grin) dealing with
unicode. I would like to know what Unicode does work with. line, item,
word, foundchunk, filter, find, etc.
Thanks
Tom
On May 10, 2005, at 1:24 PM, pkc wrote:
Hello Thomas, here is my strategy, which on the basis of my experience
so far I believe won't render all correct characters on Windows. But,
see what you can make of it.
This is the critical part of the script:
put the number of words in fld "chinese" into charCount
put 1 into lineCount
repeat
find string "= " in fld "window"
if the result is "not found" then exit repeat
put the foundChunk into thisInsert
put (word lineCount of fld "chinese") into the foundChunk
set the textFont of thisInsert to "Taipei,Chinese"
add 1 to lineCount
end repeat
I suppose it is self-explanatory. The field "chinese" contains a
series of characters, one on each line, that are fed in order into the
English text. I tried various markers, but for some reason this one
(not very intuitive) works best.
I found by trial and error that not using a variable like "thisInsert"
and just relying on floating foundChunks produced a lot of errors.
With this script, I have NO errors on the Macintosh that cannot be
traced to Unicode ambiguities. However, in Windows there is more junk
than sense in the characters. I still think that Windows is picking
up the carriage returns in the "chinese" source file and feeding them
into the English file, which with the font change at the foundChunk
renders a lot of nonsense. I don't know how to get the program to stop
it.
_______________________________________________
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
