From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Cc: Adam Lindsay <atl@comp.lancs.ac.uk>
Subject: Re: strange behaviour of \definedfont['Some Name'] in XeTeX
Date: Wed, 13 Dec 2006 12:56:19 +0100 [thread overview]
Message-ID: <6faad9f00612130356y55311985x683c593c0307cad4@mail.gmail.com> (raw)
In-Reply-To: <457EE4B3.5040806@wxs.nl>
On 12/12/06, Hans Hagen wrote:
> Mojca Miklavec wrote:
> > Hello,
> >
> > I'm probaby misusing the feature (most robably because I just didn't
> > take time to study how to do it properly), but it behaves really
> > strange.
> >
> > In XeTeX I first did
> >
> > \font\f='Some Name' \f
> >
> > which worked OK. But when I tried the same with
> > \definedfont['Some Name']
> > it resulted in strange behaviour. For some fonts, metapost has been
> > invoked and complained, but the resulting document had the proper font
> > plus "scaled 1000" written on the first page where the font has been
> > selected. For other fonts it failed completely.
> >
> > What's actually the most clean way of including an "uc-encoded" font
> > at a specific font size, but without the need of bold or any other
> > "typefaces" (just for a title for example)? (Which basically means: I
> > only want the same behaviour as the plain TeX expression above + uc
> > encoding.)
> >
> hm, that's Adam Lindsay's teritory; does "bla" work? (double quotes)
No, I tried that as well. As far as I remember this code used to work
already, but I might be wrong.
Mojca
prev parent reply other threads:[~2006-12-13 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 16:39 Mojca Miklavec
2006-12-12 17:19 ` Hans Hagen
2006-12-13 11:56 ` Mojca Miklavec [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=6faad9f00612130356y55311985x683c593c0307cad4@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--cc=atl@comp.lancs.ac.uk \
--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).