Closed GoogleCodeExporter closed 9 years ago
file
Original comment by kroko...@gmail.com
on 22 Feb 2007 at 5:59
Attachments:
The problem is not the backslash, but rather the double encoding of the << quote
(& 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
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; is a valid input and should produce
\& 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
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
I agree with your analysis.
I looked at the document: it has
& laqui;
We decode & 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
fixed.
Original comment by kroko...@gmail.com
on 23 Feb 2007 at 11:59
Original issue reported on code.google.com by
kroko...@gmail.com
on 22 Feb 2007 at 5:57