Last modified: 2011-03-13 18:05:38 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T23398, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 21398 - <pagelist> should have file parameter
<pagelist> should have file parameter
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
ProofreadPage (Other open bugs)
unspecified
All All
: Lowest enhancement with 1 vote (vote)
: ---
Assigned To: ThomasV
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-11-03 20:10 UTC by Beau
Modified: 2011-03-13 18:05 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Beau 2009-11-03 20:10:57 UTC
To use <pagelist> the name of the index page must match the name of the djvu file, which is a great limitation. There should be a parameter 'file', which allows to specify the name of djvu file.
Comment 1 ThomasV 2009-11-10 10:30:09 UTC
This limitation has a purpose. 
It preserves index pages from becoming a mess.
Comment 2 Beau 2009-11-10 10:43:57 UTC
I don't understand what you mean by mess. Are there technical difficulties? 
If not, please, bear in mind that this extension is used on many different projects, so this behaviour should be at least configurable.

For example on Polish Wikisource names of index pages does not have to match the name of files.
Comment 3 ThomasV 2009-11-10 14:59:52 UTC
A given page of the "page" namespace should have a unique 
index page, because it belongs in a single book.
A page should never be referred in several indexes.

For djvu files the best way to ensure this is to use 
the same name for the index and for the pages.

For older indexes that do not use "pagelist", 
the unicity of the index is unfortunately not ensured.

Note that another method to ensure unicity of the index 
would be complicated to implement and more difficult to 
understand for users.


Comment 4 Lars Aronsson 2010-06-28 23:26:57 UTC
Nothing is more complicated for new users to understand, than
the introduction of two new namespaces, Index: and Page:
and the need for a separate set of pages for transclusion.

It should be possible to start a new book/volume/document on
a single page, which acts as its front page and at the same
time performs the role of the Index: page. This page should
be named after the title of the volume. Then all the pages
of the volume should appear as subpages, e.g. My_book/123
If chapters need their own subpages, they can be named
with something more than just a number, e.g. /chapter_17

From such a subpage, it is obvious which the parent page is,
just by cutting away the slash and the number. Thus, no need
for an Index: namespace and no need for a Page: namespace.
Comment 5 Lars Aronsson 2010-06-28 23:27:13 UTC
Nothing is more complicated for new users to understand, than
the introduction of two new namespaces, Index: and Page:
and the need for a separate set of pages for transclusion.

It should be possible to start a new book/volume/document on
a single page, which acts as its front page and at the same
time performs the role of the Index: page. This page should
be named after the title of the volume. Then all the pages
of the volume should appear as subpages, e.g. My_book/123
If chapters need their own subpages, they can be named
with something more than just a number, e.g. /chapter_17

From such a subpage, it is obvious which the parent page is,
just by cutting away the slash and the number. Thus, no need
for an Index: namespace and no need for a Page: namespace.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links