kc3kai / kc3-translations Goto Github PK

@freezebear @KC3Kai/translators

Since I just noticed that there is TL error on the Rank for ID language, I think it'll be a good opportunity to check other languages as well for standardization.

As we know, in the english translations:

• 少将 translated into "Rear-Admiral", a two-starred Officer.
• 中将 translated into "Vice-Admiral", a three-starred Officer.
• 大将 translated into "Admiral", a four-starred Officer.
• 元帥 translated into "Marshal Admiral", a five-starred Officer or other honorary title above the 'Admiral'.

In ID TL, there is error for the 少将, which then translated into "Laksamana Pertama", which is one-starred Officer here. It should be "Laksamana Muda", the title for two-starred Officer.

For other language, please make sure that your translation refers to the correct star's titles.

Can we do something about it?
[Summer 雲 Kai]
image

The API error notice keeps popping up every time when there is an action in game, indicating api_port/port error. I'm not sure about this problem since I always play through DMM webpage mode.

Thanks!

Terminologies Added

• term_name - english_base
• term_name - english_base
• term_name - english_base

Checklist

@KC3Kai/translators, tick on your language once you're done and you have the updates in master branch.

• en English
• de Deutsch
• nl Dutch
• es Español
• fr Français
• id Indonesian
• it Italiano
• jp 日本語
• kr 한국어
• pt Português
• ru Русский
• [*] scn 简体中文
• tcn 繁體中文
• th ภาษาไทย
• vi Tiếng Việt

Terminologies Added

5 arrays in equiptype.json.
5 categories stand for: major category, minor category, master category, icon ID, aircraft image ID, which 'master category' has official Japanese texts inside master data slotitem_equiptype object, and icon & aircraft IDs are not needed to be translated indeed.

Sample texts could be found in EN / JP / SCN folder, low priority to translate 3 categories as not used much for now. currently only used in Strategory Room Equipment Library, could test them there. May be used in future for the category names of yet another equipment list page.

btw, some IDs are not used (skipped) by KC official devs, they are marked as ? for now as placeholders, donot remove them from array.

Checklist

@KC3Kai/translators, tick on your language once you're done and you have the updates in master branch.

• en English
• de Deutsch
• nl Dutch
• es Español
• fr Français
• id Indonesian
• it Italiano
• jp 日本語
• kr 한국어
• pt Português
• ru Русский
• scn 简体中文
• tcn 繁體中文
• th ภาษาไทย
• vi Tiếng Việt
• ua Українська

ETA: EVENT

er... probably not going to finish the new lines in a timely manner, if I finish them at all

• Post-maintenance verification of lines (if ticked, it's ready for a release)
• Finish adding new line translations

There are two sets of different seasonal lines for the end of the year:

• End of year cleanup (expected December 26)
• New Year's (released last year on January 1)

So there's a massive set of lines and then a few days later, another massive set of lines.

There are over 200 lines from last year to work through, so this is the largest scale seasonal line job for the entire year. I don't really expect this to work out very well, but whatever.

Tasks

• End of Year lines: Add last year's lines ahead of time
• Post-maintenance verification of End of Year lines
  (Adding of new End of Year lines in a timely manner won't happen.)
• New Year's lines: Add last year's lines ahead of time
• Post-maintenance verification of New Year's lines
• Finish adding new line translations

copy/paste-

My process for entering seasonal lines is as follows:

• Try to have last year's lines entered before the maintenance. I refer to both the English wiki and wikia for their translated seasonal lines from last year, though I tend to edit them heavily as I add them to kc3.
• Following the maintenance is the verification phase. I activate last year's seasonal lines and go through the ships to verify whether there are new lines, misplaced lines, etc. If there's a new line, I add an empty line to prevent the wrong text from appearing. Once this is complete, the subtitles are at least in a state where people won't say "this line seems wrong! Please fix!" I try to have this done as close to the end of the maintenance as possible.
• The add new lines phase. I typically wait for the wikia or wiki to translate any new lines, so this can take any amount of time or may never even be completed while the seasonal lines in question are active. At the very least, I probably won't ever solo translate a line without the Japanese text available, if I solo translate at all.

Dear KC3Kai development team,

I am a maintenance team member for the poi-plugin-subtitle, a subtitle plugin of the KanColle browser poi. Our source of the English translation has not been updated for a while, and we are desperate for an alternative. Could you please permit us to use the English translation used by kc3-translation? It would also be helpful if you could tell us the source of your English translation. If it is from en.kancollewiki.net or other organizations, we will make sure to ask them for permission as well.

Thank you very much!

Sincerely,
TrickLin

I assume this is alright as an issue.

There were a surprisingly large number of new saury seasonal lines added in the most recent update. I'll be working to get the [EN] lines done as soon as possible like always.

So basically, "this exists and I'm working on it". @dragonjet

Usually there aren't other languages working on these with the current implementation, and there's a lot of lines including fall/autumn/okto/halloween right now, so I dropped the checklist.

A new type of seasonal line. Not very many ships have them.

Tasks

• Post-maintenance verification of lines
• Finish adding new line translations

I'm going to document (iow: spam incoherently about) some things regarding the [EN] translations I had worked on, as I'd hate to see all the work I put in go to waste. This is TL;DR and I don't even care if it's ignored. Do whatever seems right. Good luck!

First of all, in the dev version of kc3kai, if you edit anything, save and try refreshing the ship library in the strategy room. If it never loads, there is an error. Changes to the quotes.json can be tested either in the ship library or the dev-only: quotes sections in the strategy room.

Second, the framework.

All ships have a remodel hierarchy where they pull their subtitles from.

• If a non-Kai ship has a poke(1) line and its Kai form also has a poke(1) line, then the Kai form's subtitles will naturally display its Kai form's poke(1) subtitles.
• However, if a non-Kai ship has a poke(1) line, and its Kai form DOES NOT have a poke(1) line assigned, the subtitles are smart enough to show the non-Kai's poke(1) line for the Kai form.* From a practicality point of view, this is excellent because you don't have to update non-Kai/Kai/Kai Ni/Kai Ni ABCD every time you want to change a ship's translation.
• There are two seasonal line subtitle IDs supported currently. 6547 is for poke(1) seasonal lines and 1471 is for poke(2) seasonal lines. These will override the ships' respective poke(1) and (2)s simply by adding them to the ships' unremodeled forms. It's therefore not necessary to add duplicate seasonal lines to their remodeled forms, so this is a convenience.
• If desired or if it's more convenient from a scripting point of view to just use the default poke(1) or poke(2) IDs for seasonal lines, then this will work, too. The only issue is that you have to worry about a ship's remodeled lines overwriting their non-kai seasonal lines.
• The game occasionally has other seasonal line types such as poke(3) or docking(2), but there is no special code for these in kc3kai. Since I wasn't running a script to add the lines, I would manually disable the respective default lines (literally by calling them, for example, "Default 2" instead of "2" in order to assign them to unused IDs).

*Due to the way subtitles are handled in kc3kai, this is also a major issue for non-English languages which do not have their own subtitle translations. The remodeled forms will not show any subtitles in those languages! There are two possibilities that Javran had suggested to counter this:

1. Have two separate quotes.json files. The first has EN subtitles as they are in the current master as of this writing. This file is not active, but it's the one that the EN translator/editor would be maintaining. The second quotes.json would be active. The second differs from the first in that a script is run to fill every ship with lines from their earlier remodels when any given remodeled line is not present.
2. (preferred) Fix the code on the non-TL side of things to not have the issue. Both issue 1861 and 1806 were made on this subject in the main kc3kai repo.

Third, an advisory based on past experience with scraping the wiki(a) for quotes. The wikis don't necessarily have the correct layout for similar lines. The poke(1) listed on the wikia may in fact be the poke(2) in-game. This has been an issue for all three poke lines, equip lines, attack/yasen lines and damaged lines. When scraping, it will probably be important to check if these match up properly in-game.

Lastly, it's probably possible to use the same ID formatting as other languages. See the JP, SCN or KR quotes as an example. I never used them because I didn't need to, but as far as I know, implementing them probably won't introduce any issues that don't already exist for EN. It would certainly make them easier to make sense of.

Terminologies Added

• GameAPIPlayFlashNoticeTitle
• GameAPIPlayFlashNoticeDesc
• GameAPIPlayFlashNoticeStep1
• GameAPIPlayFlashNoticeStep2
• GameAPIPlayFlashNoticeStep3
• GameAPIPlayFlashNoticeStep4
• APIErrorNoticeTitle
• APIErrorNoticeMessage
• Bomb201Title
• Bomb201Message (correction You have received an error 201 from the game API. You could be still logged in on another game client, or this may have something to do with macro-detection. You may ignore this notice but please play in moderation.)
• NewVerViewChangelogGithub
• NewVerViewWikiGithub
• SettingsStrategyRoom
• SettingsLevellingDifference(unused, you can remove this)
• SettingsStrategyTheme
• SettingsAPIRecorder
• MenuScheduledSoon ("Soon..." to "unscheduled")

Checklist

@KC3Kai/translators, tick on your language once you're done and you have the updates in master branch.

• en English
• de Deutsch
• nl Dutch
• es Español
• fr Français
• id Indonesian
• it Italiano
• jp 日本語
• kr 한국어
• pt Português
• ru Русский
• scn 简体中文
• tcn 繁體中文
• th ภาษาไทย
• vi Tiếng Việt

We can now create issues in the translation repository.

The main use is when new terminologies are added to the application for a new feature or enhancement, this should track progress for its translation across different languages.

The secondary but also important use it that it will notify translators since they are tagged in the issue / and-or if they are "watching" the repository via "watch" in the button at the top.

When creating a new issue, you can see that it will be prefilled with a template - which automatically tags @KC3Kai/translators so those who are not watching will still be notified as long as they're part of the TL team.

Anyone can add issues as long as you have write access if im not mistaken - and I mean it to say not only english contributors can create. For example, someone from non-EN language can add an issue for a translation of the subtitles of a new shipgirl. Or if the specific language is ahead in translating new quests, and no one has created issue for it yet.

Just make sure to group similar terms together, e.g. same feature in 1 issue, same shipgirl for quotes, same maintenance for new quests, etc.

Thanks all~!

@sinsinpub

Terminologies Added

• term_name - english_base
• term_name - english_base
• term_name - english_base

Checklist

@KC3Kai/translators, tick on your language once you're done and you have the updates in master branch.

• en English
• de Deutsch
• nl Dutch
• es Español
• fr Français
• id Indonesian
• it Italiano
• jp 日本語
• kr 한국어
• pt Português
• ru Русский
• scn 简体中文
• tcn 繁體中文
• th ภาษาไทย
• vi Tiếng Việt

关于kc3改自动调用季节性语音字幕的系统，我有一些想法与建议：

我发现现有的系统存在两个问题：
1、官方有时会将旧季节语音更换语音位置重复进行使用，（比如2@spring条目下一年可能就会变为3@spring，这时调用就会失效）需要编辑各语言的quotes文件。
2、以时长属性进行匹配语音调目，有唯一性不高的缺点。若按照我的解决思路，需要以唯一性更高的属性进行匹配。

解决思路：
减少语音字幕调用分类，直接按舰船ID作为一级目录，通过语音属性索引来匹配语音字幕条目，因为一条语音总是对应一条字幕的，这样以后即使存在语音编号移位，也会自动匹配到正确的字幕。不再需要任何调整。
唯一性不高的问题，我能想到的是以语音文件时长及大小两者作为合并条件进行匹配，如果你们能够找到更好的唯一属性就更好了。

同时，现有的各语言的quotes文件存在部分历史条目混乱的问题，若整合调整完毕，也可以对各语言的字幕数据库整理归档提供帮助

@sinsinpub

stype.json
PF->DE

You do not have to do this. However, it's difficult to tell who is inactive and who is active. If you do not want to use DE, please respond. After ~1 week, I will change the other files to DE if there is no response.

Checklist

@KC3Kai/translators, tick on your language once you're done and you have the updates in master branch.

• en English
• de Deutsch
• nl Dutch
• es Español
• id Indonesian
• it Italiano
• pt Português
• ru Русский
• scn 简体中文
• th ภาษาไทย
• vi Tiếng Việt

from here:
https://www.reddit.com/r/kancolle/comments/6cgaxl/meta_regarding_the_results_of_the_kaiboukan_poll/

Hi everyone,

With regards to the poll on the abbreviation to use for the newly released IJN Kaiboukan, the voting result is as follow:

DE: 386 votes Something else: 388

The results were debated internally on how we should interpret this and move forward. We initially believed that we would have a clear winner with a decent margin but on hindsight, we did not expect this result - a virtual tie.

2 proposals were made: the first was to run a second poll but to include DE (DE, PF, KB, EE). It was obviously going to be a formality because any sensible person can draw the conclusion with the result of the current poll. The other proposal was to declare DE the winner in view that despite DE losing by 2 votes, it is technically the majority, the winner, because the other 388 votes from "something else" is a combination of options that would have no chance to win against DE when pitted against it one-on-one.

The group are in view that the latter should be the answer and the former pointless, and that we have heard from you that you guys wanted to get this over and done. The exception is Tsubakura, representing Wikia, does not want to accept this resolution and have declared that Wikia will proceed with further polls on this matter. As such, any further discussions on Wikia shall be deemed as the sole decision of Wikia and in no way r/kancolle, our discord community, and other communities/platforms are in support of it, unless otherwise stated by themselves or their position changes.

With this, we would like to notify you guys that we have decided that we would accept DE as the majority vote and this debate closed.

Let us all return to our boatgirls and enjoy the game, as we should.

Cheers.

These will go live after the maintenance on January 25th. It's really nice to be able to have almost all of the lines done ahead of time.

They aren't all ritual phrases, hurray

• Add last year's lines ahead of time
• Post-maintenance verification of lines (if ticked, it's ready for a release)
• Finish adding new line translations

In en/servers.json/etc., for Kure it should be 203.104.209.87 (http://203.104.209.7/gadget/js/kcs_const.js).

Terminologies Added

• InstalledTitle - "KC3改 ready for service!"
• InstallText - "Thank you for installing KC3改! We hope that these tools can help you play KanColle and make it a better experience! Do not hesitate to approach us if you need help. Check the about page to know where we can be reached."
• UpdatedTitle - "KC3改 has been updated!"
• UpdateText - "If you are currently playing KanColle, some features in the viewer might be bugged. Please close the game tab and restart the game. If you are in the middle of a sortie, please finish it first, but know what some features such as info and prediction might not work as expected before restarting."

Reference

5de7357

Checklist

@KC3Kai/translators, tick on your language once you're done and you have the updates in master branch.

• en English
• de Deutsch
• nl Dutch
• es Español
• fr Français
• id Indonesian
• it Italiano
• jp 日本語
• kr 한국어
• pt Português
• ru Русский
• scn 简体中文
• tcn 繁體中文
• th ภาษาไทย
• vi Tiếng Việt

There's a bugged(?) quest where old quest descriptions may cause players to waste their time and get angry about it. In fact, that's already happened. Anyway, you may want to adjust your quest description for Bm4 if you haven't already. It's your choice.

Copy/paste what @Crazyteitoku wrote:

Due to the amount of people reporting Warspite not being eligible for Bm4 completion as noted:

• http://wikiwiki.jp/kancolle/?%C7%A4%CC%B3#Routine-M
• http://kancolle.wikia.com/wiki/Warspite

"259": {
        "code": "Bm4",
        "name": "Monthly Deploy a Battleship Squadron",
        "desc": "Sortie 3 BB (Yamato-class, Nagato-class, Ise-class or Fusou-class ONLY) + 1 CL + 2 additional ships to [W5-1]. S-Rank the boss node."
    },

Checklist

@KC3Kai/translators, tick on your language once you're done and you have the updates in master branch.

• en English
• de Deutsch
• nl Dutch
• es Español
• fr Français
• id Indonesian
• it Italiano
• jp 日本語
• kr 한국어
• pt Português
• ru Русский
• scn 简体中文
• tcn 繁體中文
• th ภาษาไทย
• vi Tiếng Việt

Let's see if I can force myself to update/communicate properly what the hell my progress on this is.

Going by 2014 and 2015, Christmas seasonal lines should go up following the next maintenance on the 9th. Last year there were almost 140 lines.

My process for entering seasonal lines is as follows:

• Try to have the 2015 lines entered before the maintenance. I refer to both the English wiki and wikia for their translated seasonal lines from last year, though I tend to edit them heavily as I add them to kc3.
• Following the maintenance is the verification phase. I activate last year's seasonal lines and go through the ships to verify whether there are new lines, misplaced lines, etc. If there's a new line, I add an empty line to prevent the wrong text from appearing. Once this is complete, the subtitles are at least in a state where people won't say "this line seems wrong! Please fix!" I try to have this done as close to the end of the maintenance as possible.
• The add new lines phase. I typically wait for the wikia or wiki to translate any new lines, so this can take any amount of time or may never even be completed while the seasonal lines in question are active. At the very least, I probably won't ever solo translate a line without the Japanese text available, if I solo translate at all.

Checklist

• Add last year's lines ahead of time (there is no reason to upload it at this stage, though)
• Post-maintenance verification of lines
• Finish adding new line translations
• Dec. 22 Post-maintenance verification of lines
• Finish adding new line translations

Hi, I have a question about how seasonal keys work in quotes.json.

For example, now is Setsubun season. If a ship has "2@Setsubun" and "2@Setsubun2024", which quote will be loaded?
And if a ship only has "2@Setsubun2016", will this be loaded?
Should I better add the year number or not?

Another question is: How does the program decide which quotes are for the current season? As an example, in the season of Saury, kcwiki.cn shows many ships also have special voices for Fall or LateFall.

Hi all,

I am here to officially state that I will be suspending support of KR terms update altogether.
I have left the game at the time of Winter Event 2017, and foresee that I will not be returning to it any time soon, if ever.
With that states, I am willing to pass the rein of the core work to another capable translator to spearhead the project.
I will continue to update new quote lines that come in for new girls.
However, KR will NOT get any support regarding seasonal lines, as I am extremely against the way that the seasonal lines are being implemented for EN right now. (Purely technical perspective. Kudos for nonsensed for having it working despite such manual labor)

See screenshot at PR KC3Kai/KC3Kai#1638

Terminologies Added

• BattleAirDefend - I use Air Base in English for two reasons: Air Defend looks too long although its length is the same with Air Battle; Air Base could indicate this activity is not normal ships battle, and could be joined with the next line's Losses.
• BattleAirDefendYes - Interceptors: {0}. This row shows which base(s) of Interceptor Squadrons it sent on enemy raid, not the amount of planes or squardons. (planes count are shown at usual place)
  Take care of its length, long text will be hidden.
• BattleAirDefendNo - No Interceptor
• BattleAirBaseLoss - Losses, means the damage and losses result of air base. As there is word 'losses' already at left column, I remove it from airraiddamage in battle.json. BTW, u can consider the LBAS as Land-Base Aircraft Squadron 😂

battle.json added

	"airraiddamage" : [
		"",
		"Resources",
		"Resources & LBAS",
		"LBAS",
		"No damage"
	]

Checklist

@KC3Kai/translators, tick on your language once you're done and you have the updates in master branch.

• en English
• de Deutsch
• nl Dutch
• es Español
• fr Français
• id Indonesian
• it Italiano
• jp 日本語
• kr 한국어
• pt Português
• ru Русский
• scn 简体中文
• tcn 繁體中文
• th ภาษาไทย
• vi Tiếng Việt

The code of the 348 quest on KR should be C53

See

and