Skip to main content

Our Superficial Review of Surface: It Works with Tizra!


The new Microsoft Surface tablet was on the doorstep at Tizra HQ this morning, and we took a little time to run it through some basic tests.  Overall, our feeling was in line with the reviews: Nice hardware, and potentially attractive for those looking for a more mobile way to use MS Office.  Still a ways to go on software, though.

We tried the Windows RT version of Internet Explorer 10 on a few Tizra sites, and overall they worked as expected, though interactions with the new reading interface we've just developed (more on this soon) were sluggish.  Part of it may be incompatibility with some underlying scripts, which will be tuned as IE 10 becomes more of a factor.  Part of it was probably just our unfamiliarity with new Metro interface.

So for now, our minds are open on Surface as a device, but more importantly, we're thrilled to see another major player striving mightily to develop better ways for users to interact with the great content our customers deliver through Tizra.

Comments

Popular posts from this blog

Using XML to Create a Better Online Reading Experience for the American Payroll Association

Congrats to the American Payroll Association on their recent launch of XML-based publications on Tizra!  Thanks to this collaboration, APA's authoritative books for payroll professionals are now available in crisp, reflowable HTML, creating a user experience that feels like a truly digital native product, rather than a conversion from print. XML-based publishing also creates a better mobile reading experience, supports more precise search and navigation, and opens the door to better accessibility for users with low vision and other disabilities. Our partners at  Scribe  did a great job supporting APA through the process of producing the XML for loading into Tizra, and we’d definitely recommend them to anyone interested in such a transition. It’s hard to overstate what a big step forward this is for Tizra as a platform and a company. XML has long been planned for in the product's architecture, but now for the first time, we have a working example that demonstrates t...

The XML Paradox

I have been working on my tutorial for the O'Reilly Tools of Change conference. I'm presenting PDF as a cost-effective option to create revenue from the the backlist as an alternative to XML. As a dedicated markup advocate from the days of SGML, and someone who helped simplify SGML down to XML, I still find it odd to be talking about other kinds of solutions, but I think I learned something from my custom web site customers... The XML Paradox is that XML is a high-quality archival medium, and obviously then, books and scholarly content would make the jump first. It just makes sense that everyone would use the high-value format for the longest-lived, highest value content. Wrong! The economics of publishing have played out the opposite way. The more ephemeral the content, the faster production methods can change. So newspapers were doing full-text databases from very early on. In the scholarly markets, journals are now almost all electronic. Books, however, are only start...

Pure Coolness

I have seen far from all the talks here, but from what I've seen and the buzz that I've heard the winner of the "coolest presentation award" was Manolis Kelaidis. He showed a paper e-book device that he's been prototyping. By means of conductive ink traces, a person touching a button on the page can trigger an action by an embedded processor.  He had a book where pads on the page triggered actions on his laptop: going to web pages, playing songs on iTunes, and so forth.  It  was a hand-bound Bluetooth book! There's clearly a huge expense still involved in platform building and so on, but everything he did is compatible with contemporary printing technology, using inks that are commercially available (not experimental). Other developments in printable circuitry play into this as well: printable batteries, printable electronic components,  printable speakers. Of course this is a technology, not a solution, and there's a huge chain of associated requirements ...