[tei-council] <rendition scheme="xslfo"> ??? (fwd)

[David Sewell]

>From John Walsh. This answers my question, and suggests that there is no
need at this time to pursue an expansion of the content model of
<rendition> beyond the proposed @scope.

David

---------- Forwarded message ----------
Date: Thu, 26 Mar 2009 10:14:47 -0400
From: John A. Walsh <jawalsh at indiana.edu>
To: David Sewell <dsewell at virginia.edu>
Subject: Re: [tei-council] <rendition scheme="xslfo"> ???

David,
I helped put together the original <rendition>/@rendition proposals
for P5 and have been following this thread on the council list.The
thinking was that one could embed FO style syntax in <rendition>
without including full-blown FO XML.  For example:

<rendition xml:id="redhead">font-size="16pt" font-family="sans-serif"
color="rgb(255,0,0)"</rendition>

A transformation could then produce the valid FO XML a user might want
to use to generate output.
I realize the presence of things that look like attributes but aren't
might seem inelegant to some, but we see the same thing in processing
instructions. And of course the CSS fragments found in <rendition>
elements aren't by themselves valid CSS; similarly these fragments of
FO syntax in <rendition> are not valid FO XML, but in both cases the
CSS and FO fragments can be utilized in an XSLT transformation to
produce valid CSS or FO XML, respectively.

As to the issue of allowing full blown FO XML inside rendition, we did
not think of that. It's an interesting idea, but, as others have
pointed out, complicated.

Feel free to share my thoughts with the council if that would be useful.

John



On Thu, Mar 26, 2009 at 9:55 AM, David Sewell <dsewell at virginia.edu> wrote:
>
> To clear up any confusion, Brett in his SF ticket doesn't say anything
> about FO--he is just interested in more CSS support within <rendition>.
>
> However... if we truly want to allow <rendition> to contain arbitrary
> stylesheet language, should we in fact redefine its child content as
>
>  ( macro.limitedContent | macro.anyXML )
>
> ?
>
> I don't use FO enough to know how one might want to apply it to a TEI
> document, which is why I asked "How might one use it in practice?"
>
> David
>
> On Thu, 26 Mar 2009, Sebastian Rahtz wrote:
>
> > David Sewell wrote:
> >
> > > But as elements in the fo: namespace cannot be children of <rendition>
> > > (without customization), what was the thinking behind including XSL-FO here?
> > > How might one use it in practice?
> >
> > presumably he is assuming we _do_ allow FO as children of
> > <rendition>. that would be fairly scary, and make for a
> > even bigger scheme.
> >
> > or we just make the model macro.anyXML and allow any XML markup
> > in there (cf constraint)
> >
> >
> >
>
> --
> David Sewell, Editorial and Technical Manager
> ROTUNDA, The University of Virginia Press
> PO Box 801079, Charlottesville, VA 22904-4318 USA
> Courier: 310 Old Ivy Way, Suite 302, Charlottesville VA 22903
> Email: dsewell at virginia.edu   Tel: +1 434 924 9973
> Web: http://rotunda.upress.virginia.edu/
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council



--
| John A. Walsh
| Assistant Professor, School of Library and Information Science
| Indiana University, 1320 East Tenth Street, Bloomington, IN 47405
| www: <http://www.slis.indiana.edu/faculty/jawalsh/>
| Voice:812-856-0707 Fax:812-856-2062 <mailto:jawalsh at indiana.edu>