From: Ognyan Kulev <ogi@fmi.uni-sofia.bg>
Cc: emacs-devel@gnu.org
Subject: Re: TUTORIAL.bg
Date: Wed, 27 Nov 2002 12:40:22 -0200 [thread overview]
Message-ID: <3DE4D956.6090803@fmi.uni-sofia.bg> (raw)
In-Reply-To: Pine.SUN.3.91.1021124074341.13311A-100000@is
Eli Zaretskii wrote:
> However, please note that you must put (codepage-setup "1251") in the
> Local Vars section of the file, otherwise people who don't have their
> defaults set to cp1251 will not be able to read the file correctly
> because codepages are not set up until you explicitly do so.
The reason I asked about cp1251 or windows-1251 is that
emacs/lisp/language/cyrillic.el uses windows-1251 for Bulgarian and
other language environments. (See at the end of the file in CVS HEAD
Emacs.) There are some `(features code-pages)' that I don't understand
well. The standard name is windows-1251[1] so I prefer windows-1251.
I added `eval: (codepage-setup 1251)' before `coding: cp1251' but it
doesn't work the first time. Next time I load TUTORIAL.bg (in the same
Emacs session) it is loaded correctly.
BTW I've signed papers for bulgarian.el and all future changes.
[1] http://www.iana.org/assignments/character-sets
Regards
--
Ognyan Kulev <ogi@fmi.uni-sofia.bg>, "\"Programmer\""
next prev parent reply other threads:[~2002-11-27 14:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 23:29 TUTORIAL.bg and typo in TUTORIAL Ognyan Kulev
2002-11-23 22:56 ` Richard Stallman
2002-11-24 5:48 ` Eli Zaretskii
2002-11-24 22:07 ` Richard Stallman
2002-11-25 6:13 ` Eli Zaretskii
2002-11-26 11:15 ` Richard Stallman
2002-11-26 17:03 ` Eli Zaretskii
2002-11-28 7:25 ` Richard Stallman
2002-11-28 7:54 ` Ognyan Kulev
2002-11-28 17:10 ` Eli Zaretskii
2002-11-30 14:04 ` Richard Stallman
2002-11-17 8:37 ` Ognyan Kulev
2002-11-24 5:46 ` Eli Zaretskii
2002-11-27 14:40 ` Ognyan Kulev [this message]
2002-11-27 14:18 ` TUTORIAL.bg Eli Zaretskii
2002-11-29 15:03 ` TUTORIAL.bg 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=3DE4D956.6090803@fmi.uni-sofia.bg \
--to=ogi@fmi.uni-sofia.bg \
--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).