From Wikipedia, the free encyclopedia
Jump to: navigation, search
How to report issues How to escalate issues
  • please check whether this issue is already known
  • provide a link to an article that is affected by the issue
  • report only one issue per section
  • select a descriptive title
  • consider to prefix the title with Bug, Proposal, Question, Comment, Task ...
  • remember to sign your post with ~~~~
  • consider to warn readers of the problem by placing |bug=... in the {{saved book}} template of relevant books

There is a central page at gathering all major issues with this extension. Issues that can't be solved and are not yet covered on the page at meta should be added there.

For obvious bugs the issue tracker is the preferred place to directly issue and check tickets.

At IRC #pediapress some immediate support might be available.

Book Splitting[edit]

Wikipedia clearly warns new editors that the Book Creator does not support large books with more than 500 pages. However, an alternative option is to fork a book just prior to the 500 page limit, by saving it under a unique title (or revision), prior to proceeding to adding more pages and subsequent topics, although later saves of the book may fail. Again, as already indicated, this method is highly like to error out for many users and is not recommended. This is not a problem with technology, it is a problem with editorship.

For instance, most users cannot plan their book out in advance, such that each saved volume contains 500 or fewer pages (give or take), because most books grow in an utterly random fashion similar to the Bell Curve of a pile of dung dripping from a cave ceiling, but with a tail that skews to the right. In other words, book size (as number of pages) grows non-linearly as a function of numerous random variables, including the grow of semantic topics included in the book. Perhaps the correlation closest to a linear relationship is the growth RATE in pages, against the growth RATE of topical scope, although this would be difficult to operationalize. Thus, central topics fill more pages added, in early-stage book growth, with topical scope widening at a fast rate, then narrowing again at a slower rate (of pages added per change in scope). Additionally, more fringe topics tend to fill in gaps between central topics, at a nearly steady rate per click throughout the process of book creation, but represent very nearly the ONLY added pages, near the final stages of book creation.

It is significant to note here that most users [whether planned or not] alphabetically organize their books, as a last step before saving them, although almost half of all books do not get saved permanently, and another smaller percentage of books never even get saved. This is theorized to represent compensation for lack of organization of the book. However, a much better method for compensating for lack of organization, is to actually organize the book, which might require segmentation into more manageable chapters and volumes first. Thus, for a typical non-linear, poorly planned, and unpredictable 'non-central growth' model and given the likelihood that few pages will be deleted from most created books, either as drafts or in a final pruning or quality control stage, editors can save lower quality final works as multiple volumes instead of higher quality single volumes, and still retain the option of future refinement, without any immediate compromise in total pages included.

The best approach to content splitting (for the average editor) is to save a work-in-progress multiple times (under 2 titles), and then delete pages from each volume accordingly, prior to adding pages to each volume. By such a method therefore, a multi-volume book might grow indefinitely through iterative splits. For example, at 500 pages, one could save one's book with the title "Big:Volume 1", and then immediately save exactly the same book again as "Big:Volume 2" (still, with exactly the same 500 pages). Next, the user would delete pages 250-500 from Volume 1, and delete pages 1-250 of Volume 2. Then the user could proceed (once again) with the task of randomly surfing and "filling in" their book with accidentally discovered candidate pages for each of the two volumes (technically, now two separate books), via the navigation patterns of click-through behavior documented by web analytic research. Of course, an even superior method (albeit unlikely) would simply be to plan one's editorial work out in advance, in terms of topical coverage, order, audience, goals, etc., and use an iterative PAGE-DELETION methodology with at least two drafts, thus excluding less critical pages and creating a final piece of higher value.

Can't find the way to include pages from different languages in one book[edit]

(I'm sorry if this should be reported elsewhere but I couldn't find this information neither in FAQ nor in Help pages). I'd like to include Wikipedia pages from different languages to single book, but it seems that Book creator is always initialized independently for each language and pages are added independently as well - does it mean that there is no way to combine such pages? Maybe it's worth to include the answer to the FAQ. Thanks.

When I download a book I only get the title page[edit]

Download this book: Book:Maya_Angelou_autobiographies. When I download as a PDF, it's just one page, yet it should contain all of her works. This was on the main page a few days ago, which is how I came upon it. -- (talk) 23:53, 10 July 2014 (UTC)

Book Creator Box Inside Hidden Sitenotice[edit]

The book creator box won't show for me and I checked the source and the site notice is hidden which includes this box in it.

02:19, 17 August 2014 (UTC)

Bug: Chess boards do not render well[edit]

Chess boards do not render with captions or chessman when exported to PDF or ODT formats. Examples included Colle System and English Opening. An example book may be found at

Krazyclown (talk) 22:34, 22 August 2014 (UTC)

Handling italics[edit]

I've been informed that italics need to be handled a certain way due to Help:Books/for experts. Shouldn't that page have some explanation? czar  16:46, 12 September 2014 (UTC)

I've added it. Headbomb {talk / contribs / physics / books} 19:24, 12 September 2014 (UTC)

Rendering fails if Chinese text present[edit]

If I try to make a book (or download as PDF) the article China, I eventually get a message that rendering failed with "Status: ! LaTeX Error: Command \hansfont already defined.". This happens with a few other articles that have Chinese text. Articles without Chinese text seem to download as .PDF fine. I couldn't find anything when I put "\hansfont" in the search box. --Wtshymanski (talk) 03:49, 3 October 2014 (UTC)


I tried to download Book:Roses yesterday and today, but got a txt-file instead of a pdf. Any ideas why?
Best wishes, Anna reg (talk) 10:09, 3 October 2014 (UTC)

Rendering failed[edit]

While in book creator I used to see 'download as ZIM, ODT, PDF etc. But now its missing for few days. And any type of rendering doesn't work. Thay all fail no matter what the format is. here is a link what happens when i try to render a book - — Preceding unsigned comment added by (talk) 13:19, 7 October 2014 (UTC)


Neither on WP:Books, nor Help:Books can I find any kind of policy regarding books in the Book: namespace. In particular, are such "public" books to be edited by others than their creators, or are they private? QVVERTYVS (hm?) 08:54, 8 October 2014 (UTC)

Those in the Book namespace (or "community books") are like anything else on Wikipedia. Anyone can edit them. Books in userspace ("user books") are like anything else in userspace. The user usually has more or less full control over them, save for attack pages and other similar things. Headbomb {talk / contribs / physics / books} 12:01, 8 October 2014 (UTC)

Non 0 exit code after progress reaches 100%[edit]

I am trying to create a copy of this book ( I tried 3 times but the result is the same. After the progress reaches almost 100% the process fails with a non zero exit code.

May I know whether I can do something? Thanks. Sarmadys (talk) 20:07, 13 October 2014 (UTC)

Infoboxes and tables do not appear in PDFs[edit]

I wonder why the infoboxes and tables do not appear in the PDF version of articles, after rendering. I tested a few articles in Wikipedias in English (en) and Portuguese (pt), and the problem persists in both versions. Thanks in advance! Fúlvio (talk) 22:41, 15 October 2014 (UTC)

Same problem on my Mac 10.6.8. PDF rendering worked fine till a couple of weeks ago, then consistently leaves out infoboxes and tables. Have I accidentally changed PDF preferences? Djbcjk (talk) 10:53, 19 October 2014 (UTC)