Template talk:Translation header

Add topic
Active discussions

Required functionsEdit

Some functions required by this template:

  • Match existing functions of {{header}}   Done
  • Original language to be displayed in header (ie. "translated from [LANGUAGE] by Wikisource")   Done

- AdamBMorgan (talk) 22:03, 5 June 2013 (UTC)

New categories required by this template:

- AdamBMorgan (talk) 21:34, 5 July 2013 (UTC)


The following amendments need to be made to MediaWiki:Common.css to add support for this template:

/* Real header templates */
.translationheadertemplate, .processheadertemplate, .portalheadertemplate, .authortemplate, .headertemplate {
	width: 100%;
	margin-bottom: 5px;
/* Notes field */
.translation_notes, .process_notes, .author_notes, .portal_notes, .header_notes {
	width: 100%;
	font-size: 0.9em;
	line-height: 1.4em;
	margin-bottom: 0.5em;	/* a bit of space before body-text; 1em might be better... */

The following needs to be added as well:

/* Translation_header template */
.translationheadertemplate {
	border: 1px solid #FF6;
	background-color: #FFC;
.translation_notes {
	border-bottom: 1px solid #A88;
	background-color: #FAFAFF;

Suggested colour schemeEdit

For reference, this table should show the existing header template colours and suggested translation header colours.

Header template colours
Template Background Border
Header #E4F2E4 #ADA
Author #E4D8D8 #BEA2A2
Process #DCA #966
Portal #DDE #36A
Translation #FFC #FF6
Translation #FDFD96 #FFEF00
Translation #E4D96F #FF7E00
Translation #82D9AD #A3BFB1
Translation #E8ADAA #7F525D

Feel free to add suggestions to the table. - AdamBMorgan (talk) 13:17, 26 June 2013 (UTC)

I'm fine with any of the color schemes. I just changed the current one because the border color seemed too soft; I couldn't distinguish it from the body. - Theornamentalist (talk) 15:52, 5 July 2013 (UTC)
The notes field was still blue-ish, not too good with selecting since now I feel the border is way too bright. I know it's mostly trivial, but I'm looking at the main page in wikiquote; they use yellow similarly and it looks good. Anyone with any eye for this should probably jump in. - Theornamentalist (talk) 01:18, 6 July 2013 (UTC)
Added notes to a work, and the white space between the notes and main looks very specific and a little out of place. I looked at {{header}} and the notes section colouring is quite mute/toned down. So maybe we need something a little more dominant in the upper section, and something a little more washed-out/greyed in the lower section. — billinghurst sDrewth 02:07, 23 April 2014 (UTC)

Interwiki parametersEdit

I haven't documented this yet but I've added two mandatory parameters not present in the standard header. These are language and original. Language is the ISO 639 language code (eg. "en" for English, "de" for German, etc) and Original is the page title on the alternative Wikisource. Together they create an interwiki link to the original on another Wikisource. If either is not used, a tracking category will be added (once I've created the categories anyway). The language parameter alone is also displayed in the header and used in the categorisation. I need to add something to deal with links to (a) oldwikisource, and (b) variants of English on this Wikisource, but it otherwise seems to work for now. - AdamBMorgan (talk) 00:00, 6 July 2013 (UTC)

remove language parameter being mandated in subpagesEdit

When a work has subpages, it does not make sense to make compulsory to state in the header that a work is translated from a language, nor to mark the work in a category. It is quite sufficient to just have that stated at the top of the work, not onwards. — billinghurst sDrewth 08:24, 27 July 2013 (UTC)

Further, I am not sure why original is mandated either. Not all works that we have the locals translate will be hosted on an interlanguage wiki, so the link is empty; if the link is empty then there is no requirement to mandate it. Sure stick in in the preloaded version, but no requirement to mandate. — billinghurst sDrewth 08:33, 27 July 2013 (UTC)
It was a result of the RfC that all Wikisource translations here must indeed have an original on another Wikisource project. The original parameter allows the header template to track that (via categories) and serves as a reminder to users that such a link is required. If we are going to change that we need another discussion. As for disabling it on subpages, I will get on that soon (possibly with the red-linked subpage version of the template). - AdamBMorgan (talk) 23:33, 30 July 2013 (UTC)


I've included a "translator" parameter, if the WS translation is a modification of a previous public domain translation, such as this one. --D.H (talk) 11:36, 18 August 2013 (UTC)

Stopping making year mandatoryEdit

Re: recent edit (stopping making {{{year}}} mandatory, we don't do it in main ns)...

Isn't the reason for not forcing the {{{year}}}} parameter in the original mainspace header more due to the fact that it was added long after the template's usage without the param was well into the tens-of-thousands and would have required heavy "maintenance" to catch-up with a new standard than anything else? I would think forcing compliance in this case is a "no-brainer" for the same justifications we used to add {{{year}}} to the familar ns-0 header to begin with but with the reality it being a "founding" requirement could not cause the same headaches at the same time. What am I missing here; thanks. -- George Orwell III (talk) 00:00, 23 April 2014 (UTC)

No, it more relates to subpages. Plus, we are not stopping the addition, nor discouraging the addition as it still shows in the template, it is the forcing of it as a component of a work. Further, for Wikisource translations, they don't and won't have a year for the translation as it is a dynamic thing with our translation possibly taking years.
@Billinghurst: -- Well I'm not even going to get to the lack of "enforcement" on the sub-pages point - I pretty much knew that was going to go right out the window from the start. Plus they have nothing to do with the info [supposedly] being gathered in any, top-level article page for a work regardless of the namespace in question {though admitedly the Translation: namepace is still not properly setup for true proofreading, etc. The bugzilla still awaits attention on that point too).

But the piece I think you're missing (or misconstruing?) here in particular is that {{{year}}} is tied to nothing other than the original work being translated alone (i.e. is metadata &/or microformat &/or wsexport related; take your pick). As far as I can tell, the param [as coded] in no way relates to anything having to do with the translated product at all. -- George Orwell III (talk) 02:19, 23 April 2014 (UTC)

Re setup, have you asked Tpt? You asked why the parameter should not be mandated, and I gave you the primary reason. You again insinuated that it is me that is wrong, yet where is the community discussion for mandating the field, it has not been had for header template nor for here, irrespective of whichever reason, it simply has never been proposed, let alone discussed, so no authority to mandate. I have stopped nobody from using it, and have changed no guidance, just stopped it being mandated. Re the use of the year parameter, that is not my assessment nor the working practice that I have seen to represent a year of publication, but that is not for this page. — billinghurst sDrewth 13:03, 23 April 2014 (UTC)
I didn't say you were wrong at all; I just wanted clarification. And, with all due respect, its an odd justification you're giving when the YYYY bang was set to impose the equivalent of manually adding the parameter to "force" compliance upon 1st new edit just as if the param was removed after the fact. You mention Tpt but its really the header=1 in the pages command string that is the issue there; the optimal path (or logic train) was one day to be able to hand down the date from the book or info template to the mainspace for all works.

That aside, obviously your issue is with sub-pages so I can't understand why one would alter the "core" template at all? Is the default forcing the cascasding of the default down to the sub-page header or something? I can try correcting that if it is the case. -- George Orwell III (talk) 13:27, 23 April 2014 (UTC)

There is no demonstrated need for a mandation of the year parameter in the template, and such a mandation should be a decision of the community. — billinghurst sDrewth 05:49, 26 April 2014 (UTC)

Ancient Greek WikisourceEdit

Ancient Greek texts are on el.wikisource.org. The language code grc should produce links to it. Prosody (talk) 04:35, 1 February 2016 (UTC)

noyear parameter not fully functioningEdit

When the parameter noyear = is used, it blanks the year from the header, and is still meant to categorise. It has stopped categorising. — billinghurst sDrewth 12:07, 23 July 2017 (UTC)

spurious year error is other categorisationEdit

@Xover: That spurious year appears from this logic, so there is something wrong with it in a larger sense. Fixing immediate display error though we need to review what it is doing as some conditionals are layered wrong.

the code before I removed {{Header/year|{{{year|}}}}} in special:diff/10725249

Categorise page by year, track pages with no year (only if not a subpage or disambiguation page)
              |[[Category:Pages with override year]]
            }}<!-- end if override_year
              |[[Category:Pages with noyearcat]]
            }}<!-- end if noyearcat -->
           |{{Header/year|{{{year|}}}}}<!-- REPLACE THIS -->
         }}<!-- end if override_year/noyearcat -->
      }}<!-- end ifeq disambiguation -->
   }}<!-- end ifeq BASEPAGENAME

billinghurst sDrewth 22:27, 22 December 2020 (UTC)

Extraneous comma and space when no authorEdit

In works that don't list an author, such as Translation:Talmud, the by Author is removed, but the comma and space which follow are not. I'm not familiar enough with the code to fix this myself, but it would be great if someone could—perhaps by copying whatever {{header}} does when there's a translator but no author.

CalendulaAsteraceae (talk) 06:48, 2 April 2021 (UTC)

@CalendulaAsteraceae: This template is likely to be migrated to use Module:Header as a backend in the not too distant future. At that point it'll inherit a bunch of basic behaviour (like this issue) from that, and it'll be a lot easier to tweak where needed. --Xover (talk) 09:01, 2 April 2021 (UTC)
@Xover: Thank you, that's good to know! —CalendulaAsteraceae (talk) 09:03, 2 April 2021 (UTC)