<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Links</title>
    <link rel="alternate" type="text/html" href="http://www.manning.com/links/" />
    <link rel="self" type="application/atom+xml" href="http://www.manning.com/links/atom.xml" />
   <id>tag:www.manning.com,2007:/links//1</id>
    <link rel="service.post" type="application/atom+xml" href="http://www.manning.com/blog-mt/mt-atom.cgi/weblog/blog_id=1" title="Links" />
    <updated>2006-10-26T13:39:43Z</updated>
    <subtitle>Get inside the heads of Marjan Bace, Manning publisher, Mike Stephens, our Associate Publisher, and Ron Tomich, our Head of Sales and Marketing who write about our books, the publishing business, and other topics.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.2ysb5-20051201</generator>
 
<entry>
    <title>Why we call it &quot;Java Persistence with Hibernate&quot;?</title>
    <link rel="alternate" type="text/html" href="http://www.manning.com/links/2006/10/why_we_call_it_java_persistenc_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.manning.com/blog-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=39" title="&lt;a name=&quot;jhibernate&quot;&gt;&lt;/a&gt;Why we call it &quot;Java Persistence with Hibernate&quot;?" />
    <id>tag:www.manning.com,2006:/links//1.39</id>
    
    <published>2006-10-26T03:44:27Z</published>
    <updated>2006-10-26T13:39:43Z</updated>
    
    <summary>Every publisher with a little experience will make sure that a second edition of a book rides on the success of the first. The more successful the first edition has been, the more tightly publishers tend to associate the second...</summary>
    <author>
        <name>Marjan Bace</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.manning.com/links/">
        <![CDATA[<p>Every publisher with a little experience will make sure that a second edition of a book rides on the success of the first. The more successful the first edition has been, the more tightly publishers tend to associate the second with it. So why would Manning ignore that rule and call the second edition of <em>Hibernate in Action</em> by a different name: <em>Java Persistence with Hibernate</em>? </p>

<p><em>Hibernate in Action</em> has been one of our all-time best sellers, <em>persistently</em> performing ever since we published it in August 2004. It was named the best Java book in 2005 by the Java Developer's Journal after an extensive polling of the Java community. We believe the book has been, at least in part, the reason Gavin King got invited to join the EJB 3.0 standardization committee. This had the later consequence that much of Hibernate's philosophy and many of its solutions became adopted within EJB 3.0 and Hibernate is now also bundled with the JBoss EJB 3.0 server software.</p>

<p>So the book has been part of a spectacular success story for a young programmer from Melbourne, and his young ally in Germany, who at some point had the guts to launch a project to single handedly replace commercial software worth hundreds of thousands of dollars, just by making something better. It has also been a success for Manning who believed in the project at a time when few had even heard of it. </p>

<p>So, why would we want to jeopardize the second edition's success by calling it something different? The answer is in the EJB 3.0 connection: "Java Persistence 1.0" is what the EJB 3.0 persistence layer is formally called within the standard, and since in many ways it is based on Hibernate concepts and APIs the two are now closely related. From a programmer's POV, Java Persistence 1.0 is the central concept now and Hibernate just one of the many tools that implement it. The current version of Hibernate implments the standard by adding a layer on top of the extensive and mature Hibernate software. Our new title uses the term that Java programmers now or soon will use as a matter of course. </p>

<p>In making this unorthodox publishing decision we have in effect chosen the preferences of our readers over our trade partners. In the meantime, this latter group is a critical link between us and those same readers. Not a pleasant choice.</p>

<p>We hope our friends in the bookselling world will understand our titling decision. It was ultimately a question of who will be more important for the fate of the new book: our booksellers or our readers? If you see it that way I hope you will agree with our choice and help us make this book a success. The Manning Early Access Program (MEAP) release of this title has so far been great. Judging by that, strong bookstore sales are likely to follow!</p>]]>
        
    </content>
</entry>
<entry>
    <title>Why small is sweet</title>
    <link rel="alternate" type="text/html" href="http://www.manning.com/links/2005/02/why_small_is_sweet.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.manning.com/blog-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=26" title="Why small is sweet" />
    <id>tag:p.hostingprod.com,2005:/@www.manning.com/links//1.26</id>
    
    <published>2005-02-28T22:46:06Z</published>
    <updated>2006-03-14T22:46:53Z</updated>
    
    <summary><![CDATA[ When the Manning page design couldn't be rendered by the OSoft ThoutReader, what do you think OSoft told us? They said, &quot;we will release a new version of the ThoutReader to support the functionality you require.&quot; Imagine the answer...]]></summary>
    <author>
        <name>Marjan Bace</name>
        <uri>http://www.manning.com</uri>
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.manning.com/links/">
        <![CDATA[<div class="contentbody"> When the Manning page design couldn't be rendered by the OSoft ThoutReader, what do you think OSoft told us?<br /><br /> <a name="more" />They said, &quot;we will release a new version of the ThoutReader to support the functionality you require.&quot; Imagine the answer we would have received if OSoft were a few hundred million dollar company.<br /> <br /> One of the people commenting on my last blog, <a href="http://www.manning.com/links/archives/9-DRM,-so-what-have-we-learned.html#c82">Carl-Eric Menzel in comment #11</a>, thought the design of the TR pages he saw was unattractive. I agree with him. But we never planned to use OSoft's default design for our books and now that the technology is maturing it's time for us to develop a new design for Manning books in the TR format. Here's a <a href="http://www.manning.com/images/marjan/chapter1_final.gif">snapshot</a> that will give you a sense of what we're striving for. <br /> <br /> <a href="http://www.osoft.com/">OSoft</a> is currently working on getting that design to render nicely in TR. We are grateful they are small! </div>  <div class="content"> <div class="contenttitle"> <h2>Comments</h2> </div> <a name="c" /> <div class="itemcomment id0"> <h3><a href="mailto:cm.manningpublications@bitforce.com"> Carl-Eric Menzel</a> wrote:</h3> <div class="commentbody"> You're cheating, this is OSX ;-) On a more serious note: That looks much better. If you can get it to look this good on all three of the important systems, then I'll be impressed *and* pleased. I recommend taking a look at some of the available look-and-feels for Swing, there are some that look much cleaner than the default designs, especially now that Sun included that hideous WindowsXP-pseudo-lookalike. Carl-Eric </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:tony@llifion.nildram.co.uk"> Tony</a> wrote:</h3> <div class="commentbody">Something I'd like to know if possible (may be too early to tell as yet) - is/will print quality results be comparable to those of the existing pdf eBooks? I - like many others I'm sure - like to print out relevant sections to work with, and occasionally it is nice to read it on paper :) Many thanks </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:maba@manning.com"> Marjan Bace</a> wrote:</h3> <div class="commentbody"> The printed pages will be high quality, with fonts printed at the resolution of your printer like an HTML page </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="http://www.manning-blogs.com/nucleus/index.php?itemid=11"> Tony</a> wrote:</h3> <div class="commentbody">Thanks for the reply Marjan. I've just checked my existing copy of ThoutReader and can't see a print dialogue. Is this one of the extensions in functionality that Osoft are adding by request - or part of the default product (I'll check Osoft's site out shortly). Thanks </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:rickblair@mac.com"> Rick Blair</a> wrote:</h3> <div class="commentbody">Hi Tony, I am one of the Osoft developers. We have posted version 1.8 that does have print support. It was a long time in coming, but I think you will be pleased. Let me know if you have any questions, comments, or complaints. Thanks Rick </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="http://www.manning-blogs.com/nucleus/index.php?itemid=11"> Victor</a> wrote:</h3> <div class="commentbody"> The snapshot link in the original post is broken. </div> <div class="commentinfo"> 17/02 20:15:35 </div> </div> </div>]]>
        
    </content>
</entry>
<entry>
    <title>DRM, so what have we learned?</title>
    <link rel="alternate" type="text/html" href="http://www.manning.com/links/2005/01/drm_so_what_have_we_learned.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.manning.com/blog-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=25" title="DRM, so what have we learned?" />
    <id>tag:p.hostingprod.com,2005:/@www.manning.com/links//1.25</id>
    
    <published>2005-01-28T22:43:05Z</published>
    <updated>2006-03-14T22:45:46Z</updated>
    
    <summary><![CDATA[ My last post received a number of comments some of which came in by mail. Some people don't believe or care that... Manning is losing business selling unencrypted PDFs. They argue: &quot;I don't steal so what's Manning's problem?&quot; But...]]></summary>
    <author>
        <name>Marjan Bace</name>
        <uri>http://www.manning.com</uri>
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.manning.com/links/">
        <![CDATA[<div class="contentbody"> My last post received a number of comments some of which came in by mail. Some people don't believe or care that...<br /><br /> <a name="more" />Manning is losing business selling unencrypted PDFs. They argue: &quot;I don't steal so what's Manning's problem?&quot; But that assumes no-one else does either. These people are not going to make the switch to see things from Manning's side whatever I say, so here's what I think we might do: <br /> <br /> When you purchase a Manning ebook we'll give you both the encrypted version and the unencrypted PDF. How crazy, you say, wasn't the whole point to take unencrypted books out of circulation? Yes, that was and is the ultimate goal, but we'd like to give our customers a chance to to experience using ThoutReader first. Maybe they will like it. TR has certain advantages they might decide are worth the small burden of dealing with TR's encryption.<br /> <br /> Here are some TR advantages:<br /> <br /> 1. Search</div><div class="contentbody"><br /> With TR you'll be able to search through the entire library of TR content with a single stroke. After you've accumulated more than say two books, this will definitely be more powerful than Acrobat's search which stays within just the one active document.</div><div class="contentbody"><br /> 2. Notes</div><div class="contentbody"><br /> You can add notes to the TR version right now and in the very near future OSoft will develop the feature I mentioned in my last blog: a public notes feature which lets your notes be publicly shared over the Web. I can imagine how this might become a valuable thing, but only experience will tell us for sure. This feature will also let us add errata to the exact place where they belong in the book&acirc;&euro;&rdquo;an elegant improvement over the clumsy way we do it now.</div><div class="contentbody"><br /> 3. Boomarks</div><div class="contentbody"><br /> With TR you can jump from any section of any TR book to any other--can't do that with PDFs.<br /> <br /> This list will grow. TR is an open source tool--if people start using it they will come up with new ideas and develop exciting features unavailable in Adobe's closed product. In the meantime, I am excited about the already available timed-key feature. If you are interested in browsing a Manning book you'll be able to see the entire book--for a preset period. Isn't that the brick-and-mortar experience that&acirc;&euro;&trade;s really <br /> missing online? </div>  <div class="content"> <div class="contenttitle"> <h2>Comments</h2> </div> <a name="c" /> <div class="itemcomment id0"> <h3><a href="mailto:jake@softpro.com"> Jake</a> wrote:</h3> <div class="commentbody"> Why not just make books that are going out of circulation (out of print) unencrypted and leave the in-circulation books encrypted? You'll be offering one service, while maintaining another... </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="http://www.manning-blogs.com/nucleus/index.php?itemid=9"> Marjan Bace</a> wrote:</h3> <div class="commentbody">We tend to keep our titles in print for a long time. A transitional period in which we try to figure out what our customers like fits my way of thinking best. I think we'll do that. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:y@yahoo.com"> Yura</a> wrote:</h3> <div class="commentbody">Just one thought from Russia ;-) As you ever make DRM (but as I see from your site, you've already made) that would be your biggest mistake. I'm getting exciting about Manning books and I think e-book format needed for book's examination. If person likes e-book, that person purchases print format of the same book. Please beleive me untill now there is no DRM technology could not be cracked. One stupid example is DVD region zone. If Manning hopes to limit themself from piracy this way, it looks like they all are childs. I'm sorry for my words, I do not want to hurt you. Also, ThoutReader is terrible comparing to Acrobat (sorry, OSoft guys). It took years to make pdf great and readable. Simple xml transformations using xsl, css, whatsoever is not even getting close in quality and usability of pdf! Please, DO not make that mistake! </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:maxvamp@comcast.net"> Hugh McCreery</a> wrote:</h3> <div class="commentbody">I own a few ebooks from Palm ereader. One approach that they use is to use the purchasing credit card as the encryption key. Perhaps any unencrypted ebooks could have this number. This would/should discourage some ditrobution. I actually don't mind the DRM so long as it is portable to many platforms ( used Zinio for Mags, seems to work on Mac ). The only request that I have is the Thout adds a Zoom feature. My eyes get tired easy ( resulting in migraines ) and a zooming the text makes life many times easier. Thank you, Hugh </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:mcarey@osoft.com"> Mark Carey</a> wrote:</h3> <div class="commentbody">Yura, In some respects you are right. The ThoutReader was never meant to compete against or replace Acrobat Reader. In fact, we use .PDF formatted documents on our website for sample chapters. The ThoutReader WAS designed specifically for technology use, not as a general purpose document reader. [I would not want to read War and Peace by Leo Tolstoy in the ThoutReader format.] To be succinct, most open source documentation sucks. Even though it is needed by developers, most people don&acirc;&euro;&trade;t want to think about it or deal with it, even though they need it. There&acirc;&euro;&trade;s no consistency and no standards. Documentation comes in different formats and different locations, making information hard to find when, where and how you need it: this means a lot of inconvenience and frustration by developers. The ThoutReader&acirc;&bdquo;&cent; allows developers to browse, search, bookmark, and append their favorite library of open source documentation and reference books (read Manning) - from one program, in one format, at the same time - even off-line. Adobe's Acrobat Reader is not open source. The ThoutReader is. There is no telling what direction the ThoutReader will take in the future. On the planning table right now are the following: * Public notes - the ability to collaborate with other developers around the world to specific sections within content. * Merged notes - individuals can merge notes from other developers (students could merge instructor notes at the end of a course) * Plug-ins - ability to add video and audio plug-ins * Advanced search capability - already the ThoutReader allows user to search select titles or an entire library of content. It also accepts regular expressions. * Eclipse plug in * Cross linking - ability to link from one document or book to another * Embedded as a help file within an application * Ability to read docbook and other file formats natively * ThoutCreator tools will allow developers to distribute their own content We are excited about our relationship with Manning because of their Java focus. The ThoutReader was written in Java and Manning readers are some of the smartest developers in the world. Manning will be featuring contests and other incentives to continue to develop the ThoutReader. When was the last time you were asked to make improvements to Adobe's Acrobat Reader? What the ThoutReader becomes is up to you and thousands of other developers and Manning readers who wish to contribute to our open source project. I for one look forward to the next few years. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:werpu@gmx.at"> Werner Punz</a> wrote:</h3> <div class="commentbody">I have bought several Mannings ebooks in the past and probably will continue to do so in the near future, due to its excellent content. But plugging DRM onto the thing is a problem. I move the books between several dev machines (have them on the harddisk there), there is several what ifs. I want to print them myself, I want to move the books, because I move between machines. If the DRM becomes to restrictive, there is no way I will purchase future books, because the advantage is gone, and paperbacks from other publishers like OReilley are easier to get where I live. So Mannings has to be careful, so far I have bought about 4-5 PDFed books from them. I dont have any problems with the name watermarks they introduced recently (in fact I liked it because I thought that they were going the watermark route instead of restriction route to keep the warezers out) But if DRM is introduced and introduced to restrictively, Mannings will have lost a customer (and a good one because I usually look at the Mannings site first for a book) </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:bayard@generationjava.com"> Henri Yandell</a> wrote:</h3> <div class="commentbody">DRM is a tricky one isn't it. The only way to solve the grievous problem of major theft, is to bludgeon to death the freedom of sharing. My only complaint with DRM'd texts is that I can no longer have them sitting on the shelf at work where people can come grab them and share. The only obvious solution to me there is to have a public/private key encryption. As the owner of the text, I have it privately encrypted/signed, and I supply the public key to people I wish to share it with. They're all able to share it. If I share it too much, I get punished. The problem however is in noticing how much I share it. While my putting a pdf on my webserver at work is hardly a capital crime (4 developers), if I worked at IBM and put it on the internal network it'd be quite a bit worse. Maybe the solution there is to allow a set number of public/private keys to exist on the document. It's hard to define it without having constant internet access to make sure people are obeying the rules, and then you've lost the competitive edge over Safari. That said, I'm still paying Bookpool for dead-wood versions of books as time away from a monitor/keyboard to read is the only thing keeping my carpal tunnels and near-sightedness within limits. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="http://www.manning-blogs.com/nucleus/index.php?itemid=9"> Marjan Bace</a> wrote:</h3> <div class="commentbody">Werner, we want to keep you as a customer. We will listen to you and others and adjust things until we get it right. When the ThoutReader&acirc;&bdquo;&cent; was developed, content restrictions were added as an afterthought. They did not &acirc;&euro;&oelig;code&acirc;&euro; commercial content to a specific machine because that would have been too restrictive. Instead, they chose a simpler solution. It allows you to download and install any Manning content on any number of computers. The user key only needs to be installed once per machine. After that, any Manning content you buy can be opened without any further hassle. TR gives us the control of printing restrictions. Printing can be turned All On, All Off, or selective on (code snippets). I think that its current feautures are already pretty compelling and future ones will make it better. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="http://www.manning-blogs.com/nucleus/index.php?itemid=9"> Daryl Robbins</a> wrote:</h3> <div class="commentbody">There are two points that I would like to bring up. First, how many people that downloaded pirated versions of Manning books would actually have bought them? If this number is only a small percentage, then the majority of honest customers are being penalized for the actions of a small minority. Second, from my quick look at ThoutReader, its output is relatively ugly. It may look good for an HTML document, but it's nowhere close to emulating printed material, which Adobe Acrobat does quite well. Not only are PDF documents prettier, they are much easier to read. Sounds like we&acirc;&euro;&trade;re regressing here. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:cm.manningpublications@bitforce.com"> Carl-Eric Menzel</a> wrote:</h3> <div class="commentbody">I was one of those who reacted with a hopefully polite but strong answer when you first sent out the questionnaire regarding DRM. I still appreciate it very much that you simply talk with your customers about these issues. Back then I said I would not, under any circumstances, buy anything that is not in a documented, open format (Acrobat is borderline, but seems to be OK). This is still basically true, though I have some more thoughts on it since then. My refusal still applies to anything that limits what I can do with an ebook. I want to use it on as many devices as I want, I want to print it and I want to copy and paste bits of the text. I could agree to buying encrypted content as long as the format is still open and documented and doesn't restrict me more than maybe having to enter a password every now and then. My main concern is that I do not want to be dependent on any sort of infrastructure outside of my control. One of the worst examples of this is the Steam system used to deliver Half-Life2. The game is unusable once a Steam server goes down, even in single player mode. So I want something where I will be able to use (not just read) the ebook in the future, even on different systems, or if Manning or OSoft or anybody else goes out of business. I hope you will all stay afloat for a long time, but one never knows. Most current DRM &quot;solutions&quot; don't offer that, as far as I know. I haven't yet had a closed look at the ThoutReader DRM, so I can't comment on that. (Is there a good introduction to that anywhere?) Thanks for the great books Carl-Eric </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:cm.manningpublications@bitforce.com"> Carl-Eric Menzel</a> wrote:</h3> <div class="commentbody">I forgot one thing I wanted to mention: I have no trouble with watermarking - if you can somehow identify the buyer of the ebook within the file, it should discourage most illegal sharing of the book. It doesn't have to be overly restrictive in that case. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:mcarey@osoft.com"> Mark Carey</a> wrote:</h3> <div class="commentbody">Thanks for your comments Carl. When the developed the ThoutReader, DRM was an afterthought. After listening to a lot of customer feedback, we came up with a unique solution that was minimally invasive. All you have to do is register as a user 1x, and all of the content you purchase from Manning after that will open without further intervention on your part. We chose not to &quot;imprint&quot; the DRM to a particular machine but rather the user. This means you can install and use any Manning title you purchase on any machine you use. Best of all, you do not have to be online to use or validate anything. I hope this information helps. We start rolling out the Manning titles beginning next week. Let me know if you have any questions. Mark Carey OSoft.com </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:cm.manningpublications@bitforce.com"> Carl-Eric Menzel</a> wrote:</h3> <div class="commentbody"> Yes, I have a few questions :-)  Just to satisfy my curiosity and try things, will I be able to download the ebooks I already purchased as ThoutReader documents?  Is there a good overview/documentation of the ThoutReader format and its encrypted version?  Thanks Carl-Eric </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:hetr@manning.com"> Helen Trimes, Marketing</a> wrote:</h3> <div class="commentbody">We certainly thought that Manning ebook customers would want to convert their PDF ebooks to the ThoutReader version. That's part of the beauty of the new system, having all your reference material accessible in one place. We're working on how to best do that and hope to get the word out very soon! Right now, one of the best places to get an overview of the ThoutReader is at OSoft: http://www.osoft.com/store/pages.php?pageid=featurebenefit While you are there, you can download the ThoutReader and some of the free packages and try it out for yourself. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:graham@biomedcentral.com"> Gaham Triggs</a> wrote:</h3> <div class="commentbody">Search is hardly an advantage of ThoutReader. Maybe compared to the standard PDF reader it is, but our systems are (or can be) so much more than that. Desktop search engines index PDFs, so with the PDFs, we can not only search our digital libraries, we can do the search across *all* the documents on our systems (well, the unencrypted ones at least). </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="http://www.manning-blogs.com/nucleus/index.php?itemid=9"> Peter</a> wrote:</h3> <div class="commentbody">You keep talking about how ThoutReader is not restrictive etc., but that completely misses the point. Not only is its output unbearably *ugly* as already pointed out (when I pay $20+, I insist on having printed book quality, i.e. PDF, not HTML!), it's annoying to be forced to use a reader don't like and am not used to. I use KPDF to read the PDFs, not Acrobat Reader, and it has pretty much all the features I need for comfortable reading. I do *not* want to change my reading habits and if the only way to buy an ebook from you is to use some weird reader, I'll manage without the book. For example, I could use Lucene in Action when developing our product, but I'd rather spend one or two days more on understanding the parts I need from Lucene's sources and examples than to waste $20 on inferior quality ebook... </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:cm.manningpublications@bitforce.com"> Carl-Eric Menzel</a> wrote:</h3> <div class="commentbody">I've tried ThoutReader now. I think I could warm up to the concept, but form my point of view it is still lacking in some respects. I definitely have to agree on the looks. Compared to a ClearType/CoolType enabled Acrobat, its screen output really is, well, not ugly, but a big step backwards. I don't see layout equality with the printed version as an absolute requirement, though it would be nice. But reading this completely unaliased and without any typographical or layouting niceties simply is less enjoyable. And while the content is of course most important, I don't think we should step back on the niceties, when it is already possible to have them. I do have a suggestion, though: Can you manage to embed a different browser widget? I.e. Mozilla/Gecko instead of the Java Swing browser. That way we could use any of the capabilities of the OS, like ClearType. And we would have a lot more CSS compliance, which would enable better layouting. Which leads me to my second suggestion: *Please* let a good page/type designer create the CSS layout for these files. &quot;from developers for developers&quot; is good when it's about the content, but I have never seen it work when it comes to UI or page design. The layout of the printed Manning books (and the PDFs) is beautiful and well readable. Even taking into account the differences of reading on screen instead of paper, what I have seen so far as ThoutReader files simply doesn't do that justice. Third suggestion: Use SWT instead of Swing. You get a lot of the niceties for free with that. Fourth suggestion: UI improvements. Let me get that sidebar on the left completely out of the way while I'm reading. My conclusion so far: Yes, I can see that ThoutReader *might* become an interesting alternative to PDF, if its advantages are fully used, and the content enhanced to that effect. Right now, it's interesting, but to me, subjectively, not as pleasant to use as Adobe Reader. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="http://www.manning-blogs.com/nucleus/index.php?itemid=9"> Robert Varga</a> wrote:</h3> <div class="commentbody">Sorry Mark, but I cannot quite grasp, why you think, that any free/opensource developers would be thrilled to help you creating or improving a software which in turn restricts their freedom. If you want those features to be developed, then why do you not make a software which does not restrict people at the same time of helping them do something... Also, if you think that reading large novels in TR is not really an enjoyable experience, not even compared to PDF, then why don't you try to change THAT? So I guess, if you really want to attract developers to your product, you should try to find a development direction, which is useful for those developers you try to attract. I actually downloaded quite a number of books from the internet, but mostly used them to get a glimpse into a book, to determine if it is worthy of buying. And afterwards I bought them in paper form. I know, it is not really environment friendly, but being a hedonist when I am reading, it is much more practical and comfortable to read a paper book instead of an ebook. Since I payed for the book, even more than what the ebook costs, and I don't really use the ebook once I got the paper one, I don't really feel like I was cheating anyone out of money. The unprotected PDF actually provided an incentive of buying the book. And where did that require any use of DRM? Nowhere. Would a DRM restriction hinder me in any of my capabilities? Yes, it would restrict my capability of exercising my freedom, since I would be required to install a software to get a peek into the book, for which I have absolutely no use otherwise. Would it bring more money for the publisher? Definitely not from me, since I don't like to read lots of stuff on the internet, I like them in the handheld form, while lying on my bed. So honestly, I don't really see any attraction in TR, and probably lot of other readers are seeing things this way, too. Particularly while it is not offering the visual quality of PDF. Regards, Robert Varga </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="http://www.manning-blogs.com/nucleus/index.php?itemid=9"> Lars Goldschlager</a> wrote:</h3> <div class="commentbody">1 advantage and 1 dissadvantage more compared with Adobe: A1) You can get and read DRM books on Linux with ease. D1) You can't read un-drm books on a Palm pilot (beleive me, getting your DRM pdf into a palm is hell). not until someone ports the format to a palm reader app (I don't have the time to do it right now) </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="http://www.manning-blogs.com/nucleus/index.php?itemid=9"> Yuri Khupchenko</a> wrote:</h3> <div class="commentbody">If TR is an Open Source, why don't you put to its site some encrypted document (with any text) to check for developers that TR provides realy strong protection? Until now, we only know some basic things. But nobody can't say for sure that your invetsments (I mean Manning) really protected by TR. As for me, I think within a month or two would be possible to find in eDonkey and others Manning books again, but now in TR format. Also, I agree PDF needed to check is it worth or not to purchsase a printed edition. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:Reiner.Proels@laposte.net"> Reiner</a> wrote:</h3> <div class="commentbody">What about Palms e-Reader? It also supports encryption of eBokks. And I like it to read books in the train using my Palm, so I think it is good idea to support eReader also. PS: Reading PDFs on a Palm is not very comfortable (at least you should use a PDF creator which adds tags)! R </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:iash@manning.com"> Iain Shigeoka</a> wrote:</h3> <div class="commentbody">Hi Reiner, We'd love to support the Palm e-Reader (and also the Microsoft PocketPC Reader, Symbian reader, etc). Unfortunately Manning is a pretty small company and we simply don't have the resources to create infrastructure, buy and use conversion software, etc to support all these different formats. Even very large publishers don't support more than one or two ebook formats (if they support any at all). This is even worse for small markets like computer technical books because the number of paying customers that would buy ebooks in any one of those formats is very small. So for better or worse, Manning must focus on one ebook format and try to make that choice as smart as possible; to serve both our customers with ease of use and functionality and our authors (who need to get paid for their work). Our decision of TR will hopefully be able to work on quite a few platforms including palm (J2ME support for TR is not available yet although OSoft has it on their wishlist and with TR being open source, hopefully, someone will &quot;scratch that itch&quot; and start a port sooner rather than wait for OSoft who has their hands full). We certainly don't claim TR is perfect today, but we hope that it's the best choice for us and provides the ability to rapidly improve and expand in the future. -iain </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:gvarnell@osoft.com"> Gary Varnell</a> wrote:</h3> <div class="commentbody">Carl, We agree completely and have decided to re-implement the Thout Reader in C++ using Mozilla. This is a side project to the current java roject, but that is the beauty of having an open source reader. Anyone can potentially re-write the Thout Reader using any language they want. QT is making some great strides and promises windows GPL with 4.0 due later this year. Currently Thout uses a non-validated xml format that is simple to create and render. In fact in testing with Mozilla we were able to render Thout documents with nothing more than an attached xslt style sheet. With Thout 2.0 we will have a validating XML format which will make document creation easier using existing xml tools. Anyway I just wanted to let you know that we hear you, we agree and we are doing everything we can to make the Thout reader meet and exceed your expectations. Please be patient with us and continue to give us your objective criticisms as they help us make the right decisions to enhance Thout. While I am typing here (there are more appropriate threads for this) I would like to address some of the DRM concerns. DRM in Thout is very unobtrusive. The first time you download a book a user key is generated. You download your user key as a file. This user key file can be backed up to cd and saved along with your downloaded Thout packages. You can install this key on as many machines as you would like, and it is independent of Osoft in that it will always work to unlock your content whether OSoft servers are online or not. Once you register your Thout Reader by clicking file/register and browsing to your key file (MANNING.key) you can open any encrypted Manning book without entering a password or any invasive dialog whatsoever. This was the least intrusive method we could conceive. Still we have seen some very good ideas in this forum. Gary Varnell - CTO OSoft </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:cm.manningpublications@bitforce.com"> Carl-Eric Menzel</a> wrote:</h3> <div class="commentbody">OK, that sounds pretty interesting already. It's good to see that we're being taken seriously ;-) Of course I can't stop nitpicking and will say that having it all in Java would still be nice, but I guess basing it on Mozilla isn't bad either. I will follow this development with interest. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:gvarnell@osoft.com"> Gary Varnell</a> wrote:</h3> <div class="commentbody">Carl, The C++ project is a completely seperate effort. The Thout Reader will always be available in Java. The only reason I mentioned the C++ project is because it will use Gecko for rendering and XML transformations. We have researched many open source embedable browser options for Java and Gecko appears to be the best option. Currently however embedding Gecko in Java is difficult. There are projects such as JRex that provide a Java interface for Gecko that we are looking into. By starting a sideline project in C++ we will be able to use the Gecko api natively. I mentioned QT before, and it is very possible that this will solve most of our problems allowing Gecko to be embeded in Java, Perl, and C++ applications. Unfortunatly however we have to wait a bit as currently QT is not available under GPL on Win32. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:werpu@gmx.at"> Werner</a> wrote:</h3> <div class="commentbody">Just checked out Toutreader, I dont really like it, the fonts are a non issue here on OSX, but the main problem as others pointed out, HTML as markup for the Layout. The next problem, I gave my worst fear a shot and tried to print something out, there simply was no print menu item. Sorry to say that, I also would prefer watermarking as I already have pointed out. Watermarking is strong enough to prevent sharing to a certain degree. But it leaves everything open to the single user on what to do with it. Also sorry to say that, but one of the big plus points of buying mannigs was that I had the option to print out the books for me as often as I wanted (usually one for work and one for at home) if the printing is disabled or crippled in the end, I will go for printed books again, but this time for books I can get easily, which over here (Europe german speaking country) is definitely not Manning. (usually OReilley or local publishers are in stock here) </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:mcarey@osoft.com"> Mark Carey</a> wrote:</h3> <div class="commentbody">Werner, Unfortunately, your evaluation is not based on a Manning title. The same meticulous care Manning puts in their printed books has gone into the ThoutReader implementation. OSoft built and released a new version of the ThoutReader in order to support the functionality Manning required. The font is easier to read and the images have been colorized. Manning books CAN be printed in the ThoutReader. Mark Carey President OSoft </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3><a href="mailto:Jim.Cooper@sas.com"> Jim Cooper</a> wrote:</h3> <div class="commentbody"> On the subject of DRM, perhaps someone could review this page:  <a href="http://www.baen.com/library/">http://www.baen.com/library/</a><br /> <br />Baen books (one of the &quot;biggies&quot;) has been supplying copies of older books in completely unprotected format for a while, now, and have found that it has only BOOSTED sales, rather than lost them money.<br /> <br /> They also have a &quot;webscription&quot; service, where you can purchase new books a chapter at a time, for a reasonable price.<br /> <br /> Admittedly, this is in a different genre (SF/Fantasy), but the distribution model should still be at least somewhat applicable to all. </div> <div class="commentinfo"> 15/02 08:27:02 </div> </div> </div>]]>
        
    </content>
</entry>
<entry>
    <title>Strong opinions on ebooks</title>
    <link rel="alternate" type="text/html" href="http://www.manning.com/links/2004/11/strong_opinions_on_ebooks.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.manning.com/blog-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=24" title="Strong opinions on ebooks" />
    <id>tag:p.hostingprod.com,2004:/@www.manning.com/links//1.24</id>
    
    <published>2004-11-15T22:40:20Z</published>
    <updated>2006-03-14T22:42:51Z</updated>
    
    <summary> Opinon on DRM seems to be formed. But I remain agnostic. People appear to think that Digital Rights Management has been proven not to work. But it&apos;s important to remember that when you are trying something new, failing is...</summary>
    <author>
        <name>Marjan Bace</name>
        <uri>http://www.manning.com</uri>
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.manning.com/links/">
        <![CDATA[<div class="contentbody"> Opinon on DRM seems to be formed. But I remain agnostic.<br /><br /> <a name="more" /> People appear to think that Digital Rights Management has been proven not to work. But it's important to remember that when you are trying something new, failing is easy. Succeeding requires insight and persistence, and usually some luck--succeeding is hard. I simply don't believe that enough options have been tried in using DRM, and with enough imagination. We want to try out some interesting ideas before giving up. Maybe we'll find that what our readers get outweighs the negatives. <br /> <br /> I want to mention a few of these attractive ideas, but let me first say something about the reactions against Manning introducing any controls whatsoever. The current technical ebook market consists of Manning with unencumbered PDF ebooks, and all the other publishers with no ebooks.(+) Several offer the online web service, Safari. On a scale of 1 to 10 with 1 being tyrannical DRM and 10 being complete freedom, Manning PDFs are a 10, Safari is about a 3. Our competitors with no ebooks at all are about a zero. :) We're seeking an alternative somewhere between those endpoints but still heavily favoring ebook freedom, maybe around an 8. Most realistic solutions in real life are in a gray zone between total black and total white.<br /> <br /> Of course, Safari <em>is</em> an option, but we've decided against it. It is nice if you are online, but you cannot use it on the train like Manning ebooks. And the name wickedly favors one of the members of the Safari collaboration. Our participation would implicitly be promoting a competitor's brand.<br /> <br /> The negatives of DRM are pretty obvious, so what are some interesting possibilities? One I love is the idea of using a timed key to allow people to come into our &quot;store&quot; and browse through the <em>entire</em> book for a certain time. Normally online you get unencumbered PDFs of one or two chapters. But with timed-key encryption we can give you the entire book for say an hour. Or two. That parallels the physical bookstore experience and is definitely better than what we can offer you now.<br /> <br /> The timed key idea could be used for the actual sale too, although we're not actively thinking about that. For example, we could let the buyer tell us how long he wants the book for and a formula would tell him the cost; the timed key would enforce the agreement reached.<br /> <br /> Another sequence of ideas applies to ThoutReader, deriving from the fact <a href="http://sourceforge.net/projects/thout/">it's open source</a>. TR already includes annotations, unlike Acrobat (although the new Acrobat 7 apparently will allow them). By analogy with the physical book I've always considered the capability to annotate an ebook a desirable feature. Thinking by analogy doesn't always work, but if the feature is well implemented it might help people find places they have read, a bit like finding the worn or dog-eared pages of the physical book. It could let them add and then find their own additions to the content, without limitation in size. And it would allow something Iain Shigeoka suggested, sharing of annotations between our readers. As Iain sees it, sometimes the shared annotations can be more useful than the original content itself. I doubt that could happen with Manning content :) but it's a great idea I'd like to see tried.<br /> <br /> The TR option appeals to me because it is open source and pure Java. I think we should try it and maybe even some of the people now telling us not to will join in to develop exciting new features none of us can quite imagine now.<br /> _______________________<br /> (+) I've recently been made aware that the Pragmatic Programmer does offer  <br /> unencumbered PDF ebooks. The above statement is in error, but it remains <br /> that they are a rarity.  </div>   <div class="contenttitle"> <h2>Comments</h2> </div> <a name="c" /> <div class="itemcomment id0"> <h3> Mark Carey wrote:</h3> <div class="commentbody"> As one of OSoft's developers for the ThoutReader, I would like to share with you how we plan on positioning the reader. The ThoutReader is an open source cross-platform multi-document help system that allows developers to view ALL of their favorite reference material including application documentation, books, tutorials, even their own contributions - offline. OSoft's vision is to train, educate, and help the open source community by providing a standardized training platform that would allow customers to buy, create, or modify training content in a standardized format while supporting current industry standards DRM is optional and can co-exist with non-encrypted material. It is minimally invasive and does not require passwords for each use, log-in, or constant validations. We realize no DRM is foolproof and therefore implemented it is a deterrent that signals ones intent to ignore IP and copyright laws should the DRM be circumvented. We believe that Manning readers will thoroughly enjoy the ThoutReader. The ThoutReader is an open source Java application designed to promote the creation, distribution and usability of technical information. Many of Manning's readers are Java experts and we very much value your opinion on our creation. Future versions (2.0) of the TR will include a plug-in architecture using the open source JPF framework. This will allow anyone familiar with creating Eclipse plug-ins to create plug-ins for the ThoutReader. We are also working to handle existing formats such as DocBook, Tex, Javadoc etc. natively as well as incorporate other features such as public annotation. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3> Satish Srinivasan wrote:</h3> <div class="commentbody">I am a Java developer by trade, Mark Carey, and I have purchased almost all the Manning e-books that have come out in the last couple of years. Haven't read many (?most) of them, but that's a different story. <br /> If Manning e-books were DRMed I would NOT buy them any more. Period. And I bet there are many others like me.  <br /> Books get pirated anyway. Whether they are from O'Reilly or Addison Wesley. Marjan, you may feel the pinch more because Manning is smaller than many others, but do you really think Manning books are pirated any more than say, O'Reilly books ? Not at least in my experience... <br />Instead, I'd argue that there is a valid case for lowering the already reasonable price of Manning e-books from 22$ to say 10-12$. At that price-point, I believe many/most developers, at least in America and Europe would buy rather than pirate. <br />If you are willing to experiment with DRM, which so many of your long-standing customers are so vocally against, surely you could try out a lower price-point to see if whether that makes a difference in reducing piracy and increasing the volume of sales ? <br />If that experiment fails, and you decide you need more protection for your titles, the maximum restriction that I for one, would be ready to accept, would be say a variation of the Sourcebeat model, where you password protect the PDF with the email-address of the licensee. Have you considered that option ? <br />I have enjoyed buying and reading many Manning titles over the last couple of years. Please, pretty please don't go the way of DRM :-( </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3> Marjan Bace wrote:</h3> <div class="commentbody">Satish, let's do this: when we have the TR-format ready for the books you have bought from Manning, we'll give them to you at no charge. I simply cannot accept that anyone can be certain about this without trying it out. Can we agree that you will at least try it and come back then with your reactions? On the matter of price, I wish you were right. But the indications we have are that price appears to make little difference. Our current ebook prices are about 50% off the list price. When we started selling ebooks it was 70% off. At the time we made the transition we saw no change in the number of copies sold--zip! On your suggestion that books get pirated no matter what, when we last looked there were a lot of O'Reilly books on the networks, but as I recall, they were all from off the CDs they used to add to the back of their books. There were no recent titles there, since they stopped providing the CDs and went to Safari. I could be recollecting this wrong and when I get some time I'll try to verify it. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3> Satish Srinivasan wrote:</h3> <div class="commentbody"> Marjan, you make lots of good points that need a considered response. I'll frame one in a PM... </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3> Eric wrote:</h3> <div class="commentbody">Marjan, The reason that O'Reilly has discontinued their CD Bookshelf series is because of piracy, or so I've been told. We have corporate-wide subscriptions to all of their CD Bookshelves, and they're great, but we won't be seeing any updates unfortunately. I can definitely understand Manning's stance on trying to stop piracy. I'll give the TR-protected version a try before I pass judgement. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3> Andre Roodt wrote:</h3> <div class="commentbody">I have bought a couple of DRM ebooks recently, and while it has been a pain in terms of downloading the book, once on my pc or device it poses no problem at all. DRM doesn't restrict you to the number of devices you read the book on, as long as you have activated acrobat on that device. So if you are not interested in sharing your ebooks with others, why the fuss? </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3> Axel van Lil wrote:</h3> <div class="commentbody">Hi, just a quick comment from a java developer. I LOVE your ebooks, have lately bought 4 of them. So do my colleagues. Our absolute No. 1 argument pro manning e-books is the file-format. PDF. No need for an additional reader, no drm-stuff, looks good in all kind of viewers (Adobe, xPDF, etc.). A dependency on a specific application to read the files destroys this advantage. We would return to the regular printed versions (and a budget is a budget is a budget, resulting in less bought books). Sorry about that, but that's ho we'll act. My 2 cents... </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3> Iain Shigeoka wrote:</h3> <div class="commentbody">Hi Robert, We do &quot;stamp&quot; all our PDFs with name and emails and have been doing it for a while. I think the entire catalog started being stamped early last year, and we were experimenting with it half a year or more before that (by stamping MEAP chapters and finished ebooks). I believe this was before Pragmatic Programmer existed. In any case, PDF stamping doesn't appear to be a significant barrier to ebook theft. We are taking our switch to TR format slowly and hopefully we can make the transition a successful one. We will be allowing customers to purchase both TR and traditional Manning PDF ebooks. We feel pretty confident that we'll be able to grow the TR platform in such a way that customers will prefer that format over PDFs. And if we can't make TR format desireable to customers, then we can reevaluate your decision and maybe try some different strategy. This should be be a win-win situation for all our customers. -iain </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3> Robert McGovern wrote:</h3> <div class="commentbody">*I've recently been made aware that the Pragmatic Programmer does offer unencumbered PDF ebooks* Well one thing they do is to embed the purchasers name into the text of the document at the bottom of every page but other than that they are unencumbered. (I pointed this out in the customer survey you'se carried out last year, I gather it didn't get passed up the chain of command) I think Manning will partly shoot themselves in the foot if they go with DRM / TR. While it might stop piracy it will also put readers off purchasing Manning eBooks. </div> <div class="commentinfo"> 30/11 00:00:00 </div> </div><div class="itemcomment id0"> <h3> Robert Varga wrote:</h3> <div class="commentbody">Marjan, I would say that your recollection is not really 100% correct. I saw copies of several titles from O'Reilly floating around on the net, among them titles for which I purchased the printed versions and those titles arrived without a CD (even titles from 2003). So there are definitely pirated versions of newer versions on the net. After all, a script recreating a html structure from individually received html files automatically traversed and downloaded with a certain delay after each other is not black magic. I would also be rather disappointed to see Manning go on the DRM way. The advantages of DRM can be enjoyed without bearing with the disadvantages. Why not just provide the advantages? Or why not give a choice to the customer? Let him decide which version he wants to download... the static non-DRM-encumbered one, or the collaboration-enabled DRM-encumbered... I personally would opt for a collaboration site without DRM. If you want to provide your customers with additional services then do that, but don't try to chain him down with DRM simultaneously. That is not a good package deal. And if you want additional income, then for each page where the customer does not have the respective ebook or printed book purchased, put on some paid ads (although I don't really know how much income is realisable from banners nowadays...). Actually I don't know if there is a reliable way of determining whether the person has the printed version (except registering the printed version like O'Reilly does). Obviously the word on page XXX is not reliable. </div> <div class="commentinfo"> 02/11 05:14:18 </div> </div><div class="itemcomment id0"> <h3> Jimm wrote:</h3> <div class="commentbody">I whole heartdly agree with you. I have purchased dozen of java ebooks from manning, and personally, at times when i wanted to buy a book, but the high prices discouraged me, manning's ebook always saved the day. Also, i have my reading moods, and it always helps to buy and download ebook at that time and get some substantial reading done. </div> <div class="commentinfo"> 05/11 07:05:53 </div> </div><div class="itemcomment id0"> <h3> John Munsch wrote:</h3> <div class="commentbody">&gt;I simply cannot accept that anyone can be certain about this &gt;without trying it out. Can we agree that you will at least try it &gt;and come back then with your reactions? I'm sorry that you cannot accept that. But I am quite certain, DRM = no purchase. It's as simple as that. If you use DRM you _will_ lose some sales. Perhaps it will only be a few, perhaps it will be a lot. How many you will lose and whether it will be outpaced by gains, if any is the open question. As for pirated O'Reilly books, I saw a site as recently as a couple of months ago that looked like an O'Reilly bookshelf. Probably at least a hundred titles if not more. It's possible they were all older titles from CD but I was unaware that they had released that many at any point. Either way it doesn't really matter to me, I haven't shared my two Manning titles purchased in ebook form with anyone, nor did I download any O'Reilly titles when the opportunity presented itself. Here's what DRM gets you. I paid for Safari for close to a year before I quit, what do I have to show for those months of $15 payments? Nothing. </div> <div class="commentinfo"> 05/11 07:41:00 </div> </div> <h3> Max Khesin wrote:</h3> <div class="commentbody">A note on Safari: it is not a competition to your current method of distribution at all (even if they promote it as such). Their books are TOO annoying to reas AS books. What Safari is occasionally useful for is looking things up, sort of MSDN for open source technologies. Whether that justifies the pricetag I will leave to my employer, but they are not ebooks. Another note on piracy. People who stuff their HDs with pirated ebooks are not lost customers (which is not the case with movies) - the effort to actually read a book is much greater. So while I am not saying that piracy is a big problem, I am suggesting that it cannot be judged by the traffic of pirated material on the networks. Lastly, piracy's role as advertising should not be ignored. Software companies have long known this fact and incorporated it into the way they persecute violators. I occasionally use the networks as the &quot;ultimate try and by&quot; mechanizm - I downloaded a physics lecture from ripped from a teach12.com CD and that led to over a thousand $ of business for them. </div>]]>
        
    </content>
</entry>
<entry>
    <title>Ebook publishing in the real world</title>
    <link rel="alternate" type="text/html" href="http://www.manning.com/links/2004/10/ebook_publishing_in_the_real_w.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.manning.com/blog-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=23" title="Ebook publishing in the real world" />
    <id>tag:p.hostingprod.com,2004:/@www.manning.com/links//1.23</id>
    
    <published>2004-10-07T22:37:16Z</published>
    <updated>2006-03-14T22:40:09Z</updated>
    
    <summary> We feel we have to make a change in the way we publish our ebooks. We have to start protecting them. We have no hard data, but a lot of anecdotal information is adding up to a coherent picture:...</summary>
    <author>
        <name>Marjan Bace</name>
        <uri>http://www.manning.com</uri>
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.manning.com/links/">
        <![CDATA[<div class="contentbody"> We feel we have to make a change in the way we publish our ebooks. We have to start protecting them. <br /><br /> <a name="more" />  We have no hard data, but a lot of anecdotal information is adding up to a coherent picture: For certain kinds of books, unprotected PDFs are exchanged massively over peer-to-peer networks and the hardcopy sales are hurt. For other books the losses appear to be small or non-existent, but I'm not terribly confident about it. It is possible that those sales too are being damaged but less so, and we're simply unable to distinguish the signal from the noise.<br /> <br /> We have decided to start protecting our content with some hesitation and trepidation. Our open PDFs have been a popular feature with our bona fide customers (they've been popular with the thieves too, but we're not sure we care). As I started thinking about writing this blog, I received a message with this subject line: <a href="http://www.manning-sandbox.com/thread.jspa?threadID=10782">&quot;Thank you for your eBook policy&quot;</a><br /> <br /> Here's the core of the message:<br /> <br /> &quot;...I'd like to thank you for your policy of providing Manning eBooks in a simple, unencumbered format... When I purchase electronic books from others (such as Wrox through amazon.com), I have to go through all sorts of acrobatics (pun not intended)... Manning, on the other hand, just gives me a simple PDF that I can use like any other. The book is inscribed with my name and email address, which is the perfect sort of copy protection for honest users.&quot; (Complete message)<br /> <br /> We have heard this same thing from many readers. It is tough to let them down!<br /> <br /> So what are our options? There appear to be only two. Thout and ACS.<br /> <br /> A new Open Source format from OSoft comes with a free reader, called ThoutReader. See <a href="http://www.osoft.com/">OSoft home</a><br /> <br /> The OSoft approach is not to nail the content to a CPU, like Adobe does with its ACS (Adobe Content Server), but to tie content to individuals through the use of a single user key that opens any content purchased by that user. This makes it hard to freely exchange open content since individual user keys reside in the encrypted content and the reader separately.<br /> <br /> This is still being worked on and I am tremendously pleased to have found (they actually found us) a company that is small enough to listen to its customers' needs: they are actually adjusting their protection mechanism in response to our needs.<br /> <br /> We've been thinking about the ACS option but we fear its way of protecting the content is unacceptable to our buyers who want to freely copy our books onto any of their machines. So the OSoft way looks like the likely way out for us. <br /> <br /> OSoft's CEO says this about their approach: &quot;ThoutReader is an open source documentation platform available free at www.osoft.com, for the distribution of eBooks and other OS documentation. While the Acrobat Reader has served us well in the past, the ThoutReader will allow users to browse, search, bookmark, and append not only Manning books, but other open source documentation [in this format] at the same time off line.&quot;<br /> <br /> &quot;The registration process is simple and convenient and does not require the user to log-in or be online every time they wish to use the content. There are no limitations on the number of computers a user may view their purchased content. Each individual is given a user key which is installed in the ThoutReader. Any Manning book you purchase will automatically be configured to be read by your key. Just load and go.&quot;<br /> <br /> Soon something will be decided and put to the ultimate test--the response of the end buyer. </div>  <div class="content"> <div class="contenttitle"> <h2>Comments</h2> </div> <a name="c" /> <div class="itemcomment id0"> <h3> Robert Thau wrote:</h3> <div class="commentbody"> Hi. I'm one of your customers -- I've spent $44 on Manning ebooks over the past week or so, for something that really amounts to a hobby project, but only after I verified that the file format was plain PDF, for which I already had a viewer. If they were DRM-encumbered, depending on the details, I most likely wouldn't have bought either one. Nor would I have gone to file-sharing networks; I just would have done without. And you already have evidence that there are other customers with preferences similar to mine. So, if DRM makes any sense as a business decision, it has to capture more revenue from readers who aren't paying now than it would lose from the existing customers who would be driven away. And here, it seems, you don't have much hard evidence. Nor do I -- but just intuitively, it seems unlikely to me that a truly effective DRM solution would convince anyone who was pirating ebooks on Kazaa to pay for them. They'd more likely just find something else to pirate. What I can say is that the most successful ebook program I'm aware of is unencumbered -- and in entertainment, a domain where you might expect piracy to be more of a problem than for technical books. I'm referring specifically to Baen's program of publishing ebooks of science fiction novels in unencumbered formats. Baen knows full well that they're getting shared -- in fact Baen <a href="http://www.baen.com/library/">gives some of them away for free</a> as loss leaders for the hardcopy. The program has been going for years now, long enough for them to get numbers on it, and they're convinced that it works; see <a href="http://www.baen.com/library/palaver6.htm">here</a> for hard numbers.  I'd urge you to talk to them, and review published SF author Cory Doctorow's <a href="http://craphound.com/msftdrm.txt">thoughts</a> on the topic, before doing anything that would turn existing customers away. Moreover, I'm not sure I see how the kind of DRM solution you outline does a whole lot to reduce piracy. If what you need to read the ebook is a specific crypto key, then what prevents the pirates from distributing ZIP files containing both the reader and the key? The most you'd gain from imposing this kind of system is knowing the identity of the person to whom the pirated copy was originally sold (who may or may not be the pirate, computer security being what it is these days). But you're already baking that into the footer of every page of your PDFs. This is on top of the generic problem with all DRM schemes that the reader software is under control of, well, the reader, who can modify it to defeat the security, by, e.g., saving out an unencrypted copy. Having the source code available makes this easier, but not by as much as you'd think. If you tried to require physical books to be glued to a desk to keep people from sharing them around the office, you might get an extra sale or two from former &quot;office pirates&quot;. But nowhere near as many as you'd lose because of the inconvenience. I'd urge you to do a little more research before concluding that ebooks are all that much different. </div></div><div class="itemcomment id0"> <h3> Eric wrote:</h3> <div class="commentbody">Manning has, to me, replaced O'Reilly as the definitive technical publisher. It used to be that if I needed a technical book, I bought whatever O'Reilly had on the subject. Now, it's Manning. The ebook program is great. I've bought four ebooks (soon to be five when I get finished writing this comment). If the files aren't in a simple PDF format any more, then this will be my last ebook from Manning. Manning won't lose a customer, though, I'll just buy the dead tree version from now on. </div>  </div><div class="itemcomment id0"> <h3> Iain Shigeoka wrote:</h3> <div class="commentbody">Hi, First, thanks for the kind words about Manning books. A quick question; did you try the OSoft ThoutReader and decide you would not use it as an alternative to the Acrobat Reader or are you refusing any alternative to the PDF format? Or are you opposed to DRM and don't care whether a book is in PDF or ThoutReader format as long as the DRM is absent? Manning is developing a close working relationship with OSoft and have had several in depth discussions with them on both a business and technical level about DRM options. The basic thought is that we (Manning) know that we don't fully understand what DRM scheme (if any) will work for both us and our customers. OSoft is interested in working with us and our customers to explore the DRM spectrum to find the best solution. We all gain the benefit of being able to try one scheme, decide that it doesn't work, and try something else. We'll make every attempt to allow you to move from an old abandoned DRM scheme to a new one as we change (aka go from a hardwark locked book, to a periodic server re-authorization, etc). In addition, the process of exploring DRM options will rely on customers like you telling us what works, what doesn't, and offering suggestions on other possibilities to try. We believe our legitimate customers would like to have a convenient and powerful ebook experience while allowing Manning authors to get paid for their hard work. We need help in coming up with a new solution because the current unproctected PDFs fail to treat our authors fairly. -iain </div>  </div><div class="itemcomment id0"> <h3> Barry Gaunt wrote:</h3> <div class="commentbody"> If you have to restrict access to your books theough a reader, please make sure it runs on non Microsoft operating systems. </div>  </div><div class="itemcomment id0"> <h3> Eric wrote:</h3> <div class="commentbody">iain, I've never tried ThoutReader, but your comment has at least caused me to read about it now. :-) Anytime I hear about alternative documentation formats, I immediately jump to the conclusion that support for alternative platforms (like the ones I use, Linux and Mac OS X) will be non-existent. Call it conditioning! Looks like the OSoft people are pretty savvy and wouldn't have that problem. I still like PDF because I know the reader(s) and I know how they work, how to bookmark, etc. I like OS X's Preview and like Acrobat Reader on Linux. But, I'll concede and say that I'm willing to at least give it a go on a ThoutReader-published book. Thanks for your insight! </div>  </div><div class="itemcomment id0"> <h3> Iain Shigeoka wrote:</h3> <div class="commentbody">Hi Eric, We're very aware of the fact that our readers are on a wide variety of platforms so that was one of the first things we made sure was supported. Many of the Manning staff is on OS X so we also have personal reasons for making sure alternative platforms are supported. The one missing 'platform' is J2ME (PDAs like palm pilot). OSoft has said they would be willing to investigate a J2ME version of the ThoutReader if enough readers requested it. I'm glad you're willing to give ThoutReader a spin and see if it will work. Hopefully it does, and if it does not, we always have other options or hopefully OSoft can modify or extend the reader to accomodate our needs. It's starting to feel like maybe we need to have a more organized way of receiving and discussing feedback since this could be an iterative process... -iain </div>  </div><div class="itemcomment id0"> <h3> Christopher A. Petro wrote:</h3> <div class="commentbody">I also object to DRM-encumbered books. I've been thrilled that Manning has used a non-encumbered format to date. I've already been through the DRM nonsense with fiction books and it was an unpleasant experience. My response there has been simple: pirate a scan or a copy that's had the DRM removed, and buy a paper copy of the book to throw in the closet and never look at. It's a waste of resources and more expensive than an e-book, but it lets me read my books the way I want to and gives the author the money I feel he deserves. (In many cases way too much goes to the publisher, but that sacrifice was the author's decision. At least authors generally get to retain their copyrights, unlike musicians.) If Manning were to move to an encumbered format, I'll snag a &quot;fixed&quot; copy off a p2p network when I find I need it at 3am, buy the dead tree version the next time I'm at the bookstore and toss it on the shelf where it will look nice. Please don't let OSoft or anyone convince you that DRM will stop even the most casual of piracy. Existing efforts have succeeded only in stopping legitimate use (this is backed up by as much evidence as can be expected, but of course it's not conclusive), and there are solid reasons--theoretical and practical--why new efforts will not be able to do any better. </div>  </div><div class="itemcomment id0"> <h3> Vik wrote:</h3> <div class="commentbody">Any particular reason that a Safari-style online reading service is not an option? The obvious downside is that you have to be online to read. In my humble opinion, this has not been a problem for me since I read at work or home -- both places with a high-speed internet connection. If I must take something on the go, I can download an individual chapter as PDF. I've been a happy safari subscriber for 3+ years now. Just a thought. </div></div><div class="itemcomment id0"> <h3> Scott Walters wrote:</h3> <div class="commentbody">I'm just finishing up writing &quot;Perl 6 Now&quot; for Apress and a small mystery was solved for me - where do all of those clean PDFs circulating on file-sharing networks come from? Apress is sending out a batch of CD-Rs with production proofs of the chapters to people to review while the book is at the press. When it comes to people trading binary copies of information the mantra to recite is &quot;it only takes one leaked copy&quot;. In Hollywood, the guys working the vault for post production were stealingt copies. Then celebrities themselves were trading promo copies of films (and then were caught by water marking). I've scanned out of print books, OCR'd them, and put them on the net. I've carefully proofread them and the quality is quite good; they're in HTML format with the diagrams as GIFs. Again, it only takes one leaked copy. If people are allowed to print copies of ebooks, they'll print to a file as PostScript and have a perfect copy. Only one person once has to figure this out (say it with me - it only takes one). The pandoras box is open. I know shrinking profits hurt but DRM amounts to a futile effort to turn back the clock to a &quot;better time&quot; when people couldn't copy things or find things. Screw that. Taking advantage of easy copying and easy dissimination of knowledge, you can hire stay-at-home-moms to telecommute, get more feedback from people in the trenches to improve the quality of books in production (think of how Perl Cookbook harnessed the power of perlfaq combined with how C2 and Wikipedia harness the spare time and knowledge of people browsing the web, this combined with your early access program). The only way to beat the curve is to stay *ahead* of it - trying to flatten it is doomed to tragic or humous failure - but always failure. The wave is technical - the financial return has been squandered by small minded paranoid men who want control, and I'm not talking about the publishing industry. Unemployment in the United States for programmers is above average, the average is at a high since the great depression. We're feeding monopolies as fast as we can, pumping billions of dollars out of the free market and into initiatives that amount to trying to flatten the curve and protect the old world from new technology. This is why people are poor and can't afford your books. This is why *I* can't afford books. Still, I've &quot;wasted&quot; hundreds of dollars I really can't spare on books. I think people are spending a dispropotionate amount of money on books considering both the economy and file trading. Don't blame yourself and don't blame your readers - just do what you have to do and cut back peoples hours, try crazy things, cut costs, get rid of offices, move to print on demand and publish half assed first editions (people talk about ORA as the pinnacle of quality but forget their origins - doing ebooks, print on demand, and publishing not entirely polished first editions). I finished _Perl 6 Now_ not knowing what my competition looks like. If I weren't writing a book and didn't have a moral duty to my fellow authors, I'd have downloaded a copy of _Perl 6 Essentials_ 2nd ed in a heart beat. But I consider this borrowing on good will when I trade - all of us - especially the kids in highschool without jobs - *want* to speak with our money, so to speak. We want to support our favorite artists, and we want to give them warm fuzzies with their record/book/whatever sales. We want to influence the economy. We want to see more of whatever kind of book or music we like in store isles and we want it to be there because we're spending money on it. We're very captialist, in the best sense of the word, we people at home. It's the capitalists in government and big business who give the culture a bad name. It's a crime that our culture has been priced at a level we can't afford and we've been improverished so we can't afford it; it isn't a crime to charge for access to culture as long as a healthy public domain exists. But when you feel entitled to make a living, or entitled to stay in business, or entitled to have a copy of the latest Emenim CD that things start to break down - bad things happen when people feel entitled. File traders shouldn't blame the artists (it isn't their fault that the music industry is broken or the economy is rotten) and arists shouldn't blame file traders (ditto). Speaking of culture, whens the last time you've been to the library? They have CDs and books, but mostly books, and they represent the pinnacle of our culture (or perhaps colleges do, in which case college libraries are the place to be). People read books for free all day long. Books and CDs are more popular than they ever were, but libraries are in decline. Reading a book at a library is just like downloading a book off the net - you have it, in every sense of the word, but you don't own it. And if you don't own something, you don't value it, and you don't use it, and people know this. No one wants to borrow their friends car whenever they want to go somewhere; theres bad will from the friend, and you just don't feel like you're driving _your_ car while you're driving it. The psychology is huge. ebooks aren't as popular as paper books still because people have a hard time translating feelings of ownership onto magnetic charges, photos, and electrons. I &quot;have files&quot; on my harddrive in the same way as I have a few piles of books next to me right now (entering them into bookcrossing.com - woo!) - it's a temporary arrangement but a useful arrangement and like the piles is nothing but structure and is otherwise ethereal - non-existant. If at the library you have something but don't own it, here's the converse: how bad would it suck to pay for something and not even have it? That's DRM, and it sucks beyond words. It sucks Dark Ages bad. The back of the curve isn't where you want to be. I'm not saying you should encourage people to trade books online. Here's a suggestion: get a fast network connection, run eDonkey, gtk-gnutella, Kazaa, and the rest of them, and distribute a copy of the book on all of the networks that's perfect in every way but contains some interesting information (and it is interesting) on how few actually sell (I'm told a moderately successful technical book will sell 20,000 copies), how much authors make (not much), point to your permissive DRM-free ebook policy, list topics you'd like to print books on but had to reject because the market can't currently bare them, and encourage the reader to buy the book if she enoys it and finds herself reading more than a few chapters or referencing it more than a few times. But that's not all. I'm not a hopeful idealist. Watermark all of your downloads. This will have a double effect of fragmenting the copies on file sharing networks as there will be hundreds of copies of the same thing, each different, and this will make searching, ratings, and swarming difficult. And then make it very clear as people go to download that the cost of the ebook is actually $100 more than what they've been charged at checkout but the last $100 is forgiven as long as their watermarked copy doesn't appear anywhere. Then write some software and start collecting. There are Perl modules to speak popular peer protocols and Perl modules to interact with common payment gateways. Coincidence? I think not. Human behavior can largely be explained by greed and generosity; the old &quot;gift cultures&quot; of native American indians strongly resembles the file trading culture which resebles the Free Software culture. This stems from a desire to gain value in the eyes of the men we respect the most. Greed stimulates people to pay for works-for-hire and to hoard. Hoarding information is no longer possible. So it's all works-for-hire from here on out. -scott </div>  </div><div class="itemcomment id0"> <h3> Terry Tompkins wrote:</h3> <div class="commentbody">To date, I have purchased five eBooks and either two or three dead tree versions from Manning. I sincerely appreciate the fact that the ebooks have been unencumbered with DRM. I have only a couple concerns regarding a mechanism such as OSoft's Thoutreader: I frequently copy my PDF-formatted ebooks to my PocketPC to read when I can't drag my laptop or a paper copy with me. I would want any alternative solution to be supported on Windows, Linux and PocketPC. My other conern is that I'd want the reader application to have similar features (such as search), display quality and render speed as PDF. I have no problem with positively branding a book with my identity, as long as the format NEVER locks the document to a single machine. I have several machines, and I make significant hardware changes on a regular basis, so losing an entire library after a hardware upgrade would ruin my whole day. I have paper books that have resided on my bookshelf for well over 20 years. I'd probably be quite upset if my ebooks couldn't be read some day because the company providing the format vanished and the reader tool should stop working with a future OS upgrade. So, the bottom line for me - I'll continue being a happy customer as long as the issues above are addressed with any format changes. </div>  </div><div class="itemcomment id0"> <h3> Tom wrote:</h3> <div class="commentbody">Another very important issue for me is the possibility to be able to &quot;fulltext-index and search (and preview with search-term-highlighting)&quot; the ebooks. With (unencumbered) pdf, this is possible today with some of the &quot;personal desktop search-tools&quot;, which are introduced these days from many companies (google [http://desktop.google.com/], Microsoft [soon], Apple-Spotlight [soon, see: http://developer.apple.com/macosx/tiger/index.html], X1 [my favorite at the moment, see http://www.x1.com/]). So, I don't know if this will be possible with the ThoutReader-format... </div>  </div><div class="itemcomment id0"> <h3> Azure wrote:</h3> <div class="commentbody">Yes, I do use peer-to-peer software to get books -mainly to see if they are good enough, but not to read them. Good books are the ones that you come back to, and Data Munging with Perl is one of them. I got a copy from the web but ended up buying a paper copy because I was always getting back to it. My O'Reilly books? those are fun, but not as practical as the Manning ones. And I don't own any in print. </div>  </div><div class="itemcomment id0"> <h3> Mike Shoemaker wrote:</h3> <div class="commentbody">I recently purchased Spring Live by Sourcebeat. Their &quot;protection&quot; is awful. First piece is that the pdf's are password protected. This is fine by me, I can still read the pdf anywhere and on anything. I understand that I could easily offer my password out but still it's okay protection for the nice guy. Their second approach is that they removed copy/paste. This SUCKS!!!! Now all the code snippets I find in the book, I have to type in manually. For this reason, I will never buy another Sourcebeat book. Manning, please don't go down this path! </div>  </div><div class="itemcomment id0"> <h3> roger williams wrote:</h3> <div class="commentbody">Wouldn't it be better to simply not publish books in PDF format? Why risk losing money. What do the authors of the books that get pirated think? </div>  </div><div class="itemcomment id0"> <h3> D Brady wrote:</h3> <div class="commentbody"> Well, I'm very sorry to see your initiative to DRM.  I've been a reader of your books, but I can see that will change soon. <br /> <br /> If you think less of DRM in the future I will be back.<br /> <br /> Thanks! </div>  </div> </div>]]>
        
    </content>
</entry>
<entry>
    <title>Hibernate in Action rocks</title>
    <link rel="alternate" type="text/html" href="http://www.manning.com/links/2004/07/hibernate_in_action_rocks.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.manning.com/blog-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=22" title="Hibernate in Action rocks" />
    <id>tag:p.hostingprod.com,2004:/@www.manning.com/links//1.22</id>
    
    <published>2004-07-16T22:35:57Z</published>
    <updated>2006-03-14T22:37:03Z</updated>
    
    <summary> I have a tendency to think about things that worry me--things that are not working well. So, let me even the score by talking about something positive: it&apos;s looking like Hibernate in Action will be a really successful book...</summary>
    <author>
        <name>Marjan Bace</name>
        <uri>http://www.manning.com</uri>
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.manning.com/links/">
        <![CDATA[<div class="contentbody"> I have a tendency to think about things that worry me--things that are not working well. So, let me even the score by talking about something positive: it's looking like <em><a href="http://www.manning.com/bauer">Hibernate in Action</a></em> will be a really successful book for us. <br /><br /> <a name="more" />My confidence is obviously based on the explosive growth in Hibernate adoptions, but more directly it's based on the early responses to the book itself. <br /> <br /> An initial indicator for us is how well a book does in the Manning Early Access Program. As of today, the number of MEAP subscriptions for this book is 3-4 times that of a typical Manning book and that will grow since there's a few more weeks left before the book ships. On the retail side, even before they have sold a single copy, retailers have started sending in reorders. Bookpool.com has reordered, Baker&amp;Taylor is reporting impressive demand in the last month, BN.com has now ordered two and a half times their normal number and the brick and mortar B&amp;N has just upped their order by a good percent.<br /> <br /> You have to give it to them... (Gavin and Christian, of course). </div>  <div class="content"> <div class="contenttitle"> <h2>Comments</h2> </div> <a name="c" /> <div class="itemcomment id0"> <h3> Iain wrote:</h3> <div class="commentbody"> Hi, If you purchase the hard copy book from the Manning website, you are eligible for a free eboook. However, our cart is currently unable to make this offer automatically (we're in the middle of upgrades so this is possible). However, the opposite is automatic - buy the ebook first. Then use the ebook order code as the discount code when purchasing the print book. This discounts the full price of the ebook towards the hard copy price - essentially making it free. If you did purchase a hard copy from us and want an ebook, send an email to ebooks@manning.com with your hard copy order code and we'll set up a download for you. -iain </div>  </div><div class="itemcomment id0"> <h3> Hari wrote:</h3> <div class="commentbody">Why is not the ebook download available for everyone who has purchased the book? I have a hard copy and sometimes an ebook is quicker to reference. </div>  </div><div class="itemcomment id0"> <h3> nidget wrote:</h3> <div class="commentbody">I've read it twice with an equal pleasure. It's probably one of the best IT book I've bought in the last two or three years. And you have a lot of other really good books too (I won't give the titles here as it could disadvantage other books from you catalogue that I haven't read). Thank you for bringing so many good titles to the community. </div>  </div> </div>]]>
        
    </content>
</entry>
<entry>
    <title>Erik&apos;s intuition was on the nose then.</title>
    <link rel="alternate" type="text/html" href="http://www.manning.com/links/2004/06/eriks_intuition_was_on_the_nos.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.manning.com/blog-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=21" title="Erik's intuition was on the nose then." />
    <id>tag:p.hostingprod.com,2004:/@www.manning.com/links//1.21</id>
    
    <published>2004-06-22T22:34:36Z</published>
    <updated>2006-03-14T22:35:26Z</updated>
    
    <summary> Bookstore buyers, individual and enchained, are showing a lukewarm response to our Explorer&apos;s Guide to the Semantic Web (SW) by Tom Passin. That could be serious since they stand between us and our customers. Without their support we&apos;re toast....</summary>
    <author>
        <name>Marjan Bace</name>
        <uri>http://www.manning.com</uri>
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.manning.com/links/">
        <![CDATA[<div class="contentbody"> Bookstore buyers, individual and enchained, are showing a lukewarm response to our <a href="http://www.manning.com/passin">Explorer's Guide to the Semantic Web</a> (SW) by Tom Passin. That could be serious since they stand between us and our customers. Without their support we're toast. <br /><br /> <a name="more" /> Why don't they believe in this book... yet? I can think of only one reason: they remember the buzz surrounding Tim Berners-Lee's Sci Am <a href="http://www.sciam.com/article.cfm?articleID=00048144-10D2-1C70-84A9809EC588EF21&amp;sc=I100322">article</a> published three years ago and they figure, this is old-hat stuff Manning is just getting around to publishing now.<br /> <br /> They're wrong--well, partly wrong. We did sign Tom in the afterglow of Tim's article. And, Tom did take forever. So long that Tim finally got the Millenium Prize, and is now too busy to consider writing Tom a foreword. But the interest in the future of the Web is huge and this is the only book that explains it, not to the specialist but to the rest of us.<br /> <br /> But there's another reason I know they are wrong. No, it's not because I read it and was so taken by it I was actually sorry to be reaching the end. It's because one day I got a message from <a href="http://www.manning.com/catalog/view.php?book=hatcher">Erik Hatcher</a> saying, &quot;... I gotta have this book.&quot; You see, this reminded me of the time when we were deciding whether to publish a <a href="http://www.manning.com/bauer">Hibernate book</a> by some unknown authors called King and Bauer. Our then-star-Java-author responded with, &quot;No way should Manning publish a Hibernate book&quot; (he's now writing for a competitor... :) but Erik told us how it was, that this was one fantastic piece of software and that he was investing in learning it.<br /> <br /> Since then Hibernate downloads continued to grow--starting from a small number but increasing 20 to 30 percent per month, sooner or later you get to very large numbers. I have stopped following them but those were the growth rates. Hibernate is a force out there now and expectations are EJB v3 will incorporate many of its features.<br /> <br /> Erik's intuition was on the nose then. I'm betting it is again.<br /> <br /> PS I got into this musing while reading Eric Bonabeau's HBR article, The Perils of the Imitation Age. Good stuff! The article isn't available on the net and the harcopy single issue costs something like $17. There's a brief description <a href="http://harvardbusinessonline.hbsp.harvard.edu/b01/en/common/item_detail.jhtml;jsessionid=FBCXIJ3JAGFZKCTEQENR5VQKMSARUIPS?id=R0406B">here</a>. </div>   <div class="contenttitle"> <h2>Comments</h2> </div> <a name="c" />  <h3> Alex wrote:</h3> <div class="commentbody"> Glad you were taken with the book; it does given you a more &quot;this is what it is all about&quot; view than any other source out there. I'm wondering what you mean by &quot;luke-warm&quot;, as opposed to people who in the past bought dead-trees compared to people who now buy the eBook version instead? BTW, I asked locally here in Canberra/Australia about Mannings books in general in the No. 1 computer book shop, and they had none. Do you have any clues to the Aussie/capitol market? </div>]]>
        
    </content>
</entry>
<entry>
    <title>Why are .NET books not selling?</title>
    <link rel="alternate" type="text/html" href="http://www.manning.com/links/2004/06/why_are_net_books_not_selling.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.manning.com/blog-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=20" title="Why are .NET books not selling?" />
    <id>tag:p.hostingprod.com,2004:/@www.manning.com/links//1.20</id>
    
    <published>2004-06-09T22:33:01Z</published>
    <updated>2006-03-14T22:34:22Z</updated>
    
    <summary> Because of Microsoft. No, not because MS is failing to get corporations to adopt .NET (although that&apos;s got to be going slower than they expected) but because they are in their own gentle way distorting the market for .NET...</summary>
    <author>
        <name>Marjan Bace</name>
        <uri>http://www.manning.com</uri>
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.manning.com/links/">
        <![CDATA[<div class="contentbody"> Because of Microsoft. <br /> No, not because MS is failing to get corporations to adopt .NET (although that's got to be going slower than they expected) but because they are in their own <em>gentle</em> way distorting the market for .NET books.<br /><br /> <a name="more" /> Here's a reasonably original version of an exchange I recently had with a Manning author, Erik Brown.<br /> <br /> <strong>MB:</strong> On a related question, Jack Herrington (the author of our <a href="http://www.manning.com/herrington">Code Generation in Action</a>) suggests a reason why .NET books are selling poorly. He thinks its because of MSDN. I asked a couple of other people and they appear to agree. Bob Calco first told me that he certainly was buying .NET books (he hadn't seen our <a href="http://www.manning.com/feldman">ADO.NET Programming</a> even though he was interested in the subject). Then when I mentioned Jack's idea he suddenly turned around and agreed. He said the number of .NET books he had bought recently was low and that he was using MSDN a lot. He also uses all kinds of other sources for code samples, etc. There's a lot of useful stuff out there.<br /> <br /> What do you think?<br /> <br /> <strong>Erik Brown:</strong> Well, its an interesting thought (MSDN). They certainly churn out a lot of content, with sometimes daily updates on the various online sites such as www.windowsforms.net and www.asp.net. Add to these all the other free sites out there and you can typically find a how-to for most standard things you may wish to do. So I'm sure it impacts sales. So with companies no longer paying for most books, and consultants worried about the bottom line, the MSDN content is probably used more often than it ever was before.<br /> <br /> Makes you wonder sometimes what future &quot;books&quot; will look like. The paper book is one dimensional sometimes. You could imagine my book, for example, as an electronic medium with a more streamlined and/or interactive tutorial and links to reference material both book specific and available online. Will be interesting to see what evolves.<br /> <br /> (Erik is the author of Manning's <a href="http://www.manning.com/ebrown">Windows Forms Programming in C#</a> )<br /> <br /> <strong>MB:</strong> On the future of books, I'm not sure MSDN is a good indicator. My point is simply that MS is spending a lot on that facility and that in general that isn't the case--companies have real competition and cannot afford to spend real dollars on the information side, specially when there's a whole industry (book publishing industry) willing to do it. So, maybe the situation isn't as bleak as this makes it seem.<br /> <br /> BTW I do not mean to say that books per se will not evolve. The electronic medium is so much better from many points of view. Unfortunately, reading from a screen isn't what people like. They want to recline, slouch, or simply angle their heads... :) When we can let them do that and make it electronic, then a new world of publishing will open up--I hope I'm still active then. Would love to be involved in discovering new ways to publish.<br /> <br /> <strong>MB:</strong> Oh, and Bob Calco later added this: <br /> <br /> <strong>Bob Calco:</strong> Since our conversation, I did a little more looking around here and<br /> there is another issue---most of the .NET books we do have (including<br /> subjects like ADO) are almost all from Microsoft Press. Turns out we<br /> have quite a few--and most of them were borrowed out of my library to<br /> various colleagues, hence my shock when you pointed out Jack's point and<br /> I didn't see a slew of .NET books on my bookshelves. Erik's C# book and<br /> a Prentice Hall book on .NET/COM interoperability are the only two<br /> exceptions to MS Press here at the office. Thus I'd suggest that both<br /> MSDN and MS Press are making it hard for other publishers to sell their<br /> .NET books.<br /> <br /> <strong>Final thoughts:</strong> For a few years now we have been staying away from .NET books--how many loosing business projects can a small company take on? And how many can <em>I</em> take--I hate to help good authors produce good content and then get miserable results.<br /> <br /> Of course, MS Press itself is losing (or was losing) big money on their .NET books so the problem is not just MSDN and MS Press. The problem is also the slow penetration of .NET coupled with the &quot;incredible, precipitous drop in the computer book market&quot; (see <a href="http://www.manning-blogs.com/links/archives/2_Something_new_for_Manning.html#extended">Feb 19</a>). But the market distortion they are causing may ultimately not be good for MS either. </div>   <div class="contenttitle"> <h2>Comments</h2> </div> <a name="c" /> <div class="itemcomment id0"> <h3> malcolm wrote:</h3> <div class="commentbody"> intresting what you have to say about ebooks. at the moment i am beeing sold a buisness package with resale rights on lots of email books. with the promiss of earning thousands . or perhaps thos could be an off load . in order these people might break even. what should one do? kind regards malcolm. </div>  </div><div class="itemcomment id0"> <h3> Scott Walters wrote:</h3> <div class="commentbody"> What the heck is an email book? Can someone do housecleaning around here? Oh well, never mind. <br /><br /> ORA is having the same brainstorm in the same format (public discussion). A few things are happening: people involved in open source projects are becoming valuable authors... this lets readers connect with the brains behind the creations; the Web is fostering diversity... Webseters picture dictionary is an interesting example of how publishers have to work harder as well as diversify; programming is once again largely being done for fun rather than money so the types of information requested is increasingly along the &quot;Hacks&quot; varity; disruptive technologies like P2P, Xbox Linux, datamining the blogsphere, etc are coming along, and people want to be involved in the sorts of things publishes aren't used to catering to (bunnie's Hacking the Xbox is a cool exception of where a publisher didn't drop the ball); as people depend less on their college education and more on books and the Web for their job, the demand for truly advanced books increases, and it's difficult for publishers to raise to this level - but even harder for the Web to (this has been Addison Wesley's strong hold, though I have a Morgan Kauffman book that would easily force my brain to expand out through my ears). <br /><br /> It's certain that you can't keep doing the same thing you're doing. I've been working on perldesignpatterns.com for a while (free online documentation) so I've been kicking around the ideas of technology, publishing, documentation, collaboration, commercialization, and so on... I get a lot of data on which pages people link to, read, and so on and so forth. Oh - some of the best books done in modern times and historically by ORA are nothing but a massive but organized survey of a subject-area - Perl for System Administration rocks for this reason; Perl Cookbook, ditto; Perl Graphics Programming is another example; Perl 6 Now (Apress) will certainly be one of these. I traded ideas with the original editor for two months before something was settled on; there's certainly pressure to change and lack of clear direction in which way. </div>  </div><div class="itemcomment id0"> <h3> James McGovern wrote:</h3> <div class="commentbody">Does MS have a duty to allow other publishers to make money off its technology? Of course not! One fact that wasn't addressed is the &quot;me too&quot; mindset within the publishing community. If publisher A does a book, it almost becomes a requirement for publishers B and C to do a similar book. This will ultimately lead to failure. How about publishers signing books that are a little more diverse? http://blogs.ittoolbox.com/eai/leadership </div>  </div><div class="itemcomment id0"> <h3> roger williams wrote:</h3> <div class="commentbody"> Maybe publishers should seek more diverse topics and especially smaller ones... </div>  </div>]]>
        
    </content>
</entry>
<entry>
    <title>Online publishing</title>
    <link rel="alternate" type="text/html" href="http://www.manning.com/links/2004/05/online_publishing.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.manning.com/blog-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=19" title="Online publishing" />
    <id>tag:p.hostingprod.com,2004:/@www.manning.com/links//1.19</id>
    
    <published>2004-05-18T22:31:59Z</published>
    <updated>2006-03-14T22:32:49Z</updated>
    
    <summary><![CDATA[ On March 24 I arrived at my parents home to take care of them. Both 89, they live in the outskirts of Split, Croatia. They both had pneumonia and when I arrived the household was in a &quot;state.&quot; They...]]></summary>
    <author>
        <name>Marjan Bace</name>
        <uri>http://www.manning.com</uri>
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.manning.com/links/">
        <![CDATA[<div class="contentbody"> On March 24 I arrived at my parents home to take care of them. Both 89, they live in the outskirts of Split, Croatia. They both had pneumonia and when I arrived the household was in a &quot;state.&quot; They are much better and I'm pleased to have had a calming influence. And, what a pleasure to be treated like a rather young man again.<br /> <br /><br /> <a name="more" />Split grew out of a palace built by Emperor Diocletian as his retirement place, around 300 AD. Literally. The mideaval buildings sprout like mushrooms out of the large Roman walls. The number one thing that's different from Greewich, CT is not the language, nor the culture--it's the climate. Reliable and mild, Mediterranean weather is soothing like a good, old friend.<br /> <br /> From this distance my publishing thoughts keep returning to one issue: publishing online. For me the essence of publishing is editorial--getting the writing and presentation to be good and useful, and doing it in good time. Printing, distribution, and even promotion and selling are all distractions. We should be able to create the content, post it, and be done. But here's the rub. Actually, two rubs:<br /> <br /> 1	People steal our content. A recent example was our <a href="http://www.manning-blogs.com/tate2">Bitter EJB</a>. During a casual conversation <a href="http://www.javalobby.org/">Rick Ross</a> once took a look and reported it was being distributed from 70 peer-to-peer nodes out there. In the meantime the book's performance in the stores has been weak. Worse yet are the sites that resell our ebooks. I get furious when I see them. The last one I saw was a Chinese site that accepted donations for a free download of our books, among others. The combination of theft, giving, and asking for charity strikes me as truly weird.<br /> 2 People prefer printed books. Our ebook sales keep rising but so do our overall sales. Whenever I check our ebooks are steady at a single digit percent of our totals.<br /> <br /> What a pity.<br />  </div>   <div class="contenttitle"> <h2>Comments</h2> </div> <a name="c" /> <div class="itemcomment id0"> <h3> Steven Streight wrote:</h3> <div class="commentbody"> I also had to take care of my elderly, sickly mother for a couple of years as a live-in health care provider. I know what it's like to have the honor of caring for an aged parent, and how hard it sometimes can be to remain kind, tranquil, and compassionate. Online publishing presents many challenges, I agree. There needs to be some sort of watermark type, anti-theft code embedded in the online document that prevents transfer and distribution by unauthorized parties. I'm not a programmer, so I'm in way over my head here, but I know there are some art and photo images that you cannot execute a &quot;Save As&quot; command, there seems to be some sort of hidden code that disables image saving. </div>  </div> <h3> roger williams wrote:</h3> <div class="commentbody"> Bitter EJB was an awesome book. What has Bruce got planned for future books? </div>]]>
        
    </content>
</entry>
<entry>
    <title>Something new for Manning</title>
    <link rel="alternate" type="text/html" href="http://www.manning.com/links/2004/02/something_new_for_manning.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.manning.com/blog-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=18" title="Something new for Manning" />
    <id>tag:p.hostingprod.com,2004:/@www.manning.com/links//1.18</id>
    
    <published>2004-02-19T22:30:19Z</published>
    <updated>2006-03-14T22:31:43Z</updated>
    
    <summary> My thinking was driven by the incredible, precipitous drop in the computer book market... At rates reaching 25 to 30 per cent a year (according to Bookscan), starting with the bursting of the Internet bubble, the market has kept...</summary>
    <author>
        <name>Marjan Bace</name>
        <uri>http://www.manning.com</uri>
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://www.manning.com/links/">
        <![CDATA[<div class="contentbody"> My thinking was driven by the incredible, precipitous drop in the computer book market... <br /><br /> <a name="more" />At rates reaching 25 to 30 per cent a year (according to Bookscan), starting with the bursting of the Internet bubble, the market has kept shrinking to the point where it is now less than half its original size. I was hearing that one company's professional book publishing had gone from $40M per year to $17M. Large players like Pearson had merged and reduced their various lines. Others were in their nth staff layoffs. Wrox was gone, and of course, already long ago, so was Coriolis. <br /> <br /> For a small publisher like us it's hard to &quot;see&quot; the shrinkage in our own sales numbers-each year we publish different books and different numbers of them so it's hard to compare one year to another. If you publish lots of books the fluctuations average out. A large publisher's sales in a stable market will be stable. But our sales have fluctuated a lot in all markets, so we really weren't sure what part of the poor results of 2000 and 2001 and 2002 were due to the ever shrinking market. <br /> <br /> In spite of that you do start to ask yourself some basic questions. I am a deep believer in business success ultimately deriving from market growth not business acumen. That may be because of my own lacking acumen. I assume every businessman is basically like me-- muddling along, totally unable to control the events in the outside world. It is interesting to me that almost all great companies identified by Jim Collins in <a href="http://www.amazon.com/exec/obidos/ASIN/0066620996/qid%3D1077233761/sr%3D2-1/ref%3Dsr%5F2%5F1/104-5662018-8115113"><em>Good to Great </em></a> have since his study underperformed. Seriously underperformed.] <br /> <br /> So I started wondering whether I should hedge our computer book publishing with another line; I quickly focused on business books which were nice because I could read and enjoy them myself. So I called Kurt Mathews of <a href="http://www.ipgbook.com/getpage.cfm?file=about.html&amp;userid=67135710">Independent Publishers Group</a> to see whether he had any opinions. Kurt told me there was only one market segment doing worse than computer books and that was business books. But, he said, if Manning is going to do a business book why not do one that answered the question, &quot;What the hell happened to the computer business?&quot;<br /> <br /> Sometimes things happen as if planned. It seems to me now that it was not long after my conversation with Kurt that someone called me from Gartner pitching a book and I had to tell her no. I then asked her whether she knew anyone who could write a good answer to Kurt's question, and out of that appeared <a href="http://www.wapitillc.com/page2.html">Erik Keller</a>. Erik had conveniently left Gartner a few years before and was now free to speak candidly about Gartner, the entire industry, and himself. I have been pleased that he was willing to do so. The <a href="http://www.manning.com/keller"><em>book</em></a> is no whitewash. </div>  <div class="content"> <div class="contenttitle"> <h2>Comments</h2> </div> <a name="c" /> <div class="itemcomment id0"> <h3> Scott Walters wrote:</h3> <div class="commentbody"> Hi! &quot;Netslaves&quot; by Steven Baldwin comes to mind. Humorous, educational, thought provoking, and frightening all at the same time. I hope Erik is able to take a page from it, so to speak. Apress is also publishing titles bridging business and technology. The hubris that fueled the boom and inevitable collapse isn't dead. CEOs still refuse to take responsibilities for their decisions, ignorance, or to accept fundamentals of the universe. They still try to &quot;perform&quot; by reducing services, betraying their customers, and aim for the short term instead of trying to build growth that comes from innovation. There is innovation and new product potential out there but the status quo is fighting it, not adopting it. The number of companies still catering to Microsoft even while trying to battle them and ignoring cries from consumers for something better. Sony and IBM both compete with Microsoft in some arenas and IBM have had bloody battles with them in the past, yet neither will even mention whether or not Linux or FreeBSD happens to run on any of their machines, and forget about asking for a machine without having to pay for a copy of Windows. All the while, they're spending what little money they do pull in on lobbying for more restrictive laws against innovation, trying to centralize the ownership of things like facts and ideas where smaller companies are less able to poss a threat. The result, we all sink. Meanwhile, people are enjoying things like biking, cooking, fine wine and beer, and the finer points of life - things with little or no corporate backing or massive marketplace diversity. Just like solviet russian, we're finding what solice we can in the chaos, returning to basics. I'd like to see &quot;Living Cheap in America - Programmers Guide to Slumming&quot; - I've swapped notes with other programmers on the adjustments I've had to make since the fallout (walking and public transit, noodles, rice and beans, so on and so forth). I think that would do well. -scott &quot;always good for a rant&quot; walters </div>  </div><div class="itemcomment id0"> <h3> Chris wrote:</h3> <div class="commentbody"> The reports of the death of Wrox are greatly exaggerated. :)  www.wrox.com </div>  </div><div class="itemcomment id0"> <h3> James McGovern wrote:</h3> <div class="commentbody"> Never knew that Manning even jumped into this space. This speaks to the lack of advertising. You need to get the word out... </div>  </div> </div>]]>
        
    </content>
</entry>

</feed> 

