ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: [OT] Is Indesign CS 2 better than ConTeXt ?
Date: Fri, 26 May 2006 11:52:02 +0200	[thread overview]
Message-ID: <4476CFC2.2010901@wxs.nl> (raw)
In-Reply-To: <E84F9086-CB0C-4C89-8D3B-F7CCE54025B5@fiee.net>

Henning Hraban Ramm wrote:
> Am 2006-05-25 um 13:52 schrieb luigi scarso:
>
>   
>> OK, it is a big OFF TOPIC.
>> Some notes
>> * the Elements of Typographic Style was made with Indesign (true or
>> false?) and the only
>> words about TeX is an url (true or false ?)
>> * indesign eat xml
>> * there is an indesign server; maybe actually too much complex, but in
>> the future?
>> * I don't know if IDCS2 has some programming capabilities like ConTeXt
>> Ofcourse :
>> *IDCS2 come from Adobe, so it has the feature of latest pdf spec.;
>> *IDCS2 is WYSIWYG
>> * (...possibly many others...)
>>
>> But there is one important point:
>> Can IDCS2 be view as candidate for automatic typesetting (xml- 
>>     
>>> IDCS2->pdf)  ?
>>>       
>
> At my former employer, a regional daily newspaper, we used IDCS2 in  
> an automated workflow for simple ads, not even via XML, but  
> controlling ID on a WinXP machine via VB/COM, because we needed a  
> *completely* automated solution.
> I can't tell you much about our application, because my colleague did  
> most of that job (I only delivered the data from another process).
>
> At my actual employer I use ID's XML cpabilities to typeset an event  
> calendar in a city magazine from a database. With a set of well  
> designed style templates the whole thing needs nearly no manual  
> tweaking (only with some ID bugs).
>
> But at the moment I'm planning a simple automated CD cover maker for  
> our backup CDs - using ConTeXt behind a Python GUI...
>   
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

what you use depends on taste; we've had (potential) customers who prefered 3b2 (argument: there's a big company behind it, but in the meantime they were sole twice, and the number of people who can program in (i think their special kind of javascript) interface is also limited; apart from pricing ... 

concerning id ... it's non free, never sure what happens in ten years (adobe dropped pagemaker, (i'm told) messed up frame, so ...) and in order to process older docs will run into compatibility problems some day; supporting pdf trickery is not a real argument, since my experience is that tex is always first in supporting new features; however, adobe is the typesetter company favorite, if only because they use more adobe things (and also because they can keep changing per page which is more proffitable than change for a simple stylesheet once); and ... publishers don't really care about costs anyway so ...) 

(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) 

tex will always be a niche product 

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

  reply	other threads:[~2006-05-26  9:52 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 [this message]
2006-05-26 10:38     ` luigi scarso
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=4476CFC2.2010901@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).