You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see two existing requests for additional languages, and I see the maintainer stated they have no time to implement them.
But perhaps you can indicate what it would take to support additional languages? If you could document the main requirements, I am sure people could be found to create pull requests and gradually increase the coverage of this very useful tool!
The text was updated successfully, but these errors were encountered:
Hey! So for additional languages, the main requirement is to run through the dumps server-side to create the initial data and then set up the pipeline for continously listening to the repespective event streams/pull the revision texts. That is basically just a repetition of previous languages but still requires meaningful effort for which there are no resources on my side right now. And there is not much that can be contributed through pull requests there. Also the server we are running this on right now would proably not support more than 2 larger language editions without being needed to be upgraded.
(A secondary task would be to actually test the output for additional languages, since tokenization is not 100% language-agnostic, although the rest of the algorithm is)
So bottom line I have been thinking about that it might be better to move the project to Wikimedia servers. The Wikimedia iOS team has also been reaching out and it seems that the demand for languages (and increased requests) make this a good idea.
Hello, and thank you for your work on this!
I see two existing requests for additional languages, and I see the maintainer stated they have no time to implement them.
But perhaps you can indicate what it would take to support additional languages? If you could document the main requirements, I am sure people could be found to create pull requests and gradually increase the coverage of this very useful tool!
The text was updated successfully, but these errors were encountered: