From: Alexander Shopov <ash@contact.bg>
Cc: eliz@gnu.org, anton@lml.bas.bg
Subject: [PATCH]: improving the MIK encoding in GNU emacs
Date: Tue, 09 May 2006 02:11:02 +0300 [thread overview]
Message-ID: <1147129862.3962.20.camel@Stamat.Minka.Localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
Hi guys,
I am sending you a single-line patch improving the support of the
Bulgarian encoding MIK (4 symbols in particular).
Recently I have provided such encoding for GNU libc.
The current state of MIK support in GNU emacs is provided by Anton
Zinoviev - it is based on my previous work on MIK for the unicode editor
Yudit, which was based on Czyborra cyrillic soup.
However during discussions and revealing old sources on the Bulgarian
free software translators' lists we have found that Czyborra's soup
differs somewhat from the real encoding which is more or less based on
cp437 + cyrillic letters.
As I have finished GNU libc, I have sent patches to Yudit's maintainer -
Gasper Sinai, now I am sending a patch to GNU emacs - so that all mik
encoding providers would be in unison.
I believe Anton would agree with the new definition of MIK as it was him
that revealed the sources that led to the redefinition of MIK.
Anyway - I am CCing him as well.
The patch has been produced with the command:
cvs diff -Nau
against up-to-date GNU emacs from CVS HEAD branch as of
08 May 2006 23:05 UTC
Kind regards:
al_shopov
[-- Attachment #2: emacs.mik.patch --]
[-- Type: text/x-patch, Size: 1082 bytes --]
Index: lisp/international/code-pages.el
===================================================================
RCS file: /sources/emacs/emacs/lisp/international/code-pages.el,v
retrieving revision 1.34
diff -u -b -p -a -u -r1.34 code-pages.el
--- lisp/international/code-pages.el 22 Jan 2006 08:26:45 -0000 1.34
+++ lisp/international/code-pages.el 8 May 2006 23:03:19 -0000
@@ -4497,7 +4497,7 @@ Return an updated `non-iso-charset-alist
?Ч ?Ш ?Щ ?Ъ ?Ы ?Ь ?Э ?Ю ?Я ?а ?б ?в ?г ?д ?е ?ж ?з ?и ?й ?к ?л ?м ?н
?о ?п ?р ?с ?т ?у ?ф ?х ?ц ?ч ?ш ?щ ?ъ ?ы ?ь ?э ?ю ?я ?└ ?┴ ?┬ ?├ ?─
?┼ ?╣ ?║ ?╚ ?╔ ?╩ ?╦ ?╠ ?═ ?╬ ?┐ ?░ ?▒ ?▓ ?│ ?┤ ?№ ?§ ?╗ ?╝ ?┘ ?┌ ?█
- ?▄ ?▌ ?▐ ?▀ ?α ?β ?Γ ?π ?Σ ?σ ?μ ?τ ?Φ ?Θ ?Ω ?δ ?∞ ?∅ ?∈ ?∩ ?≡ ?± ?≥
+ ?▄ ?▌ ?▐ ?▀ ?α ?ß ?Γ ?π ?Σ ?σ ?µ ?τ ?Φ ?Θ ?Ω ?δ ?∞ ?φ ?ε ?∩ ?≡ ?± ?≥
?≤ ?⌠ ?⌡ ?÷ ?≈ ?° ?∙ ?· ?√ ?ⁿ ?² ?■ ? ])
(coding-system-put 'mik 'mime-charset nil)
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next reply other threads:[~2006-05-08 23:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 23:11 Alexander Shopov [this message]
2006-05-09 0:51 ` [PATCH]: improving the MIK encoding in GNU emacs Kenichi Handa
2006-05-09 9:47 ` Alexander Shopov
2006-05-18 8:17 ` Anton Zinoviev
2006-05-19 4:29 ` Kenichi Handa
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=1147129862.3962.20.camel@Stamat.Minka.Localdomain \
--to=ash@contact.bg \
--cc=anton@lml.bas.bg \
--cc=eliz@gnu.org \
/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).