[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: DOCBOOK-APPS: Re: conditionalization of XML
--9Ek0hoCL9XbhcSqy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Norman Walsh <ndw@nwalsh.com>: > I think I'm willing to live without else. If I want else, I think the > right answer is a special-purpose XML vocabulary: >=20 > <chapter> > <prof:choose> > <prof:when condition=3D"html"> > <title>HTML Title</title> > </prof:when> > <prof:when condition=3D"print"> > <title>Print Title</title> > </prof:when> > <prof:otherwise> > <title>Print and HTML Title</title> > </prof:otherwise> > </prof:choose> > .... >=20 > Where the profiling application always removes all prof: elements. Now tell me how this differs, other than in surface syntax, from what I've already done? Yes, I could have dressed up my conditionals this way. Still could with=20 some trivial changes to my flex program. I thought it would be more honest to make them PIs. --=20 <a href=3D"http://www.tuxedo.org/~esr/">Eric S. Raymond</a> --9Ek0hoCL9XbhcSqy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9pyvPrfUW04Qh8RwRAnf4AKDmx7+dYoi1V5D5dJy/psjdOL16lACgmxGf Dd6T+925/qrXt2buOz8+7AQ= =jAvc -----END PGP SIGNATURE----- --9Ek0hoCL9XbhcSqy--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC