From owner-freebsd-newbies Thu Mar 29 1:45:20 2001 Delivered-To: freebsd-newbies@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [171.66.112.163]) by hub.freebsd.org (Postfix) with ESMTP id 40AC437B72D for ; Thu, 29 Mar 2001 01:45:15 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id BAA98118; Thu, 29 Mar 2001 01:39:34 -0800 (PST) Date: Thu, 29 Mar 2001 01:39:34 -0800 (PST) From: Annelise Anderson To: Ted Mittelstaedt Cc: Laurence Berland , lists , freebsd-newbies@FreeBSD.ORG Subject: RE: FreeBSD & GNU In-Reply-To: <004101c0b518$dd9bed40$1401a8c0@tedm.placo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-newbies@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 25 Mar 2001, Ted Mittelstaedt wrote: > >Ps: I'm sure you know, but the chapter of the book in DN is still > >incomplete. I presume it's your publisher, and not you, who has the > >problem. > > > > Unfortunately there's plenty of blame to go around on that one. Yes, > the publisher shipped out a corrupted chapter file. Nobody from DN > let me know about it, I had to find that out myself. I e-mailed > DN about it within 4 hours of the article being posted. I sent complete > HTML a week later. Unfortunately, my HTML was horrible, as it came from > a HTML converter on my masters and lacked drawings. DN was working on > fixing it up. But, I think they have been working on it less and less. I > now have the production masters but they are in Quark, and Quark can't > save-as-HTML, so converting it > that way is just as bad. I'm going to attempt a print-to-EPS-read-with > -ghostview-convert-to-html kind of business next and see what I get. Death > to Quark! Quark can produce PDF--Portable Document Format--though, which is pretty good to read on screen, search, add comments to, etc.--probably a good electronic approach to author's corrections etc. We got in a real mess with an index, and the publisher gave us the Quark docs, and we got them converted to PDF--we all had, of course, Acrobat readers. The files were too large for email but we we transferred them by ftp to various locations. (Still ended up faxing corrections page by page.) Adobe Acrobat wouldn't seem to lend itself to conversion to HTML, though. Annelise > The upshot of all of it is that despite all of the work done with HTML and > XML and all of those good things with document preparation, they have all > pretty much been lost on the print publishing industry, which is still > grappling with this entire business of electronic document handling. > Even within publishers, there's not a standard for electronic docs. The > production department likes using Quark because their printer can understand > it. But, none of the the proofreaders they use has it, and the editorial > staff all seems to not have it either. One of my first questions was "what > is the preferred document format" well there is no preferred document format > because they have solved that problem - they use paper, and are still > shipping > author's manuscripts around the country _on_paper_. > I originally submitted the manuscript via FTP - and this was a big > problem. All proofreading and corrections were done _by hand_. FedEX, > Willamette Paper, and HP Toner sales all made a lot of money off of us. > I just crossed my fingers and hoped that none of the packages got lost, > and fortunately none did. At least, though, their production department > has gotten smart enough to include all the fonts when they ship out the > document and they use honest-to-God Adobe fonts, not that TrueType trash. > > > Ted Mittelstaedt tedm@toybox.placo.com > Author of: The FreeBSD Corporate Networker's Guide > Book website: http://www.freebsd-corp-net-guide.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-newbies" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message