[<<Previous Entry]
[^^Up^^]
[Next Entry>>]
[Menu]
[About The Guide]
C H A R A C T E R T R A N S L A T I O N
GoldED implements several different proposals for character
translation in imported and exported messages:
FSC-0050 "Charset Identifier" Thomas Sundblom 2:201/114
FSC-0051 "I51" Thomas Gradin 2:200/108
FSC-0054 "CHARSET proposal" Duncan McNutt 2:243/100
No FSC "Composed Characters" Andre van de Wijdeven 2:500/131
FSC-0050 is currently implemented in the OPMED 3.00 message
editor, and will be implemented in Opus 1.20. It uses the same
identifier as FSC-0054 (a ^aCHARSET kludge), but is a lot simpler
(but not nescessarily better).
The "I51" and "CHARSET" proposals are in the process of being
merged to one proposal, which will combine the advantages of both.
They are both based on using the LATIN-1 (also known as ISO
8859-1) character set for extended ASCII. The LATIN-1 set is the
set used by Windows 3, Amiga and many other non-PC computers. In
addition to LATIN-1, I51 defines a set of escape sequences for
characters not found in the LATIN-1 set.
Composed Characters has become quite popular in Holland, but the
author has decided to drop his proposal because it relies on
escape sequences using the so called "soft-cr" (141d, 8Dh)
character. GoldED will continue to support Composed as long as it
seems nescessary.
If you want to know more about the details, I suggest you read the
proposals or contact the authors.
GoldED currently(*) uses two types of translation tables:
(*) = NOTHING IS FINAL YET. The implementation is still on the
testing stage, and later versions of GoldED will PROBABLY use
different formats for these tables. So don't spend a lot of
time reworking the tables - leave them as they are.
This page created by ng2html v1.05, the Norton guide to HTML conversion utility.
Written by Dave Pearson