From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: XeTeX and OpenType LM
Date: Wed, 31 Jan 2007 12:09:20 +0100 [thread overview]
Message-ID: <45C078E0.8080003@wxs.nl> (raw)
In-Reply-To: <6faad9f00701302044o5172093ay9510e345dc019ce3@mail.gmail.com>
Mojca Miklavec wrote:
> Hello,
>
> Since there are serious problems with XeTeX on non-TeXLive
> distributions anyway: why not mess it up properly this time?
>
>
> The attached file seems to work OK, although kpathsea complains a bit
> (but these are only warnings - no serious problems; perhaps other
> macros could or should be adapted - I didn't dig too much into the
> internals):
>
> kpathsea: Illegal fontname `[lmsans12-regular]': contains '['
> kpathsea: Illegal fontname `[lmsans10-bold]': contains '['
> kpathsea: Illegal fontname `[lmsans12-oblique]': contains '['
> kpathsea: Illegal fontname `[lmtypewriter12-regular]': contains '['
> kpathsea: Illegal fontname `[lmtypewriter10-oblique]': contains '['
>
> Can someone please take a look? I don't know how well this integrates
> with luaTeX. Perhaps the name can be changed from
> \definexetexfontsynonym to \defineotffontsynonym or something similar,
> so that the underlying code can then differ depending on whether it's
> luatex or XeTeX the one which has to access the otf fonts.
>
> If this or a modified version of it makes it into the core, I would
> suggest another (slightly radical) change - to redefine default
> encoding to "uc" instead of "ec" for XeTeX (and luatex) before loading
> the formats. It would be really great if the default XeTeX settings
> would simply work out-of-the-box, contrary to now, when the default
> ec-lmr is nearly useless.
hm, i'm still wondering why xetex needs the extra [] ; is this somewhere documented? is it something new? why not {}
having an extra series of defs for xetex is a bad idea, so i'd rather fix that 'automatically'
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-31 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 4:44 Mojca Miklavec
2007-01-31 11:09 ` Hans Hagen [this message]
2007-01-31 16:58 ` Mojca Miklavec
2007-01-31 17:16 ` Jonathan Kew
2007-01-31 19:12 ` Hans Hagen
2007-02-02 8:26 ` Hans Hagen
2007-02-02 13:23 ` Mojca Miklavec
2007-02-02 13:50 ` Hans Hagen
2007-02-02 15:40 ` Mojca Miklavec
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=45C078E0.8080003@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).