ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Missing greeks characters in texgyreheros
Date: Wed, 30 Apr 2008 21:22:03 +0200	[thread overview]
Message-ID: <2F66D480-AEDD-4A64-9D4E-1C089F5F1023@fiee.net> (raw)
In-Reply-To: <fe8d59da0804301022h2f1af4c0r7492b5efb8a995ca@mail.gmail.com>

Am 2008-04-30 um 19:22 schrieb luigi scarso:
> Ah yes, at my printing company
> 1) pfb/pfa : "good" fonts  (&  not "easy"  to install in luatex )
> 2) otf : "good" fonts  (& "easy" to install )
> 3) ttf : "bad" fonts  (& "easy " to install )
>
> Of course it's not exactly true (but maybe on average):
> a mental habitat, I must admit it, based on experience.
> Also, an helvetica like typeface is a must.

In the old times some PS Level2 RIPs couldn't handle Truetype fonts.  
And most bad fonts are Truetype.
But in fact the format tells nothing about quality or printability.

OpenType fonts can contain Truetype-based outlines as well as  
PostScript-based (quadratic vs. cubic curves). Usually .otf files  
contain PostScript-based outlines, while .ttf can mean "old" Truetype  
as well as TrueType-based OpenType. I.e. the TrueType format can  
encode its slots in Unicode (obligatory for OpenType) or in any other  
encoding.

>>  I have just uploaded a new version to the garden.
> good. Greek is really difficult for me
Yes, it's Greek to everyone ;-)


Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2008-04-30 19:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30  9:37 luigi scarso
2008-04-30  9:51 ` Thomas A. Schmitz
2008-04-30 10:06   ` luigi scarso
2008-04-30 10:13     ` Wolfgang Schuster
2008-04-30 10:25       ` luigi scarso
2008-04-30 10:52         ` Wolfgang Schuster
2008-04-30 12:49           ` Henning Hraban Ramm
2008-04-30 10:32     ` Thomas A. Schmitz
2008-04-30 10:47       ` luigi scarso
2008-04-30 12:29         ` Thomas A. Schmitz
2008-04-30 12:34           ` Wolfgang Schuster
2008-04-30 17:22           ` luigi scarso
2008-04-30 19:22             ` Henning Hraban Ramm [this message]
2008-04-30 10:34   ` Thomas A. Schmitz

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=2F66D480-AEDD-4A64-9D4E-1C089F5F1023@fiee.net \
    --to=hraban@fiee.net \
    --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).