Translation changed with https://translatewiki.net/w/i.php?title=MediaWiki:Action-edit/de&diff=prev&oldid=12415169. The change will go live on the WMF wikis probably next Thursday.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Sun, May 19
Thu, May 16
In T364742#9803569, @Nikerabbit hat geschrieben:
- Spaces were removed by Libraryupgrader on Friday 10th: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/DiscussionTools/+/1029837
- What happened here?? Was the change not detected or ignored?
In T364742#9803398, @Nikerabbit hat geschrieben:@Raymond Did you process these changes or someone else, or did they not show up at all?
Mon, May 13
Mon, May 6
Tue, Apr 30
First export for apc from translatewiki now with https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1025602
Thu, Apr 25
In T363156#9744886, @WMDE-Fisch hat geschrieben:@Raymond could you guide me in how to do this best? What would be most helpful?
Should we copy over and rename the messages with all their .json language variants to the new extension and let the bot sync it upstream with translate wiki?
or
Should we just copy the en and qqq parts, leave the name the same for now and you have some magic to sync the language variants? ( and then we rename it? )
or
Do you have some magic in the translate wiki to do all of that at once and then bot sync the messages magically into the codebase ^^'?
Apr 8 2024
Apr 4 2024
Deployed
Mar 15 2024
I am sorry, but I have not seen that this message contains <image> too, see https://integration.wikimedia.org/ci/job/mediawiki-i18n-check-docker/174270/console
Mar 14 2024
And now I have the problem, that I had to revert the export of today: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikimediaMessages/+/1010931
Mar 7 2024
Feb 22 2024
Feb 19 2024
Feb 8 2024
Deployed
Feb 6 2024
Import of new translations is impossible now, therefore export is broken too.
Feb 5 2024
Jan 29 2024
In T355857#9494632, @Nikerabbit wrote:@Nikerabbit maybe it is time to export MediaWiki automatically now too?
We can setup that. What schedule do you recommend?
Jan 27 2024
Sorry for the late answer, I was sick last days. I think this happend after starting the export script/bot on the translateiki.net shell and my laptop lost internet connectiontion during the script run. I spotted this issue in the past but was able to fix it. But not this week due due sickness.
Jan 19 2024
Jan 18 2024
Jan 12 2024
Jan 8 2024
Jan 3 2024
Deployed
Dec 15 2023
Dec 13 2023
Dec 8 2023
Dec 7 2023
Dec 4 2023
is this task a dupe of T352601? or vice versa?
Dec 3 2023
Dec 2 2023
Nov 28 2023
Nov 27 2023
Nov 26 2023
Nov 23 2023
Nov 8 2023
In T350777#9315957, @jnuche wrote:@Raymond This bug was filed while the train was being deployed to group1, which includes commons. Can you please verify the problem wasn't transient?
Also, do you have any captures/errors/logs that show the problem?
Nov 2 2023
! In T247552#9302887, @aaron wrote:
The repo isn't changing, it's just a new key that can start off with the values of an old key. The old key will get removed later.
In T247552#9296703, @aaron wrote:CC'ing @Nikerabbit . The new messages can clone the old translations. I don't know the exact TWN process for that, but it should apply here.
Oct 30 2023
Thank you for your fast fix. Export worked well now.
Oct 22 2023
Patch is live
Oct 15 2023
In T346595#9251993, @Strainu wrote:@Winston_Sung @Aklapper is it wise to update CLDR data locally? Doesn't it get overwritten when the next CLDR version arrives?
let translatewiki.net staff batch rename the remaining i18n/$langcode key names, keeping the existing translations, if that's possible.
Oct 9 2023
Oct 7 2023
Sep 30 2023
Sep 15 2023
In T243660#9169103, @WMDE-leszek wrote:
Sep 8 2023
In T345762#9152548, @Esanders wrote:@Raymond Thanks for merging, do we know when this might get deployed?
Sep 7 2023
Aug 9 2023
Jul 17 2023
Jul 15 2023
@JohanahoJ As "be" as "vitryska" comes from the Unicode project CLDR, I suggest that you open a ticket to change the Swedish translations in the Unicode project. This is the primary way to fix the issue. Please add the Unicode ticket number here, so that we can add it as comment to LocalNamesSv.