Do you want to ship the translations with the extension or fetch them with the API? In the first case, it might be easier to set them up as a new translatewiki.net project.

I had planned to fetch them with the API, but setting up a new translatewiki.net project also seems like a promising option. The only drawback I can see there is that MediaWiki might have many more interested translators than a standalone project for this extension.

Are most of the browser extension messages already present in the MW extension?

In T191846#4139896, @bearND wrote:

Are most of the browser extension messages already present in the MW extension?

See T191817 and the doc linked there for better discussion. There are some strings that don't exist at all in the extension, and others (e.g., when the user is not logged in) for which I think the string resource used there is too generic for client use.

Maybe it's better to keep these in the ReadingLists extension from the start, considering this browser extension will likely be superseded in the not-too-distant future by a full web interface.

If we end up doing this then it would be good to add an additional prefix to the messages that are only in the browser extension, so they can be easily moved to the right place. Sounds like there is not much overlap between the two in terms of message, so maybe keeping it separate from the start makes sense.

Change 427678 had a related patch set uploaded (by Mholloway; owner: Mholloway):
[mediawiki/extensions/ReadingLists@master] Add i18n messages for the browser extension

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

In T191846#4142873, @bearND wrote:

If we end up doing this then it would be good to add an additional prefix to the messages that are only in the browser extension, so they can be easily moved to the right place. Sounds like there is not much overlap between the two in terms of message, so maybe keeping it separate from the start makes sense.

I have the new messages prefixed with readinglists-browser in the patch I just pushed.

Besides the considerations mentioned above, I also opted to put the new messages in the existing MW extension because (a) there are only five of them, and (b) TWN prefers to support projects that are intended for long-term development, and this standalone browser extension is likely only a temporary project.

From TWN: "We value the work of our volunteer translators, which means we are looking for healthy projects which are actively developed for the foreseeable future."

That sounds good to me.

Change 427678 merged by jenkins-bot:
[mediawiki/extensions/ReadingLists@master] Add i18n messages for the browser extension

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