From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: MKIV, fonts, confusion
Date: Thu, 14 May 2009 14:49:43 +0300 [thread overview]
Message-ID: <20090514114943.GA5835@khaled-laptop> (raw)
In-Reply-To: <fe8d59da0905140203s4a65aeb8la757e7ace5cc1d74@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1257 bytes --]
On Thu, May 14, 2009 at 11:03:10AM +0200, luigi scarso wrote:
> $>pdffonts felltype.pdf
> name
> type emb sub uni object ID
> ------------------------------------ ----------------- --- --- --- ---------
> PDPWHW+LMRoman12-Regular CID Type 0C yes yes yes 4 0
> DUTOMC+IM_FELL_Double_Pica_PRO_Roman CID Type 0C yes yes yes 5 0
>
> $>pdffonts felltype_oo.pdf
> name type emb sub uni object ID
> ------------------------------------ ----------------- --- --- --- ---------
> FTLUYL+IM_FELL_Double_Pica_PRO_Roman Type 1C yes yes no 8 0
> FTLUYL+IM_FELL_Double_Pica_PRO_Roman Type 1C
>
> So I don't understand how OO "transform" this opentype in a Type1 ,
> and if is it possible to do the same thing in mkiv.
Not only OOo, InDesign does that too, moreover, someone said even if
LuaTeX (XeTeX too) output looked OK in Adobe reader 7, the print isn't
OK.
--
Khaled Hosny
Arabic localiser and member of Arabeyes.org team
Free font developer
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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:[~2009-05-14 11:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 13:18 afsmith
2009-05-13 13:29 ` luigi scarso
2009-05-13 14:36 ` Wolfgang Schuster
2009-05-13 14:48 ` luigi scarso
2009-05-13 15:36 ` Wolfgang Schuster
2009-05-13 15:51 ` luigi scarso
2009-05-13 16:27 ` Wolfgang Schuster
2009-05-14 7:34 ` luigi scarso
2009-05-14 9:11 ` Taco Hoekwater
2009-05-14 9:26 ` luigi scarso
2009-05-14 9:34 ` Taco Hoekwater
2009-05-14 9:48 ` luigi scarso
2009-05-14 9:56 ` Taco Hoekwater
2009-05-14 10:12 ` luigi scarso
2009-05-14 10:39 ` Wolfgang Schuster
2009-05-14 11:21 ` Arthur Reutenauer
2009-05-14 11:38 ` Taco Hoekwater
2009-05-14 11:50 ` Arthur Reutenauer
2009-05-14 23:48 ` luigi scarso
2009-05-15 6:18 ` Wolfgang Schuster
2009-05-14 11:08 ` Arthur Reutenauer
2009-05-14 12:27 ` luigi scarso
2009-05-14 9:03 ` luigi scarso
2009-05-14 11:49 ` Khaled Hosny [this message]
2009-05-14 12:10 ` Arthur Reutenauer
2009-05-13 13:32 ` Hans Hagen
2009-05-13 16:31 ` afsmith
2009-05-13 16:47 ` Hans Hagen
2009-05-13 17:23 ` Wolfgang Schuster
2009-05-13 20:23 ` Aditya Mahajan
2009-05-13 20:31 ` Wolfgang Schuster
2009-05-13 22:12 ` Mohamed Bana
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=20090514114943.GA5835@khaled-laptop \
--to=khaledhosny@eglug.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).