[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: weird formatting and characters with <xsl:text di

Subject: Re: weird formatting and characters with <xsl:text disable-output-escaping>
From: Spencer Tickner <spencertickner@xxxxxxxxx>
Date: Tue, 26 Apr 2005 15:10:55 -0700
weird text converter
Hi Michael and Wendell,

Thanks for the advice. I like Michael's idea of defining some form of
representation of the output and doing the final conversion with some
other language. Your serialization suggestion also sounds interesting
so perhaps I will spend a bit of time diving into that. Wendell as you
suggested xml can be imported into InDesign however I have found this
method to be problamatic and my end-users are used to placing tagged
text files into there various InDesign templates.

Also Michael mentioned using output-method="text" and "disable-output
escaping" this is what I tried to do in my original attempt, but came
up with badly formatted output. If you have a sec and check out my
original post maybe there is a way to get the text at least into some
nicely formatted form.

Either or, I appreciate all the advice and suggestions,

Spencer

On 4/26/05, Michael Kay <mike@xxxxxxxxxxxx> wrote:
> >
> > Shoot just realized we can't even do that as InDesign uses mandatory
> > nested tags to define paragraph styles, like <this is a tag<this is a
> > nested tag>>, so perhaps I will have to look at this all another way??
> >
>
> This is the general problem of generating output in a format that has a
> passing resemblance to XML but is not actually XML. There are a surprising
> number of such formats still in use (some of them, of course, are valid
> SGML). There are a number of choices available:
>
> (a) define an XML representation of the required output and generate that
> using XSLT. Then write a converter in some other language to convert this
> XML to the target form.
>
> (b) write a stylesheet that outputs text (xsl:output method="text")
>
> (c) write a stylesheet that outputs a mixture of XML and text (xsl:output
> method="xml" with disable-output-escaping). Messy but sometimes pragmatic.
>
> (d) implement a custom serialization method. If you have some Java skills,
> this isn't as daunting as it may sound, for example in Saxon you can do it
> by subclassing the serializer that comes with the product.
>
> The main thing is to try and keep the peculiarities contained to as small a
> part of your code as you can. I'd suggest going for (a) if you can.
>
> Michael Kay
> http://www.saxonica.com/

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.