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
Some time ago, the Wikimedia Foundation published its own translation system, MinT. It supports more than 200 languages, and it keeps getting better by using Wikimedia contributors' translations and other sources.
More informations about it can be found here and it can be used from this website as well.
Many languages available on MinT are not supported by any engine used by Dialect right now, so I think that would be a great improvement to it.
The text was updated successfully, but these errors were encountered:
The API seems straightforward to implement (https://translate.wmcloud.org/docs) but https://translate.wmcloud.org is the only instance available and is a test one, so I don't think it's right to point to it. Alternatively we could not provide a default instance and users need to provide one.
I guess we could also try to host one instance but I don't think we have the resources.
Yeah, looking at their instance's specs, i think so too.
Having users provide an instance for a service that has next to no alternative providers right now also feels like bad UX...
Why not just use the test instance for now until there are alternative instances to default to? Shouldn't really be a problem since we would only have a small subset of users switching providers in the first place. As long as MinT isn't the default, I think we should be okay, right?
Some time ago, the Wikimedia Foundation published its own translation system, MinT. It supports more than 200 languages, and it keeps getting better by using Wikimedia contributors' translations and other sources.
More informations about it can be found here and it can be used from this website as well.
Many languages available on MinT are not supported by any engine used by Dialect right now, so I think that would be a great improvement to it.
The text was updated successfully, but these errors were encountered: