Page MenuHomePhabricator

Add WS Export to translatewiki.net
Closed, ResolvedPublic

Description

Project information

Name: WS Export
Homepage: https://wikisource.org/wiki/Wikisource:WS_Export
Project link: https://github.com/wikimedia/ws-export
Code repository: https://github.com/wikimedia/ws-export.git

  • Source branch: main
  • Target branch: main

OS License: GPL 2.0 or later
Issue Tracker: https://phabricator.wikimedia.org/tag/wikisource_export/
Project contact: @Samwilson

Logo:

  • Without text:
  • With text:

Project description:

WS Export is a tool for exporting Wikisource books in EPUB, PDF, and other file formats.

NOTE: Section below will be filled by twn staff

Project setup checklist

Project configuration (for translation admins)

Namespace: NS_WIKIMEDIA
Prefix: ws-export-
Validators:

  • MediaWikiParameter
  • BraceBalance

Concerns

(FIXED) Low Priority: Suggestion for parameter documentation formatting in qqq.json file

Current:

"statistics": "Statistics statement. $1 is a link to the statistics page, with text from the 'statistics-link' message.",
"footer-version": "Application name and version statement. $1 is the application title; $2 is a link to the current version (constructed with the 'version' message below).",

Expected:

"statistics": "Statistics statement.\n\nParameters:\n* $1 is a link to the statistics page, with text from the 'statistics-link' message.",
"footer-version": "Application name and version statement.\n\nParameters:\n* $1 is the application title;\n* $2 is a link to the current version (constructed with the 'version' message below).",

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Samwilson changed the task status from Open to Stalled.Feb 5 2021, 4:36 AM

This is just a placeholder for now; the i18n work is not yet fully configured in the tool.

Intuition is set up in the tool now, and we're ready to get set up on translatewiki.

The translatewiki user has access to the Github repo.

Samwilson changed the task status from Stalled to Open.Feb 9 2021, 12:33 AM
abi_ triaged this task as Medium priority.

Thanks @abi_.

I don't quite understand the translate-page-limit-option request; is that to be used in the translatewiki interface or something?

Change 663530 had a related patch set uploaded (by Abijeet Patro; owner: Abijeet Patro):
[translatewiki@master] Add support for WS Export project

https://gerrit.wikimedia.org/r/663530

Thanks @abi_.

I don't quite understand the translate-page-limit-option request; is that to be used in the translatewiki interface or something?

@Samwilson - Please check my updated task description. It's a suggestion to change the way we format the parameters in message documentation. Using this formatting will display the nessage documentation to translators in the following formatting:

image.png (475×1 px, 90 KB)

This helps improve readability for translators especially for messages that have multiple parameters.

Yes, that makes sense. I should've done that to start with! I think I knew it was a standard. :-)

@Samwilson - We wanted to use "Wikisource Export" as the label for the project instead of WS Export which we found to be a bit cryptic. Thoughts?

Change 663530 merged by jenkins-bot:
[translatewiki@master] Add support for Wikisource Export project

https://gerrit.wikimedia.org/r/663530

@Samwilson - We wanted to use "Wikisource Export" as the label for the project instead of WS Export which we found to be a bit cryptic. Thoughts?

In addition to this, I wanted to just ask regarding updates to the tool. Translatewiki.net exports translations twice a week. How long would it take for these translations to be visible to end users? Do you have a regular deployment schedule?

We wanted to use "Wikisource Export" as the label for the project instead of WS Export which we found to be a bit cryptic. Thoughts?

Yep, that's fine. Could the page at Translating:WSExport be changed to Translating:Wikisource_Export as well then? The aim is to avoid the Scunthorpe problem.

How long would it take for these translations to be visible to end users? Do you have a regular deployment schedule?

We deploy automatically and immediately to the staging site, and then manually every week or two (as required) to production. We have a bunch of other tools in a similar situation. We get notifications in our team chat channel whenever a commit is made by translatewiki.

We wanted to use "Wikisource Export" as the label for the project instead of WS Export which we found to be a bit cryptic. Thoughts?

Yep, that's fine. Could the page at Translating:WSExport be changed to Translating:Wikisource_Export as well then? The aim is to avoid the Scunthorpe problem.

Done!

Exports to Wikisource Export will happen later today.

Change 664513 had a related patch set uploaded (by Abijeet Patro; owner: Abijeet Patro):
[translatewiki@master] Add Wikisource export to the groups in repoconfig.yaml

https://gerrit.wikimedia.org/r/664513

Change 664513 merged by jenkins-bot:
[translatewiki@master] Add Wikisource export to the groups in repoconfig.yaml

https://gerrit.wikimedia.org/r/664513

@Samwilson Is this still in dev, or can this be moved over to review/QA?

This is done and released, but there's some fixes needed, e.g. https://ws-export.wmcloud.org/?uselang=he

They can be follow-up tickets though.

dom_walden subscribed.

We now have translations in 17 different languages (bn, da, el, en, fr, gl, he, hu, it, ko, lb, mk, om, pt-br, sv, tr, zh-hant).

For example:

This change is now on production.

Test environment: WS Export test version 2.3.2.

This is now on production, and as noted above, we already have translations in some languages. I am marking this work as Done.