From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Font embedding
Date: Wed, 29 Feb 2012 12:43:14 +0100 [thread overview]
Message-ID: <CAG5iGsCAL_3i8Ko8Ta-pJTihYaQ4osErH-182chH_D2Hgc_bPQ@mail.gmail.com> (raw)
In-Reply-To: <CAG4oGFRmYtKt7c8Pb4NadBVSK14Wx6OEF9yuUsEC2gPP+xTLCg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 889 bytes --]
On Wed, Feb 29, 2012 at 12:08 PM, Honza Hejzl <honza.hejzl@gmail.com> wrote:
> I am not at linux machine now but can provide those pdfs. (Thanks for your
> recommendation of pdffonts.)
>
> http://dl.dropbox.com/u/4393365/obalka_skand_fi_x1.pdf (Scribus embedded)
>
> http://dl.dropbox.com/u/4393365/navrh_auditorium.pdf (ConTeXt subset)
If you use pdffonts and see something like
XZFSWD-<name>
Embed yes
Subset yes
then the font is embedded and subset (which are the ~99% of situations)
If you see
<name>
Embed yes
Subset no
then the glyphs of the font are completely embedded and this *MUST* be
permitted by the font licence
(there are special flags inside the fonts about this).
Even if the case, it's not the common practice.
I don't have the last scribus at hand, but I will check if it permits the
complete embedding of the font even if the licence says it's not possible.
--
luigi
[-- Attachment #1.2: Type: text/html, Size: 1471 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-02-29 11:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 11:08 Honza Hejzl
2012-02-29 11:43 ` luigi scarso [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-29 7:34 Honza Hejzl
2012-02-29 7:43 ` luigi scarso
2012-03-01 8:59 ` Hans Hagen
2012-02-28 14:39 Honza Hejzl
2012-02-28 14:48 ` Hans Hagen
[not found] ` <CAG4oGFTtx7CptROLoy7=fjdTrrtMpHpyWWdk0c4nWfZfUyUwvA@mail.gmail.com>
2012-02-28 15:13 ` Hans Hagen
[not found] ` <CAG4oGFTQ082S=c4gF4u15TZKv7VMT0m2Unr3rKTT0xnYwQi4dg@mail.gmail.com>
2012-02-28 18:08 ` Honza Hejzl
2012-02-28 20:11 ` Hans Hagen
2012-02-28 20:23 ` Martin Schröder
2012-02-28 22:38 ` Henning Hraban Ramm
2012-02-29 3:36 ` luigi scarso
2012-02-28 15:02 ` Martin Schröder
2012-02-28 17:38 ` Khaled Hosny
2012-02-28 20:22 ` Hans Hagen
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=CAG5iGsCAL_3i8Ko8Ta-pJTihYaQ4osErH-182chH_D2Hgc_bPQ@mail.gmail.com \
--to=luigi.scarso@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).