{"id":16672,"date":"2010-11-02T06:53:32","date_gmt":"2010-11-02T13:53:32","guid":{"rendered":"http:\/\/blogs.adobe.com\/jnack\/?p=3108"},"modified":"2010-11-02T06:53:32","modified_gmt":"2010-11-02T13:53:32","slug":"adobes-enhancing-webkit-for-better-typography","status":"publish","type":"post","link":"https:\/\/jnack.com\/blog\/2010\/11\/02\/adobes-enhancing-webkit-for-better-typography\/","title":{"rendered":"Adobe&#039;s enhancing WebKit for better typography"},"content":{"rendered":"<p>I&#8217;m excited to say that Adobe&#8217;s working with Google to enable better HTML-based typography, contributing the work to the open-source WebKit project.<\/p>\n<p>Why not just say &#8220;Web typography&#8221;? Because <a href=\"http:\/\/blogs.adobe.com\/jnack\/2010\/07\/html-isnt-about-web-pages.html\">HTML goes beyond the Web<\/a>, supporting apps like <a href=\"http:\/\/terrywhite.com\/techblog\/archives\/6321\">Adobe&#8217;s new tablet publishing solution<\/a>. \u00a0Trouble is, for all its strengths (e.g. separating content from layout), HTML&#8217;s type handling has been pretty limited&#8211;especially for creating print-quality layouts.<\/p>\n<p>Adobe wants to help solve the problem, making HTML better suited to more demanding applications. \u00a0Check out this demo from engineering VP Paul Gubbay:<\/p>\n<\/p>\n<p><object width=\"424\" height=\"343\"><param name=\"movie\" value=\"http:\/\/www.youtube.com\/v\/zRa4QTsb08s?fs=1&amp;hl=en_US\"><\/param><param name=\"allowFullScreen\" value=\"true\"><\/param><param name=\"allowscriptaccess\" value=\"always\"><\/param><embed src=\"http:\/\/www.youtube.com\/v\/zRa4QTsb08s?fs=1&amp;hl=en_US\" type=\"application\/x-shockwave-flash\" allowscriptaccess=\"always\" allowfullscreen=\"true\" width=\"424\" height=\"343\"><\/embed><\/object><\/p>\n<\/p>\n<p>Paul <a href=\"http:\/\/blogs.adobe.com\/designandweb\/2010\/10\/improving-the-web-for-digital-publishing.html\">writes<\/a>,<\/p>\n<blockquote>\n<p>The team has taken the approach of extending CSS with a few new elements utilizing the webkit- prefix so that the designer can adequately describe their intent for the content as the page is resized to simulate working across different screens. \u00a0We look forward to working with the Webkit Open Source project and of course the W3C to contribute our work back in the most appropriate way. \u00a0And, as always your comments are very much appreciated.<\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;m excited to say that Adobe&#8217;s working with Google to enable better HTML-based typography, contributing the work to the open-source WebKit project. Why not just say &#8220;Web typography&#8221;? Because HTML goes beyond the Web, supporting apps like Adobe&#8217;s new tablet publishing solution. \u00a0Trouble is, for all its strengths (e.g. separating content from layout), HTML&#8217;s type [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[34,6,51,9],"tags":[],"_links":{"self":[{"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts\/16672"}],"collection":[{"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/comments?post=16672"}],"version-history":[{"count":0,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/posts\/16672\/revisions"}],"wp:attachment":[{"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/media?parent=16672"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/categories?post=16672"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jnack.com\/blog\/wp-json\/wp\/v2\/tags?post=16672"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}