<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea">
    <title>gmane.comp.tex.hevea</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/161"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/160"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/159"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/158"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/157"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/156"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/155"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/154"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/153"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/152"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/151"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/150"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/149"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/148"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/147"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/146"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/145"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/144"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/143"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.tex.hevea/142"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/161">
    <title>Re: [heveau] custom float and autoref support</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/161</link>
    <description>&lt;pre&gt;Hi,

I am quite overwhelmed by work at the moment. Hence the delay.

This should ne rather easy, do you have a package name in mind?
I need to read its documentation.




Hum, looks more involved, since it probably implies altering
hevea sectionning commands (or adding a general hook to them)...

&lt;/pre&gt;</description>
    <dc:creator>luc.maranget&lt; at &gt;inria.fr</dc:creator>
    <dc:date>2011-06-17T15:04:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/160">
    <title>[heveau] custom float and autoref support</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/160</link>
    <description>&lt;pre&gt;Hi,
I'm wondering of custom floats can be supported by hevea.
To generate a custom float for listings it is only necessary to write on
Latex:
  \floatstyle{boxed}
  \newfloat{listings}{thp}{lst}
  \floatname{listings}{Listing}
This seams not to be recognized by hevea.

Also the package hyperref provides \autoref which works like \ref with
the advantage that it does not only provide a reference number.
For example \autoref{sec:tt} generates 'Chapter 3'.
\autoref works with section, chapter and floats.
Would it be possible to add the support for this macro?

Best regards,
Sébastien Fricker 
&lt;/pre&gt;</description>
    <dc:creator>sebastien_fricker</dc:creator>
    <dc:date>2011-06-03T12:05:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/159">
    <title>[heveau] CSS-based translation</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/159</link>
    <description>&lt;pre&gt;Dear Hevea-list,

I have used hevea in the past to experiment with LaTeX-&amp;gt;HTML
conversion, but this time around I am looking at ways to generate
e-book documents from LaTeX. A most promising way seems to be a
combination of hevea and calibre (via the ebook-convert utility):

LaTeX --hevea--&amp;gt; HTML --ebook-convert--&amp;gt; EPUB

This works pretty well right out of the box, except for:

1. xypic images need to be larger (easily fixed with a suitable imagen
incantation)
2. hevea hard-codes colors for \mathcal, \mathsf, etc.
3. Weird stuff happens with some displayed equations, I need to figure it out.

Anyhow, I have one question and one suggestion.

The question: what is the easiest way to prevent hevea from using
color? Should I just redefine \mathcal and \mathsf?

The suggestions: it would be really great if hevea used CSS-based
HTML, so instead of things like &amp;lt;I&amp;gt; &amp;lt;EM&amp;gt; and &amp;lt;FONT color="purple"&amp;gt; we
would use &amp;lt;SPAN CLASS="mathit"&amp;gt; and &amp;lt;SPAN CLASS="mathsf"&amp;gt;. This would
make the output much more flexible, not to mentio&lt;/pre&gt;</description>
    <dc:creator>Andrej Bauer</dc:creator>
    <dc:date>2011-04-27T09:41:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/158">
    <title>[heveau] newcommand with an href link</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/158</link>
    <description>&lt;pre&gt;Hello,

First, let me say all my gratitude towards the developers of Hevea on
this list :-)

Ok, now, I have a problem when I use Hevea, the HTML output gets some of
my links wrong. For instance, I created a command:

\newcommand{\legifciv}[1]{\href{http://www.legifrance.gouv.fr/WAspad/UnArticleDeCode?code=CCIVILL0.rcv&amp;amp;art=#1}{art. #1 c. civ.}}

This allow me to link to a legal text easily (by the way if you know a
better solution to do this, maybe I'm doing something wrong). So for
instance I can write in my text, "Blah blah as \legifciv{1143} is
saying" and in my PDF, it makes a link to
http://www.legifrance.gouv.fr/WAspad/UnArticleDeCode?code=CCIVILL0.rcv&amp;amp;art=1143

However, in the html output made by Hevea, the link gets into,
http://www.legifrance.gouv.fr/WAspad/UnArticleDeCode?code=CCIVILL0.rcv&amp;amp;art=#1


So, did I do wrong with my command? Or is it Hevea that should do
otherwise?

I hope you can have a look at this issue, and I'm sorry if it's already
been reported, I don't really know where to look (yet&lt;/pre&gt;</description>
    <dc:creator>Hugo Roy</dc:creator>
    <dc:date>2011-02-10T19:05:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/157">
    <title>Re: [heveau] Hevea image handling</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/157</link>
    <description>&lt;pre&gt;Hello,

Thanks. I  missed that in the doc. It works smoothly  now using:

\newcommand{\includegraphics}[2][]{\imgsrc[WIDTH=100\%]{#2.pdf}}


Bruno.


On Mon, 22 Nov 2010 10:09:23 +0100, &amp;lt;luc.maranget&amp;lt; at &amp;gt;inria.fr&amp;gt; wrote:



&lt;/pre&gt;</description>
    <dc:creator>Bruno Raffin</dc:creator>
    <dc:date>2010-11-22T11:15:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/156">
    <title>Re: [heveau] Hevea image handling</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/156</link>
    <description>&lt;pre&gt;Hello,

If I get it right, the issue is covered by hevea manual:
Have a look at section 8.2 ``More on included images''
&amp;lt;http://hevea.inria.fr/doc/manual018.html#toc23&amp;gt;

Hope it helps,

--Luc



&lt;/pre&gt;</description>
    <dc:creator>luc.maranget&lt; at &gt;inria.fr</dc:creator>
    <dc:date>2010-11-22T09:09:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/155">
    <title>[heveau] Hevea image handling</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/155</link>
    <description>&lt;pre&gt;Helo,

Starting to use hevea for our documentation (flowvr.sf.net), we are facing an issue with image handling.
Hevea regenerates its own images for figures (through imagen).  It leads to poor quality figures compared to the original images
we have.   Is there a way to  tell  hevea to use the original images ?



Thanks,


Bruno.




&lt;/pre&gt;</description>
    <dc:creator>Bruno Raffin</dc:creator>
    <dc:date>2010-11-22T09:04:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/154">
    <title>Re: [heveau] Re: invoking a command from HeVeA like \write18</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/154</link>
    <description>&lt;pre&gt;On Thu, 14 Oct 2010 16:23:19 +0200
Didier Remy &amp;lt;Didier.Remy&amp;lt; at &amp;gt;inria.fr&amp;gt; wrote:


Yet another option would be provide a plugin ability to Hevea, that is
to use Dynlink abilities to load some extra primitives into hevea
process, by explicit request of program arguments. One would imagine
that Ocaml type system would help the power user to develop somehow
safe hevea plugins.

Regards.

&lt;/pre&gt;</description>
    <dc:creator>Basile Starynkevitch</dc:creator>
    <dc:date>2010-10-14T19:16:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/153">
    <title>Re: [heveau] Re: invoking a command from HeVeA like \write18</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/153</link>
    <description>&lt;pre&gt;
Perhaps, an intermediate options to limit security issues could to pass the
program to call with its options on the command line and bing it to a latex
command of one's choice \myprof that can then be used to evaluate
"\myprog{arg}" to the output produced by the program "myprog" called with
arg in stdin.

         Didier

&lt;/pre&gt;</description>
    <dc:creator>Didier Remy</dc:creator>
    <dc:date>2010-10-14T14:23:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/152">
    <title>[heveau] Re: invoking a command from HeVeA like \write18</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/152</link>
    <description>&lt;pre&gt;
What you want may be  the \&amp;lt; at &amp;gt;exec primitive I do not want to include
in hevea (calling it \write18 is not a good idea
as hevea commands follow a fixed lexing scheme that does not allow
integers in command names).

Basically your code is ok, up to argument fetch, which should probably
be get_prim_arg in place of subst_arg subst lexbuf

Somthing like:

def_code
  "\\&amp;lt; at &amp;gt;exec"
  (fun lexbuf -&amp;gt;
     let com = Scan.get_prim_arg lexbuf in
     ignore (Sys.command com))

(Preferably in package.ml)

Given the potential security problems of the \&amp;lt; at &amp;gt;exec primitive
I will not include it in official hevea releases.

You are free of course to alter hevea sources and recompile them.
The modification is quite minor.

--Luc



I guess I added this and then changed my mind...



&lt;/pre&gt;</description>
    <dc:creator>luc.maranget&lt; at &gt;inria.fr</dc:creator>
    <dc:date>2010-10-14T14:14:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/151">
    <title>[heveau] Re: invoking a command from HeVeA like \write18</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/151</link>
    <description>&lt;pre&gt;

It is not exactly the same, since \write18 (at least in pdflatex, when
suitably enabled) is getting all the TeX &amp;amp; LaTeX rewriting abilities
underneath.

As a concrete example, the texments LaTeX package
http://www.ctan.org/tex-archive/macros/latex/contrib/texments/ is
incoking pygments (a customizable pretty printer/colorizer/beautifier
for 250+ programming languages see http://pygments.org for more) with
things like

 \newcommand{\usestyle}[1]{
 \immediate\write18{pygmentize -S #1 -f latex &amp;gt; \jobname.pyg}
 \input{\jobname.pyg}
 }

My own wish is for writing documentation about some domain specific
language (GCC MELT, http://gcc.gnu.org/wiki/MELT if that matters) and
I really need that the LaTeX input drives some real execution of some
commands.

From what I understand of HeVeA source code, -exec is handled in
parse_opts as the Prog constructor, in turn handled by function
read_prog in hevea.ml. But -exec is handled while parsing the program
arguments to hevea, not while parsing some LaTeX input.

So I don&lt;/pre&gt;</description>
    <dc:creator>Basile Starynkevitch</dc:creator>
    <dc:date>2010-10-14T13:05:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/150">
    <title>[heveau] Re: invoking a command from HeVeA like \write18</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/150</link>
    <description>&lt;pre&gt;Hello,

hevea has the -exec option fro this purpose.
&amp;lt;http://hevea.inria.fr/doc/manual041.html#toc119&amp;gt;

See also
&amp;lt;http://hevea.inria.fr/doc/manual038.html#toc97&amp;gt;

Hope it helps,

--Luc


&lt;/pre&gt;</description>
    <dc:creator>luc.maranget&lt; at &gt;inria.fr</dc:creator>
    <dc:date>2010-10-14T12:42:14</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/149">
    <title>[heveau] invoking a command from HeVeA like \write18</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/149</link>
    <description>&lt;pre&gt;Hello Luc and list

I find the \write18 feature of pdflatex sometimes extremly useful (but
of course it is well known that it can be abused and opens a big
security hole; however careful users can cope with that risk).

Is there any intent of adding such a feature into HeVeA?

As you probably know, the \write18 "primitive" runs a system command,
so you could of course remove all your files with \write18{rm -rf *}
but this is a well known security risk which for honest users (most
people run latex or hevea on document they are writing themselves) is
not that important.

Regards.

&lt;/pre&gt;</description>
    <dc:creator>Basile Starynkevitch</dc:creator>
    <dc:date>2010-10-14T12:30:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/148">
    <title>Re: [heveau] index</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/148</link>
    <description>&lt;pre&gt;Dear Michel,

It would really help me to help you if you provide a precise
account of the problem you encounter.
Ideally, a complete doc.tex file that reveals the problem.

However, I noticed:

1. \usepackage[index] ---&amp;gt; \usepackage{index}

2. On the ?? anchor, you probably need to run hevea several times,
   as instructed by the warning, or, better, give option ``-fix''
   to hevea.

Hope it helps,

--Luc




&lt;/pre&gt;</description>
    <dc:creator>luc.maranget&lt; at &gt;inria.fr</dc:creator>
    <dc:date>2010-10-06T08:12:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/147">
    <title>[heveau] index</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/147</link>
    <description>&lt;pre&gt;1) I have written in my doc.tex
\usepackage[index]
\newindex[thesection]{essai}{adx}{and}{Mon index}
But it seems to me that this index is ignored because later
with the hevea call, I have the message (on \index )
Index structure not found, missing \newindex{essai}

2) Before I have tried the defaut index with
\usepackage[index]
\makeindex
With hevea, the printed index (by \printindex) have an anchor with
"??". Is it possible to have another anchor name ?

    Sincerely yours

&lt;/pre&gt;</description>
    <dc:creator>michel levy</dc:creator>
    <dc:date>2010-10-06T08:03:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/146">
    <title>Re: [heveau] Re: Problems using lstlisting</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/146</link>
    <description>&lt;pre&gt;Dear Kurt,

The problem occurs at parsing of teh declaration
\lstdefinelanguage{sparql} {..

More precisely, if you erase the comment
%basewidth={0.50em,0.6em}
hevea should run without failing.
More generarally you'd better avoid comments inside the arguments
to \lstdefine etc.

Notice that hevea does not implements all listings keys (and you use many).
You may experience further problems. In particular rendering may not be
what you expect.

I advise you to use two sets of listings declarations, one
for latex and one other for hevea.

This can be achieved quite easily by putting the latex declaration
in some file say style.sty and the hevea declarations in another file
style.hva. Then add \usepackage{style} in the preamble of your document.

Doing so, you can adapt declarations for hevea without altering
the latex ones.


Hope it helps,

--Luc



&lt;/pre&gt;</description>
    <dc:creator>luc.maranget&lt; at &gt;inria.fr</dc:creator>
    <dc:date>2010-10-05T09:34:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/145">
    <title>[heveau] Re: Problems using lstlisting</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/145</link>
    <description>&lt;pre&gt;
Hello,

An update on my issue, it seems that if i remove "style=sparql" from
the lstlisting arguments Hevea is quite happy.  Alternatively,  I can
simply remove the lstdefinelanguage and lstdefinestyle directives.
This breaks latex but makes hevea happy.  Either way, I do not get the
syntax highlighting I so painstakingly programmed :)

Forgive me, but here is a dump of my lstdefinelanguage and
lstdefinestyle directives in case something here is an obvious
culprit.

thanks,
Kurt J

\lstdefinelanguage{sparql} {
morekeywords={SELECT, WHERE, DISTINCT, FILTER, ORDER, BY, ASC, REGEX, DSC},
sensitive=true,
morecomment=[l]{\#},
moredelim=[s][\color{ForestGreen}]{?}{\ }, %green variables
moredelim=[s][\color{NavyBlue}\bfseries\fontsize{10}{2}\selectfont]{&amp;lt;}{&amp;gt;},
%red URIs
morestring=[b][\color{ForestGreen}]\", %green strings
morestring=[b]"
}

\lstdefinestyle{sparql}{
language=sparql,
basicstyle=\ttfamily,
keywordstyle=\color{blue}\bfseries,
identifierstyle=,
commentstyle=\color{CadetBlue}\bfseries,
stringstyle=\col&lt;/pre&gt;</description>
    <dc:creator>Kurt J</dc:creator>
    <dc:date>2010-10-02T14:25:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/144">
    <title>[heveau] Problems using lstlisting</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/144</link>
    <description>&lt;pre&gt;Hello,

I've nearly finished my thesis in Latex and I'm hoping to HTMLify it
with Hevea.  I probably should have been doing this "as i went" but I
did not.

According to this:
http://hevea.inria.fr/doc/manual-packages.html#toc113

There is pretty good support for the listings package but I get the
following error:

$ hevea kurtj-thesis.tex
...
Giving up command: \lstlisting
Giving up command: \begin
Giving up command: \input
./content/ch-music-on-web.tex:565: Error while reading LaTeX:
Eof while looking for argument
Adios

I assume we're talking about line 565 which looks like this:

\begin{lstlisting}[float=h!, style=sparql,
  caption={SPARQL query for constructing the Discogs artist-release network},
  label={lst:discogs_sparql}]
SELECT DISTINCT ?release ?artist WHERE
{
?release a mo:Record ;
  foaf:maker ?a, ?b ;
  foaf:maker ?artist .
FILTER ( ?a != ?b ) .
}
\end{lstlisting}

Note I've defined my lstdefinestyle name "sparql".  Is this
problematic??? Do I need to use lstnewenvironment as specified in the&lt;/pre&gt;</description>
    <dc:creator>Kurt J</dc:creator>
    <dc:date>2010-10-01T19:39:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/143">
    <title>Re: [heveau] Hevea to parse selected html tags</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/143</link>
    <description>&lt;pre&gt;Dear  Andre, I doubt you can (easily) achieve what you are aiming at
by writing a .hva file.

I was rather suggesting some file manipulation that ammounts
to extracting the latex formulas, translating them with hevea
and replacing  the &amp;lt;math&amp;gt;...&amp;lt;/math&amp;gt; elements by the produced html, one by one.

As the process is certainly tedious, I was suggesting some automation by
the means of ad-hoc programs, written in ocaml perl etc.

Besides, if you need to display your files André Wobst pointer probably
is a better suggestion than mine.

--Luc


&lt;/pre&gt;</description>
    <dc:creator>luc.maranget&lt; at &gt;inria.fr</dc:creator>
    <dc:date>2010-09-30T07:56:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/142">
    <title>Re: [heveau] Hevea to parse selected html tags</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/142</link>
    <description>&lt;pre&gt;Thanks Andre

I will have a look at it...  





________________________________
From: André Wobst &amp;lt;lists&amp;lt; at &amp;gt;wobsta.de&amp;gt;
To: hevea&amp;lt; at &amp;gt;inria.fr
Sent: Wed, September 29, 2010 4:52:31 PM
Subject: Re: [heveau] Hevea to parse selected html tags

Hi,

Alternatively you may use http://www.mathjax.org/ to display math expressions 
already contained in html files.

André


Am 29.09.2010 um 11:33 schrieb luc.maranget&amp;lt; at &amp;gt;inria.fr:





&lt;/pre&gt;</description>
    <dc:creator>Andry Prima</dc:creator>
    <dc:date>2010-09-29T18:07:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.tex.hevea/141">
    <title>Re: [heveau] Hevea to parse selected html tags</title>
    <link>http://permalink.gmane.org/gmane.comp.tex.hevea/141</link>
    <description>&lt;pre&gt;

Thank you for your reply Luc,

but can it be automated like this... 

Steps:

1. I create a "theoritical hva file" called macro.hva, which contain 
    \newcommand{skiptext} ......  -&amp;gt; i'm not sure how to write it correctly but 
basically this new command will accept any string 

    enclosed by {.. } and print it as-is / or just leave it like it supposed to 
be
2, By using a text editor, I can do simple text replacement
    a. replace &amp;lt;math&amp;gt; with }
    b. replace &amp;lt;/math&amp;gt; with \skiptext{
   
    Then I re-write the input file as follows:


\documentclass{}
\begin{}
\skiptext{
&amp;lt;html&amp;gt;
&amp;lt;ul&amp;gt;
\e^{2}
}
\e^{2}
\skiptext{
&amp;lt;/html&amp;gt;
}
\end{}

3. then I run hevea macro.hva input.tex
4. If my theoritical macro works, then it should be able to show up like this:

&amp;lt;html&amp;gt;
&amp;lt;ul&amp;gt;
\e^{2}
 
e&amp;lt;sup&amp;gt;2&amp;lt;/sup&amp;gt;

&amp;lt;/html&amp;gt;

5. Correct a little bit here and there on the output file.

------------

So... do you think it will work ?
and how to create that kind of macro ?

I just can imagine it would be something l&lt;/pre&gt;</description>
    <dc:creator>Andry Prima</dc:creator>
    <dc:date>2010-09-29T18:03:53</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.tex.hevea">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.tex.hevea</link>
  </textinput>
</rdf:RDF>

