From: Hans Hagen <pragma@wxs.nl>
Cc: Jonathan Kew <jonathan_kew@sil.org>
Subject: Re: XeTeX questions
Date: Mon, 22 Jan 2007 00:19:35 +0100 [thread overview]
Message-ID: <45B3F507.5080102@wxs.nl> (raw)
In-Reply-To: <6faad9f00701211139y22c3bf6fu8339aa1b89d6905@mail.gmail.com>
Mojca Miklavec wrote:
> On 1/21/07, Taco Hoekwater wrote:
>> Mojca Miklavec wrote:
>> >
>> > But one would also need \definedfont["[KalligraphiaLTStd]" at 40pt] or
>> > a similar command (double brackets look ugly anyway) to pass the same
>>
>> Have you tried
>>
>> \definedfont[{"[KalligraphiaLTStd]" at 40pt}]
>
> Hmmm ... not until you suggested it ;)
>
> Thanks a lot! (Why on earth haven't I thought about that before?)
because it may work or not, depending on if the argument is passed on to
submacros using [] as delimiter; taco knows such dirty details -)
>
> That basically means that now I can finally try to add a bunch of
> (although ugly, but at least working) definitions to get the OpenType
> version of LM version used by default when launching XeTeX. (I tried
> it already and it seems to work OK, but it has to be completed and
> cleaned a bit first.)
are these [] really needed?
>
> Now I only have to figure out what is happening with map files. There
> were some complaints a few days ago (and at that time it worked OK on
> my computer). Now, when I tried to use OpenType LM, it complains about
> wrong (dvips) map files (my TeXLive installation is not the most
> recent one). But I noticed that there were some dvipdfm map files for
> lm added to TeXLive recently, so I hope that the problem will go away.
>
see taco's mail
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
-----------------------------------------------------------------
next prev parent reply other threads:[~2007-01-21 23:19 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 [this message]
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
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=45B3F507.5080102@wxs.nl \
--to=pragma@wxs.nl \
--cc=jonathan_kew@sil.org \
--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).