Difference between revisions of "User:Seb26/Item infobox"
(Created page with '== Ideas == * Item infobox only. Class, maps, websites should be separate. * Sole important parameter: {{code|type}} ** Determines type ({{code|weapon}}, {{code|hat}}, {{code|mis…') |
(→Ideas) |
||
Line 9: | Line 9: | ||
*** Instead: {{xt|1={{code|1={{!}} slot = primary}}}} which on German pages generates {{xt|1={{code|1=[[Primary/de|Primärwaffen]]}}}} | *** Instead: {{xt|1={{code|1={{!}} slot = primary}}}} which on German pages generates {{xt|1={{code|1=[[Primary/de|Primärwaffen]]}}}} | ||
** Attributes: | ** Attributes: | ||
− | *** | + | *** Should be plainly named |
+ | **** {{xt|1={{code|trade}}}} over {{!xt|1={{code|tradable}}}} (and variants) | ||
+ | *** Simple yes/no ('''Issue''') | ||
+ | **** Sometimes this isn't possible, need way to handle these | ||
+ | ***** Possibly "if value != yes/no, display value" (may create issues with translators who translate "yes" and "no") | ||
+ | |||
+ | === Core ideas === | ||
+ | * Efficient & translator friendly | ||
+ | * Well-documented – both on template page & on [[Help:Language translation]] | ||
+ | |||
+ | == Implementation == | ||
+ | * Research | ||
+ | ** Definite numbers on how many pages to update | ||
+ | ** Generate lists and distribute workload | ||
+ | * AWB find & replace in-template call | ||
== See also == | == See also == | ||
* [[../Category:Weapons]] | * [[../Category:Weapons]] |
Revision as of 05:35, 22 October 2010
Contents
Ideas
- Item infobox only. Class, maps, websites should be separate.
- Sole important parameter:
type
- Determines type (
weapon
,hat
,misc
,taunt
,tool
,action
) - Switches visible fields based on its value
- Determines type (
- Scattered ideas:
- Translations should be defined directly inside the infobox
- No
| weapon-slot = Primärwaffen
- Instead:
| slot = primary
which on German pages generatesPrimärwaffen
- No
- Attributes:
- Should be plainly named
trade
overtradable
(and variants)
- Simple yes/no (Issue)
- Sometimes this isn't possible, need way to handle these
- Possibly "if value != yes/no, display value" (may create issues with translators who translate "yes" and "no")
- Sometimes this isn't possible, need way to handle these
- Should be plainly named
- Translations should be defined directly inside the infobox
Core ideas
- Efficient & translator friendly
- Well-documented – both on template page & on Help:Language translation
Implementation
- Research
- Definite numbers on how many pages to update
- Generate lists and distribute workload
- AWB find & replace in-template call