From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Greek module problem
Date: Sat, 20 Dec 2008 00:43:43 +0100 [thread overview]
Message-ID: <D1E3DC02-E282-4B43-9B39-CD7DDDF7974D@gmail.com> (raw)
In-Reply-To: <6faad9f00812191531q57049f45n5a80ecd7e3779302@mail.gmail.com>
Am 20.12.2008 um 00:31 schrieb Mojca Miklavec:
> On Fri, Dec 19, 2008 at 11:57 PM, Thomas A. Schmitz wrote:
>>
>> Mojca, I'm a bit slow tonight: what's weird about these files?
>
> I have never seen <[ and << in map files before, but most probably
> these are completely legal characters. It's just my ignorance,
> probably nothing with the file, really.
>
> After taking a closer look it seems to be an extention (with very
> weird syntax) to enable otf fonts. One rarely sees support for those
> in pdfTeX. (Even ttf seems to appear weird to TeXies.)
Don't know what <[ is supposed to do but << is necessary to use
OpenType fonts with pdfTeX. Here is the explanation from the pdfTeX
manual.
If the font file name is preceded by a double <<, the font file
will be included entirely — all glyphs of the font are embedded,
including even the ones that are not used in the document. Apart
from causing large size pdf output, this option may cause troubles
with TrueType fonts, so it is normally not recommended for Type1
or TrueType fonts. But this is currently the only mode that allows
the use of OpenType fonts. This mode might also be useful in case
the font is atypical and can not be subsetted well by pdfTX.
Beware: some font vendors forbid full font inclusion.
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-12-19 23:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 19:06 Alan Bowen
2008-12-19 20:17 ` Aditya Mahajan
2008-12-19 20:28 ` Alan Bowen
2008-12-19 21:03 ` Mojca Miklavec
2008-12-19 21:26 ` Alan Bowen
2008-12-19 21:45 ` Mojca Miklavec
2008-12-19 22:57 ` Thomas A. Schmitz
2008-12-19 23:31 ` Mojca Miklavec
2008-12-19 23:43 ` Wolfgang Schuster [this message]
2008-12-20 12:38 ` Thomas A. Schmitz
2008-12-20 12:30 ` Alan Bowen
2008-12-19 21:44 ` Wolfgang Schuster
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=D1E3DC02-E282-4B43-9B39-CD7DDDF7974D@gmail.com \
--to=schuster.wolfgang@googlemail.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).