search

dquangsinh / fb2pdf

Automatically exported from code.google.com/p/fb2pdf
0 stars 0 forks source link

backslash quoting #2

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Underfull \vbox (badness 10000) has occurred while \output is active [127]
! Misplaced alignment tab character &.
l.2684 \textbackslash &
                        laquo;п║п©п╣я┬п╦я┌п╣, пЁп╣я─п╬п╦, п╫п╣я│я┐я┴п╦п╣ п╩я...

Produced on gumilev_sbornik_stihov.fb2.

Original issue reported on code.google.com by kroko...@gmail.com on 22 Feb 2007 at 5:57

GoogleCodeExporter commented 8 years ago 
file

Original comment by kroko...@gmail.com on 22 Feb 2007 at 5:59

Attachments:

GoogleCodeExporter commented 8 years ago 
The problem is not the backslash, but rather the double encoding of the << quote
(&amp; laquo;) in the source fb2 file. I'll see if I could find a good 
workaround.

Original comment by sudarkoff on 23 Feb 2007 at 5:02

GoogleCodeExporter commented 8 years ago 
Yes, backslash really was a problem. However, double-encoding is still a 
problem. And after giving it quite a bit 
of thought, I am now convinced that it is a bad idea to try to work around it 
as we might inadvertently break a 
perfectly valid text. For example &amp;amp; is a valid input and should produce 
\&amp; in the resulting TeX 
document. Plus, that extra space there -- it's just too broken!

Original comment by sudarkoff on 23 Feb 2007 at 9:03

GoogleCodeExporter commented 8 years ago 
I think fb2 document suppose to support XML entities and I implemented them. 
Looks
like they also use HTML entities and we need to support them as well.

Original comment by kroko...@gmail.com on 23 Feb 2007 at 5:39

GoogleCodeExporter commented 8 years ago 
I agree with your analysis.
I looked at the document: it has 

&amp; laqui;

We decode &amp; producing:

& laqui;

This is pretty much how it should look in resulting document. Only thing is 
missing
is quoting ampersand.

Original comment by kroko...@gmail.com on 23 Feb 2007 at 11:48

GoogleCodeExporter commented 8 years ago 
fixed.

Original comment by kroko...@gmail.com on 23 Feb 2007 at 11:59