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

Hyphenation for multipart attribute labels...

Subject: Hyphenation for multipart attribute labels...
From: Guy_Murphy@xxxxxxxxxx
Date: Tue, 23 Mar 1999 14:37:07 +0000
css hyphenation
Hi.

Before XSL goes out the door, might we consider a small but potentialy
highly significant aspect that seem to be overlooked.

For FO attributes the convention seems to hyphenate attributes of multiple
words....

*** Heyphenating multiple words is the work of the Devil ***

...Sorry. A bit reactionary maybe, but I had to get that off my chest,
after some experimenting I was doing last night.

Hyphenated words are problematic from most scripting languages. So if I
have <tag an-attribute="something" /> then we are locked into having to
using XML DOM type approaches of elObj.getAttribute('an-attibute') or
elObj.attributes.getNamedItem('an-attribute') rather than just
elObj.anAttribute. Now in the purly XML world it's all well and reasonable
to shout "do it the proper way" and use .getAttribute(), but with XSL FOs,
we're going to have an awful lot of attributes for FOs, and in an ideal
world we're going to get some sort of dynamic rendering maniplulation of
FOs in a browser, along the lines of CSS at the mo. So we're going to want
(I maybe I should restrict this to *I*) something like...

blockObj.backgroundColor

...or maybe a browser might expose...

blockObj.xStyle.backgroundColor

...which is doubly desirable when one considers that XSL will probably
co-exist along side CSS in many cases, and it would be nice to be working
with a common paradigm.

Has anybody else given this any thought? The reason why I'm thinking about
it at the mo is because I started working up some code for basic
implimentations of XSL FOs using IE5 HTCs to impliment their instantiation
and behaviour, and at the moment I am mirroring the FO properties so that
backgound-color is also available as backgroundColor to facilitate dHTML
(or should that be dFO :) and I'd be interested to hear other peoples
thoughts on the matter.

I know we'e stuck with the W3C DOM (::split::), and I'm not arguing that we
change it, simply that we consider changing the XSL FO attributes before
they go out the door.

Cheers
     Guy Murphy
     guy_murphy@xxxxxxxxxx
     http://www.guy-murphy.easynet.co.uk



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


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.