From: Steffen Wolfrum <context@st.estfiles.de>
Subject: re-using ConTeXt typescripts ?
Date: Mon, 11 Jul 2005 17:37:24 +0200 [thread overview]
Message-ID: <a06210200bef839974b46@[213.20.142.130]> (raw)
Hi Adam,
the simplicity of XeTeX's font handling is amazing -- when starting
from scratch.
But I am wondering how can I continue to use the typescripts (and
virtual files) that I used to use with ConTeXt?!
texexec --xtx --example.file
ends in an error log containing:
This is METAFONT, Version 2.71828 (Web2C 7.5.4)
kpathsea: Running mktexmf AGaramond-Regular
! I can't find file `AGaramond-Regular'.
As I do not have *any* idea where to start searching for my mistake
(resp. the place where changes have to be made) I dare to send you a
complete minimal example (that worked with pure texexec --pdf
--example.file)
Any feedback might probably help me...
Thank you,
Steffen
I have an example-file, a typescript-file and a map-file.
The example-file goes like this:
\def\typescriptfiles{type-GMTHKopie.tex}
\usetypescript[AGaramondOldStyle]
\setupbodyfont[normaltype,rm,10.2pt]%klein:10 - mittel:10.2 - gross:10.5pt
\starttext
Test WQ916
\stoptext
The type-GMTHKopie.tex:
\loadmapfile[padKopie.map]
\starttypescript [serif] [agaramond] [ec]
\definefontsynonym [AGaramond-Regular] [padr9e]
[encoding=uc] % was encoding=ec before xetex
\definefontsynonym [AGaramond-Italic] [padri9e] [encoding=uc] % =ec
\definefontsynonym [AGaramond-Bold] [padb9e] [encoding=uc] % =ec
\definefontsynonym [AGaramond-BoldItalic] [padbi9e] [encoding=uc] % =ec
\definefontsynonym [AGaramond-Semibold] [pads9e] [encoding=uc] % =ec
\definefontsynonym [AGaramond-SemiboldItalic] [padsi9e] [encoding=uc] % =ec
\stoptypescript
\starttypescript [serif] [agaramond] [name]
\definefontsynonym [Serif] [AGaramond-Regular]
\definefontsynonym [SerifBold]
[AGaramond-Semibold]%[AGaramond-Bold-OSF]
\definefontsynonym [SemiBold] [AGaramond-Semibold]
\definefontsynonym [SerifItalic] [AGaramond-Italic]
\definefontsynonym [SerifBoldItalic]
[AGaramond-SemiboldItalic]%[AGaramond-BoldItalic-OSF]
\definefontsynonym [SemiBoldItalic] [AGaramond-SemiboldItalic]
\stoptypescript
\starttypescript [serif][allbold][all]
\definefontsynonym [Serif] [SerifBold]
\definefontsynonym [SerifItalic] [SerifBoldItalic]
\stoptypescript
\starttypescript [AGaramondOldStyle]
\definetypeface [normaltype] [rm] [serif] [agaramond]
[default] [encoding=uc] % =ec
\definetypeface [boldtype] [rm] [serif] [agaramond,allbold]
[default] [encoding=uc] % =ec
\stoptypescript
The padKopie.map:
% Adobe Garamond
padr8r AGaramond-Regular "TeXBase1Encoding ReEncodeFont"
<8r.enc <padr8a.pfb
padri8r AGaramond-Italic "TeXBase1Encoding ReEncodeFont"
<8r.enc <padri8a.pfb
pads8r AGaramond-Semibold "TeXBase1Encoding ReEncodeFont"
<8r.enc <pads8a.pfb
padsi8r AGaramond-SemiboldItalic "TeXBase1Encoding ReEncodeFont"
<8r.enc <padsi8a.pfb
padb8r AGaramond-Bold "TeXBase1Encoding ReEncodeFont"
<8r.enc <padb8a.pfb
padbi8r AGaramond-BoldItalic "TeXBase1Encoding ReEncodeFont"
<8r.enc <padbi8a.pfb
next reply other threads:[~2005-07-11 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 15:37 Steffen Wolfrum [this message]
2005-07-11 16:33 ` Adam Lindsay
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='a06210200bef839974b46@[213.20.142.130]' \
--to=context@st.estfiles.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).