From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/261 Path: main.gmane.org!not-for-mail From: Berend de Boer Newsgroups: gmane.comp.tex.context Subject: RE: pdfetex Date: Fri, 20 Nov 1998 09:21:31 +0100 Sender: owner-ntg-context@let.uu.nl Message-ID: <01BE1467.29B446A0.berend@pobox.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035391126 22517 80.91.224.250 (23 Oct 2002 16:38:46 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 16:38:46 +0000 (UTC) Original-To: NTG-CONTEXT Xref: main.gmane.org gmane.comp.tex.context:261 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:261 On Thursday, November 19, 1998 6:36 PM, Hans Hagen [SMTP:pragma@wxs.nl] wrote: > I'm currently making context a bit more etex aware (etex is the > successor to tex). Now etex and pdftex are merged, I foresee that > pdfetex will be *the* tex to use: tex/etex functionality as well as > dvi/pdf output. For me, .pdf output is the only option in a world of Microsoft Word users. dvi output means that users need to have access to .pk/.tfm/... files before they can read my documents. For me, pdf output is the greatest thing since tex. I can now use tex for every document. So I'm greatly interested in the best possible pdf output. If that's etex, well I'm going to use that version. > I'm still not sure to what extend I must support etex's right-left > typesetting, not only typesetting, but also hyper features, color etc. > Any input on this is welcome. I think you must free context as is, only do some bug fixes and in the newer releases only support etex. Supporting both is error prone (for tex users) and I think you will not be able to use all etex features as best as possible. Groetjes, Berend.