Last modified: 2014-11-17 10:35:53 UTC
This is another thing which would be a lot easier to do on Wikisource/Wikibooks if we had means to associate separate pages with books (Bug 15071). Currently, for each book in those projects, we need to duplicate the list of chapters in a lot of places: * The book index * The print version (since the collection extension doesn't provide any HTML printable version) * The collection pages Besides the above, in Bug 15073 is also mentioned the need of automatic forward/back links on subpages of a book, which usually has to be done (and updated (!) in more than one place each time a page is moved) by hand on Wikibooks. For Wikisources, the Proofread Page extension do this for Wikisources, but Collection extension isn't compatible with it (Bug 21653). At pt.wikibooks we tried to use centralized templates ([[b:pt:Template:Lista de capítulos]]) to keep the list of chapters of each book, so that these templates could be used to the purposes above ([[b:pt:Template:Lista de capítulos/Imprimir]], [[b:pt:Template:Lista de capítulos/Coleção]], [[b:pt:Template:AutoNav]]/[[b:pt:MediaWiki:Gadget-Navegação automática.js]]). Currently, we are able to use such templates to automatically generate: 1. Automatic navigation between subpages of a book 2. HTML printable version 3. The wikicode for collection pages Nonethelles, even being able to workaround Bug 15071 and generate the lists of item 3 above, the collection extension doesn't create the book from that list, because it doesn't expand the templates used, as mentioned at [[Help:Books/Feedback/Archives/2010/May#The_extension_is_not_parsing_templates]] and https://bugzilla.wikimedia.org/show_bug.cgi?id=21653#c4 So, it would be really good if the extension could be indeed be enhanced to solve our current problems, as suggested at https://bugzilla.wikimedia.org/show_bug.cgi?id=15073#c1 since, until now, it is not much compatible with projects other that Wikipedia: * [[w:en:Help:Books/Feedback/Archives/2009/November#Wrong order]] * [[w:en:Help:Books/Feedback/Archives/2009/December#Access to tex sourcecode]] * [[w:en:Help:Books/Feedback/Archives/2010/March#Bug: It is not possible to define a chapter to have only one wikipage]] * [[w:en:Help:Books/Feedback/Archives/2010/May#The extension is not parsing templates]] * http://www.mediawiki.org/wiki/Extension:Collection/Wishlist#Output_HTML * Bug 21070 * Bug 15071
(In reply to comment #0) > it doesn't expand the templates used, as mentioned at > [[Help:Books/Feedback/Archives/2010/May#The_extension_is_not_parsing_templates]] > and > https://bugzilla.wikimedia.org/show_bug.cgi?id=21653#c4 I've filled this on Bug 26533.
(In reply to comment #0) > * The print version (since the collection extension doesn't provide any HTML > printable version) This seems an easy thing to add to the Collection extension. See e.g. the [[Special:PrintVersion]] provided by [[mw:Extension:BookManager#Automatic_print_version]]
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
(In reply to comment #1) > (In reply to comment #0) > > it doesn't expand the templates used, as mentioned at > > [[Help:Books/Feedback/Archives/2010/May#The_extension_is_not_parsing_templates]] > > and > > https://bugzilla.wikimedia.org/show_bug.cgi?id=21653#c4 > > I've filled this on Bug 26533. and our current workaround on Portuguese Wikibooks is to use "subst" in the template, but this requires a new edit every time the list of chapters changes. E.g.: https://secure.wikimedia.org/wikibooks/pt/w/index.php?diff=221782&oldid=216651&uselang=en
Yes, this is well known to be the single most important feature request for the Collection extension on Wikisource/Wikibooks, originally filed by Mike.lifeguard in 2008. http://web.archive.org/web/20090211185102/http://code.pediapress.com/wiki/ticket/295 When I discussed this issue with PediaPress in 2011, I proposed http://web.archive.org/web/20111002214427/http://code.pediapress.com/wiki/ticket/827 as a workaround, because we almost always use subpages; they told me that the community should have developed gadgets or bots to make such listing automatically. However that never happened. Instead we're using WSexport because it only asks the root page title and does all the rest on its own. https://wikisource.org/wiki/Wikisource:WSexport Helder, I jut got fed up and decided to make the lists "by hand" for all it.source books, see [[s:it:Speciale:Contributi/AnankeBot]] (1300 books to start with). If you're interested, we could try and work together on some standard semi-automated process for such bulk creations, that each Wikisource could then reuse. Raylton, is this on the radar for this year's development on bug 15071? If I had to pick *one* book management feature to have at the end of the year, this would be it. :)
Some notes: on Portuguese Wikibooks, we are using https://pt.wikibooks.org/wiki/Module:Book for a few of the "book management" tasks: * It generates the previous/next links for the navigation bar[1] * It produces the printable version in HTML using Special:ExpandTemplates[2][3] For this, the module parses the collection page of the associated book, e.g. https://pt.wikibooks.org/wiki/Project:Livros/Budismo We used a python script[4] to compare the index (root page) of each book to its collection, so we can keep only the collection pages and possibly deprecate the indexes. I remmember a user from fr.wikibooks was trying to do something similar a while ago[5]. I haven't used Wikisource for a while, so I don't know how things are going over there... [1] Discussed here: https://pt.wikibooks.org/wiki/T%C3%B3pico:Wikilivros_Discuss%C3%A3o:Portal_comunit%C3%A1rio/Navega%C3%A7%C3%A3o_autom%C3%A1tica [2] https://pt.wikibooks.org/wiki/T%C3%B3pico:Wikilivros_Discuss%C3%A3o:Portal_comunit%C3%A1rio/Navega%C3%A7%C3%A3o_autom%C3%A1tica/resposta_%2814%29 [3] https://pt.wikibooks.org/w/index.php?diff=268297&oldid=265600 [4] https://pt.wikibooks.org/w/index.php?oldid=268476#collection.py [5] https://www.mediawiki.org/w/index.php?title=Extension_talk:Scribunto/Lua_reference_manual#getContent_returns_the_unparsed_content.2C_but_how_to_return_the_interpreted_one.3F
