Quoting Jon Ericson <[EMAIL PROTECTED]>:

> [EMAIL PROTECTED] writes:
> 
> > A fairly straightforward subclassing of Pod::Simple to generate LaTeX 
> > output. It does translate Latin-1 characters to their LaTeX equivalents, 
> 
> If I understand everything correctly, I don't think this is needed.  See:
> http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatenc

Okay, I'll worry about focusing on making the output look a little cleaner, 
or at least come closer to Pod::LaTeX. I just did a *very* elementary 
translation, now that it's released I can worry about polishing the edges. 
And figuring out what goes wrong on one or two .pod files...

> > and I have a full table of Unicode equivalents ready to go into a
> > module 
> 
> I think one of the goals of the Omega project is to support Unicode
> input.  See http://omega.cse.unsw.edu.au:8080/index.html%3Cintro:on%3E

Right, but I wasn't going to assume Omega support. It may be the case that 
Omega is distributed with all new LaTeX distributions, but I wasn't certain 
of that. 

> > once I figure out the Right Thing to do vis-a-vis shifting in and
> > out of math mode.  Escaping every non-ASCII character into math mode
> > won't work correctly, 
> 
> I'm not sure I understand what you are trying to do.  What are you
> using math mode for?  ($~$ looks better in URLS and whatnot than \~ .
> Is that what you're doing?)

That it does, but I was thinking more in the context of a generic module to 
support translating Unicode characters to LaTeX equivalents, and how to 
handle the characters which change labels within math modes, although I 
suppose there should just be one encoding that works both within and outside 
math mode...

> > and it gets even more involved when considering \verbatim sections.
> 
> I would think this would be easier actually.  Just put a verbatim
> paragraph between \begin{verbatim} and \end{verbatim} and it should be
> typeset exactly as entered.

Well, yeah, it is. The problem appears to be that (for example) Latin-1 
high-bit characters aren't rendered properly in the resultant pdf/dvi file 
within \verbatim sections. With any luck the link you proffered has some 
straightforward advice.
--
Jeff 

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

Reply via email to