From: Anton Zinoviev <anton@lml.bas.bg>
Cc: eliz@gnu.org, Alexander Shopov <ash@contact.bg>, emacs-devel@gnu.org
Subject: Re: [PATCH]: improving the MIK encoding in GNU emacs
Date: Thu, 18 May 2006 11:17:02 +0300 [thread overview]
Message-ID: <20060518081702.GA29314@debian.inet> (raw)
In-Reply-To: <E1FdGRe-0002le-00@etlken>
I'm sorry fo the delayed report - I was on vacation.
On Tue, May 09, 2006 at 09:51:22AM +0900, Kenichi Handa wrote:
>
> > 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.
>
> Thank you. I'll commit it if Anton doesn't oppose it.
Please go ahead. The problem with MIK and the other DOS "codepages"
is that some of the codes in the codepages correspond to several
Unicode symbols. The choice of Microsoft for these symbols is not the
best but it is better to stick with it in order have everywhere only
one definition of MIK.
> By the way, don't we have to update the URL shown in the
> comment?
>
> ;; Suggested by Anton Zinoviev <anton@lml.bas.bg>: Bulgarian DOS
> ;; codepage. Table at
> ;; <URL:http://czyborra.com/charsets/bulgarian-mik.txt.gz>.
Yes this no longer will be true. You can refer to the following
"source":
http://en.wikipedia.org/wiki/MIK_Code_page
Anton Zinoviev
next prev parent reply other threads:[~2006-05-18 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 23:11 [PATCH]: improving the MIK encoding in GNU emacs Alexander Shopov
2006-05-09 0:51 ` Kenichi Handa
2006-05-09 9:47 ` Alexander Shopov
2006-05-18 8:17 ` Anton Zinoviev [this message]
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=20060518081702.GA29314@debian.inet \
--to=anton@lml.bas.bg \
--cc=ash@contact.bg \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).