From: Maurício <briqueabraque@yahoo.com>
To: ntg-context@ntg.nl
Subject: Re: How could a typesetting system be today? (slightly off-topic, flame and nostalgic)
Date: Thu, 12 Jun 2008 14:39:04 -0300 [thread overview]
Message-ID: <g2rmvr$bhd$1@ger.gmane.org> (raw)
In-Reply-To: <1213244846.7440.80.camel@elbereth>
> Do you mean like Scrivener on the Mac?
I don’t know. I tried Context, then TeX, than went back to
Context. Now also Metapost. Sorry for beeing biased, but I really
like the programer approach to computers.
> What, in any case, constitutes a universal layout approach? Does
> one exist? (...)
I don’t think we need something universal. But there is a lot of
common guidelines for most things. For instance, text, music,
chess boards and pictures all have to fit or fill their place in a
page, and all can have a common main font to be used.
> Yet he (...) sees the value of maintaining a knowledge base that
> is predictable when it runs on a program that can pass the trip
> test.
Actually, I’m trying to show my dad he can trust a computer to
typeset his class notes, if we use the right tools (i.e., Context
plus Metapost instead of what was used for his books in the 90’s,
when just a small change would ruin everything). But I’ve just
used ‘ϕ’ in a math formula for one of his papers and Context
silently ignores it. I’m sure there's a good reason for that. But
TeX is predictable when you write a default TeX style document. If
you leave it, you have to understand a lot of hidden issues, and a
dummy user like me will never know if all of them have been taken
care of.
> Lose that for the sake of innovation, and you can lose real
> knowledge. And what shall we say for troff, which still
> possesses an arcane sort of longevity?
Troff? I really miss the days of my old TK3000 text editor back in
the 80’s. It's great to use 80% of your time thinking about what
you want to write and 20% about typesetting. Today it's 4%
writing, 2% typesetting and 94% looking over thousands of pages of
wiki documentation. I still think Context is really great, but
I’ll never try to do something that’s not done in a default
installation again. Or try to understand why sometimes [n=x] works
but [n = x] doesn’t.
> (...) you can be creating documents for all the world to see
> even if you are out in the bush with a generator and mosquito
> netting.
I wrote my résume a few months ago, and sent it to a few
companies, just to know a lot of time later that most of them
could not open it, since it was a PDF revision 1.8 instead of 1.3
(or something like that).
> So TeX's stability has the interesting potential side effect of
> giving a voice to the voiceless. Our cast-off hardware becomes a
> window for freedom of speech and expression, (...)
Sure. I would like to have something simpler than TeX, not more
complex or hardware eater.
> There are places where people still go outside to relieve
> themselves, (...)
Like myself :)
> Some folks think abstractly and can whack out macros like Paul
> Bunyan chops wood. Some think visually (...)
I can only think abstractly. But TeX macros are a lot less
abstract than they could be. I believe DEK says they were never
supposed to be used the way they are.
> DEK (...) brought all his respect and research regarding
> longstanding, tried and true typographical traditions to his
> writing of TeX.
Sure. You can’t miss that even if you understand nothing about
typesetting (like myself). After using TeX for a while, it’s
almost painfull to look at text printed by usual office tools.
>> Maurício a écrit :
>> > Hi,
>> >
>> > Just because I'm curious: how could a typesetting system like TeX
>> > be if it was created today? I've tried google and wikipedia, and
>> > all I found different from TeX is a system called 'Lout', but it
>> > seems dead.
>> >
>> > (...)
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-12 17:39 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 4:18 How could a typesetting system be today? 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
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 ` Maurício [this message]
2008-06-12 17:52 ` How could a typesetting system be today? (slightly off-topic, flame and nostalgic) 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='g2rmvr$bhd$1@ger.gmane.org' \
--to=briqueabraque@yahoo.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).