Meta talk:Babylon

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose most recent comment is older than 45 days.

I'm quite an active translator here on Meta. My question is, how can I get my own translations reviewed? Or is this not possible? Thanks for your help. Lois131 (talk) 09:59, 9 July 2022 (UTC)Reply

You cannot mark yourself your own translations as “reviewed”. Anyone else can do it. Or, if someone edit your translation, you can then mark it as reviewed. -- Pols12 (talk) 13:20, 2 August 2022 (UTC)Reply

@Pols12 Thanks, okay. But then it's what's above the translations on the left: State: In progress, Needs updating, Proofreading, Ready, Published. I usually mark translations as Ready. Thanks :) Lois131 (talk) 15:22, 2 August 2022 (UTC)Reply

That’s okay. Actually, I believe this feature is rarely used. -- Pols12 (talk) 15:27, 2 August 2022 (UTC)Reply

I do quite often. Because there are few active translators in Hungarian, and I see that translation is going slowly. My time is limited at the moment, but I will have more time this weekend. Lois131 (talk) 15:34, 2 August 2022 (UTC)Reply

Since the pages with pending changes backlog is starting to get out of control again, reposting Meta_talk:Babylon/Archives/2022#Oldest pages needing changes marked for translation

1. User:Guillaume (WMF)/sandbox, since March 27, 2021
2. User:APatro (WMF)/T165128 TestPage, since February 3, 2022
3. Wiki Project Med/App, since April 8, 2022
4. Wikimedia Foundation Community Affairs Committee/2022-04-21 Conversation with Trustees, since April 25, 2022
5. Wikimedia CEE Spring, since May 15, 2022
6. Wikimedia CEE Spring 2022, since May 15, 2022
7. Wikimedia Language Diversity, since May 22, 2022
8. Template:Doppelganger, since May 31, 2022

(Feel free to ignore the user pages at the top, listing them only for completeness' sake)

* Pppery * _{it has begun} 21:15, 31 July 2022 (UTC)Reply

June 2022:

1. Community Insights/Frequently asked questions, since June 2, 2022
2. NDEC Wikimedia Bootcamp 2022, since June 3, 2022
3. Content Partnerships Hub/Background, since June 3, 2022
4. NDEC Wikimedia Bootcamp 2022/Schedule, since June 4, 2022
5. WikiConvention francophone, since June 5, 2022
6. Oral Culture Transcription Toolkit, since June 7, 2022
7. Wikimedia Canada, since June 7, 2022
8. Global blocks, since June 8, 2022
9. Wikimedia Foundation Community Affairs Committee, since June 9, 2022
10. Steward requests/Global permissions/Header, since June 11, 2022
11. No open proxies, since June 11, 2022
12. Hubs/Ongoing, since June 11, 2022
13. Wiki Loves Literature, since June 12, 2022
14. Wikidata, since June 12, 2022
15. Grants:Conference/Preload, since June 23, 2022
16. Grants:Regions/CEE and Central Asia, since June 26, 2022
17. Grants:Project/Rapid/Bachounda/Arabic Hub - regional community support structure, since June 27, 2022
18. Template:Content Partnerships Hub/Header, since June 30, 2022

* Pppery * _{it has begun} 15:43, 3 August 2022 (UTC)Reply

Next up:

1. Wikimedia Foundation Annual Plan/2022-2023/draft/Your Input, since July 1
2. Communications/Organization communications translators group, since July 1
3. Wikimedia Enterprise, since July 4
4. Wikipedia Pages Wanting Photos/Resources, since July 5
5. NDEC Wikimedia Bootcamp 2022/Reading, since July 8
6. Talk:Campaigns/Foundation Product Team/Registration, since July 8
7. Wikimedia Foundation Community Affairs Committee/2022-07-14 Conversation with Trustees, since July 11
8. Wikimedia Navigator User Group/Annual Report, since July 11
9. Oral Culture Transcription Toolkit/Interview Questions, since July 12
10. Grants:Knowledge Sharing, since July 12
11. Wiki Loves Africa 2022, since July 15
12. Wikimedia South Africa, since July 15

Thanks. * Pppery * _{it has begun} 14:42, 8 August 2022 (UTC)Reply

Next up:

1. ESEAP Hub, since July 16
2. Oral Culture Transcription Toolkit/Wiki Workflow, since July 18
3. Wikimedia Österreich, since July 19
4. Wikipedia Pages Wanting Photos 2022/Organizing Team, since July 19
5. Template:Universal Code of Conduct/Navbox, since July 19
6. Wiki Loves Women/Focus Group/SheSaid Sudan, since July 20
7. Wikimedia Foundation elections/2022/Results, since July 20
8. ESEAP Conference 2022, since July 24
9. ESEAP Conference 2022/Attend, since July 24
10. Movement Strategy/Initiatives/Funding for Underrepresented Communities, since July 25 (is tagged {{draft}})
11. Movement Strategy/Initiatives/Increased Wikimedia Awareness, since July 26 (is tagged {{draft}})
12. Wikimedia Community of Saint Petersburg User Group, since July 28
13. QW2022/call for project management, since July 29
14. ESEAP Conference 2022/Submissions, since July 31

* Pppery * _{it has begun} 16:24, 14 August 2022 (UTC)Reply

Next up:

1. Movement Strategy and Governance/Newsletter/7, since August 1
2. The Wikipedia Library/Newsletter/May-June 2022, since August 1
3. Wikimedia Foundation Annual Plan/2022-2023/Goals, since August 4
4. Wikimedia Foundation Annual Plan/2022-2023/draft/Goals, since August 4
5. IP Editing: Privacy Enhancement and Abuse Mitigation/IP Editing Restriction Study, since August 5
6. Education/News/July 2022/EtnoWiki edit-a-thon in Poland, since August 6
7. Wikimedia Endowment, since August 7
8. The WikiVibrance Project, since August 14

* Pppery * _{it has begun} 18:57, 28 August 2022 (UTC)Reply

Next up:

1. Movement Strategy/Initiatives/Methodology to improve User Experience, since August 3
2. Movement Strategy/Initiatives/Resources for Newcomers, since August 3
3. ItWikiCon/2020/Under the hood of a cozy online conference, since August 16
4. Template:Main Page/Sisterprojects, since August 19
5. WikiArabia 2022, since August 22
6. Flow, since August 23
7. Wikiarchaeologist, since August 23
8. Wikimedia Foundation elections/2022/Announcement/Election Compass page, 16-08-2022, since August 23

* Pppery * _{it has begun} 20:25, 13 September 2022 (UTC)Reply

Hello, I recently translated to French this policy, But I am not sure about some of the translations, could someone please check, Thanks SiriusSeth (talk) 18:30, 29 August 2022 (UTC)Reply

“Your” translation even contain an ad for the machine translation service you have used. Please do not use any machine translation tool without carrefully reviewing yourself the translation; else that is not helpful. -- Pols12 (talk) 20:24, 29 August 2022 (UTC)Reply

user:Pols12 I didn’t used Google Translate or Deepl (I use rarely) I translated carefully with my English-french dictionary, Because automatic translater do literal translation, (exemple : Skyline - Ligne de ciel alors que c’est Horizon) En tout cas merci pour votre/ton avis Thanx for this review SiriusSeth (talk) 06:29, 30 August 2022 (UTC)Reply

Could someone help ? We are two users trying to set up translation tags on that page but we are not sure of what we are doing, see the history and talk page.

Also, the page should be renamed Lingua Libre/SignIt, as a sub project of Lingua Libre. Yug (talk) 20:31, 1 September 2022 (UTC)Reply

I have moved the page as requested. --Ameisenigel (talk) 09:06, 2 September 2022 (UTC)Reply

Could an admin delete Movement Strategy and Governance/Termbase/Table/zh-hant? We made mistake during imports and accidentally used zh-hant instead of zh. Context in https://phabricator.wikimedia.org/T316612. Nikerabbit (talk) 07:44, 6 September 2022 (UTC)Reply

@Nikerabbit: Done. —MarcoAurelio (talk) 10:00, 6 September 2022 (UTC)Reply

The Language team has implemented a feature to automatically add source language heading anchors to translation pages. With this feature manual anchors are no longer needed for the purpose of being able to link to a specific section of a translatable page.

This will be deployed here very soon, it's part of this weeks deployment train. Translation pages are not updated immediately to have these anchors, only when they are updated for any reason. We may consider running a script to refresh all translation pages eventually.

Please let us know if you notice any issues or have other feedback. This feature is tracked in https://phabricator.wikimedia.org/T62544 Nikerabbit (talk) 14:26, 8 September 2022 (UTC)Reply

Small correction: it's part of this weeks train (1.40.0-wmf.1), not last week's as I claimed. Nikerabbit (talk) 07:17, 12 September 2022 (UTC)Reply

Greetings,

The Language engineering team has implemented a new functionality that allows translation of JSON content called message bundles. Message bundles contain strings in key-value JSON format representing a message group that can be translated. Each key represents a translation unit and the value is the translation unit source that can be translated.

For this feature, we’ve added a new page content model: Translatable message bundle. To create a message bundle, user’s can create a page with JSON content, and then change the content model to translatable message bundle. We hope that this will be used by volunteers to translate courses from WikiLearn, and in the future to provide localisation support for Scribunto modules.

Changing the content model requires the editcontentmodel right which is currently only available for administrators on Meta-Wiki. There has been some plan to enable it for other users but that hasn’t happened yet.

We would like to grant the editcontentmodel right to translation admins group on Meta-Wiki so that the message bundle feature can be utilized. We will go ahead and do this after one week if there are no objections.

APatro (WMF) (talk) 14:58, 8 September 2022 (UTC)Reply

• I kind of thought about this proposal when Meta:Requests for bot status/WikiLearnBot occurred. This could be a possible solution for 'WikiLearnBot'; it can be granted TA so I support this proposal. Kind regards, — Tulsi 24x7 15:22, 8 September 2022 (UTC)Reply
• Why can't users immediately create a page as a "translatable message bundle"? --MF-W 17:22, 8 September 2022 (UTC)Reply

  My tests reveal that creating a page directly with the content model as translate-messagebundle also requires the edicontentmodel right. See this proposal that requests that the existing editcontentmodel be broken down into two rights with one allowing users to create pages with non-default content models. APatro (WMF) (talk) 09:36, 12 September 2022 (UTC)Reply

  @APatro (WMF) so, fix that? — xaosflux ^Talk 13:33, 12 September 2022 (UTC)Reply

  ..And not by needing another permission, by doing using the same functionality that is extant for SCSS, CSS, JS, JSON already. — xaosflux ^Talk 13:34, 12 September 2022 (UTC)Reply

• I would prefer T300497 get implemented and then translation admins get setcontentmodel instead on general principle of least privilege grounds, but I guess don't have a formal objection to this as is. * Pppery * _{it has begun} 20:22, 8 September 2022 (UTC)Reply

  T300497 has been implemented and is available for use on Meta-Wiki. APatro (WMF) (talk) 09:21, 12 September 2022 (UTC)Reply

  Regarding the setcontentmodel right, there is no such right as of now. I think its being explored in T248294 APatro (WMF) (talk) 09:45, 12 September 2022 (UTC)Reply

  Oops, that was the link I meant to post, must have copy-pasted the wrong thing. * Pppery * _{it has begun} 13:49, 12 September 2022 (UTC)Reply

• Proposal crossposted to Meta:Babel#Grant editcontentmodel right for translation administrators. —MarcoAurelio (talk) 09:48, 12 September 2022 (UTC)Reply
• It seems like this already came up somewhere else. The workflow to build these new pages should be build such that it works without needing this. A hook may be needed. For examples, pages can already be created directly in to other content models such as JS, JSON, CSS, SCSS. The workflow shouldn't require manually authoring a JSON page, then manually changing it to another content model - what is the benefit of putting this extra work in to this worflow? — xaosflux ^Talk 13:30, 12 September 2022 (UTC)Reply

  That all being said, I don't have a specific problem with TA's having changecontentmodel access here - but I don't like this workflow and don't want to have to give TA to everyone that needs to workaround this wonky workflow. — xaosflux ^Talk 13:33, 12 September 2022 (UTC)Reply

  My tests reveal that creating a page directly with the content model as translate-messagebundle also requires the edicontentmodel right which is disabled for normal users on Meta-Wiki. See: T85847

  See this proposal that requests that the existing editcontentmodel be broken down into two rights with one allowing users to create pages with non-default content models. APatro (WMF) (talk) 14:55, 12 September 2022 (UTC)Reply

  @APatro (WMF) sure - today, I'm saying: fix that, just the same way that users can create pages in all sorts of content models already. Building out this entirely new content model should come with building out all the tools needed to support it. For example, if you go to create User:APatro (WMF)/apage.json, it gets made as a json page - not because you have a special permission, but because there is a workflow for that that just makes it work. Also don't see why you want users to create a page in JSON, then have to go and change it to TMB. Why not just make creating TMB's directly be a thing that doesn't require each project that would ever use this to have to worry about this? — xaosflux ^Talk 15:50, 12 September 2022 (UTC)Reply

  Thanks for your input.

  Adding this right to translation administrators is the first step to having this feature generally available. We are considering using the title suffix approach for future integrations but have not come up with a good pattern that would be suitable for e.g. for WikiLearn.

  APatro (WMF) (talk) 15:17, 13 September 2022 (UTC)Reply

  Even if this were done, I doubt we are going to start making anyone that wants to contribute a translation in to a TAdmin, so how are translating editors suppose to even use this? Is there some documentation of the end user workflow (directions and procedures for contributing that worked in the lower environments) for this? — xaosflux ^Talk 13:36, 14 September 2022 (UTC)Reply

  The process would be similar to how we handle translatable pages.

  The translation administrator prepares the message bundle. After that they change the content model of the page containing the message bundle to translatable message bundle. The strings in the message bundle will then be available for translators to translate. Individual translators need not have the editcontentmodel right. APatro (WMF) (talk) 14:25, 14 September 2022 (UTC)Reply

  @APatro, how does a Translatable-message-bundle page look, in read mode? If JSON is displayed as raw-text, I think this kind of pages should not be in main namespace. So creating a dedicated namespace would solve this issue. -- Pols12 (talk) 14:23, 14 September 2022 (UTC)Reply

  We want to provide translation administrators a general feature to create a message bundles for translation. While we will use this for WikiLearn for now, in the future, we will have more options to create a message bundle automatically.

  Using namespaces or subpages is the plan for more use-cases we will have in the future, such as lua modules and gadgets but it makes sense to keep the WikiLearn courses in the main namespace. APatro (WMF) (talk) 16:44, 14 September 2022 (UTC)Reply

•  Weak support lots of reservations above that this should be done in another way, but as this won't be needed by editors making translations, just those aleady doing the markup, not seeing a big problem. — xaosflux ^Talk 15:15, 14 September 2022 (UTC)Reply