Re: windows-1251 language environment

[Kenichi Handa <handa@m17n.org>]

At first, I have installed a mechanism of auto-loading a
coding system.  As Dave suggested long ago, I added a code
to auto-load a coding system in the function
Fcheck_coding_system.  See the change in code-pages.el which
adds one autoload cookie for iso-8859-11 as an example.

I have not yet tested it fully.  We may have to add GCPROs
in several places.

In article <200310060013.52049.pogonyshev@gmx.net>, Paul Pogonyshev <pogonyshev@gmx.net> writes:
>>  [Not even utf-8?]  That's not the point, though.  You're arguing
>>  essentially for an explosion of language environments crossing the
>>  existing ones with windows-125N &c (not just Cyrillic ones).  We think
>>  that isn't the right way to approach the problem and no-one else seems
>>  likely to work on this.

I agree that we should avoid creating many many predefined
language environments.

> This basically ends the discussion.  However, i don't agree that it's the
> most intuitive interface.

Right.  I think what we need for language environment is a
mechanism similar to face; i.e. creating a new one easily
while allowing inheriting, and customizing an existing one
easily.

> Let's imagine how it happens.  People look at language/coding support and
> see language environment.  They think: "Aha, i set a language environment
> and everything works".  But then they suddenly discover that setting
> "Russian" (or some else) language environment doesn't suffice.  They look
> for another, similar environment, but with different codepage.  And don't
> found it.

For instance, in such a case, we can allow people to create
a new lang. env. by inheriting, for instance, Russian, and
modifying coding-system to windows-1251.

C-h L (describe-language-environment) should also have
these clickable lines:
	You can customize this language environment.
and
	You can create a new language environment that inherits
	this language environment.

---
Ken'ichi HANDA
handa@m17n.org