[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: [xsl] Register Marks, Funny Character Problems


Subject: RE: [xsl] Register Marks, Funny Character Problems
From: Edward.Middleton@xxxxxxxxxxx
Date: Thu, 16 Jan 2003 16:15:13 +0900

Please give more details, how are you using XSL.  If you are only using XML then you have posted in the wrong list.

First question:

Do you really need 50MB of data or just a small fraction of it.   If you really need to transmit so much data, brack it up into smaller xml files.  If you only need a small fraction of it only convert that fraction to xml.  There are parsers that will handle large files but basically all they do is exchange memory usage for speed.  

Second question:

1. Work out what characterset is being used in your database and set the encoding correctly in your xml files.  You will also need to check that your parser can handles this encoding.
http://www.w3.org/TR/2000/REC-xml-20001006#charencoding

2. work out what characters are in the data and convert them to character references.
http://www.w3.org/TR/2000/REC-xml-20001006#sec-references


Edward Middleton

-----Original Message-----
From: Scott Purcell [mailto:spurcell@xxxxxxxxxxxxx]
Sent: Wednesday, January 15, 2003 11:40 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: [xsl] Register Marks, Funny Character Problems


Hello,

I have been given a project, in which I am creating xml files of data coming from our Oracle db. The files get quite large, as a xml document we have seen the ASCII files get up to 50MB. 

We are NOT using dom to assemble these xml files, due to the fact that dom puts the whole document into memory, and since this is a web app, will probably bring down the web server.

The developer created some class files and basically is creating the xml by printing the data to a text file.

First question: I know this is probably not the right way, but what should one do when the files get huge like this?

Second question: The way we are doing this, there are trademark, and register symbols in the database that are screwing up the xml when we try and parse it later.

Does anyone have any insight into this problem arena?


Thanks,
Scott

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list



Current Thread
Keywords
xml