From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: xetext-pdftex differences
Date: Tue, 10 Apr 2007 21:27:47 +0200 [thread overview]
Message-ID: <6faad9f00704101227u1fd43e52wf55050e5cc918374@mail.gmail.com> (raw)
In-Reply-To: <20070408221618732639.581a6a4d@st.estfiles.de>
On 4/8/07, Steffen Wolfrum wrote:
> Hi,
>
> as there are some on this list working/playing with xetex/context:
> Where do I go when I experience differences between context/pdftext and context/xetex?
What do you mean?
> For example with context/xetex I get ...
>
> ! Undefined control sequence.
> \stopframedtext ->\dostopframedtext
Which version of ConTeXt? It works OK here with 2007.03.22, but I need
to try the new beta. In principle this should not happen, it's
probably a bug or some other local problem.
> ... and I do get "SS" instead of eszett ("ß") with the following:
Interesting effect ... (as if the encoding was unknown)
> \usetypescriptfile[type-gyr]
> \usetypescript[times][ec]
This should be
\usetypescript[times][uc]
but in principle it shouldn't work without additional definitions in
typescript files. See below.
> \mainlanguage[de]
> \enableregime[utf]
> \setupbodyfont[times,9pt]
Or, to prevent from an additional source of problems (overloading
times properly):
\definetypeface[times][rm][serif][termes][default][encoding=uc]
\setupbodyfont[times,9pt]
> Hello Thermes! 1234567890 üööäß
>
>
> Whom to tell this?
Mailing list is the perfect place.
OK, so here are some additional definitions (which should probably go
to type-gyre.tex one day):
A complete list of synonyms:
\definetypescriptprefix [n:adventor] [TeXGyreAdventor] % gothic URW Gothic L
\definetypescriptprefix [n:bonum] [TeXGyreBonum] % bookman
URW Bookman L
\definetypescriptprefix [n:chorus] [TeXGyreChorus] % chancery
URW Chancery L
\definetypescriptprefix [n:cursor] [TeXGyreCursor] % curier
Nimbus Mono L
\definetypescriptprefix [n:heros] [TeXGyreHeros] % helvetica
Nimbus Sans L
\definetypescriptprefix [n:pagella] [TeXGyrePagella] % palatino
URW Palladio L
\definetypescriptprefix [n:schola] [TeXGyreSchola] % schoolbook
Century Schoolbook L
\definetypescriptprefix [n:termes] [TeXGyreTermes] % times
Nimbus Roman No9 L
\definetypescriptprefix [f:adventor] [ag]
\definetypescriptprefix [f:bonum] [bk]
\definetypescriptprefix [f:chorus] [zc]
\definetypescriptprefix [f:cursor] [cr]
\definetypescriptprefix [f:heros] [hv]
\definetypescriptprefix [f:pagella] [pl]
\definetypescriptprefix [f:schola] [cs]
\definetypescriptprefix [f:termes] [tm]
Then you need definitions for uc encoding:
\starttypescript [serif] [adventor,bonum,heros,pagella,schola,termes] [uc]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-Regular]
[file:texgyre\typescripttwo-regular] [encoding=\typescriptthree]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-Italic]
[file:texgyre\typescripttwo-italic] [encoding=\typescriptthree]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-Bold]
[file:texgyre\typescripttwo-bold] [encoding=\typescriptthree]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-BoldItalic]
[file:texgyre\typescripttwo-bolditalic] [encoding=\typescriptthree]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-Caps]
[\typescriptprefix{n:\typescripttwo}-Regular]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-ItalicCaps]
[\typescriptprefix{n:\typescripttwo}-Italic]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-BoldCaps]
[\typescriptprefix{n:\typescripttwo}-Bold]
\definefontsynonym
[\typescriptprefix{n:\typescripttwo}-BoldItalicCaps]
[\typescriptprefix{n:\typescripttwo}-BoldItalic]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-Slanted]
[\typescriptprefix{n:\typescripttwo}-Italic]
\definefontsynonym [\typescriptprefix{n:\typescripttwo}-BoldSlanted]
[\typescriptprefix{n:\typescripttwo}-BoldItalic]
\stoptypescript
% definitions for SmallCaps are wrong, since they're a feature in OT
fonts and that is a bit broken (or at least not stable enough) at the
moment.
And you also need the following:
% ec,texnansi,cs,el,qx,rm,t5,t2a,t2b,t2c,l7x
\starttypescript [serif] [times] [uc]
\definefontsynonym [Times-Roman] [TeXGyreTermes-Regular]
[encoding=\typescriptthree]
\definefontsynonym [Times-Italic] [TeXGyreTermes-Italic]
[encoding=\typescriptthree]
\definefontsynonym [Times-Bold] [TeXGyreTermes-Bold]
[encoding=\typescriptthree]
\definefontsynonym [Times-BoldItalic] [TeXGyreTermes-BoldItalic]
[encoding=\typescriptthree]
\definefontsynonym [Times-Caps] [TeXGyreTermes-Caps]
[encoding=\typescriptthree]
\definefontsynonym [Times-Slanted] [Times-Italic]
\definefontsynonym [Times-BoldSlanted] [Times-BoldItalic]
\stoptypescript
Something strange is happening though. If you load these definitions
with XeTeX, it works OK. If one loads them with pdfTeX, it doesn't
work, since TeXGyreTermes-Regular isn't defined. When I think a bit, I
understand why it's not defined (because it's part of "termes" family,
not part of "times" family), but I don't understand why these
definitions work in XeTeX then.
Of course one could also say
\definefontsynonym [Times-Roman] [file:texgyretermes-regular] [encoding=uc]
but there should be a better way than to define the same font twice.
Is there any nice way to make "times" aware of "TeXGyreTermes-*" font names?
At the beginning I had problems with XeTeX as well since Times
resolved to 'Times Roman:mapping=tex-text', which resolved to the name
'mapping=tex-text' (a side effect of recent that should probably be
fixed somehow in the near future), but that problem disappeared later.
I had to temporary fix this (leftovers before TeXGyre family managed
to overload everything perhaps?):
\starttypescript[serif][times][uc]
\definefontsynonym[Times-Roman] [Times Roman] [encoding=uc]
\definefontsynonym[Times-Italic] [Times Italic] [encoding=uc]
\definefontsynonym[Times-Bold] [Times Bold] [encoding=uc]
\definefontsynonym[Times-BoldItalic][Times Bold Italic][encoding=uc]
\stoptypescript
Mojca
next prev parent reply other threads:[~2007-04-10 19:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 20:16 Steffen Wolfrum
2007-04-10 19:27 ` Mojca Miklavec [this message]
2007-04-11 9:09 ` Steffen Wolfrum
2007-04-11 15:44 ` Mojca Miklavec
2007-04-11 17:22 ` Hans Hagen
2007-04-12 7:37 ` Steffen Wolfrum
2007-04-12 10:41 ` Hans Hagen
2007-04-12 7:53 ` Steffen Wolfrum
2007-04-12 10:46 ` Hans Hagen
2007-04-12 13:53 ` Steffen Wolfrum
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=6faad9f00704101227u1fd43e52wf55050e5cc918374@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--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).