From: Maurício <briqueabraque@yahoo.com>
To: ntg-context@ntg.nl
Subject: Re: How could a typesetting system be today?
Date: Wed, 11 Jun 2008 21:12:21 -0300 [thread overview]
Message-ID: <g2ppl7$mr7$1@ger.gmane.org> (raw)
In-Reply-To: <g1nv5v$ajm$1@ger.gmane.org>
Sorry to insist, but I would be really interested in approaches
that are not just great things we could add to TeX.
For instance: would it be possible to have some kind of “layout
engine” to which text processing would be just one among other
plug-ins? I wonder what kind of information that engine should
share with plug-ins. Do you think such system is possible? Or
something else?
Maurício
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 0:12 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
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 [this message]
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='g2ppl7$mr7$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).