Am 12.07.2015 um 08:43 schrieb Gerard Meijssen:
> Hoi,
> The drawbacks are that you make assumptions about languages. Also having
> localised names prevents the copying of functionality from one to the other. So
> I would not use it, I would show a localised name and its desctription but store
> the property identifier. Text in this is a service not to be relied upon.

It seems like this argument would applied to all magic words used in wikitext,
such as __NOTOC__ or #REDIRECT. These support localization, and many are
localized. But I don't know how widely the localoized versions are used.

Would you say we should drop localization for magic words for the reasons given
above (compatibility between wikis, mainly)?

Actually, the same argument also applies to the names of templates. Templates
very often use other templates. Re-using such a construct on another wiki
requires all the templates names to remain stable. Should we use english names,
or better, numeric names, for all templates?

Oh, the same applies to namespaces, too - let's just use {{#ns:14}} everywhere
instead of "Category" and its localized equivalents.


For magic words and namespaces, there is a mechanism that allows the english
name to always work. So users can pick: use a portable name (english), or use a
localized name. It's the same with property names: you can use the portable
numeric ID, or a localized name. We are currently trying to deal with the issue
that unlike namespaces and magic words, properties can be renamed.

--
Daniel Kinzler
Senior Software Developer

Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.

_______________________________________________
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata