Re: [Bug-teseq] codesets are not shown

[Bruno Haible]

Micah Cowan wrote:
> I was hoping, though, to leave intact the simpler names ("Spanish", etc)
> to make it crystal clear to whoever reads it, what language the
> character set had been intended for (where this is known). But I can add
> these back in later.

Yes, I can easily imagine that every entry in iso_ir_names be followed by
a description of the encoding in parentheses. E.g.

  /* 025 */ "ISO646-FR1", /* = "NF_Z_62-010_1973" */
becomes
  /* 025 */ "ISO646-FR1 (original French variant of ISO 646; aliases: 
NF_Z_62-010_1973)",

> What I meant was that a user who puts Japanese text through Teseq will
> have very good reason to expect that the multibyte charset being
> switched to is most likely Japanese. :)

Not necessarily: ISO-2022-JP-2 also contains Chinese, Korean, and Greek
character sets.

Bruno