Template:TranslationDef - Revision history

76561198026315966: obelisk-bot: Adding new tables for hero skill rolls

2026-05-19T01:14:14Z

obelisk-bot: Adding new tables for hero skill rolls

← Older revision		Revision as of 01:14, 19 May 2026
Line 18:		Line 18:
	<pre><nowiki>		<pre><nowiki>
	{{TranslationDef		{{TranslationDef
	\| target_id = String <!-- the parent entity's id (Unit.id, Faction.id, …); ~~empty~~ for catch-all rows ~~keyed by~~ subtype -->		\| target_id = String <!-- the parent entity's id (Unit.id, Faction.id, …); for catch-all Entry rows (attack_archetype, ui, …) duplicates subtype so the join column is uniformly non-null -->
	\| type = String <!-- e.g. unit, faction, hero, attack_archetype, spell_rank -->		\| type = String <!-- e.g. unit, faction, hero, attack_archetype, spell_rank -->
	\| subtype = String <!-- secondary key component; sparse -->		\| subtype = String <!-- secondary key component; sparse -->
Line 30:		Line 30:

	== Field notes ==		== Field notes ==
	* '''Primary key is <code>(target_id, type, subtype, variant, language)</code>''' as a tuple. <code>type</code> / <code>subtype</code> / <code>variant</code> are tiers of the same discriminator pyramid; <code>target_id</code> is the entity id and ''usually'' pairs with a <code>type</code>, but that coupling isn't enforced by the architecture. Most entities use only <code>target_id</code> + <code>type</code>; catch-all ~~reference~~ rows ~~(the ones that used to live on~~ <code>~~Entry~~</code>~~) use~~ <code>~~type~~</code> + <code>~~subtype~~</code> + <code>~~variant~~</code> and ~~leave~~ <code>~~target_id~~</code> ~~empty~~; per-level rows (spell ranks, law levels, skill levels) carry the level in <code>variant</code>.		* '''Primary key is <code>(target_id, type, subtype, variant, language)</code>''' as a tuple. <code>type</code> / <code>subtype</code> / <code>variant</code> are tiers of the same discriminator pyramid; <code>target_id</code> is the entity id and ''usually'' pairs with a <code>type</code>, but that coupling isn't enforced by the architecture. Most entities use only <code>target_id</code> + <code>type</code>; catch-all [[Template:EntryDef\|Entry]] rows are identified by <code>(type, subtype, variant)</code> conceptually, but the emitter duplicates <code>subtype</code> into <code>target_id</code> so self-joins across languages work uniformly (Cargo stores blank parameter values as SQL <code>NULL</code>, and <code>NULL = NULL</code> doesn't match in a join); per-level rows (spell ranks, law levels, skill levels) carry the level in <code>variant</code>.
	* '''Joins from parent entities''' include the type discriminator and the language filter, e.g. <code>Unit.id = Translation.target_id WHERE Translation.type='unit' AND Translation.language='{{{lang\|en}}}'</code>.		* '''Joins from parent entities''' include the type discriminator and the language filter, e.g. <code>Unit.id = Translation.target_id WHERE Translation.type='unit' AND Translation.language='{{{lang\|en}}}'</code>.
	* '''English is in this table''' as <code>language=en</code> — it is not a special case. Parent entity tables no longer carry inline English <code>name</code>/<code>description</code> columns; all display text for every language comes from here.		* '''English is in this table''' as <code>language=en</code> — it is not a special case. Parent entity tables no longer carry inline English <code>name</code>/<code>description</code> columns; all display text for every language comes from here.
Line 58:		Line 58:
	\| Spell rank \|\| <code>Spell.id</code> \|\| <code>spell_rank</code> \|\| \|\| <code>level</code> (1-4)		\| Spell rank \|\| <code>Spell.id</code> \|\| <code>spell_rank</code> \|\| \|\| <code>level</code> (1-4)
	\|-		\|-
	\| Attack archetype \|\| \|\| <code>attack_archetype</code> \|\| <code>melee</code> / <code>ranged</code> / … \|\|		\| Attack archetype \|\| <code>melee</code> / <code>ranged</code> / … (= subtype) \|\| <code>attack_archetype</code> \|\| <code>melee</code> / <code>ranged</code> / … \|\|
	\|-		\|-
	\| Law level \|\| <code>Law.id</code> \|\| <code>law_level</code> \|\| \|\| <code>level</code>		\| Law level \|\| <code>Law.id</code> \|\| <code>law_level</code> \|\| \|\| <code>level</code>

76561198026315966: obelisk-bot: Pushing translation table rework

2026-05-14T20:48:39Z

obelisk-bot: Pushing translation table rework

Show changes

76561198026315966: obelisk-bot: uploading initial Cargo templates

2026-05-13T01:12:58Z

obelisk-bot: uploading initial Cargo templates

← Older revision		Revision as of 01:12, 13 May 2026
Line 154:		Line 154:
	\| zh_tw_name = {{{zh_tw_name\|}}}		\| zh_tw_name = {{{zh_tw_name\|}}}
	\| zh_tw_description = {{{zh_tw_description\|}}}		\| zh_tw_description = {{{zh_tw_description\|}}}
	}}</includeonly>		}}
			Created <code>Translation</code> entry: <code>{{{type\|}}}/{{{target_id\|}}}</code></includeonly>

76561198026315966: obelisk-bot: uploading initial Cargo templates

2026-05-13T00:42:20Z

obelisk-bot: uploading initial Cargo templates

@@ Line 89: / Line 89: @@
 == Field notes ==
 * '''Primary key is <code>(type, target_id)</code>''' as a tuple. Joins from parent entities include the type discriminator: e.g. <code>Unit.id = Translation.target_id WHERE Translation.type='unit'</code>.
-'' ''*English defaults are ''not'' here.** They live on each parent entity's row (<code>Unit.name</code>, <code>Faction.name</code>, <code>HeroClass.name</code>, etc.) so the most common query — "give me the English label for this unit" — needs only a single-table read. Translations are the i18n payload only.
+* '''English defaults are ''not'' here.''' They live on each parent entity's row (<code>Unit.name</code>, <code>Faction.name</code>, <code>HeroClass.name</code>, etc.) so the most common query — "give me the English label for this unit" — needs only a single-table read. Translations are the i18n payload only.
 * '''Language-code mapping''' (game directory → two-letter code):
 ** <code>BRportugese</code> → <code>pt_br</code>
@@ Line 117: / Line 117: @@
 <code>(type, target_id)</code> discriminator means Cargo can store many rows in
 a single table without page-naming collisions.
 [[Category:Cargo Definitions]]

76561198026315966: obelisk-bot: uploading initial Cargo templates

2026-05-13T00:02:39Z

obelisk-bot: uploading initial Cargo templates

Show changes

76561198026315966: obelisk-bot: uploading initial Cargo templates

2026-05-12T23:33:29Z

obelisk-bot: uploading initial Cargo templates

New page

<noinclude>
A single shared table for '''all per-entity i18n payloads'''. Replaces the parallel <code>UnitTranslation</code>, <code>FactionTranslation</code>,
<code>AttackPassiveTranslation</code>, … tables we used to ship — same shape,
one row per (entity-type, entity-id) pair, discriminated by <code>type</code>. See D-026.

The bot never extracts <code>TranslationDef</code> rows on their own; each parent entity's emit function appends a <code>{{TranslationDef | type=… | …}}</code> call to its own page, right after the entity's structural row. The
<code>{{TranslationDef}}</code> MediaWiki template's job is to call <code>#cargo_store</code>
on this table.

== Schema ==
{{#cargo_declare:_table=Translation
| type = String
| target_id = String
| name_sid = String
| desc_sid = String
| pt_br_name = String
| pt_br_desc = Wikitext
| cs_name = String
| cs_desc = Wikitext
| fr_name = String
| fr_desc = Wikitext
| de_name = String
| de_desc = Wikitext
| hu_name = String
| hu_desc = Wikitext
| it_name = String
| it_desc = Wikitext
| ja_name = String
| ja_desc = Wikitext
| ko_name = String
| ko_desc = Wikitext
| pl_name = String
| pl_desc = Wikitext
| ru_name = String
| ru_desc = Wikitext
| es_name = String
| es_desc = Wikitext
| tr_name = String
| tr_desc = Wikitext
| uk_name = String
| uk_desc = Wikitext
| zh_cn_name = String
| zh_cn_desc = Wikitext
| zh_tw_name = String
| zh_tw_desc = Wikitext
}}

<pre><nowiki>
{{TranslationDef
| type = String 
| target_id = String 
| name_sid = String
| desc_sid = String


| pt_br_name = String
| pt_br_desc = Wikitext
| cs_name = String
| cs_desc = Wikitext
| fr_name = String
| fr_desc = Wikitext
| de_name = String
| de_desc = Wikitext
| hu_name = String
| hu_desc = Wikitext
| it_name = String
| it_desc = Wikitext
| ja_name = String
| ja_desc = Wikitext
| ko_name = String
| ko_desc = Wikitext
| pl_name = String
| pl_desc = Wikitext
| ru_name = String
| ru_desc = Wikitext
| es_name = String
| es_desc = Wikitext
| tr_name = String
| tr_desc = Wikitext
| uk_name = String
| uk_desc = Wikitext
| zh_cn_name = String
| zh_cn_desc = Wikitext
| zh_tw_name = String
| zh_tw_desc = Wikitext
}}
</nowiki></pre>

== Field notes ==
* '''Primary key is <code>(type, target_id)</code>''' as a tuple. Joins from parent entities include the type discriminator: e.g. <code>Unit.id = Translation.target_id WHERE Translation.type='unit'</code>.
'' ''*English defaults are ''not'' here.** They live on each parent entity's row (<code>Unit.name</code>, <code>Faction.name</code>, <code>HeroClass.name</code>, etc.) so the most common query — "give me the English label for this unit" — needs only a single-table read. Translations are the i18n payload only.
* '''Language-code mapping''' (game directory → two-letter code):
** <code>BRportugese</code> → <code>pt_br</code>
** <code>czech</code> → <code>cs</code>, <code>french</code> → <code>fr</code>, <code>german</code> → <code>de</code>, <code>hungarian</code> → <code>hu</code>, <code>italian</code> → <code>it</code>, <code>japanese</code> → <code>ja</code>, <code>korean</code> → <code>ko</code>, <code>polish</code> → <code>pl</code>, <code>russian</code> → <code>ru</code>, <code>spanish</code> → <code>es</code>, <code>turkish</code> → <code>tr</code>, <code>ukrainian</code> → <code>uk</code>
** <code>zhCN</code> → <code>zh_cn</code>, <code>zhTW</code> → <code>zh_tw</code>
* '''Sparse output''': any per-language slot the bot couldn't resolve is omitted. Some entities (e.g. faction-shared <code>magic_desc</code> / <code>might_desc</code> for HeroClass) deliberately reuse a single SID across many parents — those parents will all carry the same per-language text on their own Translation row.
* '''The <code>desc</code> field is Wikitext''' because translations may include HTML-bold and HTML-italic tags from the L10n corpus, which the bot's resolver converts to wiki markup (<code>'''</code> and <code>''</code>) before storing.

== Entity types currently emitted ==
{| class="wikitable"
! <code>type</code> !! Parent entity !! <code>target_id</code> !! Emit site
|-
| <code>unit</code> || [[../Unit|<code>UnitDef</code>]] || <code>Unit.id</code> || <code>emit_unit_page</code>
|-
| <code>unit_ability</code> || [[../UnitAbility|<code>UnitAbilityDef</code>]] || <code>UnitAbility.ability_id</code> (composite) || <code>emit_unit_page</code>
|-
| <code>attack_passive</code> || [[Template:AttackPassiveDef|<code>AttackPassiveDef</code>]] || <code>AttackPassive.attack_passive_id</code> || <code>emit_attack_passive_page</code>
|-
| <code>faction</code> || [[../Faction|<code>FactionDef</code>]] || <code>Faction.id</code> || <code>emit_faction_page</code>
|}

(Hero-side entries: <code>hero</code>, <code>hero_class</code>, <code>hero_specialization</code>,
<code>hero_sub_class</code> — added as those entities come online.)

== Page layout ==
Translation rows do '''not''' live on their own wiki pages. Each row is emitted as a <code>{{TranslationDef | …}}</code> invocation on the parent entity's data page, immediately after the entity's structural row. The
<code>(type, target_id)</code> discriminator means Cargo can store many rows in
a single table without page-naming collisions.

== Wiki template notes ==
<syntaxhighlight lang="mediawiki">
<noinclude>
Per-entity i18n payload, shared across all categories. Invoked from each parent entity's data page (Data:Unit/<id>, Data:Faction/<id>, etc.) — there is no Data:Translation/… page namespace.
</noinclude><includeonly>{{#cargo_store:_table=TranslationDef
| type={{{type|}}}
| target_id={{{target_id|}}}
| name_sid={{{name_sid|}}}
| desc_sid={{{desc_sid|}}}
| pt_br_name={{{pt_br_name|}}}
| pt_br_desc={{{pt_br_desc|}}}
| cs_name={{{cs_name|}}}
| cs_desc={{{cs_desc|}}}
| fr_name={{{fr_name|}}}
| fr_desc={{{fr_desc|}}}
| de_name={{{de_name|}}}
| de_desc={{{de_desc|}}}
| hu_name={{{hu_name|}}}
| hu_desc={{{hu_desc|}}}
| it_name={{{it_name|}}}
| it_desc={{{it_desc|}}}
| ja_name={{{ja_name|}}}
| ja_desc={{{ja_desc|}}}
| ko_name={{{ko_name|}}}
| ko_desc={{{ko_desc|}}}
| pl_name={{{pl_name|}}}
| pl_desc={{{pl_desc|}}}
| ru_name={{{ru_name|}}}
| ru_desc={{{ru_desc|}}}
| es_name={{{es_name|}}}
| es_desc={{{es_desc|}}}
| tr_name={{{tr_name|}}}
| tr_desc={{{tr_desc|}}}
| uk_name={{{uk_name|}}}
| uk_desc={{{uk_desc|}}}
| zh_cn_name={{{zh_cn_name|}}}
| zh_cn_desc={{{zh_cn_desc|}}}
| zh_tw_name={{{zh_tw_name|}}}
| zh_tw_desc={{{zh_tw_desc|}}}
}}</includeonly>
</syntaxhighlight>

== Notes ==

[[Category:Cargo Definitions]]
</noinclude><includeonly>{{#cargo_store:_table=Translation
| type = {{{type|}}}
| target_id = {{{target_id|}}}
| name_sid = {{{name_sid|}}}
| desc_sid = {{{desc_sid|}}}
| pt_br_name = {{{pt_br_name|}}}
| pt_br_desc = {{{pt_br_desc|}}}
| cs_name = {{{cs_name|}}}
| cs_desc = {{{cs_desc|}}}
| fr_name = {{{fr_name|}}}
| fr_desc = {{{fr_desc|}}}
| de_name = {{{de_name|}}}
| de_desc = {{{de_desc|}}}
| hu_name = {{{hu_name|}}}
| hu_desc = {{{hu_desc|}}}
| it_name = {{{it_name|}}}
| it_desc = {{{it_desc|}}}
| ja_name = {{{ja_name|}}}
| ja_desc = {{{ja_desc|}}}
| ko_name = {{{ko_name|}}}
| ko_desc = {{{ko_desc|}}}
| pl_name = {{{pl_name|}}}
| pl_desc = {{{pl_desc|}}}
| ru_name = {{{ru_name|}}}
| ru_desc = {{{ru_desc|}}}
| es_name = {{{es_name|}}}
| es_desc = {{{es_desc|}}}
| tr_name = {{{tr_name|}}}
| tr_desc = {{{tr_desc|}}}
| uk_name = {{{uk_name|}}}
| uk_desc = {{{uk_desc|}}}
| zh_cn_name = {{{zh_cn_name|}}}
| zh_cn_desc = {{{zh_cn_desc|}}}
| zh_tw_name = {{{zh_tw_name|}}}
| zh_tw_desc = {{{zh_tw_desc|}}}
}}</includeonly>