From: James Cloos <cloos@jhcloos.com>
Subject: Re: Re: Accents in MathML
Date: Sat, 28 May 2005 09:33:34 -0400 [thread overview]
Message-ID: <m3y89z5vbl.fsf@lugabout.cloos.reno.nv.us> (raw)
In-Reply-To: <4295E5D9.3040603@capdm.com> (Duncan Hothersall's message of "Thu, 26 May 2005 16:06:01 +0100")
I gave the original snippit a test.
The mail was in latin1, so I had to convert the file to utf8.
Once I did that texexec and dvips processed it w/o error.
The resulting postscript had the correct accent.
The relevant chunk of the postscript is:
%%Page: 1 1
TeXDict begin 1 0 bop 1738 77 a Fa(1)-9 563 y(Maths)33
b(with)g(accen)m(ts:)1622 773 y(in)m(ter)m(\023)-46 b(es)p
eop end
%%Trailer
Where you can see that the acute (\023) was overlapped
on the suceeding e, rather than using a precomposed é.
This is on a gentoo linux¹ box w/ tetex-3.0.
-JimC
¹ Have to add that now that gentoo has bsd and osx support. :)
--
James H. Cloos, Jr. <cloos@jhcloos.com>
prev parent reply other threads:[~2005-05-28 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050526100002.E69D8127D0@ronja.ntg.nl>
2005-05-26 15:06 ` Duncan Hothersall
2005-05-28 13:33 ` James Cloos [this message]
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=m3y89z5vbl.fsf@lugabout.cloos.reno.nv.us \
--to=cloos@jhcloos.com \
--cc=ntg-context@ntg.nl \
/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).