ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: John McChesney-Young <panis@pacbell.net>
Subject: Re: Footnotes Without Text Marks?
Date: Mon, 12 Jan 2004 07:47:19 -0800	[thread overview]
Message-ID: <p0601020cbc2732ab994b@[192.168.0.4]> (raw)
In-Reply-To: <Pine.LNX.4.44.0401110928020.29905-100000@gaston.free.fr>

Dear Peter,

Thank you very much for your clear and simple response.

You wrote:

>to get correct hyphenation, the accented characters have to be in the font,
>as they are in Latin Modern or EC. In CM the é is a composition of an e and
>the accent.

Now I understand. That makes a great deal of sense.

I followed the installation instructions at:

http://www.uoregon.edu/~koch/texshop/texshop.html

for i-Installer and that included downloading 
(and I assume i-Installer installing) the 
CM-Super fonts. Since the readme says:

http://www.ctan.org/tex-archive/fonts/ps-type1/cm-super/README

"All European and Cyrillic writings are covered," 
would that mean that using CM-Super rather than 
CM would solve the problem? How do I get ConTeXt 
to switch to Super? Or am I missing something 
painfully obvious (as with composite vs. unitary 
symbols)?

The readme also says, "The goal was to provide 
full support for a wide number of fonts used in 
LaTeX," which makes me suspect that I'll either 
have to move files around or somehow convert them 
for use by ConTeXt, but if someone could explain 
exactly how (and your saying that EC seems to be 
difficult to support with ConTeXt makes me think 
this process might not be trivial) I'd appreciate 
it, although if necessary I can just try to 
figure it out from the CM-Super FAQ and readme 
and Installation documents. I expect it would 
improve my character to do so, but I'm not sure I 
want it improved quite that much.

>It's not in the manual, but it seems that \useregime does nothing, it only
>pre-loads a "regime" to make it available for an \enableregime
>command. Since there is already a "\useregime[def,uni,ibm,win,il1,mac]" in
>regi-ini.tex, you'll need an extra \useregime only for other regimes.

Thank you for explaining this as well, and for 
saving me a fruitless search in the manual.

Best,

John
--


*** John McChesney-Young  **  panis@pacbell.net 
**   Berkeley, California, U.S.A.  ***

  reply	other threads:[~2004-01-12 15:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 17:23 footnotes are lost!! endnotes don't work ? (URGENT) Steffen Wolfrum
2004-01-09 18:16 ` Hans Hagen
2004-01-10 17:18   ` Footnotes Without Text Marks? John McChesney-Young
2004-01-11  0:45     ` Adam Lindsay
2004-01-11  1:58       ` John McChesney-Young
2004-01-11  8:50         ` Peter Münster
2004-01-12 15:47           ` John McChesney-Young [this message]
2004-01-11 10:37     ` address labels R. Ermers
2004-01-11 11:20       ` Hans Hagen
2004-01-11 11:55       ` Willi Egger
2004-01-11 14:11         ` R. Ermers
2004-01-13 13:40     ` Footnotes Without Text Marks? Hans Hagen
2004-01-13 21:30       ` John McChesney-Young
2004-01-14  9:35         ` 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='p0601020cbc2732ab994b@[192.168.0.4]' \
    --to=panis@pacbell.net \
    --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).