|General | Proposals | Projects | Featured books||General | Technical | Administrative||Deletion | Undeletion | Import | Permissions | Renaming|
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.
Open source PDF creation of Wikibooks using LaTeX is now part of the current release of Ubuntu. See  for details. Binaries for Windows are also available. See  --Dirk Hünniger (discuss • contribs) 13:44, 3 November 2013 (UTC)
I put it online on a server
Hi, apologies for posting this in English, but I wanted to alert your community to a discussion on Meta about potential changes to the Wikimedia Trademark Policy. Please translate this statement if you can. We hope that you will all participate in the discussion; we also welcome translations of the legal team’s statement into as many languages as possible and encourage you to voice your thoughts there. Please see the Trademark practices discussion (on Meta-Wiki) for more information. Thank you! --Mdennis (WMF) (talk)
Call for comments on draft trademark policy
Literate programming with Wikibooks?
… While I do not entirely believe in the literate programming cause, it seems like an apt approach in certain cases, which makes me wonder if anyone has tried it on Wikibooks (or perhaps the other Wikimedia projects, of which Wikiversity seems like the only other sensible choice for such a kind of work)?
Essentially, literate programming means that instead of writing a program as a description and instruction for a computer to follow, one writes such a description in a natural language, with the code for computer embedded in the text. A separate program (which could be external to the MediaWiki engine) is then used to extract the code and present it as one or more source code files.
While I would hesitate to use literate programming for most of the software I work on, it seems particularly useful for writing guides for the software which follow the code as configuration approach (such as GNU Emacs, for instance), allowing for such a guide, or selected parts thereof, to be instantly “converted” into a configuration file for the reader.
- When I finally get my interactivity tools working on Wikinews, and have some experience using them to build cool stuff like an article wizard, I've had in mind to propose introducing those tools here. Because building a book is a task requiring expertise — in fact, building any one particular book is an expert task that may differ somewhat from the task of building any other book. Wikibooks isn't just one project; it's really hundreds of projects, each of them very very small, and all banding together for common cause. With, in effect, another small project concerned with administrating the collection of them as a whole. (My understanding of how to successfully conduct a small project —understanding which I apply day-to-day at Wikinews— comes in part from what I've learned by watching indivudal books at Wikibooks; because most individual books at Wikibooks are projects so small that they make Wikinews look enormous.)
- One has to be careful, when introducing tools on top of existing infrastructure, not to make it harder to work without the tools. I've seen this already, for example, with the translation mechanism on Meta: I actually found an error on a page, and tried to fix it, and was able to fix it for every language except English; I was prevented from fixing the English version because on one hand I was told it was a translation, and on the other hand when I tried to treat it as a translation I was told I wasn't allowed to do so because I couldn't translate from English into English. --Pi zero (discuss • contribs) 14:52, 20 November 2013 (UTC)