From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: emacs-devel@gnu.org
Subject: Re: auto-coding-function for LaTeX
Date: Fri, 12 Nov 2004 21:51:09 +0100 [thread overview]
Message-ID: <v9654aokoy.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: 87lld7sh07.fsf@seamus.arnested.dk
On Fri, Nov 12 2004, Arne Jørgensen wrote:
> None of the coding systems you added are present in my Emacs. So why
> add them? To make it easier for a user to customized when/if they are
> added? Or are they present in your Emacs?
All mentioned cp* codings are available, but not by default, see `M-x
codepage-setup RET TAB TAB'. I don't know if there is some mechanism
in Emacs call `codepage-setup' automatically.
I'm not sure about the cp437 vs. cp437de issue (β = \beta vs. ß = \ss
= S SHARP). Maybe this is good enough, see [1]. It seems that both,
`code-pages.el' and `codepage.el', use S SHARP.
> The re-search-forward searches until position 1000. Should that
> number be customizable? The functions in `auto-coding-alist' get an
> argument of 249 for number of positions to search, but I think that
> is not enough for LaTeX files.
Yes, a limit of 249 surely is not enough for typical LaTeX files.
Maybe the search could stop either at a certain number or when
"\begin{document}" was found. It should also be checked that the
"inputenc cookie" isn't a LaTeX comment.
If your code cannot be integrated in Emacs, I would propose to add it
to AUCTeX.
Bye, Reiner.
[1] See e.g. this article by Markus Kuhn in a German newsgroup:
,----[ Translation of the most relevant part: ]
| Microsoft Code Page 437 officially contains LATIN SMALL LETTER SHARP
| S on position 0xE1 (though the designers of IBM CGA card ROM's
| apparently thought more of a beta at that time (~1979)). Many
| conversation programs ([...]) map both s sharp (U+00DF) and beta
| (U+03B2) to 0xE1 in CP437. Hopefully GNU iconv starting from glibc
| 2.2 will get this right.
`----
,----[ Original article: ]
| From: mgk25@cl.cam.ac.uk (Markus Kuhn)
| Subject: Re: recode latin1:cp437 und 'ß'
| Newsgroups: de.comp.os.unix.apps, de.comp.standards
| Date: 2000/04/22
| Message-ID: <8ds839$anv$1@pegasus.csx.cam.ac.uk>
|
| >> Georg Schwarz <schwarz@physik.tu-berlin.de> wrote:
| >>
| >> > Wenn ich Text auf einem Epson Stylus 800+ direkt drucke, schiebt der
| >> > Druckertreiber ihn zunächst durch recode latin1:cp437 (GNU recode
| >> > 3.4.1). Allerdings wird ein 'ß' nicht korrekt ausgegeben. Ich denke daß
| >> > code page 437 gar kein ß enthält.
|
| Microsoft Code Page 437 enthält offiziell LATIN SMALL LETTER SHARP S auf
| position 0xE1 (auch wenn die Designer des IBM CGA-Karten ROM's
| offensichtlich damals (~1979) eher wohl an ein beta gedacht haben).
| Sehr gute Konvertierprogramme (und dazu darf man GNU recode 3.5 wegen
| der vielen Fehler in den zudem nur injektiven Tabellen leider
| noch nicht zaehlen!) mappen sowohl das scharfe s (U+00DF) als auch as
| kleine beta (U+03B2) auf 0xE1 in CP437. GNU iconv wird das hoffentlich
| ab glibc 2.2 entlich richtig hinkriegen.
| [...]
| Quellen:
|
| ftp://ftp.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/PC/CP437.TXT
| ftp://ftp.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/PC/CP850.TXT
`----
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-11-12 20:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 20:41 auto-coding-function for LaTeX Arne Jørgensen
2004-11-11 12:59 ` Bug in widget-complete (was: auto-coding-function for LaTeX) Arne Jørgensen
2004-11-11 21:59 ` auto-coding-function for LaTeX Juri Linkov
2004-11-11 22:50 ` Arne Jørgensen
2004-11-11 23:56 ` Arne Jørgensen
2004-11-12 1:12 ` Reiner Steib
2004-11-12 6:44 ` Arne Jørgensen
2004-11-12 20:51 ` Reiner Steib [this message]
2004-11-12 21:07 ` Reiner Steib
2004-11-13 14:14 ` Juri Linkov
2004-11-13 14:47 ` David Kastrup
2004-11-13 16:38 ` Richard Stallman
2004-12-07 0:53 ` Arne Jørgensen
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=v9654aokoy.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--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).