From: "Hongzheng Wang" <wanghz@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] TeX - Plan 9 model
Date: Fri, 14 Mar 2008 11:22:50 +0800 [thread overview]
Message-ID: <b954b2060803132022r167a1e20y4644f45868fbb09e@mail.gmail.com> (raw)
In-Reply-To: <9f3897940803131512p25746b70j2c691c300d58c350@mail.gmail.com>
It may be difficult. XeTeX needs a fonts management layer to handle
Truetype/Opentype fonts, such as fontconfig in Linux.
I am not sure if there is such a library in Plan9.
On Fri, Mar 14, 2008 at 6:12 AM, Paweł Lasek <pawel.lasek@gmail.com> wrote:
> 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).
>
>
>
> On Wed, Mar 12, 2008 at 7:17 PM, Joel C. Salomon <joelcsalomon@gmail.com> wrote:
> > On Wed, Mar 12, 2008 at 11:02 AM, Jeff Sickel <jas@corpus-callosum.com> wrote:
> >
> > > I'd highly recommend going the pdftex route instead http://www.tug.org/applications/pdftex/)
> >
> > Except the PDF library they're using is written in C++. I found that
> > out when I was looking into porting luatex (which is pdftex with lua
> > scripting so it can support Unicode & OpenType fonts).
> >
> > --Joel
> >
> >
>
>
>
> --
> Paul Lasek
>
>
--
HZ
next prev parent reply other threads:[~2008-03-14 3:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 17:28 lucio
2008-03-11 18:03 ` erik quanstrom
2008-03-11 18:29 ` lucio
2008-03-11 18:58 ` erik quanstrom
2008-03-12 4:40 ` lucio
2008-03-12 11:47 ` Robert Raschke
2008-03-12 12:09 ` lucio
2008-03-12 15:02 ` Jeff Sickel
2008-03-12 16:04 ` Hongzheng Wang
2008-03-12 16:18 ` Russ Cox
2008-03-12 18:17 ` Joel C. Salomon
2008-03-13 22:12 ` Paweł Lasek
2008-03-14 3:22 ` Hongzheng Wang [this message]
2008-03-14 4:51 ` lucio
2008-03-12 10:20 ` lucio
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=b954b2060803132022r167a1e20y4644f45868fbb09e@mail.gmail.com \
--to=wanghz@gmail.com \
--cc=9fans@9fans.net \
/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).