ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <gip.bilotta@iol.it>
Subject: \enableregime, \setupbodyfont and the amsl module
Date: Tue, 13 Jan 2004 17:15:46 +0100	[thread overview]
Message-ID: <949706400.20040113171546@iol.it> (raw)

Hi Hans and all,

a user on it.comp.software.tex just noticed a funny interaction
between the amsl module and an appropriate choice of fonts and
encodings. The following minimal test file shows the problem:


\setupbodyfont[ber,pos]
\usemodule[nath]
\enableregime[il1]
\starttext
\`e è un'attività
\stoptext 

Notice that accented letters come out like letters with two
commas below.

The amsl module has to resort to this trick:

%D Font Stuff
%D
%D First of all, we need Fraktur to be loaded correctly, something
%D which ConTeXt doesn't do by default (at least by now)
%D Can't find a better, faster, cleaner way to do it;
%D it should probably be added to ConTeXt default for AMS, anyway

\definebodyfont [12pt,11pt,10pt,9pt] [mm] [mc=eufm10 sa 1]
\definebodyfont [8pt,7pt,6pt]        [mm] [mc=eufm7 sa 1]
\definebodyfont [5pt]                [mm] [mc=eufm5]

%D to make sure they get loaded, we make a font change
%D we restore rm afterwards, not having a way to decide which one
%D was active (anyway, rm is a pretty safe bet when loading
%D a module \dots)

\switchtobodyfont[mm]
\switchtobodyfont[rm]


So I *know* where the problem comes form, but I don't know how
to fix this. Can anybody come up with a sensible solution?

-- 
Giuseppe "Oblomov" Bilotta

             reply	other threads:[~2004-01-13 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 16:15 Giuseppe Bilotta [this message]
2004-01-13 16:44 ` Hans Hagen
2004-01-13 23:38   ` Re[2]: " Giuseppe Bilotta

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

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

  git send-email \
    --in-reply-to=949706400.20040113171546@iol.it \
    --to=gip.bilotta@iol.it \
    --cc=ntg-context@ntg.nl \
    /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.
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 NNTP newsgroup(s).