Magnus Manske wrote: It's a cause for joy to see that some progress is being made in this area. Although I seak as a non-technical person I can appreciate the concerns that Timwi has raised. Still I would dearly love to see something on line soon. The features that I consider important remain the same as they have been at other times when this subject has been raised. An article must be capable of accepting multiple categorizations in multiple systems. Plain text categories are essential, but so too should various coding systems. My simple suggestion remains that a category which begins with two capital letters would indicate a code; exactly which code would be indicated by the specific choice of those two letters. I know that my suggestion will lead to many schemes that go nowhere, but I believe that that process is a natural part of organic wiki growth. If a particular categorization scheme turns out to be nothing more than clutter, the community will make that decision by failing to use it. Ec

On Apr 20, 2004, at 08:49, Ray Saintonge wrote: A page may be assigned to arbitrarily many categories. Category pages themselves may be assigned to categories, giving rise to a hierarchical categorization system (though right now it's a little awkward to navigate.) Parallel hierarchies shouldn't be a problem. The category names are opaque to the software; it doesn't have any interest in what naming conventions are used. Codes are fine, but they should be sufficiently legible that having a bunch of them appear at the top of an article won't be confusing. -- brion vibber (brion @ pobox.com)

Erik Moeller wrote: Another bug: Subcategories are displayed with underscores instead of spaces (e.g. "Rock_music" instead of "Rock music").

Magnus- Please turn E_NOTICE on in your PHP config. We use E_NOTICE now for debugging purposes. The category code triggers a notice in Parser.php, line 291, when viewing a category page, which is this line: if ( count ( $y ) == 2 && $y[0] == $cat ) It complains that $cat is an uninitialized variable. $cat seems to be used nowhere in Parser.php, which proves the usefulness of E_NOTICE. I suggest you replace it with the correct variable name, if any. I've seen quite a bit of strange behavior (including such things as templates being listed as subcategories), but let's start with this stuff. Incidentally, it would be very useful if you would add some comments to your code. Presently the only comments in the function categoryMagic() are: # Children # Articles Neither of which is particularly informative .. Regards, Erik

Magnus Manske wrote: 15? ... Hm ... 0: Articles; 1: Talk; 2-3: User [talk]; 4-5: Wikipedia [talk]; 6-7: Image [talk]; 8-9: MediaWiki [talk]; 10-11: Template [talk]. That's all I know so far ... with Category and Category talk that makes only 14, or "up to" 13 in numbers (I think that's what you meant). In URLs we also have "Special:" but you said you didn't count that one. In links we have "Media:" but that uses the "Image" namespace. So what is/are the remaining one/two namespace(s)? However, this reminded me of something. It would be useful to be able to use the Category scheme to categorise Wikipedia-namespace pages too (e.g. "Help" pages, "Policy" pages, etc.) However, those categorisations should be separate from article categorisations. Therefore would we want a "Wikipedia category" and "Wikipedia category talk" namespace too? :) Things like "List of Wikipedians from $country" could also be replaced by a "User category" namespace. The same argumentation could apply to the "Template" namespace :) Timwi