Scala | 9 Aug 2010 09:28
Picon
Picon
Favicon

Re: [scala-bts] #1118: Represent empty XML elements in short form

#1118: Represent empty XML elements in short form
------------------------+---------------------------------------------------
Reporter:  brian0       |        Owner:  scala-xml_team
    Type:  enhancement  |       Status:  new           
Priority:  normal       |    Component:  XML support   
 Version:  Scala 2.8.0  |   Resolution:                
Keywords:  xml          |  
------------------------+---------------------------------------------------
Changes (by rytz):

 * cc: acruise (added)
  * owner:  acruise => scala-xml_team
  * status:  assigned => new

--

-- 
Ticket URL: <https://lampsvn.epfl.ch/trac/scala/ticket/1118#comment:12>
Scala <http://lampsvn.epfl.ch/trac/scala/>
Scala Programming Language
Scala | 9 Aug 2010 16:43
Picon
Picon
Favicon

Re: [scala-bts] #1118: Represent empty XML elements in short form

#1118: Represent empty XML elements in short form
------------------------+---------------------------------------------------
Reporter:  brian0       |        Owner:  scala-xml_team
    Type:  enhancement  |       Status:  new           
Priority:  normal       |    Component:  XML support   
 Version:  Scala 2.8.0  |   Resolution:                
Keywords:  xml          |  
------------------------+---------------------------------------------------

Comment(by acruise):

 Can I get some feedback on my patch?  It addresses this issue, adds
 another test, and is basically ready to commit.

--

-- 
Ticket URL: <https://lampsvn.epfl.ch/trac/scala/ticket/1118#comment:13>
Scala <http://lampsvn.epfl.ch/trac/scala/>
Scala Programming Language
Scala website | 21 Aug 2010 15:32
Picon
Picon

Mailing list reminder: Scala-xml

Welcome to the "Scala-xml" mailing list.

This automatic reminder is sent once a month to the list,
to keep subscribers up-to-date with the mailing list services,
and to help keeping the list on topic.

-------------------------------------------------------------------

The "Scala-xml" mailing list:

This is the main interest list for coders interested in using
the XML manipulation capabilities of Scala.

Topics appropriate to this list include:

 * The Scala XML infrastructure, bugs, development
 * How to use the Scala XML features while writing code

Use this list to discuss any topic related to the Scala/XML
interoperability.

-------------------------------------------------------------------

Other information:

There are several Scala lists devoted to individual topics (and
more may be created in the future). For the full list, please
see: http://www.scala-lang.org/node/199

Try to avoid cross-posting whenever possible. If you can, select
(Continue reading)

David Winslow | 26 Aug 2010 16:03
Picon
Gravatar

DTD with relative SYSTEM references

Hi all,


I have found some strange behavior related to DTD handling in the scala.xml package.

Context:
I'm dealing with stylesheets for map rendering.  Specifically, I want to create a conversion tool for importing stylesheets from Mapnik to GeoServer.  I am using the recently released stylesheets from http://open.mapquest.co.uk/ as a sample input to start.  These stylesheets are available on github at http://github.com/MapQuest/MapQuest-Mapnik-Style .

Problem:
The Mapquest styles are distributed across several files, using DTD declarations like:
<!ENTITY % entities SYSTEM "mapquest_inc/entities.xml.inc">
 
As a sort of #include mechanism.

Symptoms:
When I attempt to parse with scala.xml.XML.loadFile("mapquest-uk.xml") I get an exception: 
java.io.FileNotFoundException: /home/dwins/MapQuest-Mapnik-Style/mapquest_inc/mapquest_inc/layers-uk.xml.inc
 
The mapquest_inc segment of the path is duplicated.  Interestingly,  this is the second reference to a DTD file in the mapquest_inc/ directory; the first apparently succeeds.  If I modify the file to use absolute paths to reference the DTDs, then it succeeds.

When I attempt to parse with scala.xml.parsing.ConstructingParser.fromFile("mapquest-uk.xml", true), I simply get comments for all entity references indicating that the entity was unknown.

Moving Forward
I'd be happy to submit a patch for this if I knew where to look.  I've been poking around the sources a bit already, but I wasn't able to track down the problem further than what I described above.

thanks for any insight

--
David Winslow

Gmane