ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
* InDesign/InCopy vs. TeX and friends
@ 2008-05-31 17:26 Charles P. Schaum
  2008-06-01 14:43 ` Idris Samawi Hamid
  0 siblings, 1 reply; 3+ messages in thread
From: Charles P. Schaum @ 2008-05-31 17:26 UTC (permalink / raw)
  To: ntg-context

I would say that TeX is a way in which a mathematician / theoretical
computer scientist that is well-steeped in music, languages, art,
literature, and other areas might approach the issue. InDesign is the
way in which a large number in the design community might approach the
issue.

I use mainly InCopy because I'm an editor, but I work closely with the
designers. Here's a few things I see that could stand some improvement:

1. What does it mean to have either an overfull hbox or vbox?

You might think, duh! But overfull boxes and copyfitting issues are not
sets of the same cardinality or topology in the problem domain.

First of all, some do make a distinction between intraword and interword
spacing, although this need not necessarily be made. It does become
helpful, however, when setting Sperrdruck and noting the rules for
commas, periods, etc. The soul package in LaTeX does well here, although
if there were essentially two realms, intraword and interword, with
different letterspacing controls for each, this could result in the
following solution:

If (overfull hbox) then
    Apply an algorithm taking into account aesthetic rules for adjusting
intra- and interword spacing within tolerance n and produce a warning
that says either:
          Spacing adjusted to fit copy in hbox on line nnnn
          or
          Copyfit warning for hbox in line nnnn

Similarly, leading (interline spacing) ought to be considered, but
horizontal spacing, especially when pagefitting copy to avoid widows and
orphans, can be tied with interline spacing to get the desired result.
Tweaking the font size is generally a poor solution.

Boxes and glue is good if you are modeling classical typesetting. I
believe that is what DEK was shooting for. In 1978, that made good sense
because electronic means were not well-defined and were sometimes quite
displeasing. For modern digital needs, boxes and glue may not be
appropriate in every situation.

InDesign and InCopy simply pop up a warning when you have copyfitting
issues. Still, there must be a standard approach when a designer fixes
such issues (apart from an editor doing some rewording) in order to give
one's products a good look and feel. Even with InDesign, copyfitting
issues are not a no-brainer.

That's where generating a preview that would step through copyfitting
issues and allow input for heuristics might be helpful.

2. The box or the text frame?

Ever use LaTeX and BibTeX to do a bib and footnotes and all of a sudden
your URLs go right off the line? How annoying is that? The text frame
should have priority over the boxes in it and should trigger copyfitting
rules to enforce that priority unless locally or globally suppressed.

3. Multi-author workflow

InCopy works with InDesign to allow an editor to work with a "story"
that may be in one text frame or spread over multiple frames. It allows
check-out and check-in of a story and locks the story when checked out.

Of course, this implies that the workflow happens off a central server.
Nevertheless, this allows the document to be constructed in parallel
with designers, substantial/copy editors, proofreaders, and so on
working on different parts as needed.

TeX may be batch-oriented, but it is also single-user oriented unless
you have a master with lots of linked input. The problem is that InCopy
and InDesign can show you your work in relation to the whole, giving a
better idea of what you need to do to fit your work in harmony with the
others. TeX cannot do that.

4. TeX is still better at some things.

Kinda like GraphViz, TeX has its area where it just shines. Those
schemata that I was doing are a major pain to do in something else.
TeX's ability to intermix math mode and regular mode is probably unique.
I would bet that one could do things like sentence diagrams and grammar
theory much more easily in TeX than elsewhere.

5. Toward Generalization, but Keep the Good Stuff

It would be neat to sit down with experienced designers or professors of
design and see where DEK's solutions and those built on them work well
for today's expectations and where they do not. Curiously, if you look
at Wikipedia on page design, typography, and other design-related issues
and TeX does not really show up in the external links.

My design books are almost twenty years old. They are:

Collier and Cotton. Basic Desktop Design and Layout
Murphy and Rowe. How to Design Trade Marks and Logos
Devall. Desktop Publishing Styleguide
White. Graphic Design for the Electronic Age
Craig. Designing with Type, 3rd ed.

Still, one can see even there certain relationships of parts to whole
that, in the main, ConTeXt has done better than any other TeX variant to
address. I find the \setuplayout and related general layout, makeup,
sectioning, and other features to be substantially superior to LaTeX,
where the publishers do the styles and the scientists write the content,
or plain, where you have to do everything (not always bad, but Herculean
for a large project).

Charles

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: InDesign/InCopy vs. TeX and friends
  2008-05-31 17:26 InDesign/InCopy vs. TeX and friends Charles P. Schaum
@ 2008-06-01 14:43 ` Idris Samawi Hamid
  2008-06-01 15:28   ` Matthias Weber
  0 siblings, 1 reply; 3+ messages in thread
From: Idris Samawi Hamid @ 2008-06-01 14:43 UTC (permalink / raw)
  To: mailing list for ConTeXt users

Hi Charles,

On Sat, 31 May 2008 11:26:50 -0600, Charles P. Schaum  
<verbo.solo@sbcglobal.net> wrote:

> I would say that TeX is a way in which a mathematician / theoretical
> computer scientist that is well-steeped in music, languages, art,
> literature, and other areas might approach the issue. InDesign is the
> way in which a large number in the design community might approach the
> issue.

Thank you for your very detailed comments. I would like to this and the  
other comments in the "How could a typesetting system be today?" thread  
summarized into a wiki page or even an article. I don't have InDesign so I  
can't test these things directly, but I'd like to cooperate with folks  
here like Charles, Yue, luigi, Henneng and others to create a complete and  
precise comparison contrast between InDesign and luaTeX, with a view  
towards future development challenges.

Best wishes
Idris

-- 
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shi`i Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
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
___________________________________________________________________________________


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: InDesign/InCopy vs. TeX and friends
  2008-06-01 14:43 ` Idris Samawi Hamid
@ 2008-06-01 15:28   ` Matthias Weber
  0 siblings, 0 replies; 3+ messages in thread
From: Matthias Weber @ 2008-06-01 15:28 UTC (permalink / raw)
  To: mailing list for ConTeXt users

One thing that hasn't been emphasized enough in this thread is the  
beneficial effect of TeX for the scientific community,
in particular the mathematical, physical, and chemical sciences. TeX  
has made it possible to easily&freely
prepare and distribute manuscripts. There even is a preprint server  
(www.arxiv.org) that accepts mostly TeX,
giving worldwide access to many papers that would after their  
publication only be available through
expensive journals. I don't know whether anybody has ever estimated  
the costs that all these benefits
would have if one was using alternatives to TeX. It must be in the  
billions of dollars.

Besides the ability of TeX to typeset formulas and its costs,  it is  
its level of standardization that makes it
so useful for scientists: TeX is an extremely well-defined system.
My 15 year old TeX files still `TeX',  despite changing computers and  
operating systems multiple times.
The only drawback for the scientific community is that there is no  
easy way to parse TeX into
Mathematics, i.e. make the formulas one can typeset intelligible to a  
computer algebra system.
This is of course possible now with MathML.

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2008-06-01 15:28 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-05-31 17:26 InDesign/InCopy vs. TeX and friends Charles P. Schaum
2008-06-01 14:43 ` Idris Samawi Hamid
2008-06-01 15:28   ` Matthias Weber

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