Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 108484 - app-xemacs/psgml xml-namespace parsing problem
Summary: app-xemacs/psgml xml-namespace parsing problem
Status: RESOLVED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: XEmacs team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-08 06:18 UTC by Andreas Conz
Modified: 2006-11-11 01:29 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Conz 2005-10-08 06:18:56 UTC
The psgml package has problems recognizing xml nmaspace specifications

The parser is not able to recognize the : character used for separtion in the
<html xml:lang='en' > tag.

This leads to wrong behavior when indenting the following lines using the TAB
key (as seen in this example).

Reproducible: Always
Steps to Reproduce:
1. enter the following text into xemacs
<?xml version="1.0" encoding="UTF-8"?>
<html xmlns='asdasd' xml:lang='en' >
<head>
<title>Test</title>
<meta name="author" />
</head>
</html>

2. indent each line using the TAB key starting from the beginning
Actual Results:  
<?xml version="1.0" encoding="UTF-8"?>
<html xmlns='asdasd' xml:lang='en' >
      <head>
        <title>Test</title>
    <meta name="author" />
  </head>
</html>


Expected Results:  
<?xml version="1.0" encoding="UTF-8"?>
<html xmlns='asdasd' xml:lang='en' >
  <head>
    <title>Test</title>
    <meta name="author" />
  </head>
</html>


a solution to the problem is discussed at 
http://lists.xml.org/archives/xml-dev/199907/msg00243.html

the linenumber in the patch are not accurate because of its age
Comment 1 Hans de Graaff gentoo-dev Security 2006-11-11 01:29:10 UTC
I have just updated app-xemacs/psgml to version 1.44. I can't verify if this problem is fixed because I could not reproduce the issue and the code mentioned in the link you included has been changed quite a bit. Hopefully that means it is fixed. :-) 

Feedback about that would be appreciated.