Open supertassu opened 4 years ago
This is definitely in the plan for UTRS 2 and is a big point why laravel's built in translation system would be used. I was going to leave it till later, but you are definitely right about it easier being started now.
I never considered getting translatewiki to help. How exactly does that work?
I haven't used translatewiki, but I think that the idea is that their bot will add the english translations into MW's Translate extension and then when they are translated they will be updated back to translation files that Laravel understands.
Doesn't sound like a bad idea. So the question is can we integrate with it. I'll authorize @supertassu to work on my behalf for this, and let me know if you need anything in terms of information for them. Please report back if this is doable and if any major changes are required before we proceed with development.
@Matthewrbowker could you provide us any insight into this service and things we should know?
FYI: changes in #158 use Laravel's own translation system
At this time, this task needs more research, and maybe recreation at this point because the original task needs a full redefine. The use of the existing system, while it was easy, is not sustainable. translatewiki.net needs to be fully explored and a plan be drafted to tackle it.
The other thing that needs to be looked at here is the email replies (which might need to be databased) and the statuses that are submitted that can't be changed.
Especially if UTRS is used on other wikis or for global (b)locks, it should be possible to translate UTRS into more than one language. Laravel has it's own built in translation system, using it is probably a good idea. Using translatewiki.net for editing non-source languages (not English) is also an idea worth exploring.
Initially prioritizing this as medium as this is much easier to implement when there aren't that many phrases, feel free to change.