Multilingual Sample

---

First, type following characters and send with Magellan.

All these characters are of Western European (Latin1).

Received result by Outlook Express

All characters are shown correctly. There is no problem in use of single Western European language. Outlook Express can select character set automatically.

Received result by Netscape Communicator

All characters are received and shown correctly. There is no problem in use of Western European language.

Then, type as following on Magellan and send by Unicode.





Received result on Outlook Express sent by Unicode from Magellan

Some character of Latin is wrong ("i" is changed.) however most of them are shown correctly. As the picture shows, some of Kanji and Hiragana characters are changed. It is because received Unicode message is considered as Chinese or Korean, not as Japanese. If some of characters are shown incorrectly, the e-mail client software does not support Multilingual. Outlook Express is known to have problems in Unicode conversion.

Received result on Netscape communicator sent by Unicode from Magellan

All characters are received and shown correctly. There is no problem in Unicode conversion of Netscape communicator.

Received result on Outlook Express sent by MultiScript from Magellan

If the character set is Japanese (Auto-select), most Japanese part is shown correctly, and Latin part is illegible. If the character set is ISO-8859-1, only Latin characters are shown correctly. As the above description, lingual attribute will not be lost in MultiScript and some times it is more profitable in reuse of text data than sending by Unicode. Notice: Repeated change of character set causes that Japanese cannot be indicated correctly on some version of Outlook Express.

Received result on Netscape Communicator sent by MultiScript from Magellan

If the character set is Japanese (Auto-select), Japanese are shown correctly and Latin characters part will be illegible. If the character set is iso-8859-1, Latin characters part will be shown correctly but the Japanese part will be illegible. As the above description, lingual attribute will not be lost in MultiScript and some times it is more profitable in reuse of text data than sending by Unicode.

If the message is received by Magellan, both Unicode and MultiScript can be shown correctly.

Handling of languages on e-mail

Magellanis able to receive almost all languages on the Internet correctly. If any monolingual message is sent by Magellan, Outlook Express, Netscape Communicator and other e-mail client that can control decoding of languages can receive it correctly. Multilingual message from Magellan to other e-mail client E-mail client that supports Unicode ,such as Outlook Express or Netscape Communicator, can receive multilingual message from Magellan. As for multilingual e-mail, why is other e-mail client Outlook Express or Netscape Communicator? Because Outlook Express and Netscape Communicator is able to indicate various languages discriminating encoding/decoding automatically. Most of other e-mail clients cannot use encoding/decoding well as Outlook Express and Netscape Communicator. Is not Magellan compatible with other e-mail client software in the use of multilingual e-mail? More than talking about compatibility, multilingual e-mail was almost impossible. Magellan has enabled to send multilingual e-mail by MultiScript format first. What is the difference between multilingual e-mail client and multilingual word processor? They are completely different technology. Word processor works on the technology which effects only on its operating system such as World Script, TextEdit, Font Manager, etc and their combinations. On the other hand e-mail have to be handled by sender and receiver correctly even their operating system is different. Additionally, each languages on e-mail are standardized by ISO. E-mail have to keep the rules. In other words, word processor is allowed to conclude in itself, e-mail have to adjust to the partner.