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: How could a typesetting system be today?
Date: Fri, 30 May 2008 21:04:50 +0200	[thread overview]
Message-ID: <F21F41CB-FDE0-4DF0-93F6-A6A9E99598E3@fiee.net> (raw)
In-Reply-To: <op.ubyvqmeznx1yh1@your-b27fb1c401>

Am 2008-05-30 um 14:31 schrieb Idris Samawi Hamid:
>> There is no denying that many advanced features in InDesign are
>> missing in TeX(like) related software. What's more, the
>> internationalization of InDesign is better.
>
> Can you give a precise list of the features contained in InDesign  
> that are
> missing in (lua)TeX or which TeX does not support well?


- much faster (i.e. I don't need to wait for several TeX runs e.g. if  
I need to check if some tweak fixed my page breaking)
- optical (vs. metrical) kerning
- a GUI ;-) and thus layout by "let's try how it looks"
- layout definition (I struggle with ConTeXt's \setuplayout every time)
- better page breaking constraints (you can define in your style  
sheets "keep n lines together" and "keep this together with the next  
paragraph)
- PDF/X output
- color profile conversions
- image processing features like crop paths, feathered edges, drop  
shadow (in ConTeXt I need to prepare such in Photoshop in the right  
size - but I guess it would be possible to write a module that uses  
ImageMagick to achieve something similar)

Problems in TeX *and* InDesign:
- Unicode handling (composed and decomposed UTF-8 with or without BOM,  
UTF-16, different line endings)

Working with InDesign as a developer I know that TeX's documentation  
is far better. Adobe's developer docs (e.g. on API, XML format,  
InDesign tagged text) are incomplete and errorneous.

I don't think you can call the one or other "better" or "more  
advanced", it's just a different approach, and I choose the right tool  
for every project. (I.e. I only use TeX if I need the same content in  
different versions, if I can automate something or for books.) But the  
layout applications like InDesign (there's still also ugly old  
QuarkXPress, coming-of-age Scribus and some others) have learned a lot  
of the former domains of TeX, like registers and toc generation.

There are still some areas where you need a programmable system, even  
trivia like chapter dependant running titles (in ConTeXt: headertexts).


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-05-30 19:04 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30  4:18 Maurí­cio
2008-05-30  5:08 ` Aditya Mahajan
2008-05-30  7:10   ` luigi scarso
2008-05-30  7:12   ` Yue Wang
2008-05-30  9:53     ` Steffen Wolfrum
2008-05-30 10:00     ` Steffen Wolfrum
2008-05-30 12:24       ` Yue Wang
2008-05-30 12:31         ` Idris Samawi Hamid
2008-05-30 19:04           ` Henning Hraban Ramm [this message]
2008-05-31  2:20             ` luigi scarso
2008-05-31 10:18               ` Henning Hraban Ramm
2008-05-31 11:32                 ` luigi scarso
2008-05-31 12:57                   ` Yue Wang
2008-05-31 15:29                     ` luigi scarso
2008-05-31 15:28             ` luigi scarso
2008-05-31 21:23               ` Hans Hagen
2008-06-01 16:58             ` luigi scarso
2008-06-03  0:02               ` the error of xetex Yanli Li
2008-06-03  6:04                 ` Wolfgang Schuster
2008-06-03  7:58                   ` Yanli Li
2008-06-03  8:08                     ` Wolfgang Schuster
2008-06-03 11:58                       ` Yanli Li
2008-06-03 12:34                         ` Wolfgang Schuster
2008-06-03 12:59                           ` Yanli Li
2008-06-03 12:48                         ` Mojca Miklavec
2008-06-03 16:39                           ` Peter Münster
2008-06-03 12:16                       ` Yanli Li
2008-06-03 13:05                         ` Wolfgang Schuster
2008-05-30 14:15         ` How could a typesetting system be today? Steffen Wolfrum
2008-05-30 14:45           ` Alan BRASLAU
2008-05-30  7:37   ` Taco Hoekwater
2008-05-30 11:23     ` Martin Schröder
2008-05-30  7:26 ` Taco Hoekwater
2008-05-30  8:40   ` Yue Wang
2008-05-30 11:07 ` Olivier Guéry
2008-06-12  0:12 ` Maurí­cio
2008-06-12  0:35   ` Idris Samawi Hamid
2008-06-12 18:26     ` Maurí­cio
2008-06-13 17:26       ` Henning Hraban Ramm
2008-06-13 18:32         ` Maurí­cio
2008-06-13 19:45           ` Charles P. Schaum
2008-06-14 16:24         ` Olivier Guéry
2008-06-12  4:27   ` Charles P. Schaum
2008-06-12 17:39     ` How could a typesetting system be today? (slightly off-topic, flame and nostalgic) Maurí­cio
2008-06-12 17:52       ` Hans Hagen
2008-06-12 18:34         ` Aditya Mahajan
2008-06-13 15:41           ` Maurí­cio

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=F21F41CB-FDE0-4DF0-93F6-A6A9E99598E3@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).