Re: preformatted text not handled properly

Hello Wolfgang,

On Wed, 28 Jun 2006 21:10:00 +0200
Wolfgang Jeltsch <wolfgang@jeltsch.net> wrote:

> 
> Am Freitag, 23. Juni 2006 15:18 schrieb Irene Vatton:
> > On Wednesday 21 June 2006 23:43, Wolfgang Jeltsch wrote:
> > > Hello,
> > >
> > > the document on
> > >
> > >     http://www.badgers-in-foil.co.uk/projects/docbook-css/cvsspam-doc.xml
> > >
> > > is a DocBook document which uses some cool CSS stylesheet for DocBook.
> > > However, when displayed in Amaya, one can see that Amaya doesn't seem to
> > > handle preformatted text as such.  The document is correctly displayed in
> > > Mozilla Firefox 1.0.4.
> >
> > It would be managed correctly if XML elements have a XML attribute
> > xml-space="preserve". The preserve constraint concerns the document contents
> > (spaces should be still preserved when the document is saved after an edit).
> > CSS concerns only its current presentation.
> 
> Thank you for pointing this out.  However, I experienced that Amaya killed all 
> newlines in preformatted text upon saving the file.  To reproduce this, 
> please first create a file with the following content (preferably without the 
> linebreaks and the indentation in the processing instruction):
> 
> 	<?xml version="1.0"?>
> 	<?xml-stylesheet
> 		href="http://www.badgers-in-foil.co.uk/projects/docbook-css/driver.css"
> 		type="text/css"?>
> 	<article>
> 	</article>
> 
> Then open this file in Amaya.  Now create a programlisting element.*)  Set 
> xml:space to preserve.  Enter some text containing line breaks.  If you save 
> the file, you can see that they don't occur in the file.

Indeed, the xml:space="preserve" attribute is correctly handled when a xml document is loaded and displayed , but not taken into account when an element with such an atttribute is edited (whatever the xml language).
I have added this problem in the open_bugs file.

> 
> > [...]
> 
> Best wishes,
> Wolfgang
> ____________________
> *) In order to do this, you probably first have to enter some character and 
> delete it afterwards since Amaya seems to be unable to create an element 
> otherwise.  This should maybe be changed.  In addition, it would be good if 
> the element types would appear strictly alphabetically ordered in the XML 
> Element type widget.

Added in the open_bugs file too. Should be easier to fix.

Thanks for the report,

-- 
  Laurent Carcone	
  carcone@w3.org              W3C/ERCIM
  +33 (0)4 76 61 52 67        INRIA Rhône-Alpes, 655 Avenue de l'Europe
                              38334 Saint Ismier Cedex - France

Received on Friday, 30 June 2006 15:04:32 UTC