JA> This sounds like you are planning on doing this within the
JA> ISO 2022 framework.
Not really. I'm trying to have a unified set of data structures that
will be useful both for ISO 2022 and for dealing with codepages. I'm
not expecting users of the codepages to use ISO 2022 escape sequences,
but rather to set the initial state at program startup time.
JA> then it would make sense that you would have to map C1 to the 128
JA> character set independently of the mapping of G1 to the same 128
JA> character set.
I haven't decided yet whether I'm going to allow switching C0 and C1.
I've never seen this feature used, and I currently don't.
JA> A code page is a 256 character range not two 128 character sets.
And ISO 8859-1 is a 192 character set, not one 94- and one 96-character
set. But ISO 2022 decided to treat it as such. Kinky.
In the same vein, I've declared CP 1252 to be a 94 character set and a
128 character set. The distinction will never be visible to the user
(unless s/he pervertedly insists on using ISO 2022 escape sequences),
it is just a convenience for the internal structure of the code.
Of course, if escape sequences for CP 1252 are defined (yuck), and
they become popular, then I'm going to have to reconsider. But I'd be
surprised if that were to happen.
Regards,
Juliusz
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
