From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@9fans.net Date: Fri, 14 Mar 2008 06:51:17 +0200 From: lucio@proxima.alt.za In-Reply-To: <9f3897940803131512p25746b70j2c691c300d58c350@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] TeX - Plan 9 model Topicbox-Message-UUID: 793db864-ead3-11e9-9d60-3106f5b1d025 > That might be an interesting case for Plan 9 GCC port - May I also > suggest XeTeX? I didn't check it fully, but it directly uses > TrueType/OpenType fonts. Unfortunately, it outputs only PDF or it's > own internal xdvi format (incompatible with normal dvi). Slighty, but not altogether off topic... The more I look at P9GCC the more concerned I become. It is an enormous vicious circle: for every feature you think you can address, you discover one or more preconditions that require some of your objectives to have already been satisfied. My current line of attack is to use NetBSD as a cross-platform development tool, but even that has its shortcomings: my current stumbling block is the need to use ./configure to construct the BFD library with P9 "aout" as the output format. But then again, I still can't really figure that part of the binutils out, they are so tangled up. A day or two face to face with Ian Lance Taylor or one of the other Cygwin developers may solve a lot of problems, of course. ++L