{"id":32,"date":"2004-09-01T10:11:04","date_gmt":"2004-09-01T18:11:04","guid":{"rendered":""},"modified":"2016-05-25T23:34:40","modified_gmt":"2016-05-26T06:34:40","slug":"sifr-update","status":"publish","type":"post","link":"https:\/\/mikeindustries.com\/blog\/archive\/2004\/09\/sifr-update","title":{"rendered":"sIFR Update: More Enhancements on the Way"},"content":{"rendered":"<p><strong>UPDATE:<\/strong> Version 2.0 is now available. <a href=\"\/sifr\/\">See article here<\/a>.<\/p>\n<p>Three days and tens of thousands of hits later, sIFR has so far held its own as a solid, compatible way to replace browser text with custom typography.  I&#8217;ve released a few new updates in response to minor glitches reported, but more importantly, a solid release is only days away.  In the meantime, please feel to <a href=\"\/blog\/files\/sifr\/sIFR-1.1.4.zip\">download version 1.1.4<\/a> which simply refines the replacement function a bit so that it should work on very complicated replacement rules and such. I&#8217;ve also updated the <a href=\"\/blog\/files\/sifr\/sifr.html\" target=\"_blank\">example page<\/a>.<\/p>\n<p>Here are some of the issues which I plan to address in version 1.2 (to be released hopefully in the next few days):<\/p>\n<ol>\n<li>Simple instructions your mom can follow. This thing can really be implemented across an entire site in under ten minutes if the instructions are clear enough.<\/li>\n<li>Support for international character sets.  This is an issue I haven&#8217;t solved yet because I&#8217;m a snooty uncultured American whose foreign language acumen is largely limited to profanities.<\/li>\n<li>A more rock-solid replacement function that is perhaps even quicker than the current one.<\/li>\n<li>A built-in adjustment for Flash&#8217;s tendency to position text a tiny percentage away from its textbox origin.<\/li>\n<li>Ability to include a reduced character set, for extra bandwidth savings. Most people probably only need standard letters, numbers, and punctuation, so by eliminating all of the characters you&#8217;d never use (like a degree symbol maybe), the .swf filesize can be reduced by, in some cases, 50%. This will involve having an actual textbox on stage in the .fla instead of dynamically creating one. Not as pure as I&#8217;d like, but I don&#8217;t think there is a way to selectively embed character subsets using pure Actionscript.<\/li>\n<li>An adjustment for the box-model problem in IE 5.x (PC) whereby offsetHeight and offsetWidth are reported slightly differently if padding is included in the element.<\/li>\n<li>A change to the display method of the hidden browser text so that it is even more accessible.<\/li>\n<li>Lockability of .swf files by domain. This will prevent others from using your font .swf file.<\/li>\n<\/ol>\n<p>I&#8217;m probably missing some stuff, but those are the biggies. I want to again thank everyone who has taken the time to put this thing through its paces over the last few days. sIFR is nice in that it is portable enough to pop into your site fairly quickly, and pop out of your site even quicker. The nice side-effect of this is that when I release updates, they should be fairly easy to apply. The upcoming 1.2 release will have its own dedicated page with release notes, but I&#8217;m a designer so don&#8217;t expect a full-on SourceForge repository or anything.<\/p>\n<p>Please feel free to comment on any of the items above&#8230; especially if you have solutions to suggest or additional features to request.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Three days and tens of thousands of hits later, sIFR has so far held its own as a solid, compatible way to replace browser text with custom typography.  I&#8217;ve released a few new updates in response to minor glitches reported, but more importantly, a solid release is only days away.  In the meantime, please feel to download version 1.1.4 which simply refines the replacement function a bit so that it should work on very complicated replacement rules and such. I&#8217;ve also updated the example page.<\/p>\n<p>Here are some of the issues which I plan to address in version 1.2 (to be released hopefully in the next few days):&#8230;<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36,282],"tags":[],"class_list":["post-32","post","type-post","status-publish","format-standard","hentry","category-design","category-original"],"_links":{"self":[{"href":"https:\/\/mikeindustries.com\/blog\/wp-json\/wp\/v2\/posts\/32","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mikeindustries.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mikeindustries.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mikeindustries.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/mikeindustries.com\/blog\/wp-json\/wp\/v2\/comments?post=32"}],"version-history":[{"count":0,"href":"https:\/\/mikeindustries.com\/blog\/wp-json\/wp\/v2\/posts\/32\/revisions"}],"wp:attachment":[{"href":"https:\/\/mikeindustries.com\/blog\/wp-json\/wp\/v2\/media?parent=32"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mikeindustries.com\/blog\/wp-json\/wp\/v2\/categories?post=32"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mikeindustries.com\/blog\/wp-json\/wp\/v2\/tags?post=32"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}