From: Christopher Creutzig <christopher@creutzig.de>
Subject: Re: Why uses Context 8r encoding used instead of the specified ec encoding?
Date: Thu, 10 Feb 2005 13:56:03 +0100 [thread overview]
Message-ID: <420B59E3.7080608@creutzig.de> (raw)
In-Reply-To: <420A4725.5060307@wxs.nl>
Hans Hagen wrote:
> \def\loadmapline
> {\dodoubleempty\loadmapline}
>
> \def\loadmapline[#1][#2]%
> {\loadallfontmapfiles % ! ! !
> \doloadmapline{#1}{#2}}
I'd be surprised if that worked. The second \def overwrites the first.
Christopher
next prev parent reply other threads:[~2005-02-10 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 19:55 Stefan Wachter
2005-02-09 14:11 ` Taco Hoekwater
2005-02-09 9:27 ` Hans Hagen
2005-02-09 11:54 ` Stefan Wachter
2005-02-09 12:12 ` Hans Hagen
2005-02-09 12:24 ` Thomas A.Schmitz
2005-02-15 8:27 ` Stefan Wachter
2005-02-09 17:23 ` Hans Hagen
2005-02-10 12:56 ` Christopher Creutzig [this message]
2005-02-10 14:02 ` 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=420B59E3.7080608@creutzig.de \
--to=christopher@creutzig.de \
--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).