It’s not exactly clear what we should do. For now don’t mark the lines, we need a bit more direction with the markings if we do so. We need to be able to 100% say that a line is correct and it can be marked. We could have people marking lines x or o when the translation is completely wrong. IMC needs to guide the translation a bit more, its getting hectic with the influx of translators. There is 48 pull requests…
Edit: 50 pull requests…
I would love to help, but there are a few points I need made clear before I can really contribute:
I like you. You decided to ask the appropriate questions instead of ignoring any indication of guides and contributing useless clutter, like 90% of the current contributors. You don’t need a beta key, right?
I was fortunate enough to get into the beta already, yes - which is good since it means I can see where these texts actually appear in the game. Thanks for implying an offer, though!
For the record, I’d basically name Ensata the leader. They’re organized and take the project seriously. It’s just that new people don’t normally take Ensata’s (or anyone else’s) advice on what conventions to follow. 
I really hope someone drums up some guidelines on translation. Things like tone/context really shouldn’t be looked past and I have a feeling that with the announcement of the key’s given to helpful translators we now have TOO many people trying to commit unnecessary changes to the files. Adding/changing things to “flavored” text is not okay. There is no context for most things so it should just be straight forward until IMC does things like that…
I hope IMC asks some of the more dedicated people to try and deal with this kind of stuff. I’m new to it and all these recent commits are overwhelming so I’ve just been fixing things like “teh” to “the” and such…plus github destroys my browser, haha.
Github is really awkward and I really hope I’m not accidentally sending the team 20 mild versions of one edit since it sounds to me like you guys have quite enough crap to deal with…
Honestly its quite maddening, it seems like people are just trying to hop on the bandwagon and try to get a key or something. If they had mentioned keys when they started the GitHub it would have been a much bigger mess. But look at it now, its way too much. IMC needs to be upfront with the suggestions Ensata has made as well as other members. It’s getting to be way too much. I was busy for nearly the last month and after coming back to check some of the GitHub this past week, its a mess. Way too many people trying to make edits which don’t need to be edited. Too many people editing the same lines, not following guidelines, being too liberal. We truly don’t know the context of a lot of these lines but I see so many members changing the entire meaning of a sentence. This just snowballs and makes things worse in the end. It’s not a bad idea to start small with the little changes like teh to the. When the beta rolls around it should be a bit easier to confidently change lines when given context.
I personally would’ve preferred they gave out the keys in secret, just as a kind of “Thank you”. It would’ve alleviated a lot of these problems…or not started them at all.
But I understand why they would want to show they support the community, so it’s a hard call there.
I’ve already received a key, so I don’t have to worry about getting one through translations one way or another I just want to help out but it’s almost like working backwards trying to force all these commits down their throats…
Wait until the Pull Requests are all filtered out and merged or closed. Then you can try and work on some lines. I’d look deeper into files because so many people just do the first 100 lines of a file which have been completed 293638726 times now.
We truly don’t know the context of a lot of these lines
Personally if I have no idea why a line is showing, I don’t touch it. I’ve been focusing on ETC and a lot of the lines near the bottom mean absolutely nothing to me… I mean, I can wildly guess that they’re alerts during special events or dungeon instances, but until I know exactly where and when it appears on the screen, I can’t commit a “final version” in good faith.
I might be a bit more bold after playing through the beta for a day or two, of course.
Well you kinda picked a bad example for trying to figure out the context of lines since ETC lines are usually just that, ETC. They are lines which are scattered throughout the game in random parts, whether it be UI, Quests, Dialogue, ETC. They are miscellaneous lines with little to no context in most cases. ETC is a tough one to translate. If you want to get a feel for context I’d look at quest files, as those still need revisions, and they provide more context as you read through.
That’s precisely why I started with ETC. They’re generally standalone lines, so they’re much easier to edit into something readable.
The other lines, of course, I’m not going to mess with until I’ve played the game to see where they are.
I think I’m going to go ahead and quit helping after reading all these comments. While I have done this sort of thing in the past for work, I don’t want to step on people’s toes or create more work for anyone just because they disagree with my changes.
Not to mention, as several have said, without context certain aspects of proofreading and editing the English translations become extremely difficult. Linguistic/grammar rules are heavily context dependent when it comes to the tone or “flavor” of writing. I might know more about grammar rules than the average Joe, but I am by no means an expert authority on the subject.
I think that the in-game translator will be your best tool in helping if it’s implemented, as it’ll allow you to have things in context. So you might fare better with that…
Yes it’s going to be in.
Yeah I just asked a streamer to try it out in kCBT3 and it seems to work there too.
That’s kind of a unfair claim to make, I didn’t even know that there is a way for people who don’t know korean to help until this week. And honestly, I was very hesistant first with trying to make any changes since I was worried about doing something wrong. But when I actually did something wrong Ensata actually made a comment on my pull request to correct a mistake I made. I didn’t even know about any guidelines until someone pointed them out in this thread either. I suppose I’ll just give up on trying to help for now
Sorry that was a little harsh. I did not mean it that way. I am not entirely sure if everyone’s doing it for that or its just the excitement of the game launching soon. Just don’t get discouraged. I know it’s a lot to deal with but every little bit helps. Following the guidelines will help a lot to avoid mistakes early on. Think about what you edit before you edit it and you shouldn’t be too worried about mistakes. Don’t take my ignorant comment personally, please.