Community noticeboard/Archive 37

__NOINDEX__

Establish a "Translator Wiki" for global translators
Before I get started, let me state one thing: I don't know if Miraheze already has such a wiki to help translators in wikis like MetaWiki discuss translation norms.

A simple description of the problem scenario: a translator of a language translates a page and is unsure whether there is a de facto specification for some aspect, which results in a translation that differs from the rest of the page and ultimately makes the content incomprehensible to users.

One possible version: a translator's space with a translator's noticeboard, a translation norm and a translator's teahouse to address this type of problem.

For this one possible scenario, it is also considered that for other wikis that may need to be regulated, a separate translator space may not meet the needs, so a wiki may be needed to solve the problem.

So,

Solution - Translator Wiki

Site address: translator.miraheze.org

Acting on:

1) Norms in proactively accepted global wiki

2) A teahouse for translators

3) Some of the common translation norms in force for the global wiki

Reason for establishment：

See A simple description of the problem scenario and One possible scenario .

The specific implementation of the translator's wiki and related policies are subject to discussion.

Thanks. Chisato (talk) 13:07, 16 March 2023 (UTC)


 * I'm not against giving translation more attention especially since I think the way it's done now is problematic at best, but I'm not sure an entirely split wiki is proportionate. This seems like it would fit in an expanded guide for translators to learn the basics and its talk page that functions as a translation noticeboard. The suggestion seems to be 3 pages tops of content and could be more concise than that. If in the general sense, there is TranslateWiki.net though I'm not entirely sure what goes on there and couldn't say if it helps this niche. --Raidarr (talk) 14:20, 16 March 2023 (UTC)
 * Set up under the right condition, this could be a useful tool. However, it would require creation of the "Global Translator" group, which would have to be an RfC. BrandonWM (talk • contributions • global • rights) 15:20, 16 March 2023 (UTC)
 * Yep, so I'm keeping the namespace instead (the namespace can be changed to anything else like that depending on the discussion). Chisato (talk) 15:37, 16 March 2023 (UTC)
 * I hadn't fully considered the 'global translator' thing. Honestly, we have such a limited and scattered group of translators in the first place that I would also oppose that role specifically. We don't even have a good way of holding the Meta translators we have accountable, I've seen enough questionable translations that I've been meaning to check them out but I lack the native understanding to know if the translated version is the same grade as the English understanding. Not enough wikis utilize the mechanic and in my frank opinion I think there's not much translation here does that can't be achieved by end users with one of numerous plugins on their browser. I'd revisit this if it is demonstrated that there is actually a need and for that matter, volunteering base to do it. And yes, establishing global translator as a group means this should be discussed in an RfC, but it is useful to discuss here so a concise RfC can be formed, if it is necessary. --Raidarr (talk) 15:53, 16 March 2023 (UTC)
 * (To BrandonWM and Raidarr) Actually, there is no need for a new global user group, which is a wiki for coordinating translations. However, this led me to consider a new possibility. For "multilingual wikis" (generally referring to wikis with the translation extension enabled), a new global user group can indeed be created for all "multilingual wikis" that voluntarily accept translator wikis for translation work management. A user group is granted to all users by default (the permission is translation), but the translation quality is obviously poor (especially fully machine translation), and those who have not improved will be reminded several times by stewards or "translate clerks", and then stewards or "translate clerks" can remove their translator rights. Chisato (talk) 00:05, 17 March 2023 (UTC)
 * This may provide a new option for translation work for the newly created "multilingual wiki". Chisato (talk) 00:07, 17 March 2023 (UTC)

Notice regarding spambot accounts
There have been some worries expressed regarding the fact that registered spambot accounts who have not yet edited due to our abuse filters might be "sleeper accounts" and be reactivated at some stage and get through the filters. Additionally, for a while now users have complained that they don't know who the users in Special:ListUsers are and why they are attached to their wikis. And least importantly, it would be nice if we could have more accurate statistics for how many users we have not counting all the spambots. For this reason, the Steward team is considering a mass global lock of all accounts that: (a) fit a regex for known spambots (this is private as if it were public it could be exploited by them), (b) were created more than a year ago, (c) have 0 edits on any wiki. Reception123 (talk) ( C ) 07:50, 17 March 2023 (UTC)
 * Concur. An account with no edits for a year?  If it's a legitimate user, he can always pick a different user name and start over.   20:35 17-Mar-2023 20:35, 17 March 2023 (UTC)
 * Or request an unlock. I imagine we can be very lenient towards any user locked in this way who requests an unlock. -- Void  Whispers 20:37, 17 March 2023 (UTC)

logo scaling and format
Hi! Sorry if I'm asking something obvious. What is the best logo format to use, and should I scale in specific width or hight? is it ok if the logo is a vector with transparent. Now I use this file: https://static.miraheze.org/timelabwiki/5/50/This_is_Timelab_logo.png but it is not scaled correctly. Marieke Timelab (talk) 14:28, 17 March 2023 (UTC)


 * Preferable resolution is 135x135px, format can be either svg or png. KatozzKita (talk) 16:19, 17 March 2023 (UTC)