From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] latex problem
Date: Fri, 10 May 2002 07:37:32 -0400 [thread overview]
Message-ID: <badcae5e6d8a37c8c466a38951ddd94e@plan9.bell-labs.com> (raw)
> It doesn't have support for acute accents and introduces a space after
> accentuated letters, which it shouldn't :-(. I am fixing it and will send
> a diff when I have some time. Anyway, it would be better to fix the generation
> of the TOC in Latex. I would if I knew from where to start...
both of those derive from the fact that
i wrote it so i could share math-heavy
tex files with non-plan 9 users.
extra spaces don't matter in math mode.
i have little idea how to start looking
at the toc generation. perhaps you could
start by looking at the unicode support that
howard wrote, which appears to work its magic
by setting all the bytes that are valid first
bytes in a multibyte utf-8 sequence to be
escape codes of some form. or so i gather.
i'm very foggy about it. _the latex companion_
probably will tell you how the tocs are
generated.
i am always amazed by people who swear off
troff as too much black magic and turn instead
to latex.
russ
next reply other threads:[~2002-05-10 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 11:37 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-08 15:13 Russ Cox
2002-05-10 9:29 ` paurea
2002-05-07 23:57 paurea
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=badcae5e6d8a37c8c466a38951ddd94e@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).