[[:Category:term cleanup/with sc]]

Jump to: navigation, search

I thought this was still recommended (as it is with {{t}} and so on) as it saves time to specify the script rather than have the server look it up using the language declaration.

Mglovesfun (talk)09:23, 22 April 2013

That category contains pages that use {{term}} with no language but with a script. So it's not quite what you had in mind. I suppose adding a script when a language is already specified does speed things up slightly, but that is only really recommended in the short term. Once a template is converted to Lua, it will not make a difference anymore. So I really recommend just not doing it, to avoid (possibly confusing) redundancy if nothing else, and also since it's only a short term improvement.

CodeCat12:19, 22 April 2013

Is it safe to say that these entries need to be cleaned up by hand? If so I'll help out.

Ultimateria (talk)17:54, 22 April 2013

All help is welcome, but it would probably better to work on the main Category:term cleanup category first. The subcategories are there because they help to separate out things that a bot might fix from things where it's not as simple.

CodeCat18:02, 22 April 2013

Shouldn't instances of {term} that leave the first parameter blank be filtered out since they don't create links?

Ultimateria (talk)19:34, 23 April 2013

Why would that make a difference?

CodeCat19:39, 23 April 2013

It seemed to me that the two main reasons for making lang mandatory was to link to correct sections and to identify links to terms in certain languages, but correct me if I'm wrong (not a rhetorical device; I'm being sincere). And those two cases don't apply if there is no link created.

But now that I think about it I guess using {term} when there is no language isn't ideal.

Ultimateria (talk)20:09, 23 April 2013

If there is no language for a given term, and it's not translingual, then what is it? In any case, though, language codes have a purpose even without linking: they mark the text as being in that language, and select the script for that language. Of course, if the script has been provided explicitly, then there is no reason to automatically determine the script, but the first point still holds. If you write Eisenbahn in a page, then is by default marked as an English word, while Eisenbahn is marked as German. You don't see a difference, but there is a difference in the underlying markup.

CodeCat20:18, 23 April 2013

Just from cleaning up a few entries I've seen {term} used for "terms" in Germanic (lolwut - maybe you can make sense of it?) and used to link a term to itself as a very roundabout way to just put the pagename in italics.

Ultimateria (talk)20:26, 23 April 2013

I have fixed that entry a bit but it's still not terribly clear. At least the Proto-Germanic term is right now.

CodeCat20:32, 23 April 2013