<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: Table Alignment</title> <atom:link href="http://www.symphonious.net/2009/02/02/table-alignment/feed/" rel="self" type="application/rss+xml" /><link>http://www.symphonious.net/2009/02/02/table-alignment/</link> <description>Living in a state of accord.</description> <lastBuildDate>Tue, 07 Feb 2012 01:07:58 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: Asbjørn Ulsberg</title><link>http://www.symphonious.net/2009/02/02/table-alignment/comment-page-1/#comment-173920</link> <dc:creator>Asbjørn Ulsberg</dc:creator> <pubDate>Sat, 21 Mar 2009 13:00:27 +0000</pubDate> <guid
isPermaLink="false">http://www.symphonious.net/?p=1068#comment-173920</guid> <description>Ah, excellent. I think it works more than well enough. :)</description> <content:encoded><![CDATA[<p>Ah, excellent. I think it works more than well enough. :)</p> ]]></content:encoded> </item> <item><title>By: Adrian Sutton</title><link>http://www.symphonious.net/2009/02/02/table-alignment/comment-page-1/#comment-173919</link> <dc:creator>Adrian Sutton</dc:creator> <pubDate>Sat, 21 Mar 2009 11:43:08 +0000</pubDate> <guid
isPermaLink="false">http://www.symphonious.net/?p=1068#comment-173919</guid> <description>Asbjørn,
You&#039;ll be pleased to know the site now has comment preview. I&#039;m not 100% happy with the layout of it but it will do for now.
I also added openid authentication to verify your comment and skip the moderation queue.</description> <content:encoded><![CDATA[<p>Asbjørn,<br
/> You&#8217;ll be pleased to know the site now has comment preview. I&#8217;m not 100% happy with the layout of it but it will do for now.</p><p>I also added openid authentication to verify your comment and skip the moderation queue.</p> ]]></content:encoded> </item> <item><title>By: Adrian Sutton</title><link>http://www.symphonious.net/2009/02/02/table-alignment/comment-page-1/#comment-173914</link> <dc:creator>Adrian Sutton</dc:creator> <pubDate>Thu, 19 Mar 2009 17:19:05 +0000</pubDate> <guid
isPermaLink="false">http://www.symphonious.net/?p=1068#comment-173914</guid> <description>We do in fact have a filter in front of the editor, but as always there&#039;s problems there too.  If the filter aggressively normalizes content into a particular form, clients who want the original form for whatever reason will complain. So you need to preserve the non-normalized form through to the editor and only change things if the author actually changes the values - that means the editor has to deal with all the different variants though. So while the filter can at least guarantee that the content is well-formed and compliant, it still doesn&#039;t solve completely normalize the HTML.
Even with the filtering levels we have now, which are reasonably tame, we&#039;re getting a number of requests for the editor to just leave the HTML as-is. There are unfortunately, no silver bullets to this type of problem - just a whole lot of corner cases.</description> <content:encoded><![CDATA[<p>We do in fact have a filter in front of the editor, but as always there&#8217;s problems there too.  If the filter aggressively normalizes content into a particular form, clients who want the original form for whatever reason will complain. So you need to preserve the non-normalized form through to the editor and only change things if the author actually changes the values &#8211; that means the editor has to deal with all the different variants though. So while the filter can at least guarantee that the content is well-formed and compliant, it still doesn&#8217;t solve completely normalize the HTML.</p><p>Even with the filtering levels we have now, which are reasonably tame, we&#8217;re getting a number of requests for the editor to just leave the HTML as-is. There are unfortunately, no silver bullets to this type of problem &#8211; just a whole lot of corner cases.</p> ]]></content:encoded> </item> <item><title>By: Asbjørn Ulsberg</title><link>http://www.symphonious.net/2009/02/02/table-alignment/comment-page-1/#comment-173913</link> <dc:creator>Asbjørn Ulsberg</dc:creator> <pubDate>Thu, 19 Mar 2009 13:38:49 +0000</pubDate> <guid
isPermaLink="false">http://www.symphonious.net/?p=1068#comment-173913</guid> <description>I see your point entirely, but having to deal with odd markup should preferably be up to some kind of filter in front of the editor, so all the oddities are washed away and replaced with valid techniques so that the editor doesn&#039;t need to handle all the craziness your customers are generating. That would at least be my take on it.</description> <content:encoded><![CDATA[<p>I see your point entirely, but having to deal with odd markup should preferably be up to some kind of filter in front of the editor, so all the oddities are washed away and replaced with valid techniques so that the editor doesn&#8217;t need to handle all the craziness your customers are generating. That would at least be my take on it.</p> ]]></content:encoded> </item> <item><title>By: Adrian Sutton</title><link>http://www.symphonious.net/2009/02/02/table-alignment/comment-page-1/#comment-173912</link> <dc:creator>Adrian Sutton</dc:creator> <pubDate>Thu, 19 Mar 2009 08:49:20 +0000</pubDate> <guid
isPermaLink="false">http://www.symphonious.net/?p=1068#comment-173912</guid> <description>While the uses for HTMl we generate is varied and does quite often cause issues, the bigger problem is actually the incoming HTML that we have to consume.  A HTML editor doesn&#039;t always start from a blank document and shouldn&#039;t be limited to just the HTML it authored.  So we not only have to parse and display arbitrary HTML like browsers do, we have to make it fit into a sensible form within dialogs etc so the user can actually work with it and then somehow produce valid output at the end.  Plus any corrections for validity need to render exactly the same in browsers.
In other words, we poor editor guys get all the problems the browser guys do, plus all the challenges of the generator guys and few problems specific to editors. Remind me why I work here again? :)</description> <content:encoded><![CDATA[<p>While the uses for HTMl we generate is varied and does quite often cause issues, the bigger problem is actually the incoming HTML that we have to consume.  A HTML editor doesn&#8217;t always start from a blank document and shouldn&#8217;t be limited to just the HTML it authored.  So we not only have to parse and display arbitrary HTML like browsers do, we have to make it fit into a sensible form within dialogs etc so the user can actually work with it and then somehow produce valid output at the end.  Plus any corrections for validity need to render exactly the same in browsers.</p><p>In other words, we poor editor guys get all the problems the browser guys do, plus all the challenges of the generator guys and few problems specific to editors. Remind me why I work here again? :)</p> ]]></content:encoded> </item> <item><title>By: Asbjørn Ulsberg</title><link>http://www.symphonious.net/2009/02/02/table-alignment/comment-page-1/#comment-173911</link> <dc:creator>Asbjørn Ulsberg</dc:creator> <pubDate>Thu, 19 Mar 2009 08:13:18 +0000</pubDate> <guid
isPermaLink="false">http://www.symphonious.net/?p=1068#comment-173911</guid> <description>If you want your customers to be able to consume the HTML in something different from a regular web browser; yea, indeed.</description> <content:encoded><![CDATA[<p>If you want your customers to be able to consume the HTML in something different from a regular web browser; yea, indeed.</p> ]]></content:encoded> </item> <item><title>By: Andrew Herron</title><link>http://www.symphonious.net/2009/02/02/table-alignment/comment-page-1/#comment-173910</link> <dc:creator>Andrew Herron</dc:creator> <pubDate>Thu, 19 Mar 2009 00:03:08 +0000</pubDate> <guid
isPermaLink="false">http://www.symphonious.net/?p=1068#comment-173910</guid> <description>It&#039;s true editors only produce HTML, but our customers have to consume it.  It&#039;s a bit naive to think that someone could produce HTML and then not have to deal with the consequences of people trying to consume it.
And believe me, people consume HTML with some pretty strange combinations of software :)</description> <content:encoded><![CDATA[<p>It&#8217;s true editors only produce HTML, but our customers have to consume it.  It&#8217;s a bit naive to think that someone could produce HTML and then not have to deal with the consequences of people trying to consume it.</p><p>And believe me, people consume HTML with some pretty strange combinations of software :)</p> ]]></content:encoded> </item> <item><title>By: Asbjørn Ulsberg</title><link>http://www.symphonious.net/2009/02/02/table-alignment/comment-page-1/#comment-173909</link> <dc:creator>Asbjørn Ulsberg</dc:creator> <pubDate>Wed, 18 Mar 2009 22:11:24 +0000</pubDate> <guid
isPermaLink="false">http://www.symphonious.net/?p=1068#comment-173909</guid> <description>My understanding was that you produced HTML, not consumed. I see now that my understand was incorrect, so much of my comment is thus void. Wrt the difference between &#039;margin: 0 auto&#039; and &#039;margin-left: auto; margin-right: auto&#039; -- it was only an example and a shortcut. :-)</description> <content:encoded><![CDATA[<p>My understanding was that you produced HTML, not consumed. I see now that my understand was incorrect, so much of my comment is thus void. Wrt the difference between &#8216;margin: 0 auto&#8217; and &#8216;margin-left: auto; margin-right: auto&#8217; &#8212; it was only an example and a shortcut. :-)</p> ]]></content:encoded> </item> <item><title>By: Adrian Sutton</title><link>http://www.symphonious.net/2009/02/02/table-alignment/comment-page-1/#comment-173903</link> <dc:creator>Adrian Sutton</dc:creator> <pubDate>Thu, 12 Mar 2009 19:44:17 +0000</pubDate> <guid
isPermaLink="false">http://www.symphonious.net/?p=1068#comment-173903</guid> <description>Oh and yes, comment preview would be nice.  So would openid support....  Just need a few round tuits.</description> <content:encoded><![CDATA[<p>Oh and yes, comment preview would be nice.  So would openid support&#8230;.  Just need a few round tuits.</p> ]]></content:encoded> </item> <item><title>By: Adrian Sutton</title><link>http://www.symphonious.net/2009/02/02/table-alignment/comment-page-1/#comment-173902</link> <dc:creator>Adrian Sutton</dc:creator> <pubDate>Thu, 12 Mar 2009 19:43:47 +0000</pubDate> <guid
isPermaLink="false">http://www.symphonious.net/?p=1068#comment-173902</guid> <description>Except that when you deal with real world HTML you can&#039;t just limit things to CSS float and margin-left: auto; margin-right: auto  (margin: 0 auto is actually quite different to those two rules as I&#039;m sure you&#039;re aware). You&#039;re going to encounter HTML that still uses the align attribute. Plus a lot of PDF convertors and most XSLT transformations don&#039;t handle CSS well, if at all. If you live in a world where all you care about is the commonly used browsers, life is much easier - sadly, there are just enough other types of HTML parsers and just plain lousy HTML out there to cause lots of problems.</description> <content:encoded><![CDATA[<p>Except that when you deal with real world HTML you can&#8217;t just limit things to CSS float and margin-left: auto; margin-right: auto  (margin: 0 auto is actually quite different to those two rules as I&#8217;m sure you&#8217;re aware). You&#8217;re going to encounter HTML that still uses the align attribute. Plus a lot of PDF convertors and most XSLT transformations don&#8217;t handle CSS well, if at all. If you live in a world where all you care about is the commonly used browsers, life is much easier &#8211; sadly, there are just enough other types of HTML parsers and just plain lousy HTML out there to cause lots of problems.</p> ]]></content:encoded> </item> </channel> </rss>
