<?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: WYSIWYG editor spec &#8211; Tables</title>
	<atom:link href="http://alastairc.ac/2006/11/wysiwyg-editor-spec-tables/feed/" rel="self" type="application/rss+xml" />
	<link>http://alastairc.ac/2006/11/wysiwyg-editor-spec-tables/</link>
	<description>Kything web interactions</description>
	<lastBuildDate>Mon, 21 Jun 2010 21:13:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Ben 'Cerbera' Millard</title>
		<link>http://alastairc.ac/2006/11/wysiwyg-editor-spec-tables/comment-page-1/#comment-5418</link>
		<dc:creator>Ben 'Cerbera' Millard</dc:creator>
		<pubDate>Sat, 11 Nov 2006 20:48:43 +0000</pubDate>
		<guid isPermaLink="false">http://alastairc.ac/2006/11/wysiwyg-editor-spec-tables/#comment-5418</guid>
		<description>When importing data from simple CSV spreadsheets, empty cells should be fairly easy to detect for the file processing code.

Having more than one table of data in a single spreadsheet does happen &quot;in the wild&quot;. Calthorpe often send me Excel spreadsheets like this. I&#039;m not certain but I don&#039;t think the CSV format can handle more than one table per file, so a real-world editor would need to accomodate more complicated formats.

A bonus of this is that the more complicated formats would, I assume, contain the structural metadata required to identify individual tables. They might go some way towards identifying table headers, too.

The file processor could apply some heuristic tests to try and deduce the structure of the table and could be quite successful in many cases. I think things like the tide table example, are always going to be tough to sort out, but this could ease the pain somewhat.

Providing previews and adjustments at the converting stage would be complicated to implement but should be quite possible.</description>
		<content:encoded><![CDATA[<p>When importing data from simple CSV spreadsheets, empty cells should be fairly easy to detect for the file processing code.</p>
<p>Having more than one table of data in a single spreadsheet does happen &#8220;in the wild&#8221;. Calthorpe often send me Excel spreadsheets like this. I&#8217;m not certain but I don&#8217;t think the CSV format can handle more than one table per file, so a real-world editor would need to accomodate more complicated formats.</p>
<p>A bonus of this is that the more complicated formats would, I assume, contain the structural metadata required to identify individual tables. They might go some way towards identifying table headers, too.</p>
<p>The file processor could apply some heuristic tests to try and deduce the structure of the table and could be quite successful in many cases. I think things like the tide table example, are always going to be tough to sort out, but this could ease the pain somewhat.</p>
<p>Providing previews and adjustments at the converting stage would be complicated to implement but should be quite possible.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
