RE: any easy way to get Saxonica to output a different format XML header?

I'm a little surprised by the blank line - I'm not sure how its getting
there.

But I'm afraid the answer is no, there's no way of controlling this, short
of writing your own output method (which you can do by subclassing
XMLEmitter and overriding the relevant methods.) A better approach, if you
really can't fix the recipient code to follow the XML rules fully, would
probably be to put in a Perl script (or even a sed script) to massage the
output into the form that the recipient needs it.

I'm reluctant to start adding more serialization controls for this, because
it's so open-ended. Next thing, someone will be wanting spaces around the
"=" sign. The closest I might get is to define the various separators that
are used as protected fields in XMLEmitter so it's easier for a subclass to
override them.

Michael Kay
http://www.saxonica.com/
  

> -----Original Message-----
> From: saxon-help-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx 
> [mailto:saxon-help-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx] 
> On Behalf Of 
> alan.painter-Jdski0UBDJ4AvxtiuMwx3w@xxxxxxxxxxxxxxxx
> Sent: 24 June 2005 12:01
> To: saxon-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> Subject: [saxon] any easy way to get Saxonica to output a 
> different format XML header?
> 
> With this xsl:output instruction
> 
> <xsl:output method="xml" doctype-system="fsc_20.dtd" 
> encoding="ISO-8859-1"
> indent="yes" />
> 
> 
> I'm currently getting the XML header output by Saxonica in 
> this rough form:
> 
> <?xml version="1.0" encoding="ISO-8859-1"?>
> 
> <!DOCTYPE Fichier
>   SYSTEM "fsc_20.dtd">
> 
> So I have two newlines following the XML declaration and a newline
> in the middle of the DOCTYPE declaration.
> 
> I have a bad downstream client who wants to see the XML 
> declarations on the
> first line
> and the entire DOCTYPE declaration on the second line.  Is 
> there an easy
> way to
> get Saxonica to output this for me, or will I need to write some
> serialization code of my own?
> 
> thanks for help
> 
> -alan
> 
> 
> 
> ******************************************************************
> This message and any attachments (the "message") are 
> confidential and intended solely for the addressee(s). Any 
> unauthorised use or dissemination is prohibited. E-mails are 
> susceptible to alteration.Neither SOCIETE GENERALE nor any of 
> its subsidiaries or affiliates shall be liable for the 
> message if altered, changed or falsified.                     
>     ***************
> Ce message et toutes les pieces jointes (ci-apres le 
> "message") sont confidentiels et etablis a l'intention 
> exclusive de ses destinataires. Toute utilisation ou 
> diffusion non autorisee est interdite. Tout message 
> electronique est susceptible d'alteration.La SOCIETE GENERALE 
> et ses filiales declinent toute responsabilite au titre de ce 
> message s'il a ete altere, modifie ou falsifie.
> ******************************************************************
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> saxon-help mailing list
> saxon-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/saxon-help
> 




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click