Unicode mixd fonts Windows

[pkc]

Many thanks, Devin, for the suggestion. I was very attracted to it because the client I have built displays its English text entirely in HTML.  I also thought that displaying Chinse characters in such a field should work across platforms.  In practice, the problmes I had were that setting text properties for the field tended to reset font properties, and vice versa.  I did not finish experimenting with the order of these commands, so I cannot be sure that there was no way to get them to work.

So far following the suggestions you made regarding the use of htmlText has not produced accurate results for me on Macintosh (though, ironies being what they are, if I were working in Windows maybe it would look very successful to me).  there are a few things I think I still don't undrstand about this:

1) are you referring to fields showing mixed fonts? Some in English and some in Chinese or other Asian scripts?  On reading the account it seems to me it might refer to whole fields in a single Unicode font.

2) In our case, the files are already created, as it happened in Windows, but with Unifont code for the Chinese characters.  They files go between a server and a client, so they go in ascii format (as I say, in OS X this works perfectly). The characters and English text have to be recreated at the user end.  It seems to me that this shhould make no difference, if the files are put into htmlText before being sent and then put back into htmlText once they are received from the client, does that seem right?

I'm still experimenting with this general idea, and it might work (with some redundancy in the script. I just wanted to make sure that this is a strategy for working with mixed English and Asian characters.

Sincerely,
Pamela

Crossley
Dartmouth
USA

use-revolution-request at lists.runrev.com on 5/10/05 wrote:use-revolution-request at lists.runrev.com

>We have found this problem also with cross platform applications that 
>must display unicode in fields. We finally arrived at a workaround in 
>which we use html text with unicode entities. That seems to be the most 
>reliable way to get two-byte characters to show up reliably cross 
>platform. This is what we did:
>
>- Type the text into a field using Mac OS X's native input methods for 
>Chinese (in this example.)
>- put the htmlText of that field into some container, or into an 
>external file. When you do this, every unicode character is converted 
>to html unicode entities. These seem to be reliably rendered cross 
>platform.
>- When you need to display the text, set the htmlText of the field to 
>the previously-saved htmltext.
>
>Yeah, I know, kludgey but reliable.
>
>Devin
>
>Devin Asay
>Humanities Technology and Research Support Center
>Brigham Young University