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

2015-04-09 Thread Michal Hoftich
Follow-up Comment #5, bug #248 (project tex4ht):

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)
___

Additional Item Attachment:

File name: hello.cfg  Size:0 KB


___

Reply to this item at:

  

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



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

2015-04-08 Thread 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:

  

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



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

2015-04-08 Thread 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:

  

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



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

2015-03-31 Thread Rongsong Shen
Follow-up Comment #2, bug #248 (project tex4ht):

Michal,

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

Also, following code will be rejected by pdflatex:

\textsf{
   This is line 1.

   This is line 2.
}

Rongsong

___

Reply to this item at:

  

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



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

2015-03-28 Thread Michal Hoftich
Follow-up Comment #1, bug #248 (project tex4ht):

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 



Preamble{xhtml}
begin{document}
Configure{textsf}{}{}
EndPreamble


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.

___

Reply to this item at:

  

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



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

2015-03-27 Thread Rongsong Shen
URL:
  

 Summary: sometimes, oolatex may failed when \vskip nested
inside \textsf{}
 Project: tex4ht
Submitted by: shen390s
Submitted on: Fri 27 Mar 2015 04:38:13 PM 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:

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



___

File Attachments:


---
Date: Fri 27 Mar 2015 04:38:13 PM EET  Name: ex3.tex  Size: 125B   By:
shen390s


---
Date: Fri 27 Mar 2015 04:38:13 PM EET  Name: err.log  Size: 2kB   By: shen390s



___

Reply to this item at:

  

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