While working on T306573: Copy button in Codex demos copies extra newline in Chrome I was not able to set the IP and port that the server should run on when using npm run doc or npm run doc:dev. I had to modify the vite.config.ts file in order to change these configurations.

In T308720#8141902, @Wangombe wrote:

In T308720#8123066, @Tacsipacsi wrote:

In a one-column layout, I don’t think long dates look bad (they can break into multiple lines without breaking the layout); my comment was only about approach A.

You're right. The default list decoration available on the <ul> tag makes the text readable even if it wraps to the next line because it provides some visual separation between the summaries. The date with the link is also legible in this format. The UI language is in Sakha (sah). One concern I have is the number of entries (5) pushes the translation memory out of view and extra scrolling is needed to access them. I don't think this is ideal for the translators experience.

The edit summaries may also not have a new update since translations may not change for a while. Showing 5 may be a bit excessive. I propose 3 entries to give room for the translation memory.

Translations were exported today: https://github.com/Ajapaik/ajapaik_flutter_app/commit/cc8e52586d26f23c507759ee1329ed6fcfd41e50

Translatewiki exported the translations out today: https://github.com/lingua-libre/SignIt/commit/809c44c142b7a1fe8e15de3c915a93118ee21e85

For PageTranslationHooks we want to do the following:

1. Move the class under the PageTranslation namespace and rename the class to Hooks. Remove use of any deprecated methods if possible.
2. As part of another task(T314759), start implementing hook interfaces and injecting dependencies.

@Yug There have been a few issues and PR submitted to fix things:

Project is available for translation: https://translatewiki.net/wiki/Translating:Lingua_Libre_SignIt

Translations failed today due to lack of commit access for the bot. I've created an issue on GitHub: https://github.com/Ajapaik/ajapaik_flutter_app/issues/2

The editcontentmodel right is not needed if we create the page with the correct content model to begin with.

In T314253#8128845, @Yug wrote:

Nice. Thank you @Nikerabbit . I just published a stable version on Firefox.
The translations files are clean.
Also, I'm unfamiliar with your process. Do you have all what you need from me ?

We've not received any reports of these changes causing any issues. Marking this as resolved.

Tested on Translatewiki:

Deployed on translatewiki.net: https://translatewiki.net/wiki/Special:Translate?action=translate&group=ajapaik-flutter-app

For this task we believe we've fixed the out of date translation pages when translation units are deleted using Special:Nuke extension. We've created a separate bug report to track the issue related to successive reverts: T314390: Successive translation unit reverts cause out of date translation pages

Tested on translatewiki.net. I confirm that the issue is fixed.

@Wangombe - I think this issue is fixed. Can you confirm?

I do like approach A and B more because they appear less busy, but I think they will not work very well with touch devices so I would prefer to go with approach D.

This tool was used to import a large CSV file: T313051: Mass import translations from CSV file for MSG termbase and the process completed without errors. There were two improvements identified:

We've added a fix for this, and the page now renders fine. The underlying issue is tracked in a separate task.

Thanks @brennen!

I was also wondering if we could just have the date and the summary text without any spacing in between as a continuous text. Something similar to:

This is happening because we are now (ff82250e) using the TtmServerFactory to create instances of available translation services. With the configuration on MediaWiki:

Fix for this issue has been backported. It is now working as expected. Thanks you.

I am able to reproduce this locally with the following configuration set:

I'm able to reproduce this locally. Here's what I think is happening:

@Asaf - I've added some documentation regarding WikiLearn on the Meta-Wiki page here: https://meta.wikimedia.org/wiki/APatro_(WMF)/Translating_WikiLearn_Courses

Tested on MediaWiki

This workflow works as expected now.

This is fixed: https://www.mediawiki.org/w/index.php?title=Special:Translate&group=page-Category%3AContent+maintenance+scripts&action=page&filter=&language=ja&uselang=en

Note to system admin: Importing this CSV file will put a lot of jobs into the queue. Recommend running the import when traffic to the site is low.