My 2-cents: I fully agree with golem for all the reasons that he cites (and others he would agree with, I am sure).
My further comment is this: as an avid consumer of e-books and newspapers on Kindle and the iPad, I am amazed at the poor CSS coding of the products that these people sell. It is an irritant but also a reflection of the lack of care that it appears that these folks take in preparing a product for sale. My conclusion is that the formatting for most of these publications is created by an auto-formatting- Dreamweaver-thing-y (and therefore sure to produce poor code) or by poor decision-making by coders (and please know I am not referring to originator of this string - but to my overall experience as an engineer consuming a product). If a client's notion is that somehow an e-book needs to save bytes at the expense of reliable rendering, I am not sure what to say about that - other than that my advise is to educate the client. I own hundreds of e-books and have a daily subscription to the NY Times - all poorly coded but never once has the size of the file - either in storage on the device (which of course can be off-loaded, anytime) nor in the download time. Net-net, my contribution here is that style and structure must always be separated and that the overhead entailed by adding class definitions to elements within the XML of any document is trivial compared to the benefits of inter-device rendering. -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to bbedit@googlegroups.com To unsubscribe from this group, send email to bbedit+unsubscr...@googlegroups.com For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "supp...@barebones.com" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
