bugtex4ht - Bugs: bug #248, sometimes, oolatex may failed when...

Show feedback again

You are not allowed to post comments on this tracker with your current authentification level.

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

Submitted by:  Rongsong Shen <shen390s>
Submitted on:  Fri Mar 27 14:38:13 2015  
Category: NonePriority: 5 - Normal
Severity: 5 - NormalStatus: None
Privacy: PublicAssigned to: None
Open/Closed: Open

(Jump to the original submission Jump to the original submission)

Thu Apr 9 22:05:40 2015, comment #6:

thanks. yikes. i don't know.

Karl Berry <karl>
Project Administrator
Thu Apr 9 13:21:27 2015, comment #5:

I can imagine only what suggests Karl - define some command to made dangerous commands no-op inside a group. Some example is attached.

(file #203)

Michal Hoftich <michal_h21>
Project Member
Wed Apr 8 21:14:22 2015, comment #4:

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.

Karl Berry <karl>
Project Administrator
Wed Apr 8 14:54:00 2015, comment #3:

Because pdflatex can accept \vskip inside \textsf{}
we may consider following proposal:
1. configure textsf to initial a flag to indicate that we have entered a new group and clear the flag that a new par has been generated

2. using \everypar to add a hook for a new par has been generated

3. In the hook of \everypar check whether we should generate the end of last par


Rongsong Shen <shen390s>
Tue Mar 31 15:04:22 2015, comment #2:


Seems you are right. We'd better not to use \par/\vskip or others inside \textsf{}.

Also, following code will be rejected by pdflatex:

This is line 1.

This is line 2.


Rongsong Shen <shen390s>
Sat Mar 28 14:51:41 2015, comment #1:

Do you have any reason to use \vskip inside of \textsf? what is going on here is that \vskip closes current paragraph and start a new one, but this causes invalid xml, as starting and closing tags are in different paragraphs.

only way to fix that is to reset configuration for `textsf with

this will use only formatting added in dvi postprocessing, instead of semantic tags.

but the correct solution is IMHO to not use \vskip inside of \textsf and other similar commands.

Michal Hoftich <michal_h21>
Project Member
Fri Mar 27 14:38:13 2015, original submission:

run mk4ht oolatex ex3 (see attached file for ex3.tex and error log)

Rongsong Shen <shen390s>


Attached Files
file #203:  hello.cfg added by michal_h21 (410B - application/octet-stream)
file #200:  ex3.tex added by shen390s (125B - application/x-tex)
file #201:  err.log added by shen390s (2kB - application/octet-stream)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by karl (Posted a comment)
  • -unavailable- added by michal_h21 (Posted a comment)
  • -unavailable- added by shen390s (Submitted the item)

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    3 latest changes follow.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu Apr 9 13:21:27 2015michal_h21Attached File-=>Added hello.cfg, #203
    Fri Mar 27 14:38:13 2015shen390sAttached File-=>Added ex3.tex, #200
      Attached File-=>Added err.log, #201
    Show feedback again

    Back to the top

    Powered by Savane 3.1-cleanup+gray