<?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: Seven Things for June 22nd</title>
	<atom:link href="http://www.realtimerendering.com/blog/seven-things-for-june-22nd/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.realtimerendering.com/blog/seven-things-for-june-22nd/</link>
	<description>Tracking the latest developments in interactive rendering techniques</description>
	<lastBuildDate>Mon, 17 Jun 2013 03:17:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: morgan3d</title>
		<link>http://www.realtimerendering.com/blog/seven-things-for-june-22nd/comment-page-1/#comment-2175</link>
		<dc:creator>morgan3d</dc:creator>
		<pubDate>Sat, 23 Jun 2012 15:45:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.realtimerendering.com/blog/?p=3143#comment-2175</guid>
		<description>In response to &#039;ingenious&#039;, thanks for the kind words, and I acknowledge (and to some extent sympathize with) your comments about two-column vs. one-column.  It is something that we thought about carefully.  Here are some of those thoughts:


I think the two-column SIGGRAPH format is a poor fit for modern (i.e., electronic, which all proceedings now are) papers.  

I believe that the two-column format was designed to minimize the printing cost of the SIGGRAPH proceedings. For the reader (and reviewers!), it makes it hard to copy sections of text, and hard to read on a mobile device or web browser because one has to scroll in two dimensions.  

For the author, two columns it means taking equations, figures, and code that might naturally have a fairly wide layout and breaking them across lines to try and shoehorn into 3 inches.  

The JCGT template uses the same fonts and macros as the SIGGRAPH template and has strictly wider text width, which makes it easy to port papers originally formatted using the SIGGRAPH template.  We kept fairly narrow text width to improve readability, and will probably continue to tweak line spacing and text width.  Equations, figures, and code can span as much of the page (even into the margins) as they need.  

It is nice to get as much as possible on one page, and the current JCGT template does not excel in that area.  Viewing as a continuous PDF on a tablet is one solution today.  In the future, I&#039;d like to see a format with layout as precise as PDF enable reflow, which would allow papers to adapt to the reading habits and devices of the readers.  HTML 5 still provides insufficient kerning and equation formatting for a mathematically-dense technical publication (although it is getting much better), but perhaps in a few years we will see a better standard.  There have been some great graphics papers on dynamic text layout and general document resizing--perhaps a future JCGT paper will pave the way for better formatted papers everywhere.  But, this is very much in the future right now.  Choosing a widely-accepted document format (PDF) and tailoring the template to the needs of the equations and code that are the heart of a JCGT paper remains our best solution.  

For readers who prefer to see two columns, the solution is simple: from your PDF viewer, print the paper with two or four pages side-by-side.  You can print to PDF to continue reading electronically or print onto paper and read that way.

I promise to continue revisiting this issue and adjusting the template to maximize readability as we gain more experience typesetting papers for electronic-only publishing.  The first version of our template already includes bookmarks and hyperlinks within the document and to external resources, which is an important step towards leveraging the advantages of the medium.

Morgan
JCGT Editor-in-Chief</description>
		<content:encoded><![CDATA[<p>In response to &#8216;ingenious&#8217;, thanks for the kind words, and I acknowledge (and to some extent sympathize with) your comments about two-column vs. one-column.  It is something that we thought about carefully.  Here are some of those thoughts:</p>
<p>I think the two-column SIGGRAPH format is a poor fit for modern (i.e., electronic, which all proceedings now are) papers.  </p>
<p>I believe that the two-column format was designed to minimize the printing cost of the SIGGRAPH proceedings. For the reader (and reviewers!), it makes it hard to copy sections of text, and hard to read on a mobile device or web browser because one has to scroll in two dimensions.  </p>
<p>For the author, two columns it means taking equations, figures, and code that might naturally have a fairly wide layout and breaking them across lines to try and shoehorn into 3 inches.  </p>
<p>The JCGT template uses the same fonts and macros as the SIGGRAPH template and has strictly wider text width, which makes it easy to port papers originally formatted using the SIGGRAPH template.  We kept fairly narrow text width to improve readability, and will probably continue to tweak line spacing and text width.  Equations, figures, and code can span as much of the page (even into the margins) as they need.  </p>
<p>It is nice to get as much as possible on one page, and the current JCGT template does not excel in that area.  Viewing as a continuous PDF on a tablet is one solution today.  In the future, I&#8217;d like to see a format with layout as precise as PDF enable reflow, which would allow papers to adapt to the reading habits and devices of the readers.  HTML 5 still provides insufficient kerning and equation formatting for a mathematically-dense technical publication (although it is getting much better), but perhaps in a few years we will see a better standard.  There have been some great graphics papers on dynamic text layout and general document resizing&#8211;perhaps a future JCGT paper will pave the way for better formatted papers everywhere.  But, this is very much in the future right now.  Choosing a widely-accepted document format (PDF) and tailoring the template to the needs of the equations and code that are the heart of a JCGT paper remains our best solution.  </p>
<p>For readers who prefer to see two columns, the solution is simple: from your PDF viewer, print the paper with two or four pages side-by-side.  You can print to PDF to continue reading electronically or print onto paper and read that way.</p>
<p>I promise to continue revisiting this issue and adjusting the template to maximize readability as we gain more experience typesetting papers for electronic-only publishing.  The first version of our template already includes bookmarks and hyperlinks within the document and to external resources, which is an important step towards leveraging the advantages of the medium.</p>
<p>Morgan<br />
JCGT Editor-in-Chief</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ingenious</title>
		<link>http://www.realtimerendering.com/blog/seven-things-for-june-22nd/comment-page-1/#comment-2173</link>
		<dc:creator>ingenious</dc:creator>
		<pubDate>Sat, 23 Jun 2012 11:09:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.realtimerendering.com/blog/?p=3143#comment-2173</guid>
		<description>Wow, JCGT is already ganing speed! Good to see that. But is this paper&#039;s template the final JCGT one? Wouldn&#039;t something like Siggraph&#039;s two-column format be more appropriate? I find it much more easy to read (due to the narrow columns) and more space-efficient - presents more content on one page, minimizing the annoying page flipping.</description>
		<content:encoded><![CDATA[<p>Wow, JCGT is already ganing speed! Good to see that. But is this paper&#8217;s template the final JCGT one? Wouldn&#8217;t something like Siggraph&#8217;s two-column format be more appropriate? I find it much more easy to read (due to the narrow columns) and more space-efficient &#8211; presents more content on one page, minimizing the annoying page flipping.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mauricio</title>
		<link>http://www.realtimerendering.com/blog/seven-things-for-june-22nd/comment-page-1/#comment-2172</link>
		<dc:creator>Mauricio</dc:creator>
		<pubDate>Sat, 23 Jun 2012 11:06:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.realtimerendering.com/blog/?p=3143#comment-2172</guid>
		<description>Congratulations to the JCGT crew for the great start!  It is interesting to see that papers will be &quot;appended&quot; before the first issue is actually done.  No need to wait for the content.</description>
		<content:encoded><![CDATA[<p>Congratulations to the JCGT crew for the great start!  It is interesting to see that papers will be &#8220;appended&#8221; before the first issue is actually done.  No need to wait for the content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slothlovechunk</title>
		<link>http://www.realtimerendering.com/blog/seven-things-for-june-22nd/comment-page-1/#comment-2171</link>
		<dc:creator>slothlovechunk</dc:creator>
		<pubDate>Sat, 23 Jun 2012 03:27:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.realtimerendering.com/blog/?p=3143#comment-2171</guid>
		<description>I don&#039;t know if this is appropriate, but does anyone know how Jim Arvo died? It doesn&#039;t seem to be published anywhere.

I remember seeing him a few times either last summer or summer of 2010 at WDAS, and always regretted never introducing myself, now even more-so.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know if this is appropriate, but does anyone know how Jim Arvo died? It doesn&#8217;t seem to be published anywhere.</p>
<p>I remember seeing him a few times either last summer or summer of 2010 at WDAS, and always regretted never introducing myself, now even more-so.</p>
]]></content:encoded>
	</item>
</channel>
</rss>