Sorry David,
for disturbance! What I wanted to report does not conflict with yours!
To make things clearer (to other( MacUser)s as well) let me try again:
Otto Scholz asked for testing UTF-8 (etc.) cross platform "inside"
UTF-8 savvy applications and about handling UTF-8 "outside" these
applications: file name handling on/in Desktop/Finder on Mac OS 8.
(2.) Thats why I "mended" the name of the file to be tested to
"[UTF-8 for Japanese GO character].htm" - getting "%E7%A2%81.htm"
in "Netscape: Document Info" window under file/location then.
> >4. Changing desktop font to "Osaka" gives wrong Japanese characters -
> > Mac OS 8 (TEC/MRJ) simulates Unicode using the Language Kit(s) in
> > UTF-8 savvy applications (Netscape/Explorer//Cyberdog: mail only) -
> > i.e. Primary/Secondary Script/Font conflict still with Apple Kits
> > on desktop with file management. Waiting for Allegro to come soon.
(4.) On Mac OS 8 desktop this "mended" file "looks like" a Japanese
named file, but Japanese/Language Kit users don't get fooled using
UTF-8-style file names! "Osaka" will interpret UTF-8-style file names
on/in Desktop/Finder NOT the UTF-8 way - displaying "wrong" characters
on/in Desktop/Finder! But you are absolutely right in stressing:
> It just affects the Finder and Standard File (Open/Save dialogs).
The usual Primary/Secondary Script/Font conflict on Mac OS desktop
being overlapped with another MacEncoding/UTF-8-Encoding conflict.
That's the point I want(ed) to stress - but let me stress too:
> It just affects the Finder and Standard File (Open/Save dialogs).
I don't know "who" invented UTF-8 encoding and in what "environment",
but to a MacUser it looks like imitating Mac Double-Byte font format
for "universal" cross platform performance! It just needs MAC support.
I guess (and hope) upcoming "Allegro" will handle these conflicts!?!
Sorry again for disturbance!
Herbert Elbrecht
elbrecht@csi.com
http://ourworld.compuserve.com/homepages/elbrecht/
"...there is no longer a direct correspondence between the appearance of
Mac OS interface elements and their behavior." MacOS 8 HI Guidelines
------------------------------------------------------------------------
David Goldsmith wrote:
>
> Herbert Elbrecht (elbrecht@csi.com) wrote:
>
> >4. Changing desktop font to "Osaka" gives wrong Japanese characters -
> > Mac OS 8 (TEC/MRJ) simulates Unicode using the Language Kit(s) in
> > UTF-8 savvy applications (Netscape/Explorer//Cyberdog: mail only) -
> > i.e. Primary/Secondary Script/Font conflict still with Apple Kits
> > on desktop with file management. Waiting for Allegro to come soon.
>
> As far as I know, changing the desktop font to Osaka should have no
> effect on the operation of any other component of the system, including
> Language Kits, TEC, MRJ, or Netscape. It just affects the Finder and
> Standard File (Open/Save dialogs). I've never seen this effect. Getting
> the right character depends only on using the correct font and having the
> correct script system installed. I don't know how Netscape's support is
> implemented, so I can't say whether there might not be problems in this
> area.
>
> David Goldsmith
> International and Text Department Architect
> Apple Computer, Inc.
> goldsmith@apple.com
------------------------------------------------------------------------
Herbert Elbrecht wrote:
>
> Otto Stolz asked for testing his favourite: "GO"
>
> Browser | enc | text window | title bar | menus | source
> -------------+-----+-------------+------------+------------+------------
> Netscape | UTF | ok | repl.char. | repl.char. | ok (L-1)
> Version 4.05 | dec | ok | repl.char. | repl.char. | N/A
> on Mac OS 8.1| hex | wrong | not tested | not tested | N/A
> Japanese Kit | HEX | wrong | not tested | not tested | N/A
>
> 0. UTF-8 works with "Macintosh Runtime for Java (2.0)" installed only!
>
> 1. I "mended" last cell of the 1st row of the table with "Copy/Paste"
> using my "utf8site" (UTF-8 code for "GO" looks like "C1 A2 C5" on
> Mac OS platform - so don't get mixed-up entering HEX with Mac OS 8)
>
> 2. And "mending" the "test.htm" title, too - gives "%E7%A2%81.htm" in
> Netscape: Document Info window under file/location! (Again re-mix:
> Latin-1 "E7 A2 81" vs. MacRoman "C1 A2 C5" Western Encoding)
>
> 3. Japanese "GO" displayed in Netscape: Page Source window using UTF-8
> Encoding.
>
> 4. Changing desktop font to "Osaka" gives wrong Japanese characters -
> Mac OS 8 (TEC/MRJ) simulates Unicode using the Language Kit(s) in
> UTF-8 savvy applications (Netscape/Explorer//Cyberdog: mail only) -
> i.e. Primary/Secondary Script/Font conflict still with Apple Kits
> on desktop with file management. Waiting for Allegro to come soon.
>
> (With the "Unicode Standard Version 2.0" book at hand) it is easy to
> locate any character needed in "utf8site". You can "Copy/Paste" then
> all UTF-8 "code" behind characters displayed or not, assigned or not.
> That means you can edit characters you can't display on your machine!
> Click into the cell concerned to make the arrow disappear, then try
> to activate the (replacement-)/character wanted - but not in a hurry,
> otherwise Netscape "Back/Forward" dialog function will overlap and
> you will have to try again! Is this a MAC feature only? Let me know!
> Working in Netscape Composer and wanting to enter Unicode in UTF-8 code
> I would like to look-up "utf8site" for UTF-8 code in Netscape Navigator -
> and enter the found character in UTF-8 code with double click at the
> cursor position within the underlying Netscape Composer document. That's
> the way I am used to with Apple (Japanese) Language Kit - who is ready
> to do this kotoeri-like FEP feature for "utf8site" - this would make
> an overall UTF-8 Editor for all un-/assigned slots!
> A kind of "swiss army knife" for Unicode X.0!
>
> Herbert Elbrecht
> elbrecht@csi.com
> http://ourworld.compuserve.com/homepages/elbrecht/utf8site.htm
>
> P.S.: added "the radical way" page for easy look-up of "Unified Han Area".
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:40 EDT