<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Le 24/10/2010 01:31, ivo welch a écrit :
<blockquote
cite="mid:AANLkTimP0ZZzBcGxqR-VM82TLsJOv9Wr7yvpicKTutKy@mail.gmail.com"
type="cite">
<pre wrap="">won't be me. I am a casual user, though I do donate to various causes.
yes, it would be great if someone wrote a replacement for TeX and
LaTeX, taking the typesetting language and yanking the macro language.
unfortunately, nothing whatsoever seems to be on the horizon. heck,
I would pay good money for an alternative. no such thing exists.
</pre>
</blockquote>
<br>
Try InDesign. It's TeX without the language. Plus it's WYSIWYG. And
you'll pay good money, don't you worry.<br>
Or you might give a look at ANT.<br>
<br>
<blockquote
cite="mid:AANLkTimP0ZZzBcGxqR-VM82TLsJOv9Wr7yvpicKTutKy@mail.gmail.com"
type="cite">
<pre wrap="">TUG has no real power, but it has moral suasion, and it does produce
the de-facto standard through its TeXLive distributions.</pre>
</blockquote>
<br>
Except Windows user mostly go for MikTeX.<br>
<br>
<blockquote
cite="mid:AANLkTimP0ZZzBcGxqR-VM82TLsJOv9Wr7yvpicKTutKy@mail.gmail.com"
type="cite">
<pre wrap=""> if it shows
no leadership, no one else will, either.</pre>
</blockquote>
<br>
So what? It's free software after all...<br>
<br>
<blockquote
cite="mid:AANLkTimP0ZZzBcGxqR-VM82TLsJOv9Wr7yvpicKTutKy@mail.gmail.com"
type="cite">
<pre wrap=""> (yes, luatex may not be
ready, but when it is, making it THE standard would be a step in the
right direction.)
</pre>
</blockquote>
<br>
I think LuaTeX could become the standard engine but I won't force
people. They're free to use whatever engine they prefer. You know
why? Because if some years ago, somebody had said the same about
formats, if TUG had enforced LaTeX as the ``standard'', well, the
TeX world would be much less fun for me today. LaTeX is the <i>de
facto</i> standard, and I find that sufficiently annoying, so I
don't want it to become an official standard either. The same with
engines: I might be a plain TeX user that doesn't want to input
thousands of lines of exotic code to use ttf and otf fonts (the
LuaTeX way), or another plain TeX user that doesn't want fonts to be
unanalyzable entities (the XeTeX way). There are two ways to go, why
reduce them to a single path?<br>
<br>
Best,<br>
Paul<i><br>
</i>
</body>
</html>