ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gmx.de>
Cc: ntg-context@ntg.nl, Hans Hagen <pragma@wxs.nl>
Subject: Re: cm-fonts and german umlauts
Date: Wed, 20 Sep 2000 18:40:01 +0200	[thread overview]
Message-ID: <39C8E861.2792208D@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10009200713360.867-100000@erde.kosmos.all>

Hallo Albrecht, hallo Hans, hi all,

> I am typesetting german texts using ConTeXt with the option
> \useencoding[win] and cmr-fonts (\setupbodyfont [cmr]). There is a problem
> with the hypenation after a german umlaut ä,ö or ü, because of the
> 7-bit-encoding of the cmr-font.
> In LaTeX the package ae.sty provides cm-fonts as 8-bit-encoded. Has
> ConTeXt an analogous solution?
Well the ae trick isnot really done by LaTeX, but by creating a virtual
font AE
(T1 encoded).

AE styles does two things:
a) Using the virtual font [ae.sty]
b) (extended version) using EC for characters which are not in CM
   (this results in bitmaps in the PS/PDF files if you haven't bought
    the EC Type 1 fonts) [aecompl.sty]

I think this hasn't be done yet, but (a) seems "rather" trival.

Being not an expert on fonts in ConTeXt this should work:
\definefontsynonym [ComputerModern] [aer10] [encoding=ec]

The problem here is: This doesn't honour the fontsize!

(b) seems might be a little bit more complicated since you need to
support 13 extra characters.

(Hans: looking at enco-ec.tex I miss:
\def\guillemotleft{\@ae@compl{19}}
\def\guillemotright{\@ae@compl{20}}
\def\guilsinglleft{\@ae@compl{14}}
\def\guilsinglright{\@ae@compl{15}}
\def\DJ{\@ae@compl{208}}
\def\dj{\@ae@compl{158}}
\def\DH{\@ae@compl{208}}
\def\dh{\@ae@compl{240}}
\def\@perthousandzero{\@ae@compl{24}} % used in: \%\@perthousandzero
)

(Availables fonts, T1 encoded:
aeb10.vf     aecsc10.vf   aesl10.vf    aessbx10.vf  aeti7.vf
aebx10.vf    aeitt10.vf   aesl12.vf    aessdc10.vf  aeti8.vf
aebx12.vf    aer10.vf     aesl8.vf     aessi10.vf   aeti9.vf
aebx5.vf     aer12.vf     aesl9.vf     aessi12.vf   aett10.vf
aebx6.vf     aer17.vf     aesltt10.vf  aessi17.vf   aett12.vf
aebx7.vf     aer5.vf      aess10.vf    aessi8.vf    aett8.vf
aebx8.vf     aer6.vf      aess12.vf    aessi9.vf    aett9.vf
aebx9.vf     aer7.vf      aess17.vf    aetcsc10.vf  
aebxsl10.vf  aer8.vf      aess8.vf     aeti10.vf    
aebxti10.vf  aer9.vf      aess9.vf     aeti12.vf)


  reply	other threads:[~2000-09-20 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-20  5:34 Albrecht Kauffmann
2000-09-20 16:40 ` Tobias Burnus [this message]
2000-09-21  6:40   ` Hans Hagen

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=39C8E861.2792208D@gmx.de \
    --to=burnus@gmx.de \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).