ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: embed fonts
Date: Fri, 16 Oct 2009 17:51:38 +0200	[thread overview]
Message-ID: <fe8d59da0910160851s3c5eca9u35b154ad270366ed@mail.gmail.com> (raw)
In-Reply-To: <4AD88F6A.4010400@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1175 bytes --]

On Fri, Oct 16, 2009 at 5:21 PM, Hans Hagen <pragma@wxs.nl> wrote:

> luigi scarso wrote:
>
>>
>>
>> On Fri, Oct 16, 2009 at 3:34 PM, Thomas A. Schmitz <
>> thomas.schmitz@uni-bonn.de <mailto:thomas.schmitz@uni-bonn.de>> wrote:
>>
>>
>>        If they fails,
>>        then we must find a solution .
>>
>>
>>    No, the mkii solution was on the level of the map-files (just use
>>    <<font.pfb instead of <font.pfb, and it will be fully embedded);
>>    that is not applicable to mkiv.
>>
>> so "houston, we have a problem here" .
>> I think we need  Taco , or go tthrough luatex-ref.pdf .
>>
>
>

> it's no problem to provide that feature in mkiv, but i need some real
> string arguments as well as to be sure that i'll never be bothered by side
> effects of fonts not being in a pdf file
>
Fonts not included can sometimes speeds up things when you are coding, but I
never use this feature -- too much dangerous.
I never used full inclusion too, but it's a prepress job (and yes, I have a
prepress office);
there is also ghostscript that does this kind of distiller stuffs.
Full inclusion can be useful, at least to cover the same feature of pdftex.
(my 1cent)

-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 2059 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 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
___________________________________________________________________________________

  reply	other threads:[~2009-10-16 15:51 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-16 12:00 Thomas A. Schmitz
2009-10-16 12:09 ` Hans Hagen
2009-10-16 13:32   ` Thomas A. Schmitz
2009-10-17 10:46   ` Andreas Schneider
2009-10-17 13:26     ` Hans Hagen
2009-10-17 22:48     ` Martin Schröder
2009-10-19 16:10       ` luigi scarso
2009-10-19 17:53         ` Peter Rolf
2009-10-17 22:41   ` Martin Schröder
2009-10-16 12:16 ` luigi scarso
2009-10-16 13:34   ` Thomas A. Schmitz
2009-10-16 15:15     ` luigi scarso
2009-10-16 15:21       ` Hans Hagen
2009-10-16 15:51         ` luigi scarso [this message]
2009-10-16 16:28         ` Arthur Reutenauer
2009-10-16 17:10           ` luigi scarso
2009-10-16 17:17             ` Arthur Reutenauer
2009-10-16 17:24               ` luigi scarso
2009-10-16 18:59         ` William Adams
2009-10-17  8:22           ` R. Bastian
2009-10-17  8:32             ` Taco Hoekwater
2009-10-17  9:05               ` R. Bastian
2009-10-17 10:17                 ` Peter Rolf
2009-10-18  8:38                   ` R. Bastian
2009-10-18  8:40                     ` Taco Hoekwater
2009-10-18  9:05                       ` R. Bastian
2009-10-18  8:44                     ` luigi scarso
2009-10-18 11:16                     ` Hans Hagen
2009-10-18 12:15                       ` R. Bastian
2009-10-18 15:06                         ` R. Bastian
2009-10-18 15:40                           ` Peter Rolf
2009-10-18 17:56                             ` Barry Schwartz
2009-10-18 21:33                           ` Hans Hagen
2009-10-18 20:06                       ` luigi scarso

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=fe8d59da0910160851s3c5eca9u35b154ad270366ed@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).