Nikola Smolenski wrote: It's presently a tinyint, with valid values from -128 to 127. Altering its meaning would require being careful not to break existing assumptions, however, and neither 'disambiguation' nor 'stub' are imho useful or objectively calculable. -- brion vibber (brion @ pobox.com)

Nikola Smolenski a écrit : What about other langages fr : {{disambig}} --> {{Homonymie}} fr : {{stub}} --> {{ébauche}} What about defining <tt>#DISAMBIGUATION</tt> and <tt>#STUB</tt> and to insert them respectively into Template:Disambig or Modèle:Homonymie, and Template:Stub or Modèle:ébauche ???

On Monday 16 August 2004 16:20, xmlizer wrote: No need for that, this could easily be localised.

Timwi a écrit : That's why I said to use some keyword like #REDIRECT These keywords doesn't have to have a special meaning instead these keywords has to be inserted in the page (or the template) so as to have a special behaviour Before, in the database you have to declare the keywords and when the parser find a keyword it flag the cur_kind the corresponding bit Example ------------------------- | keyword | bit_position | ------------------------- | REDIRECT | 0 | | STUB | 1 | | DISAMBIG | 2 | | FOOBAR | 3 | ------------------------- Then it could be used in the cur table with the cur_kind column Secondly you could add to link to these page <a class="stub disambig foobar" ....>...</a> if the value of cur_kind = 1110b or <a class="redirect" ...>...</a> if the value of cur_kind is 1 This behaviour is indepedent of STUB, DISAMBIG etc... so could be used by any wiki and it's up to the admin of the wiki to define keywords allowed to be used Xmlizer

Nikola Smolenski wrote: For completely general stuff, one could use the 'links' table to see what templates a page includes. Then you could have features like "Average length of pages that include a given template" (and on Wikipedia, we would type 'dab' and 'stub' into the field, etc.). So far you haven't made your actual suggestion, or told us what your original idea was. An idea should ideally not start out as an implementation plan. :) You should first have an idea of what should change in the user interface. If you describe that to us, maybe someone can come up with an implementation plan that doesn't require huge changes to the DB. Timwi

Timwi wrote: <snip> Hello Timiw, I will code my draft using the link table. The disambiguation template name can then be set in the Language.php file. -- Ashar Voultoiz