[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 #248] sometimes, oolatex may failed when \vskip nested inside \textsf{}

[Rongsong Shen]

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

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

___

Reply to this item at:

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

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