On systems like Ubuntu, most software is packaged in nice .deb (or .rpm, like in Red Hat) files which contain the programs and libraries you need. These files can be downloaded or come in CDs (Ubuntu’s CD is full of them). Repositories are servers which contain sets of packages. You generally access them with tools […]
On systems like Ubuntu, most software is packaged in nice .deb (or .rpm, like in Red Hat) files which contain the programs and libraries you need. These files can be downloaded or come in CDs (Ubuntu’s CD is full of them). Repositories are servers which contain sets of packages. You generally access them with tools like Synaptic.
These tools can list all the packages you have installed (from your kernel to your favorite application with all the libraries in between) and the packages that are available in the repositories that you have configured the tool to have access to. They also let you search for simple things like “image editor”.
These tools provide a simple, centralized method of software installation and give the distributors (who set up the repositories) a centralized way to send you updates(1) to your software.
In Ubuntu you generally want to have at least Ubuntu’s repositories (which may include the install CD) but it is not uncommon to have other repositories (from other packagers) set up.
It’s important to know that most of the tools you’ll want to use in Ubuntu are already in Ubuntu’s repositories. You can go search the internet for packages, or even source code, for others, but these will be more difficult to install and won’t, most of the time, integrate as well with your system.
So now you know: no more endless searching looking for spyware-infested shareware and freeware. The vast majority of useful software available for Linux is pre-packaged for you.
Components
Software in Ubuntu’s repository is divided into four categories or components – main, restricted, universe and multiverse.
Most people will use the Ubuntu Software Centre to install the software they want. But if you’re interested in learning more about the different categories of software we include, read on! Software is grouped according to our ability to maintain it and by how well it meets the goals of our free software philosophy. The standard Ubuntu installation is a collection of software from the main and restricted components. You can install additional software from the Ubuntu Software Centre.
Main
The main component contains applications that are free software, can be freely redistributed and are fully supported by the Ubuntu team. This includes the most popular and most reliable open-source applications available, many of which are included by default when you install Ubuntu. Software in main includes a hand-selected list of applications that the Ubuntu developers, community and users feel are most important, and that the Ubuntu security and distribution team are willing to support. When you install software from the main component, you are assured that the software will come with security updates and that commercial technical support is available from Canonical.
Restricted
Our commitment is to only promote free software – or software available under a free licence. However, we make exceptions for a small set of tools and drivers that make it possible to install Ubuntu and its free applications on everyday hardware. These proprietary drivers are kept in the restricted component. Please note that it may not be possible to provide complete support for this software because we are unable to fix the software ourselves – we can only forward problem reports to the actual authors. Some software from restricted will be installed on Ubuntu CDs but is clearly separated to ensure that it is easy to remove. We will only use non-open-source software when there is no other way to install Ubuntu. The Ubuntu team works with vendors to accelerate the open-sourcing of their software to ensure that as much software as possible is available under a free licence.
Universe
The universe component is a snapshot of the free, open-source, and Linux world. It houses almost every piece of open-source software, all built from a range of public sources. Canonical does not provide a guarantee of regular security updates for software in the universe component, but will provide these where they are made available by the community. Users should understand the risk inherent in using these packages. Popular or well supported pieces of software will move from universe into main if they are backed by maintainers willing to meet the standards set by the Ubuntu team.
Multiverse
The multiverse component contains software that is not free, which means the licensing requirements of this software do not meet the Ubuntu main component licence policy. The onus is on you to verify your rights to use this software and comply with the licensing terms of the copyright holder. This software is not supported and usually cannot be fixed or updated. Use it at your own risk.
A Quick, Tongue-in-cheek Description of the Ubuntu Repositories
$release: Don’t touch it, I like consistency, even with my bugs.
$release-security: I’ll accept patches to existing versions (and very rare version upgrades if absolutely necessary) in the process of keeping my system secure.
$release-updates: Okay, some bugs are worth fixing, and I trust you this much (holds up two fingers like Maxwell Smart).
$release-backports: I have something akin to technology ADHD, needing the latest of everything I can possibly get, but I can’t handle running the development branch.
$devel: I can take it. Seriously. If you break my X, I shall become more powerful than you could possibly imagine. I’ll file and maybe even fix the bugs and I’ll do it even if power management is not so much ‘managed’ as vomited all over the wall. Come get some.
Managing Personal or Local Repositories
If there are packages you want to load outside of the supported repositories, this page explains a way to ease package dependency issues.
Lubuntu is a fast and lightweight operating system developed by a community of Free and Open Source enthusiasts. The core of the system is based on Linux and Ubuntu . Lubuntu uses the minimal desktop LXDE, and a selection of light applications. We focus on speed and energy-efficiency. Because of this, Lubuntu has very low hardware requirements. Please join us and contribute to an exciting International Free and Open Source Software project. Install Lubuntu on your computer and start getting involved. Quick links for direct Downloads of the latest version:
PCs with the Windows 8 logo or UEFI firmware, choose the 64-bit download. Visit the help pages for more info about which download is best for you. The section discusses both the standard installs and those required for computers with low memory (RAM), old chipsets (i586) and low disk-space (netbooks).
LAME is a free software codec used to encode/compress audio into the lossy MP3 file format. The name LAME is a recursive acronym for “LAME Ain’t an MP3 Encoder”.[1] Around mid-1998, Mike Cheng created LAME 1.0 as a set of modifications against the “8Hz-MP3″ encoder source code. After some quality concerns raised by others, he […]
The name LAME is a recursive acronym for “LAME Ain’t an MP3 Encoder”.[1] Around mid-1998, Mike Cheng created LAME 1.0 as a set of modifications against the “8Hz-MP3″ encoder source code. After some quality concerns raised by others, he decided to start again from scratch based on the “dist10″ MPEG reference software sources. His goal was only to speed up the dist10 sources, and leave its quality untouched. That branch (a patch against the reference sources) became Lame 2.0. The project quickly became a team project. Mike Cheng eventually left leadership and started working on tooLAME (an MP2 encoder).
Mark Taylor then started pursuing increased quality in addition to better speed, and released version 3.0 featuring gpsycho, a new psychoacoustic model he developed.
May 1999: a new psychoacoustic model (gpsycho) is released along with LAME 3.0.
June 1999: The first variable bitrate implementation is released. Soon after this, LAME also became able to target lower sampling frequencies from MPEG-2.
November 1999: LAME switches from a GPL license to an LGPL license, which allows using it with closed-source applications.
May 2000: the last pieces of the original ISO demonstration code are removed. LAME is not a patch anymore, but a full encoder.
December 2003: substantial improvement to default settings, along with improved speed. LAME no longer requires user to use complicated parameters to produce good results.
May 2007: default variable bitrate encoding speed is vastly improved.
Like all MP3 encoders, LAME implements some technology covered by patents owned by the Fraunhofer Society and other entities.[2] The developers of LAME do not themselves license the technology described by these patents. Distributing compiled binaries of LAME, its libraries, or programs that derive from LAME in countries that recognize those patents may be patent infringing.
The LAME developers state that, since their code is only released in source code form, it should only be considered as an educational description of an MP3 encoder, and thus does not infringe any patent by itself when released as source code only. At the same time, they advise users to obtain a patent license for any relevant technologies that LAME may implement before including a compiled version of the encoder in a product.[3] Some software is released using this strategy: companies use the LAME library, but obtain patent licenses.
Whenever you feel stuck with your article writing and are facing the typical writer’s block, you should go with the ‘brain dumping’ method where you write as fast as possible without thinking twice. Just write down everything that comes into your mind, and this will help the break writer’s block that you may be experiencing. […]
Whenever you feel stuck with your article writing and are facing the typical writer’s block, you should go with the ‘brain dumping’ method where you write as fast as possible without thinking twice. Just write down everything that comes into your mind, and this will help the break writer’s block that you may be experiencing. As you write down this content, the spelling, grammar and punctuation will not even be considered during this process. You will be utterly astounded by all of the content that you come up with what you have put all of your article content into written format. Later on, you can use re-structure and proof read this article to make it presentable.
Getting an ISBN That Identifies You as the Publisher of Your Title
One agency per country is designated to assign ISBNs for that country and must maintain a bibliographic database of titles published in that country. For the United States and its territories, R.R. Bowker is the official ISBN agency. R.R. Bowker is the publisher of Books in Print, the premier database for the publishing industry.
Since the US publishing industry is very large, R.R. Bowker has entered into agreements with a handful of companies to submit official applications on behalf of the self-publishers and authors with whom they work. These companies have agreed to provide special programs under which an ISBN can be assigned by the US ISBN Agency. These companies may also offer other programs and services that do not include such an ISBN. Please read all terms and conditions carefully before making your decision about the right program or service for you.
Why does this matter?
The ISBN identifies not only the specific product to which it is assigned, but also the publisher to be contacted for ordering purposes. If an ISBN is purchased from a company other than R.R. Bowker or through the special programs of the companies listed here, that ISBN will not identify you as the publisher of your title. This can have implications for your business in the publishing industry supply chain.
Companies that will submit certain
ISBN applications to the US ISBN Agency
Note to readers: I originally published the article back in 2008 and have updated it a few times, most recently on June 13, 2012. This article primarily addresses self-publishing a print book, though many of the tips apply to e-books as well. For specific information about publishing an e-book, see my companion article, “How to self-publish an ebook.”
A few years ago I wrote a book. A novel. “Knife Music.” Contrary to what you might think based on my day job, it’s not a cyber-thriller, though it is a mystery/thriller with a medical/legal slant.
Its short history is this: I worked on it for several years, acquired a high-powered agent, had some brushes with major publishers, then, crickets.
I could have tried to go for a small publisher, but I was told mine was “a bigger book” with more commercial aspirations and prestigious small publishers were interested in more literary tomes. I also learned that many small publishers were being wiped out by the “self-publishing revolution,” a movement that’s not so unlike the “citizen journalism” or bloggers’ revolt of recent years that’s had a major impact on mainstream media, including this publication. The basic premise is anyone can become a small publisher. You call the shots. You retain the rights to your book. And you take home a bigger royalty than you’d normally get from a traditional publisher–if you sell any books.
Against the advice of my agent, I began perusing the big self-publishing companies’ Web sites and evaluating what they had to offer. Then I started poking around blogs and message boards to get customer testimonials. What I found was a veritable minefield with roads that forked in every direction and very few clear answers.
After much deliberation, I chose BookSurge, a print-on-demand (POD) outfit that Amazon owned along with the more no-frills POD operation CreateSpace. In 2009, after I published, Amazon merged BookSurge and CreateSpace under the CreateSpace brand name, so when I say Booksurge going forward, you should think CreateSpace. For those new to self-publishing, it’s worth noting that CreateSpace is considered a subsidy press or author-services company. The key to these companies is that books are printed only when someone orders a copy; neither author nor publisher is forced into buying a bunch of books and having to hawk them.
Royalties are better than what “real” publishers offer, but there are caveats, and true self-publishing pros prefer to cut out the subsidy press (which takes a cut) and go straight to a POD printer like Lightning Source to maximize profits. But I was less concerned about making money from this venture and more interested in putting together a well-packaged product that I wouldn’t be embarrassed to sell and some strangers might be willing to buy. If I did it right, I thought, and managed to get it some attention, some “real” publisher might come along and discover what a gem those 20 some odd publishers had passed on.
Well, thanks to a little publicity courtesy of Apple and a rejected – then accepted – free iPhone app, four and half months after I self-published “Knife Music,” my agent sold it to The Overlook Press, an independent publisher that put the book out in hardcover in July 2010. A few months later it came out as an e-book and did very well, rising to as high as No. 4 on the Kindlebestseller list. Later this year Overlook will publish my second novel, “The Big Exit.”
As I said, that’s the short story, and many things have changed — particularly for the e-book industry — since I first wrote this column back in December 2008. But most of what I learned along the way and what I picked up from other people who’ve also self-published, applies more than ever. As always, feel free to add your own experiences to the comments section, and thanks to all the readers who’ve e-mailed in the past.
1. Self-publishing is easy.
Self-publishing a print book is easy. Self-publishing an e-book is even easier.
Since this article is mainly about self-publishing an old-fashioned print book, here’s the skinny on what it takes to put together such a book:
You choose a size for your book, format your Word manuscript to fit that size, turn your Word doc into a PDF, create some cover art in Photoshop, turn that into a PDF, and upload it all to the self-publisher of your choice and get a book proof back within a couple of weeks (or sooner) if you succeeded in formatting everything correctly. You can then make changes and swap in new PDFs.
After you officially publish your book, you can make changes to your cover and interior text by submitting new PDFs, though your book will go offline (“out of stock”) for a week or two. Companies may charge a fee (around $25-$50) for uploading a new cover or new interior.
2. Digital, not print, is your best bet.
The first thing I tell authors who tell me they want to publish a print book is that print should be their secondary focus. I’m advising people who have text-based books (no graphics, illustrations, or photos) to test the self-publishing waters with an e-book before moving on to hard copies. It’s much easier to produce an e-book, particularly when it comes to formatting and cover design. And you can also price a digital book for much less than a paperback, which makes it easier to sell (the majority of self-published print books cost $13.99 and up while the majority of indie e-books sell in the $.99-$5.99 range.
All that said, you can, of course, do both print and digital easily enough.
Once you have your book finalized in a Word or PDF file, it’s relatively easy to convert it into one of the many e-book formats — or just offer it as a download as a PDF. There are several e-publishers geared to “indie” authors, including Smashwords, BookBaby and Lulu, to name just a few. And needless to say, Amazon’s CreateSpace steers you toward uploading your book to the Kindle Store via Kindle Direct Publishing.
I can’t speak for all self-publishing companies, but the quality of POD books is generally quite decent. You can’t do a fancy matte cover (yet), but the books look and feel like “real” books. The only giveaway that you’re dealing with a self-published book would be if the cover were poorly designed — which, unfortunately, is too often the case.
4. Since self-publishing’s so easy, everybody’s doing it.
One of the unfortunate drawbacks of having a low barrier of entry into a suddenly hot market is that now everybody and their brother and sister is an author. That means you’re dealing with a ton of competition, some of which is made up of hustlers, charlatans, and a bunch of people in between.
The growth of indie publishing in the U.S. has been huge over the last couple of years. While that growth has started to level off as fewer writers have unpublished novels in their closets to publish, you can still expect to go up against thousands of other motivated indie authors.
5. Good self-published books are few and far between.
Again, because the barrier to entry is so low, the majority of self-published books are pretty bad. If I had to put a number on it, I’d say less than 5 percent are decent and less than 1 percent are really good. A tiny fraction become monster success stories, but every every few months, you’ll hear about someone hitting it big (for those who don’t know already the “Fifty Shades of Grey” trilogy was initially self-published).
6. The odds are against you.
The average print self-published book sells about 100-150 copies — or two-thirds to three-quarters of your friends and family combined (and don’t count on all your Facebook acquaintances buying). I don’t have a source for this statistic, but I’ve seen this stated on several blogs and as a Publishers Weekly article titled “Turning Bad Books into Big Bucks” noted, while traditional publishers aim to publish hundreds of thousands of copies of a few books, self-publishing companies make money by publishing 100 copies of hundreds of thousands of books.
7. Creating a “professional” book is really hard.
Barrier to entry may be low, but creating a book that looks professional and is indistinguishable from a book published by a “real” publishing house is very difficult and requires a minimum investment of a few thousand dollars (when all was said and done, I’d put in around $7,500, which included about $2,500 in marketing costs). You wonder why “real” books take nine months to produce — and usually significantly longer. Well, I now know why. It’s hard to get everything just right (if you’re a novice at book formatting, Microsoft Word will become your worst enemy). And once you’ve finally received that final proof, you feel it could be slightly better.
8. Have a clear goal for your book.
This will help dictate what service you go with. For instance, if your objective is to create a book for posterity’s sake (so your friends and family can read it for all eternity), you won’t have to invest a lot of time or money to produce something that’s quite acceptable. Lulu is probably your best bet. However, if yours is a commercial venture with big aspirations, things get pretty tricky.
9. Even if it’s great, there’s a good chance your book won’t sell.
If your book is really mediocre, don’t expect it to take off. But even if it’s a masterpiece, there’s a good chance it won’t fly off the shelves (and by shelves, I mean virtual shelves, because most self-published books don’t make it into brick-and-mortar stores). In other words, quality isn’t a guarantee of success. You’ll be lucky to make your investment back, let alone have a “hit” that brings in some real income. Don’t quit your day job yet.
10. Niche books tend to do best.
This seems to be the mantra of self-publishing. Nonfiction books with a well-defined topic and a nice hook to them can do well, especially if they have a target audience that you can focus on.Religious books are a perfect case in point. And fiction? Well, it’s tough, but some genres do better than others. Indie romance/erotica novels, for instance, have thrived in the e-book arena.
Note: If it’s any consolation, the majority of fiction books — even ones from “real” publishers — struggle in the marketplace. That’s why traditional publishers stick with tried-and-true authors with loyal followings.
11. Buy your own ISBN — and create your own publishing house.
If you have market aspirations for your book, buy your own ISBN (International Standard Book Number) and create your own publishing company.
(Credit: www.isbn-us.com)
Even if you go with one of the subsidy presses for convenience’s sake, there’s no reason to have Lulu, CreateSpace, iUniverse, Xlibris, Author House, Outskirts, or whomever listed as your publisher. For around $100 (what a single ISBN costs) and a little added paperwork, you can go toe-to-toe with any small publisher. Lulu.com sells ISBNs, other self-publishing companies don’t. The complete list of sellers is here.
Note: Most self-publishing operations will provide you with a free ISBN for both your print book and e-book but whatever operation provides you with the ISBN will be listed as the publisher.
12. Create a unique title.
Your book should be easy to find in a search on Amazon and Google. It should come up in the first couple of search results. Unfortunately, many authors make the mistake of using a title that has too many other products associated it with it — and it gets buried in search results. Not good. Basically, you want to get the maximum SEO (search engine optimization) for your title, so if and when somebody’s actually looking to buy it they’ll find the link for your book — not an older one with an identical title.
Note: On a more cynical note, some authors are creating titles that are very similar to popular bestsellers. Also, some authors use pseudonyms that are similar to famous authors’ names so they’ll show up in search results for that author. Check out this list of Fifty Shades of Grey knockoffs.
13. Turn-key solutions cost a lot of money.
You’ve written your book and God knows you’d like to just hand it off to someone, have a team of professionals whip it into shape, and get it out there. Well, there are a lot of companies that will offer to make just that happen — and do it in a fraction of the time a traditional publisher could. But those “packages” range anywhere from a few thousand dollars to upward of $25,000.
These folks can potentially put together a really nice book for you. But I’ve also heard a lot nightmare stories where people come away disappointed with the process and feel ripped off. You can do a search in Google for the companies you’re considering and find testimonials — good and bad — from authors who’ve used the services. Proceed with caution.
14. Self-publishers don’t care if your book is successful.
They say they care, but they really don’t care. You have to make them care.
15. Buy as little as possible from your publishing company.
Self-publishing outfits are in the game to make money. And since they’re probably not going to sell a lot of your books, they make money by with nice margins. That’s OK. Some of the services are worth it — or at least may be worth it. Way back when, Booksurge/CreateSpace used to have something called Buy X, Get Y program that paired your book with an Amazon bestseller. It was pricey ($1,000 a month) but in a special sale I bought 3 months for the price of 2 and ended up being paired one month with John Grisham’s new novel, which put the thumbnail image of my book in front of a lot of people. Alas, BookSurge/CreateSpace has since discontinued this program because traditional publishers were upset that shoddy self-published books were being featured on the same page as their books. It was good while it lasted and it helped me sell dozens, if not hundreds, of books.
Personally, I’d never work with CreateSpace’s in-house editors, copy editors, and in-house design people. That doesn’t mean they’re bad at what they do (I’ve seen some covers that are well-done). But if you can, it’s better to hire your own people and work directly with them. Ideally, you should be able to meet with an editor, copy editor, and graphic designer in person — and they all should have experience in book publishing.
Down the road, I suspect you’ll see more self-publishers offer high-end programs that pair you with a former editor from a major publishing house. It’s also worth mentioning that Amazon has become a publisher itself, with several imprints that it’s either bought or created. Amazon is in the process of developing a new hybrid model for publishing that aims to take the place of traditional publishers, which it sometimes refers to as “legacy” publishers. You can see a list of Amazon’s imprints here. With its flagship Encore imprint, it selects certain “exceptional” self-published titles from “emerging” authors and brings them under the Amazon umbrella so to speak. It’s a good gig if you can get it.
16. If you’re serious about your book, hire a book doctor and get it copy edited.
OK, so I’ve just told to avoid “packages” from publishers and yet I’m now saying you need editing and copy editing. So, where do you go? Well, before I sent my book out to agents, I hired a “book doctor” who was a former acquisition editor from a major New York publishing house (like most editors he worked at a few different houses). He happened to be the father of a friend from college, so I got a little discount, but it still wasn’t cheap. However, after I’d made the changes he suggested, he made some calls to agents he knew and some were willing to take a look. He was part of Independent Editors Group (IEG), a group of former acquisition editors who take on freelance editing projects for authors.
While I didn’t use his copy editor (I used a friend of a friend who currently works at a big publishing house), he and other editors in his group can suggest people. To be clear, this isn’t going to be a better deal than what you’d get from a package deal with a self-publisher, but these people are experienced and are going to be upfront and honest with you. They’re not just pushing your book out to move it along the line on the conveyor belt, though they are trying to make a living. (Warning: they don’t take on all writers).
By no means is IEG the only game in town. There are plenty of good book consultants out there, including Alan Rinzler, who has an excellent blog and straddles the line between being an executive editor at an imprint of John Wiley & Sons and providing services to private clients. And there are plenty of others.
17. Negotiate everything.
CreateSpace and other self-publishing companies are always offering special deals on their various services. There isn’t whole lot of leeway, but it doesn’t hurt to ask for deal sweeteners — like more free copies of your book (they often throw in free copies of your book). It also doesn’t hurt to ask about deals that have technically expired. In sales, everything is negotiable. Remember, these people have quotas and bonuses at stake. (For their sake, I hope they do anyway).
18. Ask a lot of questions and don’t be afraid to complain.
When I self-published, I paid an extra $300 fee to be able to talk directly to a live person on the phone for customer support. Companies like Lulu and CreateSpace have complete DIY options and require no upfront setup fees. That’s great, but when you’re dealing with a superbasic package, you’re most likely going to be doing customer support via e-mail or IM, and get very little hand-holding. It’s nice to be able to call up and complain (in a nice way, of course) directly to a live person on the phone, so take that into account when you’re examining your package options.
19. Self-publishing is a contact sport.
The biggest mistake people make when it comes to self-publishing is that they expect to just put out a book and have it magically sell. They might even hire a publicist and expect something to happen. It’s just not so. You have to be a relentless self-promoter. Unfortunately, a lot people just don’t have the stomach or time for it.
What’s the secret to marketing your book successfully? Well, the first thing I advise — and I’m not alone here — is to come up with a marketing plan well before you publish your book. The plan should have at least five avenues for you to pursue because chances are you’re going to strike out on a couple of lines of attack. It’s easy to get discouraged, so you have to be ready to move on to plan c, d, and e (and the rest of the alphabet) pretty quickly.
These days there’s a lot of talk about a “blog strategy,” and many well-known authors do virtual book tours where they offer up interviews to various blogs. You probably won’t have that luxury, but you can certainly research what blogs might be interested in your book and prepare pitches for them. There are social media campaigns to wage, local media angles to pursue, organizations to approach, and all kinds of out-of-the-box gambits you can dream up. None of this will cost you a whole lot — except time and perhaps a little pride.
Then there’s the stuff you pay for. And it’s tricky to judge what’s a good investment and what’s not because the results vary so much from book to book. A friend of mine who has a “real” book from a traditional publisher experimented with placing $1,000 in Facebook ads targeted to people in “cold” states (his book is called the History of the Snowman and it does very well around Christmas). He’s still trying to figure out what impact the ads had, but Facebook does have some interesting marketing opportunities. Google AdWords/Keywords is another popular option. And a number of self-serve ad networks are popping up, including Blogards Book Hive, which allows you to target a number of smaller book blogs for relatively affordable rates.
The author MJ Rose has a marketing service called AuthorBuzz that caters to both self-publishers and traditional publishers. She says the best thing for self-publishers is a blog ad campaign–it starts at about $1,500 for a week of ads (the design work is included) and heads up in increments of $500. She says: “We place the ads in subject-related blogs, not book blogs. For instance, if it’s a mystery about an antiques dealer, we don’t just buy blogs for self-identified readers — who are not the bulk of book buyers — but rather I’ll find a half dozen blogs about antiques, culture, art and investments and buy the ads there and track them.” Rose claims she can get your book in front of at least a half a million people with that initial investment. She also says that you can’t really spend too much, you can just spend poorly.
I agree. However, I can’t tell you what impact a week or month of ads on blogs will have on your specific book’s sales. There are simply too many variables.
Bonus tip: When it comes to self-promotion, there’s a fine line between being assertive and being overly aggressive in an obnoxious way. It also doesn’t impress people when all you tweet about is your book (the same goes for your Facebook and Google+ posts). As one friend told me, the state you want to achieve is what she likes to call “comfortably tenacious.”
20. Getting your book in bookstores sounds good, but that shouldn’t be a real concern.
You may have always wanted to see your book in a bookstore but bookstores aren’t keen on carrying self-published books and it’s extremely difficult to get good placement in the store for your book so chances are no one will see the three copies the store has on hand anyway. Furthermore, your royalty drops on in-store sales. Some of the self-publishing outfits offer distribution through Ingram. CreateSpace offers its Expanded Distribution program for a $25 a year fee. It uses Baker & Taylor, as well as Ingram, as well as CreateSpace Direct to make your book available “to certified resellers through our wholesale website.” You also get distribution to Amazon Europe (Amazon.co.uk, Amazon.es, Amazon.fr, Amazon.it, Amazon.de).
21. Self-published books rarely get reviewed — for free anyway.
Yes, it’s true. It’s very hard to get your self-published book reviewed — and the mantra in the traditional publishing world is that reviews sell books. But that’s changing a bit. People didn’t take bloggers seriously at first and now they do. And what’s interesting is that reputable book reviewers such as Kirkus and more recently Publishers Weekly are offering special reviews services geared toward self-published authors. In the case of Kirkus Indie, the author pays a fee to have the book reviewed (around $400-$550, depending on the speed) and a freelancer writes an objective critique (yes, they do negative reviews) in the same format as a standard Kirkus review. (You can also submit books that are in an e-book-only format).
As for Publishers Weekly, it offers something called PW Select. While you can submit your book for review for a fee of $149, only about 25 percent of the book submissions end up being reviewed. But for a lot of folks risking that $149 is worth the opportunity of getting into the PW door. Of course, there’s always the possibility that the review isn’t favorable.
A third option is BlueInk Review, another fee-based review service targeted at indie authors.
22. Design your book cover to look good small.
Traditional book publishers design — or at least they used to design — a book cover to make a book stand out in a bookstore and evoke whatever sentiment it was supposed to evoke. Well, with Amazon becoming a dominant bookseller, your book has to stand out as a thumbnail image online because that’s how most people are going to come across it. If you’re primarily selling through Amazon, think small and work your way up.
23. If you’re selling online, make the most out of your Amazon page.
I’m a little bit surprised by how neglectful some self-published authors are when it comes to their Amazon product pages. I’ve talked to self-published authors who spend a few thousand dollars on a publicist and their Amazon product page looks woeful — and they’ve barely even looked at it. I ask, “Where are people going to buy your book?” They don’t seem to realize how important Amazon is. True, some people market through a Web site or buy Google keywords to drive traffic there. But you need to have your Amazon page look as good as possible and take advantage of the tools Amazon has to help you surface your book (“Tags,” Listmania, reader reviews, etc.). It may not have a major impact, but it’s better than doing nothing. You should check out Amazon’s Author Central to get some helpful tips.
One tip: Make sure your book is put into five browsing categories (it’s only allowed five). It helps to categorize your book to readers and also will make your book look better if it’s a bestseller in those categories. Way back when I self-published, no one at BookSurge suggested this to me; I had to figure it out on my own. (Again, they don’t care, you have to make them care).
The manifestation of categorizing your book.(Credit: Amazon)
24. Pricing is a serious challenge.
The biggest problem with going the POD route is that it costs more to produce one-offs of your book than it does to produce thousands. I remember that you could buy my book — it was a paperback — from BookSurge for $5.70. It was about 370 pages. Now, if I went ahead and had the thing printed up directly through an off-set printer — and ordered a few thousand of them — I could probably cut the cost of the book in half, and maybe even a little more. But I’d have to pay the upfront fee to buy the books and then I’d have to figure out a way to sell them (this is how vanity presses used to work — you had to agree to buy a few thousand books).
To get a rough idea of how much money you can make selling your book, you can check out CreateSpace’s royalty calculator. Today, setting the price at $14.99, it looks like I’d make about $3.70 per book I sold. If you have a longer book, you’ll have to set the price even higher to make money.
Overall, compared with what traditional publishers pay out, royalty rates for self-published books are actually quite decent. But the fact is, to compete against top-selling titles from traditional publishers, your book should be priced $8.99 or $9.99, and that’s simply not possible if it’s longer than 250 pages.
Many of the self-publishing operations have their own online marketplaces where you can offer up your book and get a significantly better royalty rate. Lulu.com, for instance, touts its own online store, which is well designed and has a big audience. But you obviously have access to a much larger audience on Amazon, which is the first place people generally go to look for a book when they hear about it.
The trick, of course, is making people aware your book exists. I could write an entire piece on the tricks authors pull to get their books to surface better on Amazon. Amazon Author Central and Google are your best friends for helping to discover ways to better surface your book.
25. Self-publishing is a fluid business.
Self-publishing is a rapidly evolving industry with lots of competitors that are constantly throwing out new information. Publishers are continually upgrading their facilities, infrastructure, and pricing, and what I — or other pundits say today — could be wrong just a few months from now. A few years ago, Amazon was only offering 35 percent royalties on e-books. Now it’s at 70 percent for books price $2.99 and higher. What does next year hold in store?
Please comment. And please share any insights into specific self-publishing companies or the industry in general.
Smalltalk is an object-oriented, dynamically typed, reflective programming language. Smalltalk was created as the language to underpin the “new world” of computing exemplified by “human–computer symbiosis.”[1] It was designed and created in part for educational use, more so for constructionist learning, at the Learning Research Group (LRG) of Xerox PARC by Alan Kay, Dan Ingalls, […]
The language was first generally released as Smalltalk-80. Smalltalk-like languages are in continuing active development, and have gathered loyal communities of users around them. ANSI Smalltalk was ratified in 1998 and represents the standard version of Smalltalk.[2]
Smalltalk-80 is a totally reflective system, implemented in Smalltalk-80 itself. Smalltalk-80 provides both structural and computational reflection. Smalltalk is a structurally reflective system whose structure is defined by Smalltalk-80 objects. The classes and methods that define the system are themselves objects and fully part of the system that they help define. The Smalltalk compiler compiles textual source code into method objects, typically instances of CompiledMethod. These get added to classes by storing them in a class’s method dictionary. The part of the class hierarchy that defines classes can add new classes to the system. The system is extended by running Smalltalk-80 code that creates or defines classes and methods. In this way a Smalltalk-80 system is a “living” system, carrying around the ability to extend itself at run time.
Since the classes are themselves objects, they can be asked questions such as “what methods do you implement?” or “what fields/slots/instance variables do you define?”. So objects can easily be inspected, copied, (de)serialized and so on with generic code that applies to any object in the system.
Smalltalk-80 also provides computational reflection, the ability to observe the computational state of the system. In languages derived from the original Smalltalk-80 the current activation of a method is accessible as an object named via a pseudo-variable (one of the six reserved words), thisContext. By sending messages to thisContext a method activation can ask questions like “who sent this message to me”. These facilities make it possible to implement co-routines or Prolog-like back-tracking without modifying the virtual machine. The exception system is implemented using this facility. One of the more interesting uses of this is in the Seaside web framework which relieves the programmer of dealing with the complexity of a Web Browser’s back button by storing continuations for each edited page and switching between them as the user navigates a web site. Programming the web server using Seaside can then be done using a more conventional programming style.
When an object is sent a message that it does not implement, the virtual machine sends the object the doesNotUnderstand: message with a reification of the message as an argument. The message (another object, an instance of Message) contains the selector of the message and an Array of its arguments. In an interactive Smalltalk system the default implementation of doesNotUnderstand: is one that opens an error window (a Notifier) reporting the error to the user. Through this and the reflective facilities the user can examine the context in which the error occurred, redefine the offending code, and continue, all within the system, using Smalltalk-80′s reflective facilities.
Another important use of doesNotUnderstand: is intercession. One can create a class that does not define any methods other than doesNotUnderstand: and does not inherit from any other class. The instances of this class effectively understand no messages. So every time a message is sent to these instances they actually get sent doesNotUnderstand:, hence they intercede in the message sending process. Such objects are called proxies. By implementing doesNotUnderstand: appropriately, one can create distributed systems where proxies forward messages across a network to other Smalltalk systems (a facility common in systems like CORBA, COM+ and RMI but first pioneered in Smalltalk-80 in the 1980s), and persistent systems where changes in state are written to a database and the like. An example of this latter is Logic Arts’ VOSS (Virtual Object Storage System) available for VA Smalltalk under dual open source and commercial licensing.
Smalltalk-80 syntax is rather minimalist, based on only a handful of declarations and reserved words. In fact, only six “keywords” are reserved in Smalltalk: true, false, nil, self, super, and thisContext. These are actually called pseudo-variables, identifiers that follow the rules for variable identifiers but denote bindings that the programmer cannot change. The true, false, and nil pseudo-variables are singleton instances. self and super refer to the receiver of a message within a method activated in response to that message, but sends to super are looked up in the superclass of the method’s defining class rather than the class of the receiver, which allows methods in subclasses to invoke methods of the same name in superclasses. thisContext refers to the current activation record. The only built-in language constructs are message sends, assignment, method return and literal syntax for some objects. From its origins as a language for children of all ages, standard Smalltalk syntax uses punctuation in a manner more like English than mainstream coding languages. The remainder of the language, including control structures for conditional evaluation and iteration, is implemented on top of the built-in constructs by the standard Smalltalk class library. (For performance reasons, implementations may recognize and treat as special some of those messages; however, this is only an optimization and is not hardwired into the language syntax.)
Most popular programming systems separate static program code (in the form of class definitions, functions or procedures) from dynamic, or run time, program state (such as objects or other forms of program data). They load program code when a program starts, and any prior program state must be recreated explicitly from configuration files or other data sources. Any settings the program (and programmer) does not explicitly save must be set up again for each restart. A traditional program also loses much useful document information each time a program saves a file, quits, and reloads. This loses details such as undo history or cursor position. Image based systems don’t force losing all that just because a computer is turned off, or an OS updates.
Many Smalltalk systems, however, do not differentiate between program data (objects) and code (classes). In fact, classes are objects themselves. Therefore most Smalltalk systems store the entire program state (including both Class and non-Class objects) in an image file. The image can then be loaded by the Smalltalk virtual machine to restore a Smalltalk-like system to a prior state. This was inspired by FLEX,[12] a language created by Alan Kay and described in his M.Sc. thesis.
Other languages that model application code as a form of data, such as Lisp, often use image-based persistence as well.
Smalltalk images are similar to (restartable) core dumps and can provide the same functionality as core dumps, such as delayed or remote debugging with full access to the program state at the time of error.
Squeak is a modern, open source, full-featured implementation of the powerful Smalltalk programming language and environment. Squeak is highly-portable – even its virtual machine is written entirely in Smalltalk making it easy to debug, analyze, and change. Squeak is the vehicle for a wide range of projects from multimedia applications, educational platforms to commercial web application development.
Noteworthy uses of Squeak
Children’s Machine – The One Laptop Per Child (OLPC) initiative leverages Squeak to power the Etoys application shipped with every laptop around the world.
Etoys is a powerful script-based environment to learn science and math by encouraging exploration and experimentation.
Pharo is a Squeak fork that focuses on web application development. The Seaside development team does its development work on Pharo.
Cuisis a free Smalltalk-80 environment originally derived from Squeak with a specific set of goals: being simple and powerful.
Seaside is a web framework for developing complex dynamic web applications which by leveraging the Smalltalk strengths considerably ease the web application development.
Aida/Web is the web framework used to make this site.
Scratch is a new programmable toolkit that enables kids to create their own games, animated stories, and interactive art — and share their creations with one another over the Net. Scratch builds on the tradition of Logo and LEGO/Logo, but takes advantage of new computational ideas to make it easier to get started with programming (lowering the floor) and extend the range of what kids can create and learn (raising the ceiling).
The Squeak community is friendly and active. Here is a short list of resources that you may find useful:
www.surfscranton.com/architecture/KnightsPrinciples.htm
www.squeak.org
is the main web site of Squeak. (Do not confuse it with www.squeakland.org which is dedicated to the eToy environment built on top of Squeak but whose audience is elementary school teachers.)
www.squeaksource.com
is the equivalent of SourceForge for Squeak projects.
wiki.squeak.org/squeak
is a wiki with up-to-date information about Squeak.
About mailing-lists.
There are a lot of mailing-lists and sometimes they can be just a little bit too active. If you do not want to get flooded by mail but would still like to participate we suggest you to use
news.gmane.org
or
www.nabble.com/Squeak-f14152.html
to browse the lists.
You can find the complete list of Squeak mailing-lists at
lists.
squeakfoundation.org/mailman/listinfo
.
Note that Squeak-dev refers to the developers’ mailing-list, which can be browsed here:
news.gmane.org/gmane.comp.lang.smalltalk.squeak.general
Newbies
refers to a friendly mailing-list for beginners where any question can be asked:
news.gmane.org/gmane.comp.lang.smalltalk.squeak.beginners
(There is so much to learn that we are all beginners in some aspect of Squeak!)
IRC.
Have a question that you need answered quickly? Would you like to meet with other squeakers around the world? A great place to participate in longer-term discussions is the IRC channel on the “#squeak” channel at
irc.freenode.net
. Stop by and say “Hi!”
Other sites.
There are several websites supporting the Squeak community today in various ways. Here are some of them:
•
people.squeakfoundation.org
is the site of SqueakPeople, which is a kind of “advogato.org” for squeakers. It offers articles, diaries and an interesting trust metric system.
planet.squeak.org
is the site of PlanetSqueak which is an RSS aggregator.
It is good place to get a flood of squeaky things. This includes the latest blog entries from developers and others who have an interest in Squeak.
www.frappr.com/squeak
is a site that tracks Squeak users around the world. Dolphin Smalltalk, or “Dolphin” for short, is an implementation of the Smalltalkprogramming language by Object Arts, targeted at the Microsoft Windows platform.
The last major release was Dolphin Smalltalk X6, which comes in two versions:
Community Edition (free)
Professional edition (commercial) currently in version 6.02
Dolphin is notable for its integrated development environment. The toolset of this Smalltalk dialect include an integrated refactoring browser, a package browser and a WYSIWYG “view composer”. Dolphin Smalltalk deviates from the convention of the Smalltalk MVC framework with a model-presenter-view framework.
The free community version may be one of the richest free programming environments for the Windows operating system because of the nature of the tutorials and sample applications and the rich class libraries. Other Smalltalk dialects for Windows include Smalltalk MT and the Smalltalk dialects from Cincom.
Speech synthesis is the artificial production of human speech. A computer system used for this purpose is called a speech synthesizer, and can be implemented in software or hardware products. A text-to-speech (TTS) system converts normal language text into speech; other systems render symbolic linguistic representations like phonetic transcriptions into speech.[1] Synthesized speech can be […]
Synthesized speech can be created by concatenating pieces of recorded speech that are stored in a database. Systems differ in the size of the stored speech units; a system that stores phones or diphones provides the largest output range, but may lack clarity. For specific usage domains, the storage of entire words or sentences allows for high-quality output. Alternatively, a synthesizer can incorporate a model of the vocal tract and other human voice characteristics to create a completely “synthetic” voice output.[2]
The quality of a speech synthesizer is judged by its similarity to the human voice and by its ability to be understood. An intelligible text-to-speech program allows people with visual impairments or reading disabilities to listen to written works on a home computer. Many computer operating systems have included speech synthesizers since the early 1990s.
Overview of a typical TTS system
A text-to-speech system (or “engine”) is composed of two parts:[3] a front-end and a back-end. The front-end has two major tasks. First, it converts raw text containing symbols like numbers and abbreviations into the equivalent of written-out words. This process is often called text normalization, pre-processing, or tokenization. The front-end then assigns phonetic transcriptions to each word, and divides and marks the text into prosodic units, like phrases, clauses, and sentences. The process of assigning phonetic transcriptions to words is called text-to-phoneme or grapheme-to-phoneme conversion. Phonetic transcriptions and prosody information together make up the symbolic linguistic representation that is output by the front-end. The back-end—often referred to as the synthesizer—then converts the symbolic linguistic representation into sound. In certain systems, this part includes the computation of the target prosody (pitch contour, phoneme durations),[4] which is then imposed on the output speech.
Festival offers a general framework for building speech synthesis systems as well as including examples of various modules. As a whole it offers full text to speech through a number APIs: from shell level, though a Scheme command interpreter, as a C++ library, from Java, and an Emacs interface. Festival is multi-lingual (currently English (British and American), and Spanish) though English is the most advanced. Other groups release new languages for the system. And full tools and documentation for build new voices are available through Carnegie Mellon’s FestVox project (http://festvox.org)
The system is written in C++ and uses the Edinburgh Speech Tools Library for low level architecture and has a Scheme (SIOD) based command interpreter for control. Documentation is given in the FSF texinfo format which can generate, a printed manual, info files and HTML.
Festival is free software. Festival and the speech tools are distributed under an X11-type licence allowing unrestricted commercial and non-commercial use alike.
Text to Speech engine for English and many other languages. Compact size with clear but artificial pronunciation. Available as a command-line program with many options, a shared library for Linux, and a Windows SAPI5 version.
eSpeak is a compact open source software speech synthesizer for English and other languages, for Linux and Windows. http://espeak.sourceforge.net
eSpeak uses a “formant synthesis” method. This allows many languages to be provided in a small size. The speech is clear, and can be used at high speeds, but is not as natural or smooth as larger synthesizers which are based on human speech recordings.
eSpeak is available as:
A command line program (Linux and Windows) to speak text from a file or from stdin.
A shared library version for use by other programs. (On Windows this is a DLL).
A SAPI5 version for Windows, so it can be used with screen-readers and other programs that support the Windows SAPI5 interface.
eSpeak has been ported to other platforms, including Android, Mac OSX and Solaris.
Features.
Includes different Voices, whose characteristics can be altered.
Can produce speech output as a WAV file.
SSML (Speech Synthesis Markup Language) is supported (not complete), and also HTML.
Compact size. The program and its data, including many languages, totals about 2 Mbytes.
Can be used as a front-end to MBROLA diphone voices, see mbrola.html. eSpeak converts text to phonemes with pitch and length information.
Can translate text into phoneme codes, so it could be adapted as a front end for another speech synthesis engine.
Potential for other languages. Several are included in varying stages of progress. Help from native speakers for these or other languages is welcome.
Development tools are available for producing and tuning phoneme data.
SciTE is a SCIntilla based Text Editor. Originally built to demonstrate Scintilla, it has grown to be a generally useful editor with facilities for building and running programs. It is best used for jobs with simple configurations. SciTE is currently available for Intel Windows (XP or later) and Linux compatible operating systems with GTK+. It […]
SciTE is a SCIntilla based Text Editor. Originally built to demonstrate Scintilla, it has grown to be a generally useful editor with facilities for building and running programs. It is best used for jobs with simple configurations.
SciTE is currently available for Intel Windows (XP or later) and Linux compatible operating systems with GTK+. It has been run on Windows 7 and on Fedora 12 and Ubuntu 10.10 with GTK+ 2.20. Here is a screenshot of SciTE.
Questions and comments about SciTE should be directed to the scite-interest mailing list, which is for discussion of SciTE and related projects, their bugs and future features. This is a low traffic list, averaging less than 50 messages per week. To avoid spam, only list members can write to the list. New versions of SciTE are announced on scite-interest and may also be received by SourceForge members by clicking on the Monitor column icon for “scite” on the downloads page.
Lua’s name is not an acronym. It is properly spelled as “Lua” or occasionally “lua”, but never “LUA”. See lua.org/about.html for the whole story.
First of all work your way through the Programming in Lua, it should take you a day or two to get the gist of Lua. The book is free online. Besides it is the best tutorial out there on Lua,
Also: If you’re purpose is Lua for World of Warcraft (probably not but just in case) you can check out this tutorial
And: Here is a tips and tricks thread on StackOverflow, might help give you some ideas of what to expect from Lua
Suggested Programs/Exercises:
Since you’re initially looking at Lua for web development try to understand and improve the Data Description example in PIL. It’ll give you a few good ideas and a nice feel for the power or Lua.
Then you might want to try out playing with the Data Structures chapter, although Lua has a single complex data-type, the Table, that chapter will show you Lua-like ways to make a table do anything you need.
Finally once you begin to grok metatables you should design a class system (yes with Lua you decide how your class system works). I’m sure everyone that knows Lua has made a dozen class systems, a good chapter to get you started on a class system is Object-Oriented Programming
And if you got time and know C or something like that (C# and Java included) try extending an application with Lua, but that’ll take a week or two to do
To say it straight in only one sentence: gpg4usb is a very easy to use portable-application, which combines a simple text-editor with a GnuPG-frontend to write, encrypt and decrypt your text-messages and files. gpg4usb should work on almost any computer you’re working on, should it be a Linux-machine or even one with a Microsoft-OS running. Almost […]
To say it straight in only one sentence: gpg4usb is a very easy to use portable-application, which combines a simple text-editor with a GnuPG-frontend to write, encrypt and decrypt your text-messages and files. gpg4usb should work on almost any computer you’re working on, should it be a Linux-machine or even one with a Microsoft-OS running.
Almost the only thing required is an available usb-port you are allowed to access. With this application you can write safe and encrypted messages anywhere you are: should it be an internet-cafe, at work or somewhere else on holiday… and you always have the encryption-keys available for usage!
The usage of gpg4usb should be highly self-describing, since the user-interface and all the options it offers are clear cut: Simply execute the binary on your usb-pendrive and start typing e.g. the Mailtext you want to be encrypted. If you’re done, choose the right gpg/pgp-key for the person you are writing to and hit the encrypt-icon at the top of the application-window. The resulting encrypted text you can save as a text-file to send it as mail-attachment, or copy it directly into your mail-user-agent or webmail-website. To make sure, you can read this message by yourself afterwards, encrypt it for the recipient and to yourself at the same time – if you want, you can mark as much keys as you want to encrypt for.
You want to add a gpg/pgp-key to your mobile keyring? Nothing’s easier than that: just hit the crypto-menue-entry and choose Import Key from File or Import Key from Editor. This means that it’s possible to import an ascii-armored pubkey via file-dialog, or via copy&paste into your editor-window. If you find a key e.g. on a website, just copy it, paste it into the gpg4usb-editor and hit Import Key from Editor – that’s it, and the key shows up on your keyring!
Just download the zip-File and unzip it onto your usb-pendrive. Then simply change into the folder gpg4usb at your usb-drive, and execute the binary in there:
start_linux or start_windows.exe – should be easy to determine, which one’s yours
Since gpg4usb is free software, licensed under the GNU General Public License (GPL), you can use it on as many machines as you want. Copy it, modify and redistribute it, give gpg4usb to as many people as possible!
Después de leer Test Driven Development- By Example (Addison-Wesley Signature Series) me quedo un sensación mixta de intranquilidad. Seguí los ejemplos del libro, la primera parte usando C#; aunque el libro usa Java y la segunda parte con Python 3.1, haciendo algunas adecuaciones al código del libro. De hecho, primero lo intente con IronPython para […]
Seguí los ejemplos del libro, la primera parte usando C#; aunque el libro usa Java y la segunda parte con Python 3.1, haciendo algunas adecuaciones al código del libro. De hecho, primero lo intente con IronPython para seguir con el tema de .Net, pero con Python 3.1 y IDLE me fue más fácil hacer trabajar el código.
TDD es una técnica avanzada que en su expresión ortodoxa no es seguida ni por el mismo Beck. Es fácil caer en callejones sin salida y el desarrollador debe tener un plan top-down implícito basado en su experiencia y dominio técnico. Por otro lado su aceptación y referencias de éxito son evidencia de su validez.
La primera parte del libro me pareció incompleta, llena de manitas de puerco, visión nocturna, multiplicaciones por el número que pensaste, y conjuros de magia negra.
la segunda parte es de más alto nivel de abstracción pero muestra claramente los fundamentos del marco de xUnit. El uso de Python aquí parece apropiado ya que permite desarrollar la estructura básica de xUnit de manera clara y directa.
Language null true false Java null true false Python None True False Objective-C nil, or NULL, or [NSNull null], depending on context YES NO C NULL anything except 0 0 Lisp NIL T NIL Objective-C is psychotic. It’s a Smalltalk dialect built on top of C (and for the most part, it got the good […]
Language
null
true
false
Java
null
true
false
Python
None
True
False
Objective-C
nil, or NULL, or [NSNull null],
depending on context
Objective-C is psychotic. It’s a Smalltalk dialect built on top of C (and for the most part, it got the good bits of both and left out the bad bits). Obj-C lets you instantiate arrays like [NSArray arrayWithObjects:@"Hello", @"World", nil], using nil as an end-of-array marker because C’s varargs implementation doesn’t know how many args you passed. So it has this extra “null” object that’s not really null.