Tree of Savior Forum

Is it too late to change the translation platform?

Translations
#1

Not the prettiest of titles, but after I was introduced to this platform while helping a team translate their app, I just kept thinking that if IMC would have used something like this, the translation for Tree of Savior would probably go a lot more faster!

Github is… hard. Hard for coordination, hard to translate. Afterall, it’s not exactly a translation platform, but was what the devs were able to get up and running so we could help them. And, well, it’s free for them. Having in mind that they have to crowdsource their translations, I’m guessing that they aren’t swimming in money.

It would bring a little dent to their finances, to use that platform, but honestly, I think it would benefit the community a great deal!

If anyone reads this post that helped contribute in the GitHub could give their insight, comparing both platforms, that would be great.

4 Likes
#2

That looks really nice, $450 per month isn’t really that much money even for a small company and this would be a lot easier for the majority of translators to use.

#3

This is great! I hope IMC can take a look at this.

#4

[quote=“FxFighter, post:2, topic:37751, full:true”]
That looks really nice, $450 per month isn’t really that much money even for a small company and this would be a lot easier for the majority of translators to use.
[/quote]Emphasis mine. It would certainly provide a better platform than x-ing out stuff that was edited. On the other hand, I doubt it would work nicely with the OTC system we already have.

Github may be a pain to get started with for those who never used it, but it just works once you get into it. Merging translations works well, too.

The main bonus of crowdin would be an “all-in-one” package, vs our current setup of github+discord to coordinate ourselves, I guess.

#5

GitHub is way cooler … :blush:

#6

I did try to use the GitHub, but there was too many rules that were not documented well enough, too many steps to take to be able to actually contribute. It’s was just hard to get into.

Especially for someone like me that actually had no intention of translating, but of proofreading. While playing the game I found little mistakes, missing punctuation, but when I went to GitHub to try and help, constraints anywhere. Don’t send small pull requests, check the pull requests awaiting for confirmation to not repeat the same lines.

So many things that I ended up giving up, too much time consuming to do all those checks and verification.
I mean, it’s probably fine if you’re actually translation, set a range, warn people and get on with it. But otherwise…

#7

Github also has a built in agreement so anyone who translates on it cant try and claim copyright like a smuck. Which some of the people tried to do and got shut down.

AKA using Github protects IMCs property

#8

Can you elaborate on what you mean with this? I don’t quite understand what you mean by claiming copyright.
How can you exactly claim copyright on something like this? Like, say that what they translated belongs to them?

It just doesn’t make much sense in my head, but there are all kinds of crazy people, I guess.

#9

Yes people said i translated this line of text i now own it. But since they did it through Github IMC could just say no. And yes there is no limits to the stupidity of people.

#10

If everyone follows those rules, it’s easy to check to not submit duplicated work. Besides, usually there aren’t that many pull requests, it’s kind of broken now because IMC went on hiatus to parse all the data they got from the beta.

As for “too small PRs”, I agree the rule is silly and makes PRs needlessly complicated. It’s far easier to merge a one-line PR than to merge a 100 line one, the chance of merge conflicts is just that much higher. It’s not a restriction of github, though, but one chosen by the team. Meaning, that can change.

Edit: as for proofreading, all you do is read through changes in PRs and point out any mistakes you might find - that’s the easy way to get into it until you’re familiar enough to contribute your own PRs by proofreading the stuff that was already merged.

#11

GitHub is ok for single language translation, I don’t think it’s going to scale well if they end up doing another 10 languages of translations. Going to have to have a branch per language and the pull request page is going to get a bit messy along with the issue list if they do go down the route of doing multiple translations.

The Crowdin site shows a much better overview of the progress of the translations and would work better when new files are added/existing files are modified showing how much more there is to translate.

It wont affect me either way since I’ve been using GitHub for a long time for programming anyway, most people who are trying to help with translations seem to have no idea what they’re doing with GitHub (which is expected) and this just seems like a nice option to help the majority.

My other point is, anyone who’s good at their job evaluates off the shelf products that are targeted towards what they’re doing and crowdin is built for almost the exact purpose of what’s happening right now with translation of TOS. You don’t just stick with something you’re familiar with when there is something potentially better, you evaluate the other product and make an informed decision about which is going to serve you better in the long run.

I’m happy enough either way.

#12

[quote=“FxFighter, post:11, topic:37751”]
GitHub is ok for single language translation, I don’t think it’s going to scale well if they end up doing another 10 languages of translations. Going to have to have a branch per language and the pull request page is going to get a bit messy along with the issue list if they do go down the route of doing multiple translations.
[/quote] I don’t think using branches in that case makes sense, it would most likely be a separate repository.

[quote=“FxFighter, post:11, topic:37751”]
My other point is, anyone who’s good at their job evaluates off the shelf products that are targeted towards what they’re doing and crowdin is built for almost the exact purpose of what’s happening right now with translation of TOS.
[/quote]True, however the cost plays a role, too. Not only the cost of the product, but also the training cost for the people involved. In this particular case, there are no training cost because they outsourced it to the community, but I thought I’d name it anyway. The cost of crowdin is not so high, so maybe they will consider it, I don’t know. It certainly seems to fit the purpose rather nicely.

#13

A separate repo would probably be better for different languages, not sure why I didn’t think of that when I made the previous post. :3

#14

Agreed, I desire to be helpful, but the translator is so hard to use D:
seriously, I need a help how to use the translator Dx

#15

I’m part of a french translation team and I’ve started the translation project by creating a new repository. I think it would be a fine management system for IMCgames.

For now we’re doing a french clone of the original repository, we’re working on the references (wiki) and we’re waiting for IMC to update the original one as we could check if we’re good with what we’ve done already.

Then we expect to do an “owner transfer” when IMCgames will be ready to manage other language translations. Until this day we’ll work on the translation by ourselves.