Welcome to Wikimedia Incubator!

At the right there are some important links, and here are some tips and info:

If you have any questions, feel free to ask them on Incubator:Community Portal.

-- Welcoming Bot 02:32, 8 May 2016 (UTC)Reply

Mark "| status = invalidcode" doesn't mean that project is deleted

edit

By such marking, it gives people that that test wiki is deleted, however as I looked up Special:PrefixIndex/Wy/be-tarask, there's still 6 pages under Wy/be-tarask available, so please in the next time, even if you wanna delete an entire project, ask I:RFD first. --Liuxinyu970226 (talk) 11:07, 14 October 2017 (UTC)Reply

@Liuxinyu970226: More generally, KATMAKROFAN, please understand the following:
  • |status = invalidcode is used only for projects whose codes are both (a) invalid according to SIL, and (b) have not been granted some other status by WMF and LangCom. You may attempt to change some of those, but until they are changed, you need to leave those alone. Therefore:
    • avk and tlh are valid codes. WMF has decided they don't want projects in these languages. At most, you can therefore classify them as special. But I would rather you leave them alone: I know where they are, I can manage them the way they are, and I'm the one who most needs not to be confused here.
    • be-tarask, for now, is in use. I know you don't want it. Until and unless LangCom decides to close/merge all such projects, it's a special, allowed case.
    • In most of the other cases, I'd rather be able to catch them by seeing a page show up in Category:Incubator:Test wikis/code/notyetchecked.
Thank you for your understanding and cooperation. StevenJ81 (talk) 16:49, 15 October 2017 (UTC)Reply
@StevenJ81: One attention: Additions of KATMAKROFAN also results 2 duplicated arguments, and sib is pointing to another valid language called Sebop. --Liuxinyu970226 (talk) 02:46, 16 October 2017 (UTC)Reply
Note that "be-tarask" is a perfectly valid code: it's built as a standard BCP47 ITF tag, composed conformingly as a valid and standard ISO 639-1 code "be" (valid in BCP47 because it is also registered in the IANA database for IETF tags, but also valid for SIL) and a valid non-private variant subtag "tarask" (which is the correct subtag registered in the IANA database; before, Wikimedia used a private-use extension "-x-old" instead of the standard "-tarask" one)
Note that Wikimedia is still not conforming to BCP 47 for "roa-tara", whose IETF syntax would indicate the language "roa", which is invalid in IETF as it is a language family, from ISO 639-5 and not ISO 639-1/2/3, so it has incorrect scope, and because "tara" is reserved for an ISO 15924 script code (which does not exist). The only correct code for this Napoletano variant is "nap-x-tara", using the standard "nap" code for Napolitano, and the private-use extension "-x-tara" (because the Tarantino dialect has no registered variant, we MUST use the "-x" prefix to define private-use extensions, whose usage will remain valid only in Wikimedia wikis for its interwiki links, but should not even be used in HTML "lang=" attribute that should still specify lang="nap", and should not be used at all in Wikidata). The same is true for "map-bms" whose syntax is also invalid ("map" is a family, not a language, but "bms" is not a valid "extlang", as an "extlang" can only be used after a initial valid language code, and it must also be registered: such registration will never happen, because new "extlang" are no longer accepted since the adoption of ISO 639-3). These two codes are only valid in Wikimedia internal "interwikis" or in its subdomain names, but not as language/locale identifiers. Verdy p (talk) 15:41, 24 July 2019 (UTC)Reply