Template talk:recons

This does not apply the sc=Armn automatically as {{term}} does, and because of that this looks ugly. --Vahag 16:57, 7 September 2011 (UTC)Reply

I've added a 'tr' parameter, but I'm gonna leave the {{Xyzy/script}} to someone who knows how to do it (not me). Mglovesfun (talk) 17:29, 7 September 2011 (UTC)Reply

Problem is really that is accepts arguments which aren't real languages, like VL. and Vulgar Latin for um, Vulgar Latin. That can be handled via a switch, but you'd have to include all the etyl: prefixed template for it to be foolproof. Someone will sort it, I'm sure. Mglovesfun (talk) 12:00, 11 September 2011 (UTC)Reply

{{proto}} used actual language names, but this one apparently requires language codes, which I presume Wiktionary has invented, so how are you supposed to know what they are and can someone add this information to the Documentation page. Ƿidsiþ 07:02, 5 January 2013 (UTC)Reply

A convenient way is to write this as the language code: {{subst:langrev/Proto-Germanic}} for example. That will replace it with the code for Proto-Germanic. You can also look at {{langrev/Proto-Germanic}} directly. —CodeCat 13:07, 5 January 2013 (UTC)Reply

Additional discussion: User talk:Mglovesfun#"VL." isn't a language code.

This template is broken, because it half-allows etyl-templates to be used in place of language codes: for example, lang=VL. will link to a Vulgar Latin appendix, but since there's no language-template for Vulgar Latin, it ends up calling {{Eror}} as the script template.

I think the solution is not to allow etyl-templates here at all, since by definition, if we're giving reconstructed entries in it, then we're treating it as a language (albeit perhaps not a mainspace language), so it needs to have some sort of language tag/code/template (cf. {{proto:gem-pro}}). Note that we treat Vulgar Latin as Latin — attested Vulgar Latin terms are listed as ==Latin==, not ==Vulgar Latin==), so its appendices should be named Appendix:Latin/..., not Appendix:Vulgar Latin/....

—Ruakh_TALK 20:32, 31 March 2013 (UTC)Reply

In this case I agree, these should be added as Latin. —CodeCat 20:38, 31 March 2013 (UTC)Reply

Our (non-standard) -pro language codes are being omitted.

A normal use of {{recons}}, from горілка, omits the language code in the HTML. So it inherits the language value from the root html element, and the browser interprets it as English. This is incorrect behaviour.

{{term/t|sla-pro|*gorěti||to burn}}

<i class="Unicode">

Example: *gorěti (“to burn”)

If I leave out the “-pro” prefix, it seems to work properly, but with some error classes added (why Eror and not error?):

{{term/t|sla|*gorěti||to burn}}

<i class="Eror mention-Eror" lang="sla">

Example:

If I enter a language code with a correctly-formed private-use subtag, it is included, but the link is mangled:

{{term/t|sla-x-proto|*gorěti||to burn}}

<i class="Eror mention-Eror" lang="sla-x-proto">

Example:

Is this the intended behaviour? If a correct lang attribute can’t be added, then there should at least be lang="" or lang="und", indicating that this is not English. —Michael Z. 2013-04-15 16:59 z

It seems to have been changed in diff. {{Xyzy}} is a bad template IMO and it shouldn't have been used for this at all. —CodeCat 18:08, 15 April 2013 (UTC)Reply

• {{unicode}} didn't have the standard lang attribute like the other script templates. Now fixed. --Yair rand (talk) 20:26, 16 April 2013 (UTC)Reply

Thank you. —Michael Z. 2013-04-17 02:17 z

Firstly, why should we make red links black here? Second, it's not a good idea to use this class just to make links black. --Z 07:30, 3 June 2013 (UTC)Reply

I agree. —CodeCat 11:57, 3 June 2013 (UTC)Reply