Ah, ok, I see. I have to admit that I don't know anything about director
on double-byte systems (chinese, japanese, korean). Maybe the script
could be extended in this direction, if I knew more about double-byte
strings in lingo. Do you know if it's possible to install such a
Director version on a single-byte OS (Win XP or OS X 10.3, both german),
or does the OS have to be double-byte as well?

Valentin


Daniel Nelson wrote:
> Hi Valentin,
>
> Sorry, this was an imprecise use of language on my part.  I meant
> that the conversion is limited to
> those character sets that have traditionally been represented with
> single-byte encoding, as opposed
> to, say, Chinese.  And so it doesn't fully implement Unicode in
> Lingo, but it goes a long way
> towards that goal.
>
> Kind Regards,
>
> Daniel
>
> Valentin Schmidt wrote:
>> Hey Daniel,
>>
>> what exactly do you mean with "single-byte" unicode? the scripts
>> supports UTF-8 and the full "Basic Multilingual Plane" of
>> UCS-2/UTF-16, i.e. all 2-byte-chars (=the "original Unicode") from
>> U+0000 to U+FFFF (more than 60000 characters, that include all
>> alfabets in the world). Daniel Nelson wrote:
>>
>>> Oh, right, still only single byte unicode.  But that's a start in
>>> the right direction!
>>>
>>> Daniel Nelson wrote:
>>>
>>>> Thank you, Valentin!
>>>>
>>>> Unicode in Lingo without reliance on Flash was my number one
>>>> wish-list request.  Now, as long as embedded fonts work, it looks
>>>> like you've given us a way to do that!
>
> [To remove yourself from this list, or to change to digest mode, go
> to http://www.penworks.com/lingo-l.cgi  To post messages to the list,
> email [email protected]  (Problems, email
> [EMAIL PROTECTED]). Lingo-L is for learning and helping with
> programming Lingo.  Thanks!]

[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email 
[email protected]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for 
learning and helping with programming Lingo.  Thanks!]

Reply via email to