From: Hans Hagen <pragma@wxs.nl>
Subject: Re: XeTeX questions
Date: Mon, 22 Jan 2007 00:09:00 +0100 [thread overview]
Message-ID: <45B3F28C.9010607@wxs.nl> (raw)
In-Reply-To: <6faad9f00701210851p3e626e4aya35a57ba438b1129@mail.gmail.com>
Mojca Miklavec wrote:
>
> Hmmm ... you can use OpenType fonts in XeTeX in a plain-TeX-way like that:
> \font\a="[KalligraphiaLTStd]" \a
>
hm, weird syntax
> But there's no high level interface for it yet. The relevant pieces
> are in font-ini.tex:
>
> %D For \XETEX\ we need to support a bit more:
> %D
> %D \starttyping
> %D \definedfont[{cmr10} at 40pt] test
> %D \definedfont['cmss10' at 40pt] test
> %D \definedfont["cmtt10" at 40pt] test
> %D
> %D \definedfont[{cmr10} at 40pt] test
> %D \definedfont['cmss10' at 40pt] test
> %D \definedfont["cmtt10" at 40pt] test
> %D
> %D \definedfont["Gentium" at 40pt] test
> %D \stoptyping
>
> But one would also need \definedfont["[KalligraphiaLTStd]" at 40pt] or
> a similar command (double brackets look ugly anyway) to pass the same
> font name to XeTeX. If some TeXacker knows how to fix the low level
> macros responsible for it ... ;)
>
won't work ... context cannot handle nested [] without much trickery and
i' really dislike that syntax
> I was silently hoping that once that Taco or Hans implement the same
> feature in luatex, one of them would also fix the corresponding macros
> for XeTeX. My knowledge doesn't suffice for it.
>
why are the nested [] needed
(btw, later this year i may come up with an extension to the font
definition macros more suitable for open type; in that case we can
convert to xetex syntax behind the screens)
>
>> 2. When generating the formats, texexec complained about "unknow
>> control sequence" because of lines 25 and 26 in syst-xtx.tex
>>
>> \setcclcuc 201C 201C 201C
>> \setcclcuc 201D 201D 201D
>>
>> I had to comment out these lines to generate the formats (this is
>> with a texlive2007 snapshot of last week and the latest ConTeXt). Is
>> this a known bug?
>>
the enco-utf file is now shared between xetex and luatex in mkii mode;
luatex in mkiv mode does things differently
>
> Change it to \setcclcucx or wait until Hans uploads a new version ;)
>
done, but no upload yet
Hans
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
prev parent reply other threads:[~2007-01-21 23:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 13:37 Thomas A. Schmitz
2007-01-21 14:11 ` Taco Hoekwater
2007-01-21 16:25 ` Thomas A. Schmitz
2007-01-21 17:37 ` Taco Hoekwater
2007-01-21 23:10 ` Hans Hagen
2007-01-23 14:58 ` Taco Hoekwater
2007-01-21 16:51 ` Mojca Miklavec
2007-01-21 17:40 ` Taco Hoekwater
2007-01-21 19:39 ` Mojca Miklavec
2007-01-21 19:52 ` Taco Hoekwater
2007-01-21 23:19 ` Hans Hagen
2007-01-21 17:52 ` Taco Hoekwater
2007-01-21 19:35 ` Thomas A. Schmitz
2007-01-22 9:41 ` Hans Hagen
2007-01-22 9:46 ` Taco Hoekwater
2007-01-22 21:02 ` Thomas A. Schmitz
2007-01-21 23:11 ` Hans Hagen
2007-01-21 18:12 ` Thomas A. Schmitz
2007-01-21 22:59 ` Mojca Miklavec
2007-01-22 21:10 ` Thomas A. Schmitz
2007-01-21 23:17 ` Hans Hagen
2007-01-22 21:11 ` Thomas A. Schmitz
2007-01-21 23:09 ` Hans Hagen [this message]
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=45B3F28C.9010607@wxs.nl \
--to=pragma@wxs.nl \
--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).