Plantilla:Global infobox person/ús/en
Description[modifica]
The Global Infobox person is the core (transwiki) version of the "multi-language infobox person" created from the cawiki version.
It has a parameterization system that allows to make adjustments to its operation more easily and without change the code. Its functions include overriding or renaming a manual parameter, changing the text of the infotable labels, or the units of measurement that are applied by default. That is, it is ready to be used in other WPs, with the names of the parameters and the texts it displays (labels, headers, contents) adapted to the local language.
How to use[modifica]
The technical solution is based on a set of templates and modules that respond to the following relationship:
| Template to use in articles | >> | Mòdul:Preinfobox person | >> | Template:Global infobox person |
|---|---|---|---|---|
| It's just an invoke to the preinfobox.
It intends to naming infobox in local language It belongs to local platform and can changed for local team |
It manages and send to Template:Global infobox person:
It's a part of core global code |
It's the code to build the infobox, gets WD information (through Module:Wikidades) and applies the rules defined.
It's a part of core global code | ||
| ↓↓↓ | ||||
| Mòdul:Preinfobox person/i18n | ||||
| Space to define all the local values for the whole texts and parameters |
That is, to the traditional functions of the infotables, a previous piece has been added (preinfobox) that prepares the information according to the parameterization provided by local administrators, isolating the data access code and presentation (global infobox) and reducing its maintenance for parameterization reasons.
Creating custom versions[modifica]
Installing the Global infobox person on another WP requires, as before, having a copy of the necessary templates and modules. The fundamental difference with the classic model of "copy and translate" that we have all followed with templates or infoboxes from another WP, is that the linguistic adaptations are not made on the code of the infobox, but on an easy parameterization system and handled by the receiving WP.
What are the parameterization functions?
- decide the name of the infobox, for example, in the language of the environment
- exclude the treatment of properties that are not considered necessary
- adapt the texts of the labels and headers. The base version uses texts obtained from WD. Therefore, if the items used already have the local label, no further adaptation is required. Additionally, it can be changed to a more specific text provided in the i18n.
- determining the units of measurement, according to the usual ones of the environment. Changes in presentation format such as dates, abbreviation of ordinals, etc. they may require making a small code according to their language, also within the i18n.
- have a dictionary of parameter names in local language. WPs often have more than one infobox for dealing with biographies, even with different parameter names for the same concept. The Global infobox allows you to concentrate all these infoboxes into one. This operation allows them to be migrated easily thanks to the treatment of synonyms.
In addition to working with WD information, the infobox has a dictionary of manual parameters for managing information not yet provided in WD. These parameters are also part of the process of locating the name of the parameters in the language of the environment.
Installation and maintenance[modifica]
The code of the modules and templates that make up the "core structure" of the Global Infobox person, are -internally- written and documented in English: name of the parameters, templates, etc.
The kernel structure is a unique code, replicated on each user platform and its maintenance will be done on the central version and replicated on all subscribing platforms to ensure version compatibility. Improvement proposals that enrich the infobox for all user WPs will be incorporated and distributed unified.
Any WP who has installed the Global infobox can decide to start a fork and keep their own version. In this case, future enhancements applied to the global infobox will not be able to be installed automatically.
On the other hand, the i18n consists of a set of tables within a documented LUA module on how to complete them. When the global infobox is installed, an empty version is incorporated that each WP must customize from then on. Customization items are unique to each installation and will not be updated automatically when the kernel structure is modified, to avoid losing local settings.
See also[modifica]