treeofsavior / englishtranslation Goto Github PK

I have been adapting to "Attribute Point", because I think it sounds good. But it is officially Status Point (스테이터스 포인트).
What is your verdict on this matter?

I have progressed with my translation tool now so much, that I can search for standard terms in the TSV files and locate inconsistent usage of those. Right now, I get my reference data from the official wiki entries. But those entries stand in contrast with the merged translations. I think we need to find a way to fix those entries in the reference wiki ASAP, or find anther way, to create a stable reference data pool (Items, Monster, NPC names etc.).

http://pastebin.com/409fVfJk

Explanation:
Source text = Korean original
Target text = English translation
Standard term = Name as found in the reference wiki
TSV-entry = Name as found in the English translations

Some log entries don't have a TSV-entry. In that case the word was used in a longer context and you have to search for it inside the original TSV files.

How can we resolve these inconsistencies?

While evaluating a pull request of a user, I've come across the term Divine Day.
This is referred from 신수의 날 in Korean. The official site refers this important event as "The Day of Divine Tree".

Maybe @imcgames can elaborate on this? What is the actual meaning of 신수의 날? Divine Day or The Day of Divine Tree? (or should it be The Day of the Divine Tree)?

Thanks to Flash of TOSBase, you can see here CBT2 gameplay with a half-English client so we can fix the missing translations or the wrong ones.

https://www.youtube.com/playlist?list=PLZmwVtJXg551uyb5Rlsd9qdVtwkiMpaiw

English UI (Fan Translation): https://www.youtube.com/watch?v=OlBo9ixl5Z8

Do you at IMC Games want a direct translation for all of the Quest dialogue? I watched a video of a CBT2 ENG translation version of ToS and the dialogue feels clunky and forced, mostly because a lot of what makes sense and is natural in Korean doesn't translate 1:1 perfectly with English. Will there be an opportunity for the translators to see the lines we translate in-game and then be able to tweak the dialogue from there? I can see a huge potential for a much smoother/natural dialogue for quests and NPCs if there was an opportunity to put the dialogue into context (settings, character personalities, etc.).

Hi guys!

We will be updating the translation files and change its file names on July 1.
Currently, the English files have '_en' at the end of the file names but we plan to change it so that the Korean files will have indicators (maybe '_kor'), not the English files. Also, some files will have its name changed as well.
We feel that this would be necessary to make better use of github with game client such as directly using the files in github when playing the game.

Unfortunately, we haven't found a way to get github to retain file history after the name change so the file's history may not be kept after the update.
If you do know a way to keep file history even after the name changes, let us know and we'll be open to trying it out.

As you may know, we have renewed our website and opened our forums and we thank you for the warm responses you've shown us.
We hope to bring you some good news in the near future and until then, please send us your continued support for Tree of Savior.
(And of course, the translations too 😉 )

Should we be trying to stay consistent with either UK or American English?

I assume most international media these days opt to use American English, but I've noticed quite a few gaols (jail) in the translation. Are these placed with intent or just a machine translation by-product?

with open source translations maybe it would be best to do a series of find and replace edits near the end of the process to be consistent.

Just wanna check:

in ETC.tsv

Github reports We can make this file beautiful and searchable if this error is corrected: Illegal quoting in line 4563.

ETC_20150317_004563 퀘스트Name = "

There is a single double quote. There are other lines like that too. Wanna understand what is the purpose of the quote.

To make the translation process more convenient and accessible, we've also opened a Google Spreadsheet for translations to test it out here.

Please let us know what you think about it. Do you like it? Is it easier to use? Should we consider switching to Google Spreadsheet? Any other comments and feedbacks are also welcome! 😄

@imcgames : Why did you deleted some translation files with the last commits? Those files where not nearly finished and QUEST_LV_0100_en.tsv needed heavy translation checking and still a lot of editing.

It would be nice if you could use the commit message to explain why you are doing things like this. Do you intent to re-add them in a different structure? Do you considered them as "finished"?

I suppose that Tree Root Crystal of Laziness ( 나태의 나무뿌리 수정 ) will cast a spell on the player (or the party) and makes them fall asleep.
Maybe laziness is not the correct term because Laziness means a lack of personal willpower without an external factor.
Howewer we can use some alternatives to describe this spell:

• Fatigue
• Tiredness
• Sleepiness
• Drowsiness
• Trance
• Hypnosis

What do you think?

Any interest / possibility in opening a chat channel for all the fan translators and the devs responsible for this project?

It would help resolve git conflicts, overlap work, and might be nice to have a real-time way to contact the devs.

Also, it would help build some community and give us a place to complain and talk about how great we are with each other.

So if you watch the video https://www.youtube.com/watch?v=6SH7nv1SZjs&index=1&list=PLZmwVtJXg551uyb5Rlsd9qdVtwkiMpaiw#t=11m46s you'll see items you receive or need are shown as "(item name)(number amount)(ea or ea obtained)" EX: "Hanaming3 ea"

I would like to change lines 3311 and 4661 in ETC_en.tsv from "ea obtained" and " ea " " to " x#" or maybe even " x# received", where # is the amount of items. So in the previous example "Hanaming3 ea" becomes "Hanaming x3". But I wasn't sure how to write it in the line since the item amounts aren't in there; and I also want to know what you guys think before doing anything.

Refering to https://github.com/Treeofsavior/EnglishTranslation/wiki/2.1.%20Class

I'd like to make some suggestions regarding 2 class names wich are based on german names:

1. Doppelsoldner should be changed to Doppelsöldner
   It should be Doppelsöldner (see http://en.wikipedia.org/wiki/Doppelsöldner). I understand that the ö is not very common for most people but the goddesses also have names that include special characters like Giltinė so it should either removed for all names or kept for all names.
   If you really don't want to use the ö for some reason please switch to oe. It was like this before and it's also like this on the Nexon page but got changed here on github for some reason. The official replacement for ö would be oe but ö should be used if possible.

Quote from wikipedia: In other languages that do not have the letter as part of the regular alphabet or in limited character sets such as ASCII, O-umlaut is frequently replaced with the digraph "oe".

But I think in TOS there is technical reason not to use the ö.

Source:
http://en.wikipedia.org/wiki/Germanic_umlaut
http://en.wikipedia.org/wiki/Ö

2. Schwarze Reiter should be changed to Schwarzer Reiter
   I think this translation is based on this wikipedia page: http://en.wikipedia.org/wiki/Reiter
   it states: “Schwarze Reiter”—literally, "black riders"
   "Schwarze Reiter" is a plural. All other classes use the singular (e.g. Archer instead of Archers) so the correct name would be "Schwarzer Reiter" (with an additional "r") as this means "black rider" instead of "black riders". It's strange to see this one class name as plural.

https://github.com/Treeofsavior/EnglishTranslation/blob/master/ETC_en.tsv#L758

This line is not using TAB.

I was sweeping through ITEM_en.tsv and applying the official translations for proper nouns when I noticed some typos.

These are the changes that need to be made:

So the files have recently been updated with more lines, and in them there are thousands of lines of what is obviously machine translated dialog.

Looking at the new Quest files, a huge amount of these new lines are impossible to correct just by fixing the grammar or rewriting. With the bad ones, the intent of the sentence is totally incomprehensible, and even with most of the better ones it's not possible to fix without some guesswork. Some examples:

-I was burned secretly as go toilet. {Nl} Thank you very much.
-Speaking the only so, it was too burger. {Nl} However, Nante you helped me, I was really good.
-I would have thought to while watching the Ironbaum. {Nl} their friends really awesome friend.
-As before, I do I become many people who go back and forth this way. {Nl} people I'm really interesting.
-It is really embarrassing that came out to run away alone. {Nl}

I understand that our current goal here is just to get something rough and functional together for an English test client, and I suppose these are better than nothing for testers, but I think it's going to make the actual translation job harder.

People could previously just look for blank lines in the EN files to know which lines need to be done. Now that we have thousands of lines of word-shrapnel, each line needs to be carefully read and then determined to be unusable before it gets translated, which is significantly more work for the people who can actually do the translations.

I'm curious what others think, it seemed worth discussing. I'm not sure what should be done. Maybe we need pull requests with nothing but deletions of bad lines in them, or some other way to help sort out the lines that are beyond salvaging.

Needed confirmation on what you wanted to put as the various equipment slot names. In one line, for example, you have Hair Slot vs Hat Slot (could even change this to Helmet or Head Slot). If someone could clarify what the name should be standardized to that would be great.

Hello @imcgames ,

Is it possible for you to give more screenshots or a video in-game to show progress in the English TOS client using the recent localized files? Because I would love to see it since there are a few contributors who've done a good job.

Is the idea of editing awkwardly translated text, where you locate your cursor on the text and press CTRL+SHIFT with a mouse click to edit while ingame? It would certainly make this a lot easier for me.

Thank you.

The text "Chance of receiving additional exp of 50%." appears in quite a few items and is kind of vague/awkward.

Should be...
"50% chance of receiving additional exp."
or...
"Chance of receiving 50% additional exp."
depending on the intended meaning.

@imcgames please advise and I can submit a patch to fix it!

Hi guys!
It's been a few days since our test run started and for those who have been trying it out with us, we really appreciate your efforts. 👍
If you have any feedbacks and/or suggestions, we'd be glad to hear them so let us know through the comments below or you can create new issues if it calls for a new discussion 😃

I don't speak Korean so my ability to help is limited, but I notice when something sounds goofy in English. I've come across a couple words that are used a lot in the Quest file as translated so far which seem like they might not be quite right.

The first word that appears a lot is "Devil", which seems to be a major enemy type that appears many many times in the Quest dialog, and players will no doubt be fighting them a bunch. I believe the original Korean word used is "마족". The most common usage of "Devil" in English is to refer directly to Satan ("the" Devil). When it's used to refer to lesser evil spirits, it often has a kind of mischievous or impish sort of connotation. It's simply not used very often in games media to describe evil or unholy monsters.

I mentioned this in one of my pull requests and another user suggested "Demon" as a better choice. I lack the context needed to know if Demon is a more accurate translation, but it certainly seems to sound better.

The second odd word is "Revelator". The Quest file makes many mentions of "Revelations", "Revelators", and seems to refer to the player character directly as being "the Revelator", as some kind of "chosen one" title. The original Korean word seems to be "계시" or "계시자". My main problem with Revelator is that it's a very seldom used and obscure word, to the point where it ends up just sounding like a too literal translation.

I wonder if "Prophet" might be a more useful title that has more or less the same meaning as Revelator. It would be helpful if someone could provide better context for what the original script is trying to say.

Was going through the terms and found these errors that the staff might consider fixing.
https://github.com/Treeofsavior/EnglishTranslation/wiki/2.%20Reference

Format:
Korean Word - Original English Word - Suggested English Word
or
Original English Word - Suggested English Word

Class:
쿼렐슈터 - Quarrelshooter - Quarrel Shooter
도펠죌트너 - Doppelsoeldner - Doppelsoldner
크리비 - Krivi - Krivis
사두 - Sadu - Sadhu
References:
en.wikipedia.org/wiki/Doppelsöldner
lt.wikipedia.org/wiki/Krivis
en.wikipedia.org/wiki/Sadhu
These are all their original spelling, and I suggest we stick to it :)

Map:
심문실 - Investstigation Room - Interrogation/Investigation Room
페디미안 직할령 - Pedimian Territory - Fedimian Territory
수정광산 1층 - Crystal Mine 1st Gallery - Crystal Mine 1st Floor
수정광산 2층 - Crystal Mine 2nd Gallery - Crystal Mine 2nd Floor
수정광산 3층 - Crystal Mine 3rd Gallery - Crystal Mine 3rd Floor
수정광산 2광구 1층 - 2nd Mine Lot 1st Gallery - 2nd Mine Lot 1st Floor
수정광산 2광구 2층 - 2nd Mine Lot 2nd Gallery - 2nd Mine Lot 2nd Floor
칠채고원평 - Seven Hues Mesa - Seven Hues Plateau
하늘지친 고원 - Skyweary Mesa - Skyweary Plateau
큰고립 고원 - Grand Isolated Mesa - Grand Isolated Plateau
마당 고원big - Grand Yard Mesa - Grand Yard Plateau
"Mesa" is a Spanish word for Plateau, since there are other terms that are using the word "Plateau" for 고원, I believe the developer should look into which word accurately describes the map. Highland, Plateau, Mesa or etc.

Equipment:
망고슈 - Maingauche - Main Gauche
콰다라 - Guaddara - Quaddara http://commons.wikimedia.org/wiki/File:Quaddara_sword_and_kindjal_dagger.jpg
병사의 숏 로드 - Soldier'S Short Rod - Soldier's Short Rod
병사의 라이트 보우 - Soldier'S Light Bow - Soldier's Light Bow
병사의 우든 클럽 - Soldiers Wooden Club - Soldier's Wooden Club
Morningstar - Morning Star
Godendag - Goedendag - Ref: en.wikipedia.org/wiki/Goedendag
Baltas Morningstar - Baltas Morning Star
로우 폴쳔 - Low Falchion - Crude Falchion
로우 카스카라 - Low Kaskara - Crude Kaskara
I don't think "Low" is the right term to use for lower grade items. I suggest to use "Crude" instead. Also, "Coarse", "Crude" and "Low" are all three terms used in the equipment section. Perhaps we should standardize it if they are all the same meaning.

Item:
이동속도 증가 포션 - Potion Increaing Movement - Movement Increase Potion
빅 코카트리스의 심장 - Heart of Big_Cockatries - Heart of the Big Cockatrice
붉은 케파의 줄기 - Stem of Red_Kepa - Stem of Red Kepa
붉은 케파의 결정 - Crystal of Red_Kepa - Crystal of Red Kepa
씨드미아 꽃가루 - Seedmia Poleen - Seedmia Pollen
러바인러바 산성 수액 - Ravinelerva Acdic Sap - Ravinelerva Acidic Sap
빅 코카트리스의 부리 - Big_Cockatries Beak - Big Cockatrice Beak
코카트리스 가죽 - Cockatries Leather - Cockatrice Leather
코카트리스 깃털 - Cockatries Feather - Cockatrice Feather

If I found more errors I'll let you know. Suggestions for terms highly welcomed.

Fixed:
"Companion Item" and "Costume" link to the same page.

Hi, I looked at the wiki and there is a difference between Mummyghast and Mummy Ghast. Which should we use?

머미가스트 Mummy Ghast
머미가스트 카드 Mummyghast Card

Also in QUEST_100_en.tsv, there are translations having Tree Ambulo VS Triambulo.

Since tree of savior was removed from nexon 2015 releases...

Source : http://upload2.inven.co.kr/upload/2015/05/14/bbs/i11038658807.jpg

Anyone else kind of unhappy with it?

It's really disorganized and seems to be less of a forum than a page of threads that people can randomly join. For an official forum that will ideally be used for bug reporting and translation discussion I feel like it should be more organized. I put up a post on the forum about using a different forum format, don't know if the idea will stick.

I feel like even Github is more organized as a discussion board than whatever layout imc is are using for their forum..

To prevent the issue of many people translating the same lines, you may indicate and reserve lines in the comment below the ones you'd be contributing on so that others would skip those lines. :)

The current format is "Item Name X ea" but I think it's not very suitable, so we could use a format like this "Small HP Potion x 3", this format is widely used so it would be easier to understand.
What do you think?

I'm currently proofreading some of the existing translations in ITEM_en.tsv.

From my understanding, 로우 -> Low.

The existing translations are inconsistent between "Low", "Crude", and "Mediocre", and has potential for awkwardness within context. i.e., Using a recipe to craft a "Low Falchion" and receiving a "Mediocre Falchion" as a result.

I should also mention that "Low [weapon]" is awkward in English, because "low" generally refers to an amount, which is typically inferred from context or explicitly stated. Much better would be "Low-grade" or "Crude" - i.e., 로우 폴쳔 -> Low-grade Falchion or alternatively, 로우 폴쳔 -> Crude Falchion.

@imcgames what is the intended translation for 로우 in the context of weapons / equipment?

Some examples of existing translations:

• 로우 폴쳔 -> Mediocre Falchion
• 로우 카스카라 -> Mediocre Kaskara
• 로우 라이트 크로스보우 -> Crude Light Crossbow
• 제작서-로우 바스타드 소드 -> Recipe-low Bastard Sword

To prevent the issue of many people translating the same lines, you may indicate and reserve lines in the comment below the ones you'd be contributing on so that others would skip those lines. :)

Please check the wiki page for reminders before sending your pull requests :)

Hi, while translating I noticed this:

ITEM_20150323_004104 몬스터의 기운이 가득 찬 병
ITEM_20150323_004105 몬스터의 기운이 가득 찬 병.

Is this correct?

계시자로 is more like oracle or prophet. Revelator just sounds weird. Would be good to know the context.

There should be a note on the wiki page on how to do this.

For example, the character, ö, is used in multiple places, but I'm not sure how to encode this in the translations. Generally, developers would use HTML codes like {ö}... but the scheme is dependent on the project.

@imcgames could we get an official response on how to do this?

EDIT: Forgot to escape the HTML code sample...

Going through the various monster drops and am wondering if I need to leave monsters as singular.

Looks similar to a bat wing, but is actually a plant stem. Obtained from Dandels.

Makes more grammatical sense since Dandels are (presumably) a common monster and you can farm the said Item (Dandel Wing).

The alternative is to leave them singular:

Looks similar to a bat wing, but is actually a plant stem. Obtained from Dandel.

which sounds weird. Let me know what you think, I'm currently just pluralizing everything but it won't be hard to undo that in another patch.

Just finished my first check of my tool to help the translation process of ToS. I wrote a small program that scans the files for entries, with the same Korean line but different English translations. As a result I found two conflicts, which need to be resolved by a translator:

Conflict one:
ETC_20150317_005246
ETC_20150323_009673

Conflict two:
ETC_20150317_006248
ETC_20150414_010918

First of all, thank you and a big shout out to the contributors. We really appreciate your efforts 👍
If you have any feedback and/or suggestions, we'd be glad to hear them so let us know through the comments below or you can create new issues if it calls for a new discussion 😃

I just noticed that all the translated lines have shifted around since yesterday.
New translations are impossible until this has been fixed.

Hello there,

Disclaimer : I don't speak or understand a word of korean.

@Sunaries pointed out a misspell about Royal Tomb in this pull : #312

So, I checked a bit.

There is (case incensitive):

• 12 results of "Royaltomb"
• 35 results of "Royal Tomb"

Seems to be related with this word : 왕릉

This word is present 95 times in the files, but seems to be translated differently :

• Tomb
• Royal Tomb
• Royal
• King Tomb
• King
• Wang (wang is king in chinese)
• Mausoleum
• Underground Mausoleum

What is according to you the correct way to translate it, and to make it consistent ?

Some example are here :

IMCGames can you confirm if you have published ToS on Steam Greenlight?

http://steamcommunity.com/sharedfiles/filedetails/?id=441500423

"Sabre" should be "Saber" if we are sticking with US English over UK English.

This is the new issue for the Wiki Terms in continuation of the previous one : #56

As the Wiki is not yet open to public, let us know your suggestions for terms in the wiki in the comments below. We will try to consider and have the changes applied as much as possible. 😄

The wiki provides some official translations for proper nouns in this game. I was going through some item translations and realized that some of the English translations are awkward (or not even in English).

This issue is to address those awkward translations with @imcgames for their actual intended names, so I can proceed with correcting the English translations in /blob/master/ITEM_en.tsv.

As a cautionary note: I don't speak Korean, so I don't know if these particular names were intentionally chosen for some reason. A lot of these fixes were made by looking at in-game icons and searching up the official translations for a more common name.

Here's a full list of things to be changed on the Item wiki page:

Notes:

• Some translations have alternative translations / notes in parentheses.

I just noticed that the line numbers don't match up for ITEM.tsv and ITEM_en.tsv.

I was editing 2H Spear strings and line 666 in the Korean file is Two-Handed Spear [Pierce] while that line in the EN file is 667.

I'm currently proofreading some of the existing translations in ITEM_en.tsv.

From my understand, 조악한 -> coarse; poor; inferior; crude.

The existing translations are inconsistent between "Crude" and "Mediocre", and has potential for awkwardness within context. i.e., Using a recipe to craft a "Mediocre Falchion" and receiving a "Crude Falchion" as a result.

@imcgames what is the intended meaning for 조악한 ?

Some examples of existing translations:

• 조악한 글라디우스 -> Crude Gladius
• 조악한 샴시르 -> Mediocre Shamshir
• 조악한 시미터 -> Mediocre Scimitar
• 조악한 카스카라 -> Crude Kaskara

Also, it might make sense to update the wiki with an example of 조악한 usage.

can i pull request translation english to thai ?

Recently we got some requests by people who would like to help translating the client but had no experience with GitHub so we created a little Web Tool that will allow everyone to easily change some lines. The basic idea is that everyone can suggest translations and experienced translators will check those and merge them to the repository afterwards.

More information can be found here: http://www.tosbase.com/news/142/Tree-of-Savior-Web-Translator/

We hope that our tool will help on the translation process. We also plan to connect the web tool to the offline tool we mentioned in the other issue so people would be able to add suggestions from within the game.

Here is an example image:

Best regards,
Flash

Thought I'd make a StrawPoll for the font thing, here it is:

http://strawpoll.me/4639597

ETC_20150317_008124 (line 3124)

Hello! This is Salmon.

Excuse me. Why uploaded two version ETC_20150312 (removed) & ETC_20150317 (current). What are different between them? I have a project that wanna make all players of my county can join the translation work, so I have to understand all of .TSV file what they means.

Thanks much :)

I merge both of 'Korean' (xxx.tsv) and 'English in progress' (xxx_en.tsv). All users can see two languages, then system grep (detect the same words) automatically reference terms in text can be referenced for users in a message.

And this project isn't only for people that have translating skill. Everyone can vote the others translated text they agree. I think this is very important for EACH PLAYERS can help this game grow up, not only part of players.

Why we need the crowd voting? Just like this post. Different countries, languages or folkways could make the words to express means different. So we need a good and smart way to solve it, right? :)

My project is over here.

Regards, Salmon