It would seem that the HTML bundle now checks to see if a document has a doctype of XHTML and if it doesn't it defaults all tags to their HTML counterparts. This would be great if I didn't spend all day editing templates in XHTML that aren't always the portion of a page that contains the doctype.
Could someone possibly point me in the right direction to turn off the check or default to XHTML instead? I would appreciate it immensely. :)
I just noticed this a second ago and suspect I have a bunch of code I need to go through to remove the <br> tags and replace them with <br />.
Jamie _______________________________________________________________________ Email: jamie@methnen.com Homepage: http://www.methnen.com
"And I always go to pieces. And I have it in my mind, that the sky is tall and heavy, when I could be brave." -Karen Peris (Brave)
"I want to find where the maid in the street is pouring her wine, I heard she takes you in and gives you the words you need said. If you'll be her brother, she'll kiss you like a sister. She'll even be your mother, for now." -Matt Slocum (Sister, Mother)
"And we are drowned." -Annie Dillard (Tickets For a Prayer Wheel) _______________________________________________________________________
On 12. Oct 2006, at 00:16, Methnen (AKA Jamie) wrote:
Could someone possibly point me in the right direction to turn off the check or default to XHTML instead? I would appreciate it immensely. :)
I just made this change to the HTML bundle:
[NEW] HTML tags inserted which have an EMPTY content model now place the value of the TM_XHTML variable before the closing ‘>’. If you want these tags to use the minimized (XHTML) form, go to Preferences -> Advanced and set TM_XHTML to “ /”. In the future this variable will automatically be set for documents with an XHTML document type. Though let me just remind anyone planning on writing XHTML pages to (re-)read http://www.hixie.ch/advocacy/xhtml
You will need to wait for next build before you can set the variable (or checkout the HTML bundle manually) -- there will be a build in a few days.
On Oct 11, 2006, at 4:00 PM, Allan Odgaard wrote:
You will need to wait for next build before you can set the variable (or checkout the HTML bundle manually) -- there will be a build in a few days.
Ah OK. Thanks. I've gone ahead and set the variable. I can wait a few days for it to start working. I'll just be careful until then.
Jamie
_______________________________________________________________________ Email: jamie@methnen.com Homepage: http://www.methnen.com
"And I always go to pieces. And I have it in my mind, that the sky is tall and heavy, when I could be brave." -Karen Peris (Brave)
"I want to find where the maid in the street is pouring her wine, I heard she takes you in and gives you the words you need said. If you'll be her brother, she'll kiss you like a sister. She'll even be your mother, for now." -Matt Slocum (Sister, Mother)
"And we are drowned." -Annie Dillard (Tickets For a Prayer Wheel) _______________________________________________________________________
On 10/12/06, Allan Odgaard throw-away-1@macromates.com wrote:
Though let me just remind anyone planning on writing XHTML pages to (re-)read http://www.hixie.ch/advocacy/xhtml
Then read "Sending XHTML as text/html Considered Harmful to Feelings"[1]
;)
On 30. Oct 2006, at 19:12, Fred B wrote:
On 10/12/06, Allan Odgaard throw-away-1@macromates.com wrote:
Though let me just remind anyone planning on writing XHTML pages to (re-)read http://www.hixie.ch/advocacy/xhtml
Then read "Sending XHTML as text/html Considered Harmful to Feelings"[1]
Which boils down to: “but it works for me” :p
An interesting recent development: [Reinventing HTML][1] from [Tim Berners-Lee][2], the inventor of the World Wide Web:
Some things are clearer with hindsight of several years. It is
necessary to evolve
HTML incrementally. The attempt to get the world to switch to
XML, including quotes
around attribute values and slashes in empty tags and namespaces
all at once didn't
work. The large HTML-generating public did not move, largely
because the browsers
didn't complain
Though the reason is not that browsers didn’t complain, it was that they did not support the new standards, and they did not do that because there were no benefits and W3C was far too busy cranking out new standards which were just re-inventing existing stuff. I am not in the enterprise business or whatever business uses the W3C standards that go beyond HTML, DOM, and CSS, but from my POV there are a lot of standards created by W3C that should never have been created (VRML, SMIL, or even XHTML 2.0 etc.).
If we look at XML, we have XPath and XML Query to query it, we have XML Proc and XSL to transform it, we have XLink and XPointer to describe links, we have XML Scheme and the DTD to give our content model, we have XForms and the form tags in XHTML to take user input, etc. etc. I.e. in each case we actually have more than one recently created spec for the thing, and the spec is normally huge, and there is no reference implementation of it, or even an implementing -- yet we can easily achieve what these things do with the tools we already have, so no wonder the industry stopped listening to W3C ;)
[1]: http://dig.csail.mit.edu/breadcrumbs/node/166 [2]: http://en.wikipedia.org/wiki/Tim_Berners-Lee
-
Allan Odgaard -
Fred B -
Methnen (AKA Jamie)