Re: [l2h] converting quotes
On Sat, 9 Aug 2003, James Howison wrote:
Hi all,
I'd really like to convert the latex quotation marks, `` and '' to the
recommended HTML curly quotes, #8220 instead of `` and #8221 instead
of '' - standard codes that render the curly quotes beautifully.
set
$USE_CURLY_QUOTES =1;
in an initialisation file.
This is not the default, because not all browsers actually render
these characters. (At least, that was the situation 3-4 years ago when
the LaTex2HTML coding was written.)
Hope this helps,
Ross Moore
I'm sure that this is possible through latex2html - the codes are
listed around unicode.pl:722 - but either I can't find the magic
incantation to have latex2html do the conversion or there is a bug
preventing this from working in my version (1.70) or set-up.
I've tried:
latex2html -html_version 4.0,unicode test.tex
What is strange is that this does work for, say \v{Z} which converts to
the code #381; (and that is definitely happening through unicode.pl (I
changed the translation and it worked fine).
So why doesn't the translation for `` (which is correctly listed in the
unicode.pl as \`\`) and '' which is correctly listed as \'\' work?
I've had a good hunt around for this - but I can't see why the other
codes are converted but not the quotes.
Cheers,
James
ps. minimal test.tex follows
--
\documentclass[11pt]{article}
\begin{document}
``Why are these quotes not converted to unicode'' (they are in the
unicode.pl file)
While this symbol (also in the unicode.pl file) is? - \v{Z}
\end{document}
___
latex2html mailing list
[EMAIL PROTECTED]
http://tug.org/mailman/listinfo/latex2html
___
latex2html mailing list
[EMAIL PROTECTED]
http://tug.org/mailman/listinfo/latex2html
Re: [l2h] converting quotes
On Saturday, August 9, 2003, at 02:53 am, Ross Moore wrote:
On Sat, 9 Aug 2003, James Howison wrote:
Hi all,
I'd really like to convert the latex quotation marks, `` and '' to the
recommended HTML curly quotes, #8220 instead of `` and #8221 instead
of '' - standard codes that render the curly quotes beautifully.
set
$USE_CURLY_QUOTES =1;
in an initialisation file.
That's great Ross - it works fine. I'm a little concerned that I found
this so hard to find in the documentation or indeed online. In fact
this phrase is kindof a googlewhack - a word that only is indexed in
google once (and unfortunately I didn't find it because the email
writer had miss-spelled quotation!).
That won't be true after these emails are indexed though ;) Is there
perhaps a more complete list of environment variables in the works?
http://www.google.com/search?q=$USE_CURLY_QUOTESie=UTF-8oe=UTF-8
Anyvay - I'm glad that this works - thanks a million.
This is not the default, because not all browsers actually render
these characters. (At least, that was the situation 3-4 years ago when
the LaTex2HTML coding was written.)
As you point out that was indeed true - but the times are a-changing ;)
It would be great to make stuff like this more visible - obviously
without forcing it on anyone. This guy seems to have done good
research into the best way to handle this:
http://www.dwheeler.com/essays/quotes-in-html.html
Cheers
James
Hope this helps,
Ross Moore
I'm sure that this is possible through latex2html - the codes are
listed around unicode.pl:722 - but either I can't find the magic
incantation to have latex2html do the conversion or there is a bug
preventing this from working in my version (1.70) or set-up.
I've tried:
latex2html -html_version 4.0,unicode test.tex
What is strange is that this does work for, say \v{Z} which converts
to
the code #381; (and that is definitely happening through unicode.pl
(I
changed the translation and it worked fine).
So why doesn't the translation for `` (which is correctly listed in
the
unicode.pl as \`\`) and '' which is correctly listed as \'\' work?
I've had a good hunt around for this - but I can't see why the other
codes are converted but not the quotes.
Cheers,
James
ps. minimal test.tex follows
--
\documentclass[11pt]{article}
\begin{document}
``Why are these quotes not converted to unicode'' (they are in the
unicode.pl file)
While this symbol (also in the unicode.pl file) is? - \v{Z}
\end{document}
___
latex2html mailing list
[EMAIL PROTECTED]
http://tug.org/mailman/listinfo/latex2html
___
latex2html mailing list
[EMAIL PROTECTED]
http://tug.org/mailman/listinfo/latex2html
[l2h] Debugging image generation. Help!
Hi,
I am trying to debug
### Begin
Generating postscript images using dvips ...
This is dvips(k) 5.90a Copyright 2002 Radical Eye Software (www.radicaleye.com)
' TeX output 2003.08.07:1437' - C:\DOCUME~1\eda\LOCALS~1\Temp\l2h2552\image
(- C:\DOCUME~1\eda\LOCALS~1\Temp\l2h2552\image001) tex.proalt-rule.pro
texc.prospecial.procolor.pro[1]
Converting image #1
pstoimg.bat: Error: c:\local\netpbm\bin\pnmcrop.exe -verboseC:\DOCUME~1\eda\LO
eda\LOCALS~1\Temp\l2h2552\p2716.t00 failed:
Error while converting image: No such file or directory
Error: Cannot read 'img320.gif': No such file or directory
### End
How do I find what source causing it.
a. I already tried
latex images.tex
but that worked fine.
b. I looked at the postscript image and it looked wrong. In fact it was empty.
c. I did
cat *.html | img320
but it produced no reference.
So how do I figure what LaTex source that is causing problems? Source for images
are in the image.tex file. Right? Why not mark images with comment for instance
% img320
it is easy to figure what is causing problems.
Thanks in advance.
Erling
At 06:11 PM 8/6/2003 +0100, Chris Fox wrote:
On Thu, Jul 31, 2003 at 04:42:40PM -0800, Herb W. Swan wrote:
It is apparent from looking at html.sty that various
latex2html commands are implemented differently, depending
on whether pdf-TeX is in use or not. Yet I see no mention
of pdf-TeX in any of the latex2html documentation.
It would be nice if some of my internal and external
hyperlinks could make it into my final pdf document.
(Pdf is a preferable to postscript as the final form
of the written document, since it more universally
readable.) Has this already been implemented?
To what extent are latex2html and pdf-TeX compatible?
Would I be able to insert my figures into my final
pdf file if I used pdf-TeX in conjunction with
latex2html?
I frequently produce HTML and hyperlinked PDF output from the same
document sources, using latex2html for HTML output, and pdflatex or
latex-dvips-ps2pdf for PDF output. If you include figures in the
usual latex manner (e.g. with the graphicx package), and let
latex2html take care of the details, then there are few problems in
producing PDF and HTML output that contain figures. If you include
graphical elements in the latex2html output using raw HTML, or other
tricks, then you may have to do a bit more work, using conditions in
the source to use different code for the HTML and PDF output.
Your latex source document should uses the html package for the
commands that give hyperlinks under latex2html to compile under latex.
If you compile your document with pdflatex, then the html package
automatically loads the hyperref package, which allows for hyperlinks
and other things in the PDF output. Although hyperref has its own
syntax for hyperlinks, the latex2html syntax will work when both html
and hyperref packages are loaded. You may find there is an issue
getting external links to work correctly, even if you set an
appropriate path with hyperref (this could be due to an acroread bug).
Whether this is a problem for you may depend on how you make your
documents available, and how they are viewed (e.g. with a browser
plugin over http, or using a stand-alone program and the local file
system).
If you use the graphicx package to include figures (and you leave off
the filename extension for files containing the graphics), then when
compiling with ordinary latex, the package will look for files with
the extension .eps (encapsulated postscript), to be included by an
appropriate postscript driver (e.g. dvips), and under pdflatex it will
look for .(e)pdf (encapsulated PDF). If you are compiling postscript
and PDF output, you just need to make epdf versions of all your eps
files (there are ghostscript tools for this). LaTeX2html will
typically generate a GIF or PNG image for you.
If you have hyperlink aware versions of dvips or similar, you will
find that you can also produce hyperlinked PDF output even when going
via postscript (using ps2pdf for the final conversion step). In this
case you will have to explicitly load the hyperref package in your
latex source, as the html package may not know that it should load
it. Going this way, you might have to include an option an option to
hyperref, such as \usepackage[dvips]{hyperref}. Also, if you use
bitmapped fonts in your postscript (such as the original Computer
Modern, as rendered by MetaFont) the resultant PDF will look terrible
on screen and will not be searchable. Adding appropriate lines to
.dvipsrc, such as
p +psfonts.cmz
p +psfonts.amz
can fix this, if you have the appropriate type 1 fonts installed
(assuming you are using dvips).
You may find that the page dimensions of the PDF come out slightly
different depending on whether you use pdflatex or the latex, dvips,
ps2pdf combination, and depending on which versions of these programs
you are using, and how they have
[l2h] converting quotes
Hi all,
I'd really like to convert the latex quotation marks, `` and '' to the
recommended HTML curly quotes, #8220 instead of `` and #8221 instead
of '' - standard codes that render the curly quotes beautifully.
I'm sure that this is possible through latex2html - the codes are
listed around unicode.pl:722 - but either I can't find the magic
incantation to have latex2html do the conversion or there is a bug
preventing this from working in my version (1.70) or set-up.
I've tried:
latex2html -html_version 4.0,unicode test.tex
What is strange is that this does work for, say \v{Z} which converts to
the code #381; (and that is definitely happening through unicode.pl (I
changed the translation and it worked fine).
So why doesn't the translation for `` (which is correctly listed in the
unicode.pl as \`\`) and '' which is correctly listed as \'\' work?
I've had a good hunt around for this - but I can't see why the other
codes are converted but not the quotes.
Cheers,
James
ps. minimal test.tex follows
--
\documentclass[11pt]{article}
\begin{document}
``Why are these quotes not converted to unicode'' (they are in the
unicode.pl file)
While this symbol (also in the unicode.pl file) is? - \v{Z}
\end{document}
___
latex2html mailing list
[EMAIL PROTECTED]
http://tug.org/mailman/listinfo/latex2html
Re: [l2h] Converting emdashs and endashs?
On Monday, August 11, 2003, at 11:08 pm, Ross Moore wrote:
Hello James,
On Mon, 11 Aug 2003, James Howison wrote:
Now I have curly quotes happening (yay!) I am wondering about the
other
special characters. I realize that this will break back-wards
compatibility but that is not an issue for my needs.
I would like --- to be converted to #8212; as defined in the
unicode.pl file at 799 - but this doesn't seem to happen - instead it
is converted to --. This is also what happens if I change --- to
{---}.
That is definitely a lot harder; particularly since -- and --- are
rarely used correctly in LaTeX manuscripts.
So general rules may easily result in something that the author
never intended.
I use -- and --- often.
I'm still wondering, though, how to tell which conversions specified in
the unicode.pl file actually happen and which do not---and how those
are controlled ... I guess I'll spend some more time with the source ;)
Also I see from the source that converting single quotes is
tough---perhaps I'm naive but it would seem to me that this sequence
would work...
s/``/#8220;/og
s/`/#8216;/og # once the `` is gone then the ` is only used for
open single quote right?
Not at all. \` is used as an accent, and in some language variants,
the ` is made active to remove the need to use the \ .
With this active character, overloading can occur for generating
other special characters or ligatures.
Right - well I see the difficulty now. Quite an important distinction
- language compatibility being very important. The use of ` rather
than \ is not something that I'm familiar with - out of interest why is
this done - is it because the \ character is not easily accessible on
the keyboard?
Perhaps if these conversions are done _after_ the conversions from
latex-unicode then perhaps this would work (i.e. the international
characters would already be converted to their unicode expressions ...).
s/''/#8221;/og
s/'/#8217;/og # Will also replace apostrophes with close curly
single - not a bad thing.
Sorry; I cannot agree.
Every Latin-based charset encoding has an apostrophe character.
A curly-quote is most definitely *not* logically an apostrophe, even
though it may look like one.
I acknowledge that this is a matter of style---but the unicode standard
discusses this and generally prefers the use of the curly single
(#2019) to the straight mark (#0027)
http://www.unicode.org/unicode/reports/tr8/
#Apostrophe%20Semantics%20Errata
snip
The aim of an HTML translation should not be appearance.
It should be ensuring that meaning is preserved, and that no symbol
is rendered with the 'missing character' glyph.
I think one might reasonably disagree that appearance is not
important---HTML is, intentions notwithstanding, a format used for
presentation. Your point and care is about the 'missing character'
glyph is well taken, the warnings are very useful for this.
The 'div' request for CSS in Hakan's email also reflects the use of
HTML as an appearance format.
Thanks,
James
Hope this helps,
Ross Moore
Thanks,
James
On Saturday, August 9, 2003, at 02:53 am, Ross Moore wrote:
On Sat, 9 Aug 2003, James Howison wrote:
Hi all,
I'd really like to convert the latex quotation marks, `` and '' to
the
recommended HTML curly quotes, #8220 instead of `` and #8221
instead
of '' - standard codes that render the curly quotes beautifully.
set
$USE_CURLY_QUOTES =1;
in an initialisation file.
This is not the default, because not all browsers actually render
these characters. (At least, that was the situation 3-4 years ago
when
the LaTex2HTML coding was written.)
Hope this helps,
Ross Moore
I'm sure that this is possible through latex2html - the codes are
listed around unicode.pl:722 - but either I can't find the magic
incantation to have latex2html do the conversion or there is a bug
preventing this from working in my version (1.70) or set-up.
I've tried:
latex2html -html_version 4.0,unicode test.tex
What is strange is that this does work for, say \v{Z} which converts
to
the code #381; (and that is definitely happening through unicode.pl
(I
changed the translation and it worked fine).
So why doesn't the translation for `` (which is correctly listed in
the
unicode.pl as \`\`) and '' which is correctly listed as \'\' work?
I've had a good hunt around for this - but I can't see why the other
codes are converted but not the quotes.
Cheers,
James
ps. minimal test.tex follows
--
\documentclass[11pt]{article}
\begin{document}
``Why are these quotes not converted to unicode'' (they are in the
unicode.pl file)
While this symbol (also in the unicode.pl file) is? - \v{Z}
\end{document}
___
latex2html mailing list
[EMAIL PROTECTED]
http://tug.org/mailman/listinfo/latex2html
___
latex2html mailing list
[EMAIL PROTECTED]
http://tug.org/mailman/listinfo/latex2html
[Fwd: Re: [l2h] Converting emdashs and endashs?]
Original Message
Subject: Re: [l2h] Converting emdashs and endashs?
Date: Tue, 12 Aug 2003 19:35:11 +0200
From: Daniel Taupin [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: James Howison [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
Please, do not confuse shapes of quotes (single, double) which are a character
problem, with the handling of -- and ---. The last things are standard ligatures
with TeX fonts, while the first ones are a question of typing taste.
Therefore, since it is a TeX/LaTeX standard, I ask for a standard conversion
(unless in math mode) from -- to endash and a FURTHER conversion of endash
followed by a - to emdash.
On the other hand, I would disagree with a change in the behaviour of double
quotes, mainly because iot would be tricky for people performing copy/paste from
latex2html generated screens.
James Howison wrote:
On Monday, August 11, 2003, at 11:08 pm, Ross Moore wrote:
Hello James,
On Mon, 11 Aug 2003, James Howison wrote:
Now I have curly quotes happening (yay!) I am wondering about the other
special characters. I realize that this will break back-wards
compatibility but that is not an issue for my needs.
I would like --- to be converted to #8212; as defined in the
unicode.pl file at 799 - but this doesn't seem to happen - instead it
is converted to --. This is also what happens if I change --- to
{---}.
That is definitely a lot harder; particularly since -- and --- are
rarely used correctly in LaTeX manuscripts.
So general rules may easily result in something that the author
never intended.
I use -- and --- often.
I'm still wondering, though, how to tell which conversions specified in
the unicode.pl file actually happen and which do not---and how those
are controlled ... I guess I'll spend some more time with the source ;)
Also I see from the source that converting single quotes is
tough---perhaps I'm naive but it would seem to me that this sequence
would work...
s/``/#8220;/og
s/`/#8216;/og # once the `` is gone then the ` is only used for
open single quote right?
Not at all. \` is used as an accent, and in some language variants,
the ` is made active to remove the need to use the \ .
With this active character, overloading can occur for generating
other special characters or ligatures.
Right - well I see the difficulty now. Quite an important distinction
- language compatibility being very important. The use of ` rather
than \ is not something that I'm familiar with - out of interest why is
this done - is it because the \ character is not easily accessible on
the keyboard?
Perhaps if these conversions are done _after_ the conversions from
latex-unicode then perhaps this would work (i.e. the international
characters would already be converted to their unicode expressions ...).
s/''/#8221;/og
s/'/#8217;/og # Will also replace apostrophes with close curly
single - not a bad thing.
Sorry; I cannot agree.
Every Latin-based charset encoding has an apostrophe character.
A curly-quote is most definitely *not* logically an apostrophe, even
though it may look like one.
I acknowledge that this is a matter of style---but the unicode standard
discusses this and generally prefers the use of the curly single
(#2019) to the straight mark (#0027)
http://www.unicode.org/unicode/reports/tr8/
#Apostrophe%20Semantics%20Errata
snip
The aim of an HTML translation should not be appearance.
It should be ensuring that meaning is preserved, and that no symbol
is rendered with the 'missing character' glyph.
I think one might reasonably disagree that appearance is not
important---HTML is, intentions notwithstanding, a format used for
presentation. Your point and care is about the 'missing character'
glyph is well taken, the warnings are very useful for this.
The 'div' request for CSS in Hakan's email also reflects the use of
HTML as an appearance format.
Thanks,
James
Hope this helps,
Ross Moore
Thanks,
James
On Saturday, August 9, 2003, at 02:53 am, Ross Moore wrote:
On Sat, 9 Aug 2003, James Howison wrote:
Hi all,
I'd really like to convert the latex quotation marks, `` and '' to
the
recommended HTML curly quotes, #8220 instead of `` and #8221
instead
of '' - standard codes that render the curly quotes beautifully.
set
$USE_CURLY_QUOTES =1;
in an initialisation file.
This is not the default, because not all browsers actually render
these characters. (At least, that was the situation 3-4 years ago when
the LaTex2HTML coding was written.)
Hope this helps,
Ross Moore
I'm sure that this is possible through latex2html - the codes are
listed around unicode.pl:722 - but either I can't find the magic
incantation to have latex2html do the conversion or there is a bug
preventing this from working in my version (1.70) or set-up.
I've tried:
latex2html -html_version 4.0,unicode test.tex
What is strange is that this does work for, say \v{Z} which converts
to
the code #381; (and that is
[l2h] Converting emdashs and endashs?
Now I have curly quotes happening (yay!) I am wondering about the other
special characters. I realize that this will break back-wards
compatibility but that is not an issue for my needs.
I would like --- to be converted to #8212; as defined in the
unicode.pl file at 799 - but this doesn't seem to happen - instead it
is converted to --. This is also what happens if I change --- to
{---}.
I'm not sure why some of the conversions in the unicode.pl file happen,
while others do not. I can't find an equivalent of the
$USE_CURLY_QUOTES in the source code that seems relevant to mdash ...
Any ideas on how to get a maximal set of the conversions in unicode.pl
actually happening? I notice that there is no do_cmd_textemdash in
unicode.pl - is that why?
Also I see from the source that converting single quotes is
tough---perhaps I'm naive but it would seem to me that this sequence
would work...
s/``/#8220;/og
s/`/#8216;/og # once the `` is gone then the ` is only used for
open single quote right?
s/''/#8221;/og
s/'/#8217;/og # Will also replace apostrophes with close curly
single - not a bad thing.
i.e. ensure that one does the singles after the doubles ...
But there is probably a better algorithm in the source code for 'quoter'
http://www.dwheeler.com/quoter/
Thanks,
James
On Saturday, August 9, 2003, at 02:53 am, Ross Moore wrote:
On Sat, 9 Aug 2003, James Howison wrote:
Hi all,
I'd really like to convert the latex quotation marks, `` and '' to the
recommended HTML curly quotes, #8220 instead of `` and #8221 instead
of '' - standard codes that render the curly quotes beautifully.
set
$USE_CURLY_QUOTES =1;
in an initialisation file.
This is not the default, because not all browsers actually render
these characters. (At least, that was the situation 3-4 years ago when
the LaTex2HTML coding was written.)
Hope this helps,
Ross Moore
I'm sure that this is possible through latex2html - the codes are
listed around unicode.pl:722 - but either I can't find the magic
incantation to have latex2html do the conversion or there is a bug
preventing this from working in my version (1.70) or set-up.
I've tried:
latex2html -html_version 4.0,unicode test.tex
What is strange is that this does work for, say \v{Z} which converts
to
the code #381; (and that is definitely happening through unicode.pl
(I
changed the translation and it worked fine).
So why doesn't the translation for `` (which is correctly listed in
the
unicode.pl as \`\`) and '' which is correctly listed as \'\' work?
I've had a good hunt around for this - but I can't see why the other
codes are converted but not the quotes.
Cheers,
James
ps. minimal test.tex follows
--
\documentclass[11pt]{article}
\begin{document}
``Why are these quotes not converted to unicode'' (they are in the
unicode.pl file)
While this symbol (also in the unicode.pl file) is? - \v{Z}
\end{document}
___
latex2html mailing list
[EMAIL PROTECTED]
http://tug.org/mailman/listinfo/latex2html
___
latex2html mailing list
[EMAIL PROTECTED]
http://tug.org/mailman/listinfo/latex2html
Re: [l2h] Installation
Hi all, I've tried to install Latex2Html for sometimes, but not succeeded. I followed intructions in http://www.mayer.dial.pipex.com/l2h.htm but somehow the file PSTOIMG is not correctly created. If I ignore this fact and go on the installation, when I launch C:\texmf\TEXutils\Latex2html\bin\latex2html.bat Test.tex Things get wrong at the end: the latex2html can't creat images from source file. ... In an initialization file, say l2hconf.pm, make doubly sure you have set: @IMAGE_TYPES = qw(gif png); Darrell ___ latex2html mailing list [EMAIL PROTECTED] http://tug.org/mailman/listinfo/latex2html
[l2h] Feature request for CSS
Hello, currently I am converting a book project into html with l2h. The overall design of the default output from l2h is kind of poor (to be honest: it is very poor), the conversion from LaTeX to raw HTML is very good, though. So I played a bit with CSS. Unfortunately the output of l2h is not coverd by div class='logical part'/div in a consequent matter. My request is to divide every logical part of the output in a proper div/div -pair, so the enduser can modify the design easily with CSS, like: div class='navi-button-top' /div div class='navi-top' /div div class='content /div div class='footnote' /div div class='navi-bottom' /div div class='navi-button-bottom' /div I am sure, that this kind of modification is possible, but my Perl-Skills are not that good enough to make these changes by myself. Additionally I would like to know, how I can disable the Navigation-Buttons (I am using 2K.1beta (1.48)). I tried the option -noauto_navigation for that. And how do I disable the footnotes? I tried the option -nofootnode for that. (I think the correct spelling is footnote and not footnode) Possibly a bug is the output from latex2html --help for -(no)buttom_navigation. This should be either bottom_navigation or button_navigation. regards Hakan -- Dipl.-Wirt.-Ing (FH) Hakan Kuecuekyilmaz University of Applied Sciences Esslingen, Germany ___ latex2html mailing list [EMAIL PROTECTED] http://tug.org/mailman/listinfo/latex2html
