Re: [tex4ht] [bug #309] tex4ht does not work with package savetrees

[Karl Berry]

Hi Michal,

is updated usepackage.4ht:

Fantastic.  I'm surprised Eitan did not create a mechanism like this.

Anyway, can you commit the lit changes for the new usepackage or send
them to me, if nothing more is pending for it?  Thanks!! -k

Re: [tex4ht] issue with tex4ht and minted package, extra space added

[Karl Berry]

Hi Deimi,

Great sleuthing.

Verbatim from fancyrb, which does have a tex4ht configuration.
The fifth parameter of "\Configure{fancyvrb}" is set to two spaces.

I don't get it.  If fancyvrb itself doesn't insert any indentation by
default (xleftmargin default is zero, I gather), shouldn't tex4ht follow
suit?  Maybe Eitan was looking at the fancyvrb manual, which does mostly
use "two spaces".  Hmm.

Thanks,
Karl

Re: [tex4ht] Bug identified: tex4ht to .odt (also identifying bugs in MiKTeX's setup)

[Karl Berry]

Thank you for the detailed report.  I hope we (Michal ...?) can
look into the tex4ht stuff.

As for the miktex bug:

the first command line above needs a space after "xhtml,":
1. htlatex test "xhtml, ooffice" "ooffice/! -cmozhtf" "-coo -cvalidate"
If you don't leave a space, MiKTeX's latex get confused, and can't run.

needs to be reported in whatever way miktex likes.  I don't think anyone
here has any particular knowledge of (or even uses) miktex.  I don't,
for sure.

Thanks again.  --karl

[tex4ht] [bug #136] #line in output

[Karl Berry]

Follow-up Comment #6, bug #136 (project tex4ht):

perfect, thanks so much!  i'll see if i can put together a new protex release,
at least ...

___

Reply to this item at:

  

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #136] #line in output

[Karl Berry]

Follow-up Comment #4, bug #136 (project tex4ht):

hi deimi - thanks for the patch.  agreed about protex. i've never imported
protex into the tex4ht repository since we hadn't yet needed to make changes
there. however, i see no problem in doing so.

what's on CTAN is current as far as i know.  maybe you could work up the patch
against that, send it here. i'll see about importing protex into our repo and
making a release. unless someone else here would like to take that on ...

as for an option: for the C files, I see no need for an option.
but for the TeX-related .4ht and other files, it seems it would be prudent to
be able to turn off line numbers at the beginning of a given tex4ht-*.tex
literate file, since I can imagine the extra comments causing problems
sometimes.  we all know about TeX and input parsing ... thanks, k.

___

Reply to this item at:

  

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #136] #line in output

[Karl Berry]

Follow-up Comment #2, bug #136 (project tex4ht):

hi deimi - wow, that is great!  the only (trivial) thing is that the strings
should start with "#line ", rather than "// line".  #line is what the C
preprocessor recognizes.

Can you send me the changes you made to insert those?
(That is, assuming you're ok with them being distributed under the LPPL.)

Just wondering -- is there any chance that perhaps the same code could be done
for the generated .4ht and other files?  (%line 777 "tex4ht-4ht.tex", etc.)
The derivation is so complex, it's often quite hard, at least for me, to track
back a given line to the source.

thanks!



___

Reply to this item at:

  

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

Re: [tex4ht] issue with tex4ht and minted package, extra space added

[Karl Berry]

Found a big problem with tex4ht adding extra space at start
of each listing line in HTML, 

It's easy to believe that an extra space is being created somewhere
along the line.  Especially since there is no minted.4ht, and minted.sty
necessarily has to play games with the ~ character.

Unfortunately I cannot run the document, since I get (after installing
the python-pygments package on my CentOS 6 system):

  *** Error while highlighting:
  ClassNotFound: filter 'tokenmerge' not found
 (file "/usr/lib/python2.6/site-packages/pygments/filters/__init__.py", 
line 47, in get_filter_by_name)

And so the output is entirely empty.  I don't know where that "filter"
is supposed to come from.  Some web searches didn't turn up anything
obvious.  Sorry ... I submitted the bug report to the tracker.  -k

[tex4ht] [bug #308] extra space from minted.sty

[Karl Berry]

URL:
  

 Summary: extra space from minted.sty
 Project: tex4ht
Submitted by: karl
Submitted on: Mon 30 May 2016 02:43:34 AM EEST
Category: None
Priority: 5 - Normal
Severity: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

from nasser: http://tex.stackexchange.com/questions/311284
http://tug.org/pipermail/tex4ht/2016q2/001471.html

make4ht foo.tex "--shell-escape" on

\documentclass[11pt]{article}%ext
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{color}
\usepackage{minted}
\usepackage{upquote} %to fix string quotes
\setlength\parindent{0pt}
\begin{document}

\begin{minted}[linenos=false,fontfamily=tt,frame=leftline,
   showspaces=false,stripall=true,xleftmargin=0pt]{matlab}
clear all; close all;
t   = 0:0.05:50;
s   = tf('s');
sys = 1/(s^2+0.2*s+1);
\end{minted}
\end{document}





___

Reply to this item at:

  

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

Re: [tex4ht] Decimal comma and specing (bug?)

[Karl Berry]

The problem is, the tex4ht command is written in C and it seems that
nobody understand it, so it is quite unlikely that we can fix it.

If someone can tell me how to change it, I expect the change can be
implemented.  The hard part is figuring out what to do.  I find the C
program more or less equally inscrutable with all other aspects of
tex4ht source, not especially worse (or better).  -k

[tex4ht] [bug #277] make timestamps in HTML output optional

[Karl Berry]

Update of bug #277 (project tex4ht):

 Open/Closed:Open => Closed 

___

Follow-up Comment #5:

thanks.  i found several more uses of :today, and either configured them
similarly (off by default, timestamp option to enable) or just deleted them
(css files, a couple others where the code wasn't following the same pattern.
installed in tex4ht (r164) and tl (r40194).

the massive code duplication throughout the sources continues to be a big
headache.  sigh.


___

Reply to this item at:

  

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #275] titlesec package slows down tex4ht

[Karl Berry]

Follow-up Comment #2, bug #275 (project tex4ht):

the maintainer of titlesec is javier bezos.  he is still around. if we asked
him to just make titlesec a no-op for tex4ht, he might be willing. would one
of you be willing to ask him about it?
thanks, k.

___

Reply to this item at:

  

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #277] make timestamps in HTML output optional

[Karl Berry]

Follow-up Comment #3, bug #277 (project tex4ht):

thanks for the report (Erik) and patch (Michal).
 
unless someone objects, i actually think it would be better to remove
timestamps by default and let enabling them be the option. those gratuitious
changes in the output have always been a hassle.
wdyt?



___

Reply to this item at:

  

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #276] avoid multiple runs of latex

[Karl Berry]

URL:
  

 Summary: avoid multiple runs of latex
 Project: tex4ht
Submitted by: karl
Submitted on: Tue 29 Mar 2016 01:54:02 AM EEST
Category: None
Priority: 5 - Normal
Severity: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

re http://tug.org/pipermail/tex4ht/2016q1/001414.html

don't think we need to turn tex4ht into another latexmk or texi2dvi, but the
scripts could easily have some kind of option to run the latex+tex4ht+t4ht
command just once, which a higher-level script could more easily make use of.

(among many, many, many, other things to tweak in the scripts.)





___

Reply to this item at:

  

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

Re: [tex4ht] problem with slow compilation of large latex file with large math content

[Karl Berry]

more active in supporting TeX4ht,

Help is always good.  There are plenty of open bugs at
  https://puszcza.gnu.org.ua/bugs/?group=tex4ht=browse=open
That's probably the simplest place to start.

Thanks,
Karl

Re: [tex4ht] problem with slow compilation of large latex file with large math content

[Karl Berry]

 make:htlatex()
 make:htlatex()
 make:htlatex()

P.S. The texi2dvi script implements one way to check how many runs are
needed: it compares auxiliary files and keeps running TeX until they
stabilize.  I suspect latexmk and others do the same thing, though I've
never looked at them.  So it is doable, though far from trivial.  -k

Re: [tex4ht] problem with slow compilation of large latex file with large math content

[Karl Berry]

What are these rules? 

I just explained it.

(that is why we need design documents)

There's no use in continuing to repeat this wish.  We all agree.  What's
needed is more people to do work, not more work to be done!  -k

Re: [tex4ht] problem with slow compilation of large latex file with large math content

[Karl Berry]

But I do not know how to decide if I need one run or two or three?

You need three runs if you are starting from scratch.
After the first time, in general, you only need one run unless you are
modifying the things that go into the cross-references (section names,
labels, bib entries, etc.).  

Ordinarily it's not worth thinking about, since the runs are fast
enough.  I only mention it here because if you're repeatedly doing three
five-hour runs when you only need to do one, that would clearly be
undesirable.

I call make4ht to compile the file

I don't know anything about make4ht, that's Michal's bag ... Perhaps it
is already smart enough to avoid multiple runs when it's not necessary.
(I'm having deja vu, did we already discuss this, Michal?)  -k

Re: [tex4ht] problem with slow compilation of large latex file with large math content

[Karl Berry]

Hi Nasser,

TL is more optimized for native Linux vs. cygwin.

Just to remark: TL specifically is not "optimized" for any particular
platform (all binaries are built natively).  I think the difference you
are seeing here is an inevitable consequence of running a
resource-intensive job on an emulation layer (cygwin) vs. a native layer
(gnu/linux).  (As for native Windows, it is fundamentally inefficient,
so I'm not surprised it is slow too.  Cygwin or vbox is thus the worst
of both worlds.)

buying new PC and installing Linux on it just in the hope

Wow.  I suspect you are the only person in the world buying hardware to
placate tex4ht!

then it starts to slow down, the higher the number becomes

I think we need some kind of profiling of the TeX run to find the facts.
I don't have an easy recipe at hand.  (And I'm currently trying to get
the next TUGboat out the door, plus prepare for the TL pretest, so it's
going to be hard to devote significant time to this for a while,
unfortunately ...)

But the issue is, pdflatex and lualatex take about 5 minutes
on the same file to compile it to pdf !

Ok, so let's consider PDF first, since that is simpler to think about
than HTML.

I have many many latex files this large

Is the one you provided already one of the smaller ones?  The smaller
the file that still exhibits the problem, the easier to debug.

given that lualatex takes one hr or so.

Oh, lualatex is another important part of the story.  LuaTeX is already
significantly slower than standard TeX (or XeTeX), and depending on what
your document is doing, we may be hitting some kind of new/unusual
slowdown that is specific to luatex.  Must you use luatex?

Finally, is there a document that describes the passes/process
that tex4ht uses to compile to HTML at some high level?

The htlatex script is six lines long, and is the clearest possible
summary of what is run.  I'll omit the TeX gobbeldygook that Eitan
uses.

#!/bin/sh
latex $5 ...
latex $5 ...
latex $5 ...
tex4ht -f/$1  -i~/tex4ht.dir/texmf/tex4ht/ht-fonts/$3
t4ht -f/$1 $4

I assume Michal's make4ht is fundamentally equivalent.

As CVR says, the reason for the three latex runs is simply to resolve
references.  Thus if you are repeatedly running the same doc, with all
aux files already in place, one run would suffice.


For sure, a design document, among many others, would be extremely
desirable, not to mention many updates to the code, not to mention a new
release, not to mention ...  What's fundamentally needed are more
volunteers with time and ability to help develop and document this
highly complex system!

karl

Re: [tex4ht] just forked svn repo to github repo, first time contributor to the project

[Karl Berry]

Hi Jason,

made a few changes to normalize spacing 

I don't know what "normalize spacing" means, but if you're talking about
removing trailing whitespace or collapsing whitespace, it is not clear
to me that it's really worth massive changes for such cosmetic issues at
this time.  Virtually every single source file has cosmetic problems of
one kind of another.  That was not Eitan's forte.  I guess there's no
harm, but I've tried to only touch things when something functional is
actually being changed.

Fixes to functionality are of course (very) gratefully received.

my attempting to use mk4ht to convert my latex resume to
opendocument format, which wasn't working for me properly yet.

I'm not surprised.  Thanks for getting as far as making a copy of the
sources.  That's more than nearly anyone else has ever done!

I mention my git repo above.

Thanks, but I cannot guess what to do (or if I want to do it) just based
on a pile of files in git.  If there are changes you'd like me to
consider merging upstream, please send a diff (to here), ok?

Happy hacking,
Karl

[tex4ht] [bug #271] Wrong characters in PCR family

[Karl Berry]

Follow-up Comment #3, bug #271 (project tex4ht):

anthony thyssen has written much, much, information about the problem (as he
has about seemingly all aspects of imagemagick).
http://www.imagemagick.org/Usage/compare/

there are some scripts and recipes in there among all the explanations.  once
you have an actual case at hand, it might be simplest to just ask anthony
(assuming he's still active) for advice.


___

Reply to this item at:

  

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #271] Wrong characters in PCR family

[Karl Berry]

Update of bug #271 (project tex4ht):

 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

thanks, installed in tex4ht and tl.

maybe some kind of image comparison program could avoid some of the manual
validation?  if each char can be dumped to an individual image.  i could send
you some tips i received one for doing comparisons with imagemagick if you
like.

___

Reply to this item at:

  

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #268] tex4ht breaks with biblatex 3.1

[Karl Berry]

Update of bug #268 (project tex4ht):

 Open/Closed:Open => Closed 

___

Follow-up Comment #2:

installed in tex4ht + tex live, thanks as always.


___

Reply to this item at:

  

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

Re: [tex4ht] Too many DVI errors. stack empty at pop command, conficts, bm package, siunitx, dvilualatex

[Karl Berry]

I'm not sure if you determined if all of this is a dvisvgm bug,
but if not:

Here is a MWE, which shows the issue. What happens is that
DVI creates corrupted DVI file or has an error making the dvi.

When dviluatex (or any engine) creates a corrupted DVI file (i.e.,
dvitype cannot successfully read it), under any reasonable
circumstances, it's certainly an error.

However, the LuaTeX developers fixed the previous DVI-generation bug,
and it could well be related.  Unfortunately, we'd have to compile from
the original source to get the fix, and I don't see that happening.
I could report it to them to try, except:

Here is MWE

As discussed last time: to debug, the LuaTeX people need an invocation
of dvilua(la)tex, not an invocation of make4ht.

Best,
Karl

Re: [tex4ht] tex4ht puts the wrong link when splitting document. How to make the top of the page visible?

[Karl Berry]

destination link is inserted after section number, 

Seems like before the section number would be better.
What's the advantage of moving to after the number?
Just seems confusing.

Re: [tex4ht] erorr code 256, possible perl error code, come up with using --lua option with make4ht, error --- Improper dvi file

[Karl Berry]

kb> Copying the dvilualatex command from the make4ht output and running it
> by hand results in a perfectly fine .dvi file.

I was wrong.  It fails the first time for me too.  I was misled by
dvitype exit status.

So does this mean dvilualatex  is generating bad dvi?

Apparently so.

I'll try reporting it in the luatex tracker.  We'll see.  

Thanks,
K

[tex4ht] [bug #264] Fix support for textcomp package

[Karl Berry]

Follow-up Comment #1, bug #264 (project tex4ht):

i haven't installed this since you said "some testing is needed". what testing
:)?

probably your new version is at least a good improvement over the existing
one, right?  so if i install it, maybe people will test it through tl ...


___

Reply to this item at:

  

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #262] Support for \textsubscript

[Karl Berry]

Update of bug #262 (project tex4ht):

 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

i installed the changes and updated html4.4ht, ooffice.4ht, and subscript.4ht
(would that be better as textsubscript.4ht?) in TL.  Thanks Michal.

By the way, it would be a help if you could draft a ChangeLog entry along with
changes in the future.  Since you know better than me what you are doing :). 
It does not have to be involved; see what I wrote for this one for a sample.

Thanks as always for doing the work.

___

Reply to this item at:

  

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

Re: [tex4ht] tex4ht Digest, Vol 68, Issue 10

[Karl Berry]

Hi CVR - it was not clear to me, and indeed still is not clear, whether
the changes you made back in June were the final word, or if more were
expected.  Thus I did not update TL at the time.  And then I forgot to
check back about it.  Oh well.  I've updated TL now with the current
version.

I believe the bug report was https://puszcza.gnu.org.ua/bugs/?252.
The OP reported some stuff after applying your patch.
It wasn't clear to me if those reports implied further changes, or if
the one-off document configurations sufficed.

Michal, I guess the smallcaps patch you refer to in that bug is
https://puszcza.gnu.org.ua/bugs/?253
Can you confirm my supposition in the newest comment there, that
those two .htf files are the only ones needed to be updated/added?
(I accidentally left the f off the second one.)

Thanks,
Karl

[tex4ht] [bug #257] \includegraphics fails with LuaLaTeX backend

[Karl Berry]

Update of bug #257 (project tex4ht):

 Open/Closed:Open = Closed 

___

Follow-up Comment #5:

ok, thanks. i (finally) installed the change and updated tex live.
don't have the energy to talk to latex people about dvips.def, so closing i
guess ... if you have any time to report the issue to them, please do.


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?257

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #257] \includegraphics fails with LuaLaTeX backend

[Karl Berry]

Follow-up Comment #3, bug #257 (project tex4ht):

why shouldn't the problems be fixed in the latex drivers?  what makes any of
this htlatex-specific?  just trying to understand.

___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?257

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #260] Hnewline inserts a spurious space character

[Karl Berry]

Follow-up Comment #2, bug #260 (project tex4ht):

Thanks.  My only concern is that seems like such an obvious mistake, I wonder
if it is really a mistake.  I wonder if it used somewhere else and the space
is somehow desired.  Anyway, I'll look/apply when I have a chance (next
week).


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?260

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #257] \includegraphics fails with LuaLaTeX backend

[Karl Berry]

Follow-up Comment #1, bug #257 (project tex4ht):

as you say, evidently the problem has nothing to do with tex4ht. 

shouldn't those rules be added to latex's dvips.def, or something in latex be
changed so that dvilualatex uses a different driver that can do the right
thing?


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?257

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

Re: [tex4ht] Huge update of tex4ht-fonts-noncjk.tex

[Karl Berry]

for example I've tried to make fonts for `LGR` fontenc 

Looks like Eitan defined some lgr-related aliases for libertine, e.g.,
tex4ht/ht-fonts/alias/libertine/fxlri-xl-lgr.htf
contains the two lines:
---
.fxlr-xl-lgr
htfcss: fxlri-xl-lgrs font-style:italic;
---

So maybe other fonts can point to .fxlr-xl-lgr?

Also, FWIW, the gfs fonts (gfsdidot, gfsbodoni, etc.) support LGR, also
cbfonts.  They don't have htf files, but maybe htfgen could actually
work.  I know a couple of good people who can answer Greek-specific
questions (but know nothing in particular about tex4ht), if they can help.

Thanks,
Karl

Re: [tex4ht] Huge update of tex4ht-fonts-noncjk.tex

[Karl Berry]

Hi Michal,

(Sorry for the delayed reply.)

Lua file, sample TeX file and patch for tex4ht-fonts-noncjk.tex are
attached.

Fantastic.  Committed (r150).  I took the liberty of renaming the lua
and tex to t1fontmake.lua and t1fontsample.tex, hoping that will help
find them in the future.  I also added most of your email message to
tex4ht-fonts-noncjk.tex as commentary in that chapter.

I'll install all the new light htf files in TL when updates resume there.

Huge update

Indeed.  It would be nice to split up the huge source files into smaller
pieces.  It gets hard to figure out what is in them.  

For instance, looking at where the \Chapter commands are in noncjk, it
looks like the Adobe chapter deserves its own file.  And your new
Converted chapter could be its own file too.  Maybe ...

As for other support, it seems nothing comes easy.  For instance, tfm
names *-ot1.tfm (LaTeX name) should correspond to *7t.htf (fontname
name), but the only non-alias *7t.htf I see are:
  ht-fonts/unicode/adobe/courier/pcrr7t.htf - monospace
  ht-fonts/unicode/adobe/courier/pcrrc7t.htf - monospace, small caps?
  ht-fonts/unicode/adobe/times/ptmrc7t.htf - regular + small caps
  ht-fonts/unicode/adobe/times/ptmri7t.htf - italic

Why italic?  No idea.  And these might well be specially for the Adobe
base35 fonts, despite the name.  And since there are no comments
explaining what the encoding actually is, it will be laborious to
discover where the differences are.

The Cyrillic encodings *t2a, t2b, t2c, x2, might correspond (somewhat)
to existing *z.htf files.

Can we not generate .htf files from .enc files?  In the new font
packages, there should be an enc file for every user-intended tfm,
defined in the .map file in the package.

Anyway. Just stray thoughts.  Thanks so much for all your work,
Karl

[tex4ht] [bug #252] tex4ht doesn't work with latest versions of biblatex/biber

[Karl Berry]

Follow-up Comment #4, bug #252 (project tex4ht):

just to mention, this was also reported at
http://tug.org/pipermail/tex-live/2015-May/036851.html.

cvr, i hope it will not be too much trouble to update the biblatex+biber
support for the new version, when you have a chance. and that all the testing
infrastructure you built works out ...


___

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

[Karl Berry]

Follow-up Comment #6, bug #252 (project tex4ht):

or you can get them as part of the tl pretest image, if you want
(http://tug.org/texlive/pretest.html). might or might not be easier ...

(i suspect we will make this be the public release of tl'15 in another couple
of days, btw. no critical problems have been found since it was frozen a few
days ago.)

karl


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?252

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #253] Problems with fontenc and small-caps

[Karl Berry]

Update of bug #253 (project tex4ht):

 Open/Closed:Open = Closed 

___

Follow-up Comment #4:

Hi Michal - you are a wizard :).  installed in tex4ht; will install in tex
live after we unfreeze there.

it looks like the new output files are
tex4ht.dir/texmf/tex4ht/ht-fonts/alias/ec/eccc.htf
tex4ht.dir/texmf/tex4ht/ht-fonts/unicode/ec/eccc-uni.ht

does that sound right? (and no existing files were changed)

thanks so much, as ever.


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?253

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

Re: [tex4ht] TeX4ht warning --- Cannot determine size of graphic in svg graphics. Does tex4ht support bounding box on svg?

[Karl Berry]

TeX4ht needs .eps format of
the figure since it works with dvips graphics driver and hence cannot
accept any other graphics file format.

I use png and jpg with tex4ht all the time.  tex4ht.env has rules to
convert them on the fly (highly problematic in itself, but anyway).

I see a rule in tex4ht.env for svg using dvips (??) and then pstoedit.
Maybe that is what failed for Nasser, or maybe it never got run.  (It is
darn hard to figure out what parts of tex4ht.env are executed on any
given run, so far as I've ever been able to discern.  Maybe I am missing
it in the logs ...)

k

Re: [tex4ht] tex4ht.c compiling

[Karl Berry]

$ gcc -DHAVE_DIRENT_H -DKPATHSEA -lkpathsea tex4ht.c -o tex4ht

did you put the binary into place in the tl tree?

trying to use it from some separate location will surely require lots
more configuration (that i don't have any recipes for ...).

that's my first thought.

[tex4ht] [bug #252] tex4ht doesn't work with latest versions of biblatex/biber

[Karl Berry]

Follow-up Comment #2, bug #252 (project tex4ht):

michal - indeed, newer versions of biber and biblatex are in the tex live
pretest (http://tug.org/texlive/pretest.html), and the upstream sourceforge
project. i am not at all surprised that the current support does not work,
since the changes were (i gather) major.

___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?252

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #248] sometimes, oolatex may failed when \vskip nested inside \textsf{}

[Karl Berry]

Follow-up Comment #4, bug #248 (project tex4ht):

Thanks for the suggestion.  Let's see what Michal thinks.
A couple stray thoughts:

This would have to affect all \text... font commands.  There's nothing special
about \textsf.

Using \everypar seems potentially problematic to me, due to interactions with
other paragraph things.  It's a known difficulty with \everypar.

It is bizarre that LaTeX rejects \par inside \text... but accepts \vskip.  But
since it is allowed, it does seem that tex4ht should not choke on it, no
matter how illogical.

Does it matter if the \vskip is actually respected inside the \textsf?  What
if we made \vskip a no-op inside those commands?  Then at least it wouldn't
cause an error.

___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?248

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #247] mk4ht oolatex failed to process math formula when wrap fig has been loaded

[Karl Berry]

Update of bug #247 (project tex4ht):

 Open/Closed:Open = Closed 

___

Follow-up Comment #4:

thanks, all sounds good, installed in tex4ht and tex live.  did not look into
\WFclear calls :(.




___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?247

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #247] mk4ht oolatex failed to process math formula when wrap fig has been loaded

[Karl Berry]

Follow-up Comment #2, bug #247 (project tex4ht):

(sorry for the delayed reply.)

hmm. can we make the \par omission conditional on oo somehow? looking at that
code, it seems to me that the \par could be having a real effect on the
regular processing. i don't have an actual case at hand, but it is precisely
these cases where \everypar is being tinkered with, etc., that it can be
crucial.  i don't see anything else forcing tex into vertical mode if \WF@box
is void.  and \par is special in latex besides, so ...

it seems to me that the real problem here is that either
(a) a paragraph is not being opened with the formula, which it should be,
and/or 
(b) \par is generating an end-of-paragraph even when no paragraph has been
opened.

wdyt?

thanks,
k


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?247

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #245] Spanish babel

[Karl Berry]

Update of bug #245 (project tex4ht):

 Open/Closed:Open = Closed 

___

Follow-up Comment #1:

installed in tex4ht+tl. thanks as ever.


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?245

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #240] Images in subdirrectories not included correctly in the ODT output

[Karl Berry]

Update of bug #240 (project tex4ht):

 Open/Closed:Open = Closed 

___

Follow-up Comment #3:

installed in tex4ht and tl, thanks as always.


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?240

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

Re: [tex4ht] \:temp{rm}

[Karl Berry]

patch for tex4ht literary
sources and modified scr*.4ht files 

I installed this update in tex4ht and TeX Live.  Thanks as always.

[tex4ht] [bug #198] Support for quoting package

[Karl Berry]

Update of bug #198 (project tex4ht):

 Open/Closed:Open = Closed 

___

Follow-up Comment #1:

i (finally) added your quoting.4ht to tex4ht-4ht.tex, and committed it to TL. 
Thanks Michal.


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?198

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #241] grave accent letter ` (hex 60) changes to left single quotation mark (hex 0xE2 0x80 0x98)

[Karl Berry]

Update of bug #241 (project tex4ht):

 Open/Closed:Open = Closed 

___

Follow-up Comment #1:

as discussed on the mailing list, i think there is nothing to change here. the
input needs to specify a grave if that's what the output should be ...


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?241

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

Re: [tex4ht] [bug #242] Spurious semicolon produced by \textregistered command

[Karl Berry]

so this is the other approach, with extracting of
problematic code to standalone files. I figured out that there is also
problem with some Russian accents. patch is attached.

Most excellent!  I installed the changes and updated tex4ht and TL.

K

Re: [tex4ht] [bug #242] Spurious semicolon produced by \textregistered command

[Karl Berry]

compilation time is about 50% longer on sample document, 

Too bad.  

conditional including of latin1 file, 

Sounds worth looking into ...

Thanks,
K

Re: [tex4ht] [bug #242] Spurious semicolon produced by \textregistered command

[Karl Berry]

+require luatexbase.mcb

By the way, I didn't see this file in the patch (or in TL).
Not that it matters if we go the other route.

+luatexbase.add_to_callback(open_read_file, patch_latin1, 

1) For what it's worth, luainputenc.lua uses process_input_buffer instead
of open_read_file.  I don't know if performance is better.

2) Isn't the whole issue about Latin 2, not Latin 1?

K

Re: [tex4ht] [bug #242] Spurious semicolon produced by \textregistered command

[Karl Berry]

Oh, I don't get such huge diff, see the attachment.

Hmm.

caused compilation errors on tex4ht-html4.tex

Yeah, that's probably what's going on.  I'll work on it again
when I have a chance.

it is: http://www.ctan.org/pkg/tex4ht

Oops, I forgot that we moved it to obsolete.

but it seems to be really old version with obsolete message, but

It's the last release Eitan made.  We've never managed to make another.

Moving to /obsolete is usual for CTAN, though I suppose I could ask them
to delete it completely.

sometimes people try to install it, I am afraid

Really?  It never occurred to me that anyone would be crazy enough to
get that obviously-ancient tex4ht from CTAN and try to do anything with
it.  Using Eitan's packages was never the easiest thing to do ...

Thanks,
K

Re: [tex4ht] [bug #242] Spurious semicolon produced by \textregistered command

[Karl Berry]

Of course.  We have several of Eitan's releases, including that last
one, archived permanently on tug.org
(ftp://tug.org/mirror/www.cse.ohio-state.edu/~gurari/TeX4ht/*.zip at the
moment), regardless of anything else that happens.

Karl

Re: [tex4ht] [bug #242] Spurious semicolon produced by \textregistered command

[Karl Berry]

Hi Michal,

don't you mean CTAN version? 

No, I meant what I said, though I wasn't clear.  See following:

I though TL got updates.

Yes, I have been installing updated *.4ht files in TL as we make fixes
(ever since Eitan).

However, in the particular case of html4.4ht, there are significant
differences between what is in TL and what is generated from our current
source (you can do the diff as well as I can, but attached anyway).
It seems a whole chunk of code is missing.

I'm not sure at what point the differences started happening, but I kind
of suspect with TL14 or maybe TL13.  I did do a few previous updates to
html4.4ht over the past few years, so I suspect they were ok until then.

I think it should be safe to update CTAN as well, 

tex4ht has never been on CTAN.  Eitan never uploaded it there or made it
feasible for them to mirror.  Maybe one day.

so Miktex can be updated as well.

Christian (Schenk, aka MiKTeX) can get the updated *.4ht files from TL.
Whether he actually does for tex4ht, I don't know, but I have the
impression that he does get at least some stuff from TL.

I'll answer separately about latin2.

Thanks,
Karl



html4.dif.gz
Description: Binary data

Re: [tex4ht] [bug #242] Spurious semicolon produced by \textregistered command

[Karl Berry]

characters which should be replaced with entites in \url commands.

I think that's right.

this declaration is used only when `url-il2-pl` command line option is
used. not all special characters are declared. now, the problem is
with lualatex, as it is unicode engine, it reports invalid utf-8
sequence even if it doesn't use url-encoders at all.

as it is unlikely that anybody uses still latin2 encoding and special
characters in urls at the same time, and given that list of these
escaped special characters isn't comprehensive anyway, maybe we should
take that away? because it causes compile errors every time tex4ht is
used with lualatex.

Oh.  Clearly we need to solve it somehow, but I don't much like the idea
of getting rid of functionality, even something as obscure and probably
little-used as this.  Plenty of people still use Latin N encodings, and
there is an active TeX community in Poland -- I surmise that's who asked
for that option in the first place.

LuaTeX can certainly read files in any encoding, including plain bytes,
not just UTF-8.  I'm afraid I don't have any recipes at hand, though
it seems like it should be doable.

But a simpler idea comes to mind: how about replacing the problematic
characters with TeX's ^^xx notation?  I'm not sure if the conversions
will happen at the right time, given that \url is changing everything
around anyway, but we can wait and see if anyone notices.  At least it
would go through at the input level and is one step beyond just deleting it.

Another idea is to move that chunk of input to a separate file, which
only gets read when that option is in effect.

Thanks,
Karl

Re: [tex4ht] [bug #241] grave accent letter ` (hex 60) changes to left single quotation mark (hex 0xE2 0x80 0x98)

[Karl Berry]

if my system will work, we may process all fonts in texmf tree. but
manual testing of the results will be needed I am afraid, and that
would be really huge task.

Testing every glyph in every font is not required to have something
useful.  If your method creates a decent first attempt for them, we can
post those files, people can use them and report bugs.  Occasional, or
even not-so-occasional, mistakes are inevitable and expected.  As you
noted, even in Eitan's files, after all.

Thanks Michal.

K

Re: [tex4ht] [bug #241] grave accent letter ` (hex 60) changes to left single quotation mark (hex 0xE2 0x80 0x98)

[Karl Berry]

Hi Nasser and all,

I don't think it would be right to change cmtt10.htf.  What is at
position 0x60 of cmtt10 is, in fact, a directed left quote, not a grave
accent.  The fact that the standards committees screwed over all us
helpless users by making that plain ASCII character into a useless
standalone accent does not change Knuth's fonts.

What's in the PDF file has to correspond to the fonts used by the
document.  Now, what gets copied/pasted from a PDF is another matter
entirely.  Different viewers do different things there.

I realize full well that when you insert an ASCII 0x60, what you
presumably see on your screen is a grave accent (I don't, but that's
another story).  I realize full well that that is what ASCII defined at
that position.  But that is not what TeX (or, more precisely, the cm
fonts) does (do), by default, and therefore tex4ht follows suit.  That
seems undoubtedly the correct behavior to me.

So, if you want to change it, you should change it at the TeX level, and
then tex4ht should do what you want.  Michal explained how to do that
for LaTeX.  (Aside: In Texinfo, I created all kinds of stupid options so
people could get the stupid grave accent in their output, etc.  As I
expect you're aware, there is a similar issue with 0x47 being a directed
right quote in CM and a useless straight quote in the standards.)

Best,
Karl

[tex4ht] [bug #240] Images in subdirrectories not included correctly in the ODT output

[Karl Berry]

Follow-up Comment #1, bug #240 (project tex4ht):

hi michal - sounds great. my only comment is, why the Pictures/ subdirectory
in the first place?  seems like that name should be configurable as well.

regarding tex4ht.env, this is a different topic, but do we really have to have
different .env's for unix and windows?  as i recall, one of my tex live
colleagues insisted on this many years ago for the sake of some very small
difference.  unfortunately, diffs don't show anything obvious.

anyway, the near-total redundancy (even in tex4ht-env.tex!) is awful. at the
very least, the windows .env should just somehow include the unix one and then
override anything that is needed.
wdyt?

thanks,
k


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?240

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #223] Typo in tex4ht-annotated-source.tex

[Karl Berry]

Update of bug #223 (project tex4ht):

 Open/Closed:Open = Closed 

___

Follow-up Comment #1:

Hi Vincent - finally installed this typo fix (and fixed a bunch of other typos
in the tex4ht/doc directory at the same time.  just don't start looking for
typos in tex4ht/lit, they are everywhere ...)

k


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?223

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #231] eso-pic failure

[Karl Berry]

URL:
  http://puszcza.gnu.org.ua/bugs/?231

 Summary: eso-pic failure
 Project: tex4ht
Submitted by: karl
Submitted on: Thu 09 Oct 2014 08:55:49 PM EEST
Category: None
Priority: 5 - Normal
Severity: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

Regarding http://tug.org/pipermail/tex4ht/2014q3/001046.html, the author
reported in separate email that the culprit was \usepackage{eso-pic} -- this
results in the numerous empty picture complaints from tex4ht.





___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?231

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

Re: [tex4ht] bug of empty picture

[Karl Berry]

mk4ht htlatex main.tex html,mathplayer,info

Please post the contents of main.tex.

Best,
Karl

Re: [tex4ht] Small caps: LibreOffice

[Karl Berry]

Hi Guido - sorry, I have no idea how to tackle this, but there's no way
to even begin without an example document (the smaller the better).  Can
you send one, please?

Thanks,
K

Re: [tex4ht] [bug #224] package empheq does not work with tex4ht, ! Missing } inserted

[Karl Berry]

I clicked on add comment and pasted the latex code, but looking
at it in the email below, it removed all the \ from the code
I pasted in the comment window. So all the latex commands
below do not have the \.

I see the backslashes at https://puszcza.gnu.org.ua/bugs/?224.
And when I submitted a test comment there, the \ was in the email I got,
too.  Just maybe it's a bug in your mail reader?  Seems very unlikely,
but I can't think of another explanation.

k

Re: [tex4ht] tex4ht support for Non-Breaking Space according to \quad and \qquad etc..

[Karl Berry]

Hi Michal,

\Configure{qquad}{\HCode{\string\#x00A0;}}

Wouldn't it be better for \qquad to actually insert 2em, as in
  span style=width:2emnbsp;/span
(css out of my head, probably wrong, but you get the idea.)
Likewise \quad - 1em.

Also, it's not clear to me why it should be unbreakable.  It's not
unbreakable in (La)TeX.

Maybe new configuration, like
\Configure{thinspace-text} should be provided instead in text mode.

I guess.  One way or another, ideally \, would insert \thinspace (1/6em)
in text, since that'what it does in LaTeX.  \, only works in math in
plain TeX, but tugboat and other plain styles allow it to work in text
too, so why not allow it there too ...

Can you hack up a patch, perchance?

I've also found some really weird behavior of tex4ht with -utf8
option, 

(I imagine character set bugs are endless.)  I don't see anything
obvious in the binary itself.  My first suspicion is that it is a
consequence of the lengthy chain of configuration files and/or in one of
the scripts that gets called :(.

thanks,
karl

[tex4ht] [bug #205] problem with htlatex and KOMA-Script

[Karl Berry]

Update of bug #205 (project tex4ht):

 Open/Closed:Open = Closed 

___

Follow-up Comment #2:

Thanks as always, Michal.  Committed.  

Putting everything into one patch file is perfect.  You might as well put your
own name in the ChangeLog entry since you are doing the work :).  (I changed
this one; no good reason why I didn't do that in the previous ones.)

For yet more extra credit, please see the tweaks I am making to the file
headers (generated by, copywrite, etc.) -- annoying but the end result is
better.  But if you'd rather leave that junk for me, that's fine too :).  The
real work is the important part, of course.

Thanks again,
Karl



___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?205

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #214] tex4ht + hyperref + mwbk + secnumdepth issue

[Karl Berry]

Update of bug #214 (project tex4ht):

 Open/Closed:Open = Closed 

___

Follow-up Comment #2:

Thanks to both of you. I installed the patch as given (worked for me) in
tex4ht-4ht.tex and updated the tex4ht and tex live repositories.

___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?214

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #219] tex4ht mathml invalid text-align css attribute value

[Karl Berry]

Update of bug #219 (project tex4ht):

 Open/Closed:Open = Closed 

___

Follow-up Comment #4:

hi chris - thanks for doing all the work. i installed the patch and updated
the tex4ht and tex live repositories.

the | is set to be an escape character (catcode 0) in that context.  (in other
places, ` is an escape.)  all unnecessarily arcane as far as i can tell, but
that's how it appears to be.

karl


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?219

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #219] tex4ht mathml invalid text-align css attribute value

[Karl Berry]

Follow-up Comment #1, bug #219 (project tex4ht):

thanks for the report. any suggestions on what should be used instead of
text-align:axis nowadays? or just delete it?  this should be trivial to change
once we figure out what to do.



___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?219

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #214] tex4ht + hyperref + mwbk + secnumdepth issue

[Karl Berry]

Follow-up Comment #1, bug #214 (project tex4ht):

hi sylwester - thanks for the report and patch.  i'll take a look and most
probably make your change as soon as i can.  (next week, hopefully.)

___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?214

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #211] fancyvrb/alltt monospace by default

[Karl Berry]

URL:
  http://puszcza.gnu.org.ua/bugs/?211

 Summary: fancyvrb/alltt monospace by default
 Project: tex4ht
Submitted by: karl
Submitted on: Thu 03 Apr 2014 09:38:03 PM EEST
Category: None
Priority: 5 - Normal
Severity: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

want typewriter by default for fancyvrb and alltt.
(noticed in boris's tb109reviews-xie output)

div.fancyvrb {font-family:monospace}
div.alltt {font-family:monospace}





___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?211

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #212] urls mishandle _ and #

[Karl Berry]

URL:
  http://puszcza.gnu.org.ua/bugs/?212

 Summary: urls mishandle _ and #
 Project: tex4ht
Submitted by: karl
Submitted on: Thu 03 Apr 2014 09:39:54 PM EEST
Category: None
Priority: 5 - Normal
Severity: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

in tb109reviews-xie, there is a spurious _ in the visible text of reference
[7]:
 http://tug.org/TUGboat/tb31-_2/tb98ziegenhagen.pdf
although the target of the link is correct (no _).
Input from bbl was just:

\newblock \url{http://tug.org/TUGboat/tb31-2/tb98ziegenhagen.pdf}.

Boris also mentions:

]the # character] in URLs is not
translated properly, so I [need] to write something like
\href{../index.html\#xie-knitr}{\bookinfo} instead of
\href{../index.html#xie-knitr}{\bookinfo}





___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?212

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #208] lit/Makefile has extra space in latex argument confusing MikTeX latex

[Karl Berry]

Follow-up Comment #2, bug #208 (project tex4ht):

Hi Vincent - well, thanks for the report and patch, but not dequoting is a
fundamental discrepancy between shells.  I have no intention of trying to
support DOS, Windows, or anything else Microsoft.  If you want to, ok, but
otherwise, consider it unsupported.

I wrote lit/Makefile to be a convenience on Unix (and it is far from
complete); Eitan never had a Makefile at all. (Sigh.)

As far as the patch goes, htlatex is just one of many scripts.  And patching
it directly isn't possible, since those scripts are all generated from
tex4ht-mkht.tex (and other things?) in some process I haven't internalized. 
So I'm afraid I can't even tell you for sure the actual source files that need
to be changed.

All the Unix scripts have quoting problems too.  It's all a gigantic mess and
is one of the lowest-priority things to even look at :(.

  sorry,
karl


___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?208

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #200] fmtcount tex4ht conflicting

[Karl Berry]

Follow-up Comment #4, bug #200 (project tex4ht):

installing from source is likely to be a tremendous source of problems and
delays, as you have discovered.  since we have never done that and the
infrastructure simply isn't there.

what i would suggest is to find the right source file (tex4ht-4ht.tex?) and
post (or send me) the change to that file; then I can regenerate the derived
files and install the fix.  (You can also try regenerating it by hand and
maybe that will work.)

Thanks for all your efforts.

karl

___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?200

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #209] mathml, multline, pmatrix, easybma

[Karl Berry]

URL:
  http://puszcza.gnu.org.ua/bugs/?209

 Summary: mathml, multline, pmatrix, easybma
 Project: tex4ht
Submitted by: karl
Submitted on: Fri 07 Mar 2014 03:17:12 AM EET
Category: None
Priority: 5 - Normal
Severity: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

(inserting in bug tracker)

Date: Tue, 4 Mar 2014 23:25:58 -0600
From: Nasser M. Abbasi n...@12000.org
To: tex4ht@tug.org tex4ht@tug.org
Subject: [tex4ht] fyi, error with mathml switch, question posted

this is just FYI;

I think there is a problem with tex4ht when compiling a small
example using mathml mode.

Easier to post this question on tex exchange (screen shots).
But thought some here might be interested to know about it.

http://tex.stackexchange.com/questions/163746/tex4ht-compile-error-using-mathml-switch-using-multline-with-pmatrix-and-easybma

--
\documentclass{article}
\usepackage{amsmath}
\usepackage{easybmat}
\begin{document}

\begin{multline*}
\bgroup
\renewenvironment{pmatrix}{\left(\begin{BMAT}(@){c.c}{c.c}}
{\end{BMAT}\right)}
\begin{pmatrix}
A  B\\
C  D
\end{pmatrix}
\egroup
\end{multline*}
\end{document}

htlatex foo.tex htm,mathml

(/usr/local/texlive/2013/texmf-dist/tex/generic/tex4ht/html4-uni.4ht))
(./foo.aux)
l.16 --- TeX4ht warning --- \halign translated into linear text ---
! Missing # inserted in alignment preamble.
to be read again

l.16 \end{multline*}
?
-

thank you,
--Nasser





___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?209

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

[tex4ht] [bug #207] siunitx mathml

[Karl Berry]

URL:
  http://puszcza.gnu.org.ua/bugs/?207

 Summary: siunitx mathml
 Project: tex4ht
Submitted by: karl
Submitted on: Mon 24 Feb 2014 01:49:24 AM EET
Category: None
Priority: 5 - Normal
Severity: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
Originator Email: 
 Open/Closed: Open
 Discussion Lock: Any

___

Details:

http://tex.stackexchange.com/questions/161907/siunitx-package-use-with-tex4ht-and-generation-of-invalid-mathml-for-units

?





___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?207

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

Re: [tex4ht] [bug #205] problem with htlatex and KOMA-Script

[Karl Berry]

For some reason, quite a few mails related to tex4ht are sent to address
puszcza-hack...@gnu.org.ua

Sergey, I believe this is happening because the bug system on puszcza is
automatically using that address when it sends out notification email.
Not because of any individual's aliases or actions.

Specifically, when someone submits a bug, the notification email comes
in looking like this:

  From: Karl Berry puszcza-hack...@gnu.org.ua
  To: Karl Berry k...@freefriends.org, tex4ht@tug.org

Then people just reply-to-all as usual, which seems a perfectly
reasonable thing to do to me, and hence puszcza-hackers gets involved.
I think the forge code needs to use the person's email address in the
From: line as well as the To: line.  (Or an invalid generic address,
instead of a real one.)

Let me know if I'm missing something.

Karl

P.S. The same thing happens on Savannah, except that there the generic
address is configured to be invalid.nore...@gnu.org, replies there
don't go anywhere.

Re: [tex4ht] tex4ht vs pgf

[Karl Berry]

Subject: [tex4ht] tex4ht vs pgf

Thanks for these two reports, Victor.  If you can come up with fixes, so
much the better :).  Otherwise, CVR or me or someone will look as soon
as we have time.  I know CVR and I are embroiled in non-tex4ht matters
for some time yet.

Best,
karl

[tex4ht] [bug #201] Use of latexmk is preferable for documentation generation

[Karl Berry]

Update of bug #201 (project tex4ht):

 Open/Closed:Open = Closed 

___

Follow-up Comment #1:

Hi Vincent - if you're talking about the tex4ht documentation, well, latexmk
is included in TeX Live, but I don't want to depend on it (or any such tool)
for tex4ht.  I'm not sure why not, exactly, but that's how I feel :).  I will
fix it at some point.  What's in the repository now is there purely for
development purposes.  It needs a more or less infinite amount of work.

Thanks,
Karl



___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?201

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

Re: [tex4ht] [bug #188] adding support for multicols in htlatex

[Karl Berry]

When will this new update become part of tex4ht
included in texlive itself?

I've installed the changes in TeX Live now; assuming tonight's update
goes ok, you should be able to get it with tlmgr in a day or two.  Not
that there's any need for you to do so since you already installed the
files by hand.

how would one know if this fix is there or not?

By looking at the \version date at the top of multicol.4ht and html4.4ht.

Best,
Karl

Re: [tex4ht] future support for multicols in htlatex?

[Karl Berry]

http://www.12000.org/my_notes/faq/LATEX/html_and_latex.htm

Thanks again for Jagath's time on this to help make this feature
much easier to use until a final offical support for multicol is added
in tex4ht.

Jagath, could you possibly prepare it as a patch to the lit/*.tex
sources in the tex4ht svn repository?

We need such contributions (and contributors) to the tex4ht code, so CVR
doesn't have to do everything!

Thanks,
k

Re: [tex4ht] How to insert HTML code at any location in the generated HTML file?

[Karl Berry]

Runaway argument?

I see CVR solved your problem with an environment.  That's good (maybe
we should add that environment in general), but this error indicates the
problem is simply having a blank line (\par) in the argument, and we
should just make \HCode \long in order to allow it.  (I admit I didn't
actually check if something weirder is going on.)

CVR, wdyt?

k

Re: [tex4ht] Collision of /usr/bin/ht with HT Editor

[Karl Berry]

Hi Alexey - 

I'm sympathetic to the problem but don't see a good solution from this
side.  The ht executable has been since the beginning of tex4ht -- 15
years or so.  I don't want to remove it now at this late date.  If Eitan
had asked me in 1999 I would have told him no two-letter names, but he
didn't :).  (Ditto the HT Editor people -- any project thinking it can
use a two-letter command name at this point in Unix's history is, IMHO,
just plain wrong.)

What distros choose to do is not up to me, but I don't want to remove ht
from TeX Live.

(CVR, if you have any ideas on this, of course please let me know.)

Best,
karl

Re: [tex4ht] biblatex incompatibility

[Karl Berry]

CVR made extensive changes to biblatex.4ht a couple weeks ago.  Just in
case you weren't using the current version from TeX Live, please try
that.  (It's just the one file.)
http://tug.org/svn/texlive/trunk/Master/texmf-dist/tex/generic/tex4ht/biblatex.4ht

k

Re: [tex4ht] Detecting TeX4ht

[Karl Berry]

Hi Denis,

  \newif\ifhttex \ifx\HCode\undefined \httexfalse \else \httextrue \fi

Sorry for the late reply.  I just wanted to chime in that I also have
always used \ifx\HCode.

Although I understand and even agree with Eitan's response in principle
(to use configuration files), in practice it is just too much trouble.
And configuration files are barely documented at all, as far as I know.

Best,
karl

Re: [tex4ht] biblatex, biber, and htlatex

[Karl Berry]

I received http://von-wachter.de/dateien/for-biblatex-1-6/biblatex.4ht
on 14.11.2011 from Radhakrishnan. 

Fair enough :).

It is not yet at

http://svn.gnu.org.ua/viewvc/tex4ht/trunk/texmf/tex/generic/tex4ht/biblatex.4ht

Yes, so this is what I was remembering ... I was waiting for CVR's
confirmation/commit.

I hope it was all right to put in on the web. It works with biblatex 1.6.

It seems that what we really need is a biblatex.4ht that works with
biblatex 1.7, since that is what is in TL, and (as noted) it is hardly
trivial or desirable to downgrade.

I could easily be missing it, but I'm not seeing no specific bug report
regarding biblatex 1.7, just your report of failure.  Can you construct
the usual small test case / expected output vs. actual output / etc.
so CVR (or anyone :) has a chance of doing that?

Thanks,
k

Re: [tex4ht] biblatex, biber, and htlatex

[Karl Berry]

I too would like to know where the official newest version of
biblatex.4ht is to be obtained. I thought it should be at

http://svn.gnu.org.ua/viewvc/tex4ht/trunk/texmf/tex/generic/tex4ht/biblatex.4ht?view=log,

That is correct and has always been correct.  And when CVR posts a new
version there, I import it into TL (even though we've been unable to
make a full tex4ht release since Eitan died ... still in process).

http://von-wachter.de/dateien/for-biblatex-1-6/biblatex.4ht

Never seen that url before.  Don't recognize the name.  Nothing in the
file about who did it :(.

May I suggest that somewhere under http://www.tug.org/tex4ht/
instructions for using tex4ht with biblatex are posted? 

I have the impression that CVR has pending changes for biblatex.4ht and
was waiting for user confirmation on the fix.  Unfortunately I don't
have the bug report or fix at hand.

k

[tex4ht] [bug #132] Problem with biblatex+hyperref

[Karl Berry]

Follow-up Comment #4, bug #132 (project tex4ht):

You can send email to tex4ht@tug.org without registering an account.  Sorry
that wasn't clear.  And this is puszca, not savannah.  Anyway :).

As for the changes, well, they were all made for a reason.  Simply reverting
will presumably also revert back to the original problem.  I think we just
must wait for CVR (or anyone) to have a chance to investigate.  I don't :(.

Sorry for the null reply.

karl




___

Reply to this item at:

  http://puszcza.gnu.org.ua/bugs/?132

___
  Message sent via/by Puszcza
  http://puszcza.gnu.org.ua/

Re: [tex4ht] The need for STEM braille materials (slightly OT)

[Karl Berry]

TUG supports many specific project development and this is certainly one 
that is well worth it. 

If there was a developer who could get the job done, TUG could help
sponsor it.  We don't have anything like a real project budget, but a
couple thousand (max) would be doable.  The hard part, in my experience,
is finding people interested and capable of doing the work.

karl

Re: [tex4ht] unbalanced parentheses

[Karl Berry]

  http://www.albany.edu/~hammond/private/1108.5305.tex
  http://www.albany.edu/~hammond/private/1108.5305.xhtml

Thanks.  I will try to look.

for your example, \left(1,2\right]

Well, \left...\right can change what the output looks like, not
necessarily desirably.  But I take your point in general, certainly.

Thanks,
k

Re: [tex4ht] Output directory

[Karl Berry]

\Needs{mkdir -p mytmp}
\Needs{mv \jobname.{4ct,4tc,aux,css,dvi,idv,html,lg,log,xref} mytmp}

Sure, as long as \write18 is enabled, that's another way.  If you're
only using tex4ht on your own documents, that's ok, but it's much too
dangerous to enable by default.

Best,
k

Re: [tex4ht] Error in processing file with references

[Karl Berry]

 However, I don't seem to have any version from September.  What I have
 is from July.  CVR, could you send your latest to this list so everyone
 can see it, since I can't easily generate it right now?

Never mind.  I was looking at the wrong file.  The version now in TeX
Live and in tex4ht svn is indeed the September update.  CVR posted it to
the list in 
http://tug.org/pipermail/tex4ht/2010q3/000200.html.

Sorry,
karl