unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Anton Zinoviev <anton@lml.bas.bg>
Subject: Cyrillic support
Date: Wed, 27 Feb 2002 13:07:06 +0200	[thread overview]
Message-ID: <20020227130704.B18112@fmi.uni-sofia.bg> (raw)

Hi!

I'd like to work for Emacs project, mostly on the support for the
Cyrillic languages.  I decided to write here in order to avoid
different people working on the same problem.  More precisely, I'd
like to do the following:

1. Input methods for Bashkir, Belarusian, Bulgarian, Kazakh, Kyrgys,
Mongolian and Ukrainian, as well as a generic input method for Asian
Cyrillic languages (there are too many Asian Cyrillic languages and it
is not feasible to make different input method for all of them).

2. Support for CP1251 and PT154.  CP1251 is the default encoding for
GNU/Linux systems in Belarus and Bulgaria.  Now it is only partialy
supported in codepage.el -- the Ukrainian letter ghe with upturn and
many important symbols are not supported.  We need also PT154, because
CP1251 covers only the Slavic languages.  PT154 is encoding that
covers some of the Asian Cyrillic Languages (Mongolian, Kyrgyz,
Kazakh, Bashkir and others).

3. Creating language environments for most important Cyrillic
languages and generic environments for others.

4. Translate TUTORIAL to Bulgarian.

I've read that part of the Lisp sources of Emacs that interests me and
I think I understand how it works.  Actualy I've already done most of
the coding.  I maintain for Debian much Cyrillic-related stuff and
this has given to me contacts with people speaking various Cyrillic
languages.

I will be able to read Emacs mailing lists and bug-reports, but only
for a limited period of time because I have to work for other
projects.  However I will be responsible after that.

My comment on a previous post follows:

On 21 Dec 2001 Dave Love d.love@dl.ac.uk wrote:
>
> I made such an environment, with a properly-defined windows-1251 and
> an additional `bulgarian-pho' input method.  Sorry, I thought I had
> replied previously about that.
> 
> It isn't installed yet.  I have been discussing Cyrillic support with
> Handa-san and may need to ask for opinions from users on what is the
> best way to do some things.  One thing that isn't clear is whether it
> is better to use mule-unicode characters uniformly or to mix them with
> 8859-5, which take half the space in the buffer.

I think it's better to mix mule-unicode with 8859-5.  Thus, the
encodings will be more compatible.  Note that now Emacs has different
input methods for Latin-1, Latin-2, etc.  I'd like to avoid this for
the Cyrillic languages.

Regards, Anton Zinoviev

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


             reply	other threads:[~2002-02-27 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27 11:07 Anton Zinoviev [this message]
2002-02-28  4:08 ` Cyrillic support Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020227130704.B18112@fmi.uni-sofia.bg \
    --to=anton@lml.bas.bg \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).