Welcome to the General reading room. On this page, Wikibookians are free to talk about the Wikibooks project in general. For proposals for improving Wikibooks, see the Proposals reading room.
I have taken up some of the suggestions offered by reasoned contributors and am still working on implementing others.
I ask that you should read the full discussion there before proceeding further.
In the meantime your edits are adversely affecting my content creation and I ask that you revert your edits so that I can proceed unimpeded with this important work.
Any further discussion should continue in Reading_room/General with Topic "Page Size"
Yes you are right you have to use the print version of the wikibook. This is documented on the main page of the converter. It says explicitly: If you intent to compile a wikibook make sure you use the link to the printable version of the book.. Page 20 is empty. This is also intentional since new chapters can only start on pages on with an odd page number. Please feel free to report any further issues you may notice. Yours --Dirk Hünniger (discuss • contribs) 13:38, 31 December 2024 (UTC)Reply
I don't see what is wrong on page 17. I see an image of a clock showing two o'clock and no problem. Possibly you can explain a bit more what you consider to be wrong.
@Dirk Hünniger: In the original, the clock was quite small and next to the text. Here, it takes up almost a third of the page, and appears before the text.
Also, for the title of the PDF, please make it the book name ({{BOOKNAME}}) instead of the page name without the namespace ({{PAGENAME}}), since the title of the book is not "Philosophy/Print version", but "Wikijunior:Philosophy". JJPMaster (she/they) 13:48, 31 December 2024 (UTC)Reply
1) the appearance of the clock as large image taking the whole page is also intentional. The idea is to create book which does not require an internet connection to read. So the image has to be large because you can not click on it to enlarge it as you can in the web-browser. You can override this behavior by including the image in the wiki text with the 100px directive where 100px means a quarter of the page 200px means half the page and so on.
2) The title of the wikibook as it appears on the first page of the PDF is by default generated for the URL the was supplied to mediawiki2latex. So in your case it defaults to Wikijunior:Philosophy. This behavior can be changed by the user. In this case an other way of defining the printable version is needed. In your case the the printable version is created by using the template {{Printable}}, but in order to define a custom title you have to do it the same way as it is done for example in User:Dirk_Hünniger/latex. I hope the wikitext on this page is rather self explaining, otherwise just ask. Furthermore you have to tell mediawiki2latex to process it in the right way. Just change the combo box Template expansion on the generator page from Standard to Expand Templates internally
Latest comment: 1 month ago3 comments2 people in discussion
Hi everyone,
in my project Thesis Writing Guide, I've gone through some iterations and think I've settled on a structure now. I'd like to ask how the different heading levels are "commonly" used, or say "should" be used.
To my understanding right now:
Level 1 is not used at all. It resembles the Page-/Book-title and is out of question.
Level 2 is the first one used, one might call them chapter or section - let's stick to "section" for now. They give the book big, brought structure.
Level 3 is a subsection then, but immediately loses differentiation: line beneath, just bold and barely different from any level further down below.
Coming from LaTeX, I feel like there are only two real levels. Level 2 is for sections, everything else is a paragraph.
Would it be wrong to e.g. use Level 1 for Chapters?
Hi @TimBorgNetzWerk! In books, we tend to reserve Level 1 headers for the page (chapter) title. Level 2 headers and below are typically then used for sections and subsections on that page/chapter. I rarely use anything below level 4, since they become visually indistinguishable from each other below that. Hope this helps! —Kittycataclysm (discuss • contribs) 19:13, 3 January 2025 (UTC)Reply
Hello there, thanks for the feedback - it alongside your edit history has really helped me out, thanks!
I've now moved the book out of my sandbox into Thesis Writing Guide and set it up as seems right. Feel free to have a look and see if I'm missing something, otherwise I feel comfortable with everything basically shifting one level up now:
Level 1 is never used in the Source, but is the page heading (either book page or chapter page, now shifted to subpages)
Level 2 is now free since it no longer has to be used for chapter headings - that means everything can move up a level, and this Level is free for sections within chapters - great!
Level 3 is now a subsection, works
Level 4 is now a paragraph, perfect.
Thanks! With Nav and printable I feel even more motivated now, ease of navigation is always appreciated!
I've settled on listing the 10 most common chapters in a student thesis:
Chapter 1: Introduction
Chapter 2: Background
Chapter 3: Related Work
Chapter 4: Method / Approach
Chapter 5: Implementation
Chapter 6: Evaluation
Chapter 7: Results
Chapter 8: Discussion
Chapter 9: Future Work
Chapter 10: Conclusion
Very likely, no student thesis will ever have all 10, likely some will be merged (e.g. Discussion & Future Work).
It is also very likely that I am missing some, maybe even some used more often than those 10.
So how does one handle a dynamic rank with a fixed title?
Update all consecutive titles when a new insertion/deletion happens?
Name them "Chapter:Introduction" or similar, to remove the number?
Make them Submodules "Chapter/Introduction"?
Just call them "Introduction"?
This for example I cannot do, since my Book itself has an Introduction. On that note, another issue there, which I will raise as a new topic.
I would like to keep the guide universal in nature, but allow for specific modules. These I just listed by from where they would arise, so a given university in germany may have the module Thesis Writing Guide/DE/LUH/DSDL.
Is this the proper way to handle module stacking?
Should they be included in the printable version?
How can should I create an overview for them? Categories?
Latest comment: 29 days ago1 comment1 person in discussion
Please help translate to your language.
I am writing to you to let you know the annual review period for the Universal Code of Conduct and Enforcement Guidelines is open now. You can make suggestions for changes through 3 February 2025. This is the first step of several to be taken for the annual review.
Read more information and find a conversation to join on the UCoC page on Meta.
Latest comment: 19 days ago1 comment1 person in discussion
Please help translate to your language.
This is a reminder that the first phase of the annual review period for the Universal Code of Conduct and Enforcement Guidelines will be closing soon. You can make suggestions for changes through the end of day, 3 February 2025. This is the first step of several to be taken for the annual review.
Read more information and find a conversation to join on the UCoC page on Meta. After review of the feedback, proposals for updated text will be published on Meta in March for another round of community review.
Please share this information with other members in your community wherever else might be appropriate.
There should be a "Luna" dropdown menu next to "More". There, you will be able to use all of the features listed in the "Autoconfirmed" column here, which work roughly the same as they do with Twinkle (see w:Wikipedia:Twinkle/doc for information about that). JJPMaster (she/they) 01:59, 19 February 2025 (UTC)Reply
Unfortunately, Luna is not yet supported using the default mobile skin or mobile app. It does work on the mobile website if you use a skin other than the default ("MinervaNeue"). JJPMaster (she/they) 02:06, 19 February 2025 (UTC)Reply
Latest comment: 14 hours ago1 comment1 person in discussion
Hello everyone!
We’re excited to announce that the next Language Community Meeting is happening soon, February 28th at 14:00 UTC! If you’d like to join, simply sign up on the wiki page.
This is a participant-driven meeting where we share updates on language-related projects, discuss technical challenges in language wikis, and collaborate on solutions. In our last meeting, we covered topics like developing language keyboards, creating the Moore Wikipedia, and updates from the language support track at Wiki Indaba.
Got a topic to share? Whether it’s a technical update from your project, a challenge you need help with, or a request for interpretation support, we’d love to hear from you! Feel free to reply to this message or add agenda items to the document here.
Also, we wanted to highlight that the sixth edition of the Language & Internationalization newsletter (January 2025) is available here: Wikimedia Language and Product Localization/Newsletter/2025/January. This newsletter provides updates from the October–December 2024 quarter on new feature development, improvements in various language-related technical projects and support efforts, details about community meetings, and ideas for contributing to projects. To stay updated, you can subscribe to the newsletter on its wiki page: Wikimedia Language and Product Localization/Newsletter.
We look forward to your ideas and participation at the language community meeting, see you there!
