ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: fonts and typescripts
Date: Mon, 26 May 2008 19:15:54 +0200	[thread overview]
Message-ID: <483AF04A.3080401@wxs.nl> (raw)
In-Reply-To: <1211730426.16006.42.camel@elbereth>

Charles P. Schaum wrote:

> Here's an interesting point: InDesign creates ligatures, but
> irrespective of what is going on in the actual font. So, unless you use
> Unicode Greek, Hebrew, Syriac, Arabic, or whatever, the older style
> fonts that still inhabit the commercial multilingual industry get
> mangled. TeX and friends are smart and don't do that. They can handle
> some complicated typography more robustly than many others.

i'm currently reading a books with is typeset quite ok (in optima) but 
occasionally uses smallcaps with intercharacter spacing which looks ok 
apart form the occasional ligature and indeed fi a b c d liiks kin dof 
strange; it always puzzles me why professional dtp programs don't deal 
with it

anyhow, in context mkiv (luatex version) we will have way more control 
than we have now

> InDesign and InCopy use a version control system where one can "check
> out," "check in," and track changes in a parallel workflow. Grep

how do they deal with non compatible new features; for instance, at 
bachotek i learned that some otf features that are not supported in 
older versions are supported in new ones (or are supported differently); 
is there some compatibility mode (i.e. is the old behavior still present 
and the ID/IC version number stored in the document?)

> searching has also been integrated. It seems to me that if something
> like Scribus had a means to interlink with ConTeXt, cvs / svn or the
> like, and had a means of automatically generating code and previews, you
> would have a typesetting system that could compete feature for feature
> with InDesign and InCopy, and surpass it in some cases.

well, that's the idea -)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-05-26 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-25 15:47 Charles P. Schaum
2008-05-26 17:15 ` Hans Hagen [this message]

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=483AF04A.3080401@wxs.nl \
    --to=pragma@wxs.nl \
    --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).