From: paurea@gsyc.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] latex problem
Date: Fri, 10 May 2002 11:29:11 +0200 [thread overview]
Message-ID: <15579.37607.609713.201601@nanonic.hilbert.space> (raw)
In-Reply-To: <6c7a7a0842d961d2d03249c782dc6943@plan9.bell-labs.com>:Russ Cox's message of 11:13:48 Wednesday,8 May 2002
Russ Cox writes:
> From: "Russ Cox" <rsc@plan9.bell-labs.com>
> Subject: Re: [9fans] latex problem
> Date: Wed, 8 May 2002 11:13:48 -0400
>
> Doesn't directly address your problem, but
>
> http://www.eecs.harvard.edu/~rsc/utftex.c
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...
--
Saludos,
Gorka
"Curiosity sKilled the cat"
next prev parent reply other threads:[~2002-05-10 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 15:13 Russ Cox
2002-05-10 9:29 ` paurea [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 11:37 Russ Cox
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=15579.37607.609713.201601@nanonic.hilbert.space \
--to=paurea@gsyc.escet.urjc.es \
--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).