From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem of space in font names
Date: Sat, 14 Feb 2009 09:02:29 +0100 [thread overview]
Message-ID: <6faad9f00902140002o5513c739w9318358073ff543e@mail.gmail.com> (raw)
In-Reply-To: <49960FCC.10703@wxs.nl>
On Sat, Feb 14, 2009 at 1:26 AM, Hans Hagen wrote:
> Mehdi Omidali wrote:
>>
>> Hi,
>> I have noticed that luatex can not handle fonts with space in their
>> names. I haven't had this problem in the past but now it happens in
>> the latest context minimal both on windows and linux.
>
> spaces are always tricky ... in mkiv just omit the spaces (internally all
> font names are stripped from spaces and special characters and treated
> lowercase), so "Abc Def-GhI" becomes "abcdefghi" anyway
Hello Hans,
I agree that spaces are tricky, but XeTeX does require those spaces
for example\footnote{Yes, yes, I know what you wanted to repy about
XeTeX. I would rename the font as well, but on the other hand being
able to use the same definition for bothe engines is only a benefit.}.
As long as the syntax is clear:
[file:Some Name With Spaces]
this should be accepted in my opinion. If you store font names without
spaces and dashes in database, it might make sense to strip the name
in a similar manner here before trying to access the database and ask
it to give back the font.
Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2009-02-14 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 21:05 Mehdi Omidali
2009-02-14 0:26 ` Hans Hagen
2009-02-14 8:02 ` 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=6faad9f00902140002o5513c739w9318358073ff543e@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).