 | This page is an archive. Do not edit the contents of this page. Please direct any additional comments to the current main page. |
Bug: Characters not rendered in
Several of the characters in the article are rendered as boxes in pdf. These characters include ↝, ⟩, and ⟨. This happens in both renderers. (I reported this a few months ago on the meta feedback page, but haven't gotten an acknowledgement.) -- Creidieki 16:16, 4 June 2011 (UTC)
Template Nuclide2 may cause overlaps in PDF
Please see Template talk:Nuclide2#Overlaps in PDF render. I am only guessing it is {{Nuclide2}} because all the articles I looked at that use {{Nuclide}} do not show this problem. -84user (talk) 17:30, 9 June 2011 (UTC)
I created this book but it will not convert to PDF for download - it gives me an error message with a long string of incomprehensible gibberish. Anyone have any idea what's wrong? Briangotts (Talk) (Contrib) 20:02, 1 June 2011 (UTC)
- I only have a guess. This problem you are describing happened to me several times. I think the server gets overloaded if there are too many articles in the book. I don't know if increasing RAM on the computer helps or getting a better processor (both very costly), but I only have 1 GB RAM and that seems to happen a lot on that computer. The processor is lower than an Intel Core 2 Duo, so I don't know if it would ever get resolved if Wikimedia gets a better server. I'm sure lots of people trying to convert PDF's from Wiki articles at the same time bogs down the server. Just a couple of ideas I have, not much in the way of solutions. Sorry. Hopefully someone with more experience will have a more helpful solution. 97.47.73.42 (talk) 22:52, 12 June 2011 (UTC)
Bug: Some PDF articles omit certain parts of the Infobox
Hello. Some articles don't show all of the info in the Infobox. I notice that in article Infoboxes in which there is a "Release date(s)" field, if there is more than one release date, it won't show any information at all. This bug should be related to the clickable "Show" button that is in blue, that makes the collapsed information appear. In the PDF, it must be confused by the "Show" button, and so it omits the information since it doesn't know what to do with it. My example article is Super Mario Bros. 3. In other article Infoboxes, if there is only one "Release date", the information is easily transferable to the PDF. So I don't know if the problem is inherently in the PDF Converter, or rather in the "Show" button itself. Thanks, and please request clarification if necessary. 97.47.73.42 (talk) 22:46, 12 June 2011 (UTC)
- This problem already has a section (two in fact) above. McLerristarr | Mclay1 11:36, 27 June 2011 (UTC)
Printworthy redirect
It would be useful if printworthy redirects could be integrated into the books. Currently, they don't actually have a use but are tagged for the possible future. I propose that if a redirect is added to a book and is categorised as printworthy (or not categorised as unprintworthy; we should probably get rid of one of the two categories), then the redirect is somehow included, rather than the redirect being followed and the target being included. Perhaps in the contents page, it could be listed, followed by "see target" or something. Also, if the PDFs had an index, like the print books, printworthy redirects could be listed in the index, rather than the targets being listed. McLerristarr | Mclay1 10:31, 27 June 2011 (UTC)
Numbered lists
In numbered lists, if a number is set as a specific value (so the list doesn't start with 1), the altered number appears as a bullet instead. I'm not sure if this happens in every case but it happens in infoboxes which include a template such as {{Help! tracks}}. The aforementioned templates also have a border around them in print versions, apparently because of the template they use. I attempted to create a print version of {{Let It Be tracks}}, which solved the border problem but the numbering problem persists and for some reason the print version centres the numbered list, rather than having it left-aligned as it should. McLerristarr | Mclay1 11:28, 27 June 2011 (UTC)