Bug 540356 - & and & are treated as & during rendering
Summary: & and & are treated as & during rendering
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-XML-TreeBuilder
Version: rawhide
Hardware: All
OS: All
low
medium
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 657965
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-23 06:29 UTC by Sean Rogers
Modified: 2014-07-25 04:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-02 04:18:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
script displaying bug (854 bytes, application/x-perl)
2009-11-24 02:49 UTC, Jeff Fearn 🐞
no flags Details

Description Sean Rogers 2009-11-23 06:29:21 UTC
Description of problem:
When using the & or & entities in combination with other characters, it is sometimes incorrectly treated as an &, turning the letters that follow & or & into an entity.

Version-Release number of selected component (if applicable):
1.1

How reproducible:
Every time

Steps to Reproduce:
1. Use the following XML code in a DocBook doc:
< < &lt&#59; < <
2. Build using publican
  
Actual results:
Publican renders the following:
< < < < &lt;

Expected results:
Publican renders the following:
< &lt; &lt; &lt; &lt;

Additional info:
If actually trying to write the code for an element, the only possible solution is starting with an &amp; and ending with a &semi; , as shown above. For example, &amp;lt&semi;

Comment 1 Jeff Fearn 🐞 2009-11-24 02:49:11 UTC
Created attachment 373323 [details]
script displaying bug

Comment 2 Jeff Fearn 🐞 2009-11-24 02:51:46 UTC
(In reply to comment #0)
> Steps to Reproduce:
> 1. Use the following XML code in a DocBook doc:
> &lt; &#38;lt; &#38;lt&#59; &amp;lt; &amp;lt&semi;

BTW: this has two unescaped semi-colons in it:


&lt; &#38;lt; &#38;lt&#59; &amp;lt; &amp;lt&semi;
------------^---------------------^

It's still not handling #59 and #38 properly though.

Comment 3 Jeff Fearn 🐞 2009-11-24 06:10:13 UTC
Actually it handles &#38; fine, it's &#59; that is causing the issue. This is probably due to &#59; not being an XML entity. Further hunting required.

Comment 4 Bug Zapper 2010-04-28 11:25:47 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2010-06-28 15:30:12 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Jeff Fearn 🐞 2010-12-02 04:18:43 UTC
Finally! XML-TreeBuilder 4.0 is in rawhide, it deals with this issue.


Note You need to log in before you can comment on or make changes to this bug.