It's inconvenient to have users translate directly on the GH page so it's probably better to convert the PHP file to i18n and JSON and to add that to translatewiki.net
Description
Event Timeline
Doing this may not be possible. The Miraheze/landing repository seems to not use MediaWiki codebase, as such unless it is converted to do so, the normal MediaWiki i18n/*.json may not work. Although I'm not 100% certain.
I'm regrettably changing the status of this to declined. I know we had conversations on Discord about this but this is simply impossible to achieve in a sane manner.
- this is impossible to convert to json since it's not MediaWiki (unless we made it MediaWiki or extract portions of MediaWiki in order to parse the json translations)
- secondly, as you recommended on Discord, using multiple language files is also not an ideal solution because then you have to load each individual file in the repo somewhere and that just makes a mess if things. There may be a sane way to achieve this but none that I found, therefore regrettably changing this to declined.
This is not impossible? MediaWiki does it in PHP, And the relevant functions of JSON reading are PHP core.
- secondly, as you recommended on Discord, using multiple language files is also not an ideal solution because then you have to load each individual file in the repo somewhere and that just makes a mess if things. There may be a sane way to achieve this but none that I found, therefore regrettably changing this to declined.
Why is using multiple language files not ideal? It doesn't seem to be a problem currently with MediaWiki.
Oh interesting. Thanks for the reply then I wasn't aware that it was php core that MediaWiki used to do it. Thanks!
Also note that translatewiki.net supports several different formats for exporting messages, not just MediaWiki's JSON.