From: "luigi scarso" <luigi.scarso@gmail.com>
Subject: Re: [OT] Is Indesign CS 2 better than ConTeXt ?
Date: Fri, 26 May 2006 12:38:50 +0200 [thread overview]
Message-ID: <fe8d59da0605260338h643b8fd3g9d6bd901d913c3dd@mail.gmail.com> (raw)
In-Reply-To: <4476CFC2.2010901@wxs.nl>
> i always tend to say ... "the problem does not change", so, if figuring out some clever tricks to get something done, then using id or tex makes no difference: one has to figure out the best way
There are a (big) difference: a (my) solution in context costs 100€, a
solutions with IDCS2 cost 10€ , because there are more IDCS2
programmers than TeX programmers.
> concerning id ...
Does IDCS2 offers a better ways to break a paragraph into lines ?
pdfetex has space between words, and hz; it does not consider space
between letters of a word
IDCS2 has 'buttons' (my employer ask me yesterday 'Can you put buttons
on context?''
maybe exa is a way to 'put buttons' on context)
>
> (occassionally we hear stories of failed tryout with 3b2, id, quark, etc while tex base solutions did the job (end kept doing it) for years already; i think that one has to decide for each situation anew)
Another story: I'm using context from 2002 in a production env. for
automatic pricelist and labels. Every job with 'from XML/TXT to PDF'
that I have uses context.
(also: dreams come true)
Why ? Because it's a quick way for us to make a pdf from xml/txt
ready for digital printing.
> tex will always be a niche product
Why ?
But none say a word about Elements of Typographic Style
next prev parent reply other threads:[~2006-05-26 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 11:52 luigi scarso
2006-05-25 15:05 ` Steve Grathwohl
2006-05-25 21:54 ` Henning Hraban Ramm
2006-05-26 9:52 ` Hans Hagen
2006-05-26 10:38 ` luigi scarso [this message]
2006-05-26 11:36 ` Hans Hagen
2006-05-26 13:34 ` luigi scarso
2006-06-30 6:20 ` luigi scarso
2006-06-30 8:05 ` Hans Hagen
2006-06-30 9:21 ` luigi scarso
2006-05-26 11:51 ` Nikolai Weibull
2006-07-01 16:33 ` John R. Culleton
2006-07-01 17:09 ` Idris Samawi Hamid
2006-07-03 7:48 ` luigi scarso
2006-07-03 8: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=fe8d59da0605260338h643b8fd3g9d6bd901d913c3dd@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).