![]() |
|
|
|
#1 |
|
http://xstandard.com/
This has all the things that would make for a nice editor except for one thing. It won't install unless your machine supports unicode. On the website they show customizable tags such as $<custom="blahblah">text</custom>. Are customizable tags available in pure xhtml now and do they work in all browser or what? Richard |
|
|
|
|
#2 |
|
Posts: n/a
|
On Thu, 03 Mar 2005 09:38:23 -0600, Richard wrote:
> http://xstandard.com/ > > This has all the things that would make for a nice editor except for one > thing. And a second... Something about having windows on your computer... Carolyn |
|
|
|
#3 |
|
Posts: n/a
|
Richard wrote:
> Are customizable tags available in pure xhtml now No. But you could process your custom tags into real XHTML elements at the server side. Or you could use namespace prefixes, which are supported in XML-aware browsers, but will stop your site from validating. -- Toby A Inkster BSc (Hons) ARCS Contact Me ~ http://tobyinkster.co.uk/contact |
|
|
|
#4 |
|
Posts: n/a
|
Toby Inkster wrote:
> Richard wrote: > > >>Are customizable tags available in pure xhtml now > > > No. But you could process your custom tags into real XHTML elements at the > server side. Or you could use namespace prefixes, which are supported in > XML-aware browsers, but will stop your site from validating. > That's what XSLT is for XHTML for example. -- x theSpaceGirl (miranda) # lead designer @ http://www.dhnewmedia.com # # remove NO SPAM to email, or use form on website # |
|
|
|
#5 |
|
Posts: n/a
|
It was somewhere outside Barstow when SpaceGirl
<> wrote: >That's what XSLT is for >XHTML for example. XSLT can't generate XHTML. It'll do HTML, or it'll do XML, but it just can't do that one in the middle, if you want to really work with the Appendix C-ness of things. (You can guess what has been ruining _my_ day today) |
|
|
|
#6 |
|
Posts: n/a
|
Andy Dingley wrote:
> It was somewhere outside Barstow when SpaceGirl > <> wrote: > > >>That's what XSLT is for >>XHTML for example. > > > XSLT can't generate XHTML. It'll do HTML, or it'll do XML, but it > just can't do that one in the middle, if you want to really work with > the Appendix C-ness of things. > How come? Not that I've ever used XSLT, but isn't the idea that it maps an XML document to another type of document, which could be an XML document, which could be XHTML? XHTML isn't "in the middle" really, it's perfectly valid XML. -- Oli |
|
|
|
#7 |
|
Posts: n/a
|
It was somewhere outside Barstow when Oli Filth <>
wrote: >XHTML isn't "in the middle" really, it's perfectly valid XML. XHTML is perfectly valid XML, but not all well-formed XML (including some variants that XSLT likes to generate) is good-practice XHTML according to Appendix C -- Smert' spamionam |
|
|
|
#8 |
|
Posts: n/a
|
Andy Dingley wrote:
> It was somewhere outside Barstow when Oli Filth <> > wrote: >>XHTML isn't "in the middle" really, it's perfectly valid XML. > > XHTML is perfectly valid XML, but not all well-formed XML > (including some variants that XSLT likes to generate) > is good-practice XHTML according to Appendix C That doesn't matter. Appendix C only applies when the document is being served as text/html. If XSLT is doing the conversion, it's just as easy to produce HTML 4.01 as text/html as it is to produce XHTML 1.x as application/xhtml+xml, unless you have a requirement to use XML-only features within the output (eg. Mixed namespaces, etc). -- Lachlan Hunt http://lachy.id.au/ http://GetFirefox.com/ Rediscover the Web http://GetThunderbird.com/ Reclaim your Inbox |
|
|
|
#9 |
|
Posts: n/a
|
It was somewhere outside Barstow when Lachlan Hunt
<> wrote: >If XSLT is doing the conversion, it's just as easy >to produce HTML 4.01 But I don't _want_ HTML, I want XHTML. With hand-edit I can provide Appendix C-compliant XHTML that's both usable on the web and is XML. I need to get XSLT to do this, which is problematic. The xsl value. I just wish XSLT processors also supported a similar hack for Appendix C XHTML. |
|