Re: [tex4ht] [bug #618] Incomplete XML Document, domfilter error, truncated build on large file.
On 12/14/23 20:32, Nasser M. Abbasi wrote:
[...]
The above build.sh assumes you are using TL 2023, if not please change
the path shown.
Yes, I have TL 2023.
After you start ./build.sh it will take about 12-16 hrs or so depending
on the speed and memory of your PC.
This is the biggest problem. In the first place, the single source TeX
file with huge size (145MB) makes it an unmanageable beast. Need to
waste another 12 to 18h of machine time even if we could pinpoint the
error causing line.
Hence, I split the source into several files of each with 100,000 lines.
Located that the table in line number 382889 (original source) had
broken the html generation which I found its place in the fourth segment
of split files (file-4.tex).
When I ran this by inputting to the introductory chapter to replicate
the problem, it went well to my surprise. Of course, it is not usable as
the cross references would be wrong.
I had encountered two problems.
* Found two packages missing (i) myspace.sty and (ii) maple.sty. Would
you kindly send these as well?
* \usepackage[]{marginnote} has been loaded without the option 'quiet'
that caused unwanted verbose aux writing about the xpos of the
margin notes which should have been handled in a different way in
html mode (with css directive like float) so that TeX will not spend
too much time on the computation of the exact location of the margin
note in the dvi. That indeed sped up my part compilation.
The document in whole is running in another system, will get back with
the results soon.
Regards
--
Radhakrishnan
[tex4ht] [bug #254] tex4ht breaks
Follow-up Comment #1, bug #254 (project tex4ht): Without the source file, it is difficult to track down the error location and the causes for the errors. Does it generate html that renders correctly in your browser? Does it parse OK? If not, it will not pass through xtpipes. Looks line you have missing closing tag for some elements. Once it fails, strangely, the scripts triggered by t4ht grab all files in the directory and try to create an odt. Very strange behavior and is highly unreliable. I do not feel like relying on xtpipes, better, you might import the html in your preferred word processor and export to the word processor format. ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?254 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #252] tex4ht doesn't work with latest versions of biblatex/biber
Follow-up Comment #11, bug #252 (project tex4ht):
Thanks Simon for the report.
Smallcaps problem can be solved with a \Css declaration in your document or
better a tiny *.cfg:
\Css{.small-caps{font-variant: small-caps; text-transform: lowercase;}}
Second problem can be solved by adding \let\addspace\xspace. It works OK. See
the contents of the archive and my.cfg (included in archive), simon.zip.
I used the command:
htlatex simon my
(renamed your MWE to simon.tex)
Radhakrishnan
(file #213)
___
Additional Item Attachment:
File name: simon.zip Size:65 KB
___
Reply to this item at:
http://puszcza.gnu.org.ua/bugs/?252
___
Message sent via/by Puszcza
http://puszcza.gnu.org.ua/
[tex4ht] [bug #252] tex4ht doesn't work with latest versions of biblatex/biber
Update of bug #252 (project tex4ht): Status:None = Ready For Test ___ Follow-up Comment #8: I did work on the newest version of biblatex (3.0) and biber (2.1) and the modified version of biblatex.4ht is forwarded now. All the example files provided in the biblatex bundle generated right kind of html as with the pdf's. Simon may kindly test this version and confirm if it works satisfactorily. If yes, I shall update the sources and commit to svn. Radhakrishnan (file #211) ___ Additional Item Attachment: File name: biblatex.4ht Size:17 KB ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?252 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #252] tex4ht doesn't work with latest versions of biblatex/biber
Follow-up Comment #5, bug #252 (project tex4ht): Karl, et al., so sorry, I could not find time to fix this bug. Will try my best to attempt this immediately. Guess, I need to grab biber and biblatex from CTAN, right? Not yet available with tlmgr. ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?252 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #252] tex4ht doesn't work with latest versions of biblatex/biber
Follow-up Comment #7, bug #252 (project tex4ht): This time, I had opted out of pretest (acute paucity of time). Will get from CTAN. ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?252 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #252] tex4ht doesn't work with latest versions of biblatex/biber
Update of bug #252 (project tex4ht): Assigned to:None = cvr ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?252 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
Re: [tex4ht] [bug #241] grave accent letter ` (hex 60) changes to left single quotation mark (hex 0xE2 0x80 0x98)
On 16/01/15 7:22 am, Nasser M. Abbasi wrote:
when running htlatex on this file
\documentclass[12pt]{article}
\begin{document}
`123`
\verb|`123`|
\end{document}
the grave accent character ` is changed to left-single-quotation-mark in
HTML. I need it to remain a Hex60 character as it is in the input.
A lasting solution would be to modify position 96 of cmtt.htf to
#x0060;. Shall we do that? Attached is my version of cmtt.htf. If that
works fine for all, we shall do it and update tex4ht.
--
Radhakrishnan
cmtt 0 127
'#x0393;' '' Gamma 0
'#x0394;' '' Delta 1 % cmtt.htf (unicode)2003-03-27 %
'#x0398;' '' Theta 2 % Copyright (C) 2000--2003 Michel Goossens %
'#x039B;' '' Lambda 3 % Eitan M. Gurari %
'#x039E;' '' Xi 4 % %
'#x03A0;' '' Pi 5 % This file can redistributed and/or %
'#x03A3;' '' Sigma 6 % modified under the terms of the LaTeX%
'#x03A5;' '' Upsilon7 % Project Public License Distributed from %
'#x03A6;' '' Phi8 % CTAN archives in directory %
'#x03A8;' '' Psi9 % macros/latex/base/lppl.txt; either %
'#x03A9;' '' Omega 10 % version 1 of the License, or (at your%
'#x2191;' '' uparrow 11 % option) any later version. %
'#x2193;' '' downarrow 12 %However, you are allowed to modify%
='=== quote 13 % this file without changing its name, if %
'#x00A1;' '' inverted 14 % you add a note of your own after this%
'#x00BF;' '' inverted 15 % copyright note. %
'#x0131;' '' dotless i 16 % %
'j''' wrong \j 17 %gur...@cis.ohio-state.edu %
'#x02CB;' '' grave 18 %http://www.cis.ohio-state.edu/~gurari %
'#x02CA;' '' acute 19
'#x02C7;' '' caron 20
'#x02D8;' '' breve 21
'#x02C9;' '' macron 22
'#x02DA;' '' ring baove 23
'#x00B8;' '' cedilla24
'#x00DF;' '' sharp \ss 25
'#x00E6;' '' aelig 26
'#x0153;' '' oelig 27
'#x00F8;' '' o with stroke 28
'#x00C6;' '' AElig 29
'#x0152;' '' OElig 30
'#x00D8;' '' O with stroke 31
'#x2423;' '' visible space 32
'!''' exclamation mark 33
'#x0022;' '' right(?) doublequote 34
'#''' 35
'$''' 36
'%''' 37
'#x0026;' '' ampersand 38
'#x2019;' '' right singlequote 39
'(''' 40
')''' 41
'*''' 42
'+''' 43
',''' 44
'-''' 45
'.''' 46
'/''' 47
'0''' 48
'1''' 49
'2''' 50
'3''' 51
'4''' 52
'5''' 53
'6''' 54
'7''' 55
'8''' 56
'9''' 57
':''' 58
';''' 59
'#x003C;' '' less than 60
'=''' 61
'#x003E;' '' greater than 62
'?''' 63
'@''' 64
'A''' 65
'B''' 66
'C''' 67
'D''' 68
'E''' 69
'F''' 70
'G''' 71
'H''' 72
'I''' 73
'J''' 74
'K''' 75
'L''' 76
'M''' 77
'N''' 78
'O''' 79
'P''' 80
'Q''' 81
'R''' 82
'S''' 83
'T''' 84
'U''' 85
'V''' 86
'W''' 87
'X''' 88
'Y''' 89
'Z''' 90
'[''' 91
'#x005C;' '' backslash 92
']''' 93
'#x02C6;' '' ring 94
'#x005F;' '' underscore 95
'#x0060;' '' left singlequote 96
'a''' 97
'b''' 98
'c''' 99
'd'''100
'e'''101
'f'''
[tex4ht] [bug #189] French babel
Update of bug #189 (project tex4ht): Status:None = In Progress Assigned to:None = cvr ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?189 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #188] adding support for multicols in htlatex
Update of bug #188 (project tex4ht): Status: Ready For Test = Fixed Open/Closed:Open = Closed ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?188 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #187] Undefined control sequence when using tabulary and colortbl
Update of bug #187 (project tex4ht): Assigned to:None = cvr ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?187 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #186] \label error with hyperref when no sectioning command is used
Update of bug #186 (project tex4ht): Status:None = Fixed Assigned to:None = cvr Open/Closed:Open = Closed Summary: \label error with hyperref when no sectioning command is used = label error with hyperref when no sectioning command is used ___ Follow-up Comment #1: Problem has been fixed by inializing \NR:Type as suggested by David Carlisle. Lit sources modified and committed. New version of nameref.4ht is attached. (file #141) ___ Additional Item Attachment: File name: nameref.4htSize:4 KB ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?186 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #183] Images after odt conversion are only shown in post stamp size
Update of bug #183 (project tex4ht): Open/Closed:Open = Closed ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?183 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #156] tex4ht incompatibility with bidi and xepersian packages
Update of bug #156 (project tex4ht): Status:None = Ready For Test Assigned to:None = cvr ___ Follow-up Comment #1: Submitted archive is utf.targ.gz that has an example file namely, cn.tex which is utf-8 encoded text in several languages like, Chinese, Japanese, Persian, Hebrew, Malayalam (incidentally my language that is spoken in Kerala, India), Hindi, Latin, Polish, Russian, Greek, etc in one document. By running utf2ent.pl over it, you will get cn-ent.tex (or any name you like) in which all the utf8 charcters will be translated into their corresponding utf8 code points in ascii. And TeX4ht is happy to create cn-ent.html with usual run of htlatex without any nagging problems of htf and unicode compatibility. I can't find any other easy solution for processing utf8 text with a program that innately needs *.tfm to handle any text fed into it. perl utf2ent.pl cn.tex cn-ent.tex htlatex cn-ent firefox cn-ent.html Comments welcome. (file #127) ___ Additional Item Attachment: File name: utf.tar.gz Size:82 KB ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?156 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #156] tex4ht incompatibility with bidi and xepersian packages
Follow-up Comment #2, bug #156 (project tex4ht): The test archive has an *.odt output also. I think, RTL is not obeyed in Hebrew and Persian while I guess, it is obeyed in html version. I would request Vafa to check this issue as I do not know both these languages. ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?156 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #177] TeX capacity exceeded with index and label
Update of bug #177 (project tex4ht):
Status:None = Fixed
Assigned to:None = cvr
___
Follow-up Comment #1:
\section{The command line parameters \protect\index{parameters}} will solve
the problem.
___
Reply to this item at:
http://puszcza.gnu.org.ua/bugs/?177
___
Message sent via/by Puszcza
http://puszcza.gnu.org.ua/
[tex4ht] [bug #177] TeX capacity exceeded with index and label
Update of bug #177 (project tex4ht): Open/Closed:Open = Closed ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?177 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #175] oo-xtpipes: Looking for wrong attribute name + hard-coded conversion rate in set dimensions of figures
Update of bug #175 (project tex4ht): Status:None = Fixed Assigned to:None = cvr Open/Closed:Open = Closed ___ Follow-up Comment #1: Typo in the attribute 'svg:hieght' corrected to 'svg:height'. ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?175 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #177] TeX capacity exceeded with index and label
Follow-up Comment #3, bug #177 (project tex4ht):
Does your coding has any extra merit over the following?
\section{The command line parameters}
\index{parameters}
___
Reply to this item at:
http://puszcza.gnu.org.ua/bugs/?177
___
Message sent via/by Puszcza
http://puszcza.gnu.org.ua/
[tex4ht] [bug #126] Please resume support for biblatex
Update of bug #126 (project tex4ht): Status:Works For Me = Fixed Open/Closed:Open = Closed ___ Follow-up Comment #7: TeX4ht has been tested and found working correctly all versions through the current one, i.e., v2.5. ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?126 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #178] citet in combination with natbib and [numbers, super] produces error
Follow-up Comment #2, bug #178 (project tex4ht): Submitting an archive, stefan.tar.gz which has your MWE slightly modified by adding two more bib items and multiple authors to check if everything works fine. Modified version of natbib.4ht is also included. If everything works fine, we will commit the changes to svn. (file #126) ___ Additional Item Attachment: File name: stefan.tar.gz Size:88 KB ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?178 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #178] citet in combination with natbib and [numbers, super] produces error
Update of bug #178 (project tex4ht): Assigned to:None = cvr ___ Follow-up Comment #1: Error confirmed. Will get back soon. ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?178 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
Re: [tex4ht] htlatex and docbook
On 05/10/12 17:22, philippe wrote: Hi, i work with MikTeX 2.9 on windows7 i use to convert from latex to html+css with htlatex but i need now to produce docbook from my latex files, so I've tried the command htlatex --dtd=docbook fichier.tex but it doesn't work. It seems that option --dtd=docbook is not recognized ( I get a message like try another file name ?!?) I have also eared about htrun but I have not found htrun in MiKTeX2.9. Does any one knows something about this ? for docbook with mathml: htlatex filename xhtml,docbook-mml -cunihtf -cdocbk for docbook: htlatex filename xhtml,docbook -cunihtf -cdocbk Best regards -- Radhakrishnan smime.p7s Description: S/MIME Cryptographic Signature
Re: [tex4ht] Invitation to connect on LinkedIn
On Saturday 14 January 2012 08:14 AM, Radhakrishnan CV wrote: I'd like to add you to my professional network on LinkedIn. - Radhakrishnan Please accept my uninhibited apologies. That was a browser accident. Best regards -- Radhakrishnan
Re: [tex4ht] How to get PDF's page numbers in html output? (Accessibility issue)
On Friday 23 December 2011 05:11 AM, Herbert Sitz wrote: Susan Jollyeasjolly@... writes: This poster's question is significant for accessibility. Braille, large print, speech, and other accessible versions of print editions typically use the page numbers of the (base) print (paged media) edition to allow users of accessible documents to communicate with each other and with users of the print edition. While I appreciate that the concept of page number is somewhat meaningless when using eReaders, the accessibility community has not AFAIK addressed alternative solutions. So at least in the forseeable future this is a capability that accessible media producers need. Susan -- Good point, which I hadn't though of. My own query is driven by a slightly different but related need: an academic setting where students may be using ebook, html, and/or pdf versions. Without having some kind of location-based counter common to the text of all versions there's no good way for users of different versions to refer to reference location of a particular passage. In an online world, the concept and usefulness of pages disappear. TeX4ht works on this basic premises. Also, we have different devices with different geometry which make pages literally useless when html or XML based markup allows re-flowing of text unlike the rigid PDF. So, instead of making PDF with rigid margins as the definitive version, we have to return to the wisdom of our forefathers who created Bible and formatted it for different geometries, still retaining the ability to refer to any verse, chapter, line, etc., across all different versions in a uniform way. So, the best option is to keep paragraph numbers instead of page numbers as the basis for reference. The counter doesn't need to be the pdf page number, but that's an already-existing counter that makes sense. Whatever counter is used, it must be present in all versions. In looking further at tex4ht I'm not sure merely having ability to insert a counter at page breaks would solve this problem. I have .tex files that I process to PDF using pdflatex, and which I process with tex4ht's htlatex to get the html. TeX4ht's page break has no relation with that in the corresponding PDF. If you create an xhtml or XML with MathML, you get a dvi of many hundred pages for a single page document! Most of the pages will be having a single character text only. So, relying on TeX4ht pagecbreak does not take you anywhere. The problem I see is that tex4ht alters the formatting in the process of generating the html. tex4ht first compiles the document to an intermediate dvi, then uses that dvi to generate the html. That is correct. I had expected the pagination of the dvi file to correspond to the pagination of the pdf generated by pdflatex. Unfortunately, No. Formatting the document is not the objective, but translating from one markup to another markup is the objective where formatting of text to look exactly like in a printable version is hardly necessary to accomplish TeX4ht's objective. Unfortunately, the pagination does not necessarily match. I'm not sure what It won't match at all. formatting changes tex4ht makes as part of compiling to dvi (besides disabling The dvi is a convenient file format for TeX4ht's post-processor to extract text and markup injected into the dvi as \special's. And it provides a nicer way to replace and/or manipulate any character in any manner with the help of Eitan's ingenious hypertext fonts. header and footer, which would not necessarily affect pagination). So merely having ability to hook in and put in a page counter for each new dvi page would not necessarily give pagination markers that correspond to the PDF. The entire page breaks and line breaks differ. All attributes like bold, italic, large, etc have lost their meaning found in pdf, but have a different meaning and different markup system palatable to the browser. When glue, vertical and horizontal skips, character widths/heights lose their meaning in TeX4ht generated dvi, it is clear that we will seldom get an output which visually corresponds to pdf output if printed. I wonder whether there are some optional settings in tex4ht that would make the dvi pagination match (or even closely match) the pagination in the PDF. Sorry, I don't think that will happen. I see a non-tex4ht-related way to generate the page numbers I want in the html, but it's not trivial. Basically, the steps would be these: Sure, that is the best option. I too am interested to see a better solution. [...] Does anyone know whether there is a publicly available solution for this? I would probably write it in Python using the BeautifulSoup html api; I wonder whether something like this is already available on github or elsewhere. Or maybe there actually is some way to get tex4ht to (1) generate dvi with pagination that corresponds to PDF pagination, and (2) include a page
[tex4ht] [bug #154] error in content.xml with sectioned bibliography
Follow-up Comment #1, bug #154 (project tex4ht): Bibliography data (/home/jos/Bib/jos.bib) is not provided. Can you please submit this too? Radhakrishnan ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?154 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #154] error in content.xml with sectioned bibliography
Update of bug #154 (project tex4ht): Assigned to:None = cvr ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?154 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
[tex4ht] [bug #154] error in content.xml with sectioned bibliography
Follow-up Comment #2, bug #154 (project tex4ht):
The error is caused by the introduction of an unwanted para element in XML at
the end of bibliography, the culprit seems to be bibtopic.sty. This can be
circumvent by adding the following line after \begin{document}
\ConfigureEnv{btUnit}{}{}{}{}
If this works OK in your setup, we will revise bibtopic.4ht and release a new
version.
___
Reply to this item at:
http://puszcza.gnu.org.ua/bugs/?154
___
Message sent via/by Puszcza
http://puszcza.gnu.org.ua/
Re: [tex4ht] html output
On 10/27/2011 07:21 AM, David Denton wrote: Hi, I get a lot of PICT PICT scattered through html documents created with htlatex. I wonder if htlatex is adding them as spacers for some reason. I can delete these but is annoying. Any way to ensure that the PICTs do not occur in the first place? Can you please send me a test file off the list? -- Radhakrishnan A young man wrote to Mozart and said: Q: Herr Mozart, I am thinking of writing symphonies. Can you give me any suggestions as to how to get started? A: A symphony is a very complex musical form, perhaps you should begin with some simple lieder and work your way up to a symphony. Q: But Herr Mozart, you were writing symphonies when you were 8 years old. A: But I never asked anybody how. smime.p7s Description: S/MIME Cryptographic Signature
[tex4ht] [bug #146] index: div theindex is starting too late
Update of bug #146 (project tex4ht): Status:None = Fixed ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?146 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
Re: [tex4ht] unicode and lualatex
On 07/23/2011 10:17 AM, Johannes Wilm wrote: Hi, On the attached test file I tried to run / / /dvilualatex unicode.tex/ /dvilualatex unicode.tex/ /dvilualatex unicode.tex/ /tex4ht -f/unicode.tex -cunihtf -utf8/ I cannot figure out as what the characters are encoded in the output, but it doesn't seem to be utf8. Output has been attached. Can your example produce a valid dvi? In my tests, it didn't. TeX4ht needs a valid dvi to generate html. Actually the post-processor called tex4ht (binary) extracts the textual characters from the dvi by making a clever substitution which is based on the *.tfm of font used and *.htf (hypertext font). The post-processor needs *.tfm which unfortunately is not available for unicode fonts and then it falls back to cmr. The resulting html file will not be usable owing to unicode characters appearing as junk. If somebody comes forward with a patch to tex4ht binary which can post-process dvi without the help of *.tfm's will be a great contribution. The macro package level patching is easier than the binary level patching. Volunteers are welcome. -- Radhakrishnan It's today! said Piglet. My favorite day, said Pooh.
Re: [tex4ht] custom names of the generated HTML files
On 18/02/11 2:04 PM, Jaroslav Sobota wrote:
Hi all,
is there a way to customize the names of the generated HTML files
generated by tex4ht?
I can generate the files signal.html, signalch1.html and
signalch2.html from the attached .tex file using the command
htlatex signal xhtml,2
but I would like to obtain something like signal.html, analog.html
and digital.html. Is this possible? Renaming and editing by hand is
not an option.
You might make use of \FileStream command as provided below:
%-
\documentclass[a4paper,11pt]{book}
\begin{document}
\tableofcontents
\FileStream{analog.html}
\Link[signal.html]{}{}{[prev]}\EndLink
\Link[digital.html]{}{}{[next]}\EndLink
\chapter{Analog signal processing}
Turpis interdum eu non Cum Morbi ut ipsum Aenean Vestibulum nec.
Curabitur condimentum fringilla nibh Curabitur et hendrerit
parturient dis quis enim.
...
\FileStream{digital.html}
\Link[analog.html]{}{}{[prev]}\EndLink
\Link[signal.html]{}{}{[up]}\EndLink
\chapter{Digital signal processing}
Facilisis et tortor Quisque lorem eros pretium accumsan morbi Nunc
Sed. Orci mauris risus vitae ut Suspendisse id tellus justo amet ac.
Tellus vel sodales vestibulum semper arcu orci tincidunt tincidunt
consequat dolor.
...
%
But, I guess, you need to configure various cross links yourself as
given above which is a horrendous task.
--
Radhakrishnan
Re: [tex4ht] Missing Colors when generating HTML
On 28/12/10 9:58 PM, Kevin Erath wrote:
Hello Radhakrishnan,
thank you for the fast response! Your quick fix works with simple
Welcome.
\color commands. I found out, that alternatively the command
\textcolor also works.
OK.
Though i still have a problem with the coloring, as i also use the
lstlisting command to show various code listings with color
highlighting. Unfortunately the listings package seems not to work
with color support too.
Generally, colors shall be brought into HTML page with the help of css
which is much more easier and also elegant way to do. You might prefer
to have a small *.cfg (TeX4ht configuration file that has your custom
setup for your documents, a bit like a LaTeX style file) in which you
might provide various custom css declarations that will eventually be
written out to your \jobname.css while generating html. Of course, for
simple \color or \textcolor for random text strings, the configuration
I had given in the previous mail will help.
For example listings with the following configuration, are still
shown in blackwhite instead of green on black:
\lstdefinelanguage{Test} { basicstyle=\ttfamily\color{green},
backgroundcolor=\color{black}, }
The following \Css code can solve your problem:
\Css{div.lstlisting{font-family: monospace;
white-space: nowrap; margin-top:0.5em;
margin-bottom:0.5em;
color: green ;
background-color: black;}}
Maybe you have a solution for this too.
I have attached to this mail a specimen configuration, kevin.cfg which
shows you how to write one for your custom needs. Once you have a
*.cfg with custom setup, the invocation of TeX4ht shall be:
htlatex file kevin
(htlatex your LaTeX file with/without extension configuration)
Also attached are the TeX sources, pdf and html outputs. The advantage
of configuration is that your source file remains clean without any
TeX4ht specific stuff which allows seamless compilation with pdflatex
for pdf output.
If you are using GNU/Linux or similar OS, you might make use of a
Makefile with different targets for various outputs which makes the
process all the more enjoyable.
Best regards
--
Radhakrishnan
Celibacy is not hereditary.
kevin.pdf
Description: Adobe PDF document
kevin.tex
Description: TeX document
1Test!
Hello black, red and blue.
fori:=maxintto0dobegin{donothing}end;Write(Caseinsensitive);WritE(Pascalkeywords.);
/* start css.sty */
.cmtt-10{font-family: monospace;}
.cmbx-10{ font-weight: bold;}
p.noindent { text-indent: 0em }
td p.noindent { text-indent: 0em; margin-top:0em; }
p.nopar { text-indent: 0em; }
p.indent{ text-indent: 1.5em }
@media print {div.crosslinks {visibility:hidden;}}
a img { border-top: 0; border-left: 0; border-right: 0; }
center { margin-top:1em; margin-bottom:1em; }
td center { margin-top:0em; margin-bottom:0em; }
.Canvas { position:relative; }
img.math{vertical-align:middle;}
li p.indent { text-indent: 0em }
li p:first-child{ margin-top:0em; }
li p:last-child, li div:last-child { margin-bottom:0.5em; }
li p~ul:last-child, li p~ol:last-child{ margin-bottom:0.5em; }
.enumerate1 {list-style-type:decimal;}
.enumerate2 {list-style-type:lower-alpha;}
.enumerate3 {list-style-type:lower-roman;}
.enumerate4 {list-style-type:upper-alpha;}
div.newtheorem { margin-bottom: 2em; margin-top: 2em;}
.obeylines-h,.obeylines-v {white-space: nowrap; }
div.obeylines-v p { margin-top:0; margin-bottom:0; }
.overline{ text-decoration:overline; }
.overline img{ border-top: 1px solid black; }
td.displaylines {text-align:center; white-space:nowrap;}
.centerline {text-align:center;}
.rightline {text-align:right;}
div.verbatim {font-family: monospace; white-space: nowrap; text-align:left; clear:both; }
.fbox {padding-left:3.0pt; padding-right:3.0pt; text-indent:0pt; border:solid black 0.4pt; }
div.fbox {display:table}
div.center div.fbox {text-align:center; clear:both; padding-left:3.0pt; padding-right:3.0pt; text-indent:0pt; border:solid black 0.4pt; }
div.minipage{width:100%;}
div.center, div.center div.center {text-align: center; margin-left:1em; margin-right:1em;}
div.center div {text-align: left;}
div.flushright, div.flushright div.flushright {text-align: right;}
div.flushright div {text-align: left;}
div.flushleft {text-align: left;}
.underline{ text-decoration:underline; }
.underline img{ border-bottom: 1px solid black; margin-bottom:1pt; }
.framebox-c, .framebox-l, .framebox-r { padding-left:3.0pt; padding-right:3.0pt; text-indent:0pt; border:solid black 0.4pt; }
.framebox-c {text-align:center;}
.framebox-l {text-align:left;}
.framebox-r {text-align:right;}
span.thank-mark{ vertical-align: super }
span.footnote-mark sup.textsuperscript, span.footnote-mark a sup.textsuperscript{ font-size:80%; }
div.tabular, div.center div.tabular {text-align: center; margin-top:0.5em; margin-bottom:0.5em; }
table.tabular td p{margin-top:0em;}
Re: [tex4ht] align*, intertext and conversion to jsmath
On 08/12/10 2:58 AM, Rob Beezer wrote:
Dear CVR and Karl,
Thanks so much for your continued work on tex4ht.
I am having trouble with the \intertext{} command within an amsmath
align* environment in a conversion to jsmath. Actually, I have 76 of
these giving me trouble (across an entire textbook).
Many thanks for this bug report. There are a few problems in jsmath
configuration package of TeX4ht. If you encounter more, please do not
hesitate to post.
I have fixed your problem as provided in the test file below:
- Begin test file
\documentclass{article}
\usepackage{amsmath}
\begin{document}
\catcode`\:=11
\catcod...@=11
\def\a:math:amp{\string}
\Configure{intertext}
{\IgnorePar \ifinal...@\hcode{\string\cr }%
\else \ifingat...@\hcode{\string\cr }%
\fi\fi\AA:text{intertext}}
{\BB:text \ifvmode \IgnorePar \fi \EndP\ifinalign@
\HCode{\string\cr }\else \ifingather@
\HCode{\string\cr }\fi\fi}
\catcode`\:=12
\catcod...@=12
%
Some \verb!align*! mathematics with an \verb!intertext! line:
%
\begin{align*}
A=B
\intertext{and}
C=D
\end{align*}
%
\end{document}
- End test file
Output seems to have the ordering of some mtr and mtd tags reversed.
Actually those mtr and mtd tags shouldn't be there at all. Those
are inserted by the default configuration of \intertext command. I
have modified the same in the test file given above. If it works fine
in your case, we will fix the problem in TeX4ht packages and commit to
svn.
[...]
As an aside, I consistently get the following with SVN 66, with an
error for each line of the header comments:
tex4ht.c (Version 1.1 kpathsea)
tex4ht -f/intertext-example
-i~/tex4ht.dir/texmf/tex4ht/ht-fonts/
(/home/rob/tex4ht.env)
(/home/rob/tex4ht.dir/texmf/tex4ht/ht-fonts/iso8859/1/charset/unicode.4hf)
--- warning --- Improper entry (line 1)
%% %% %% %%
--- warning --- Improper entry (line 2)
% unicode.4hf 2009-07-25-19:06 %
You can safely ignore it, it comes from the newly inserted licence
text at the top of the file. We will fix it before next release.
Best regards
--
Radhakrishnan
Multiple-function gadgets will not perform any
function adequately.
[tex4ht] [bug #131] url/ olinkurl do not expand macros
Update of bug #131 (project tex4ht): Assigned to:None = cvr Summary: \url/\nolinkurl do not expand macros = url/nolinkurl do not expand macros ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?131 ___ Message sent via/by Puszcza http://puszcza.gnu.org.ua/
