Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com To: Markus Hoenicka Cc: cygwin AT cygwin DOT com Subject: Re: tetex-beta nitpicking [WAS: Re: no more package moratorium?] References: <007f01c16cde$5016de20$0200a8c0 AT lifelesswks> <20011114124323 DOT C24614 AT cygbert DOT vinschen DOT de> <15348 DOT 5126 DOT 44000 DOT 631380 AT gargle DOT gargle DOT HOWL> Organization: Jan at Appel From: Jan Nieuwenhuizen Date: 15 Nov 2001 20:54:25 +0100 In-Reply-To: <15348.5126.44000.631380@gargle.gargle.HOWL> (Markus Hoenicka's message of "Thu, 15 Nov 2001 19:14:14 +0000") Message-ID: Lines: 62 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Markus Hoenicka writes: > You can't even install MiKTeX unless you run the latest Windows or the > latest Internet Explorer. Strange, we haven't had any complaints. It seemst that MiKTeX installs and runs flawlessly. Note that, of course, MiKTeX is packaged in a tarball and installed through setup.exe. Maybe our Windows users are all using that latest software? > I have instructions about installing a SGML system on Windows which > also uses TeX for the printable output: > > http://ourworld.compuserve.com/homepages/hoenicka_markus/cygbook1.html Thanks, but I don't think that would do. Currently, windows users run setup.exe, and they get a working LilyPond environment. We get lots of questions and complaints if it doesn't work that way. Even if there are simple, step by step, instructions on what to do after running setup.exe. > I provide a very simple shell script (for SGML->PS/PDF > transformations) that takes care of the 'cygpath hell'. It is not > that hard. Yes, we distribute shell scripts too, that cygpath the tex/mf environment settings. But this is all rather ugly. mktextfm and such don't really work, when triggered from the kpathsea lib. > It used to work for MiKTeX and works now for fpTeX and for > Cygwin teTeX (and even for TeX on Unix platforms). Ah, but then you know how difficult it can be to write or debug a texmf.conf, and why you don't want users that haven't ever heard of TeX or environment variables (or tar for that matter) to even have to touch a tex installation? (Unless you live from giving support, perhaps :-) > Did you install the teTeX texmf tree? No, I installed tetex-beta, that's all the tetex that setup.exe will install, right? That's why we still have to distribute and maitain our own, modified setup.exe and repository (apart from the just lifted package moratorium). > Just installing Tetex-beta is not enough, as explained by the > Tetex-beta readme. Yes, I know. That's why we can't use it. Users in general won't read READMEs, let alone they would be able to follow simple instructions :-( The fact that there's a README with instructions, instead of an additional tetex package, for example, tells me that there is some intelligent user-interaction required. Greetings, Jan. -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/