Repository navigation
Replies: 4 comments 16 replies
|
Quick update: Korean is in for 1.1! Your file covered about 420 of the app's ~550 strings, and the rest (mostly text that lives in the C# side, like the season review and race checks) I've drafted using the same terms you chose. I'm also adding German, French, Spanish and Portuguese. When 1.1's text is final, I'll send you the full Korean file plus a short list of the strings I drafted, if you're still up for checking them. One extra thing to look at then: the briefing tells players which LMU settings to change, so those labels need to match exactly what LMU shows in Korean. 감사합니다! |
|
Send the files over whenever they're ready, and I'll do my best to translate and review everything I can. Thanks! |
|
Thank you! The text is ready now. There's a 1.1 beta out with Korean built in, so you can see it in the app: Beta: https://github.com/factoryseatlmuapp/factory-seat/releases/tag/v1.1.0-beta (installs over 1.0.x, saves carry over) Everything in ko.json is your translation as you sent it, except the 143 strings I drafted myself (listed below). Those are the ones that need checking most. If you'd also like to go over the rest now that the app is bigger, that's welcome but not expected. One question: is 레이스 위켄드 what LMU's own Korean menu calls Race Weekend? The briefing tells players which menu to open, so it needs to match the game exactly. The same goes for any other LMU setting names you spot on the briefing. To test changes in the app: Settings › Language › Open folder, put your edited Also fixed for the beta: Korean text now wraps between words instead of in the middle of one. 감사합니다! The 143 strings I drafted (click to expand)
|
|
In-game, it is displayed as "레이스 위크엔드" (Race Weekend). While "레이스 위켄드" conveys the meaning just fine, I changed it to "레이스 위크엔드" for consistency with the official in-game terminology. "Factory Seat doesn't change the game. In LMU's {mode}, pick the circuit, car and settings listed below, and tick each one off." "Racing your custom team car in their colours? Turn this on. You paint the livery yourself in LMU; it counts if you race that car in at least half the rounds." "Factory Seat doesn't paint cars. You make the livery yourself in LMU; adding the brand here only brings its sponsor deals." I revised the three lines above because their meaning differed from the source text. Other than that, I only tweaked minor grammatical particles (조사). It shouldn't cause any issues during initial playtests. Once the official build is live and more players start using it, I'll gather feedback from the Korean sim racing community and follow up if further tweaks are needed. (As a side note, players seem so used to apps like ZTA that they naturally wish for automatic setup features!) Anyway, here is the updated translation file! Everything else is fine as is, but please make sure to apply the revisions to those three specific lines mentioned above.
|
|
Thank you, this is great! All of it is in: 레이스 위크엔드 everywhere, the three lines with the corrected meaning, the livery wording, and LMU's own terms for 시간 배율, 연료 사용량 and 퀄리파잉. I checked the file against the app and every string and placeholder is intact. One tiny thing I changed myself: two of my drafted lines still said "Factory Seat은" and "Factory Seat이", so I matched them to your "Factory Seat는" / "가". If that's wrong, tell me and I'll put it back. Korean ships in 1.1.0 on Tuesday 13 October, and you're credited in the release notes. Feedback from the Korean sim racing community later is very welcome, whenever it comes. And good point on ZTA! Factory Seat itself will stay hands-off with LMU's settings, but a community member has built a SimHub overlay that reads them and shows a checklist right on LMU's race setup screen, turning green when everything matches: https://github.com/Milky28/factory-seat-companion 감사합니다! |
|
This is in for 1.1. The app now loads translations from files like the one you sent, and your Korean translation is part of it, along with German, French, Spanish and Brazilian Portuguese. Plan's here: #3. When 1.1's text is final I'll send you the full Korean file and a list of the strings I drafted myself, if you'd like to check them. Thanks again! |
|
thx!! |
|
1.1.0 is out with your Korean translation and review: https://github.com/factoryseatlmuapp/factory-seat/releases/tag/v1.1.0 You're credited in the release notes and the CHANGELOG. If Korean players report anything that reads oddly, corrections are always welcome here. Thank you, this is what made 1.1 happen! 🇰🇷 |
|
1.1.1 came out today with one new string, and I translated the Korean myself. Could you check it when you have a moment? No rush at all. English: Where it shows: after a guest drive, in the list of differences the app asks you to confirm. It appears when you raced the guest team's car under a number that isn't theirs. For example: "raced #999, Akkodis ASP Team runs #78 / #87". In the file: ko.json line 497 If it reads oddly, just post the corrected line here and I'll put it in the next release. 감사합니다! |
|
Thank you again for all your hard work on the translation. I've noticed more traffic coming from Korean forums lately, and I'm sure that's down to you. 감사합니다! |
|
Hi @arch642, 1.2 is nearly ready, and it adds a lot of new text: an inbox with a race engineer's debrief, team principal and press messages, one interview question after big moments, sponsors that approach you mid-season, a "what's at stake" card before each race, and full results with a lap analysis. I've drafted the Korean for all of it (251 new lines), using the terms you chose for 1.1 (AI 강도, 평판, 포디움, 합니다체). The table below has every new line with its English. Would you have time to look it over like you did for 1.1? Anything that sounds unnatural or reads like a translation, just mark it here and I'll fix it before the release. No rush, and thank you again. Korean players keep finding the app through Naver and dcinside, and your translation is a big part of why. The 251 new lines (English and draft Korean)
|
|
I noticed a few things that stood out and fixed them. Thanks for the update! The two main Korean sim racing communities are DC Inside and: |
|
Thank you! All 14 of your fixes are in for 1.2. They read much better. One follow-up: you changed two lines from AI 강도 to AI 난이도, but five other lines still say AI 강도 (for example "AI 강도를 한 단계 올리면…" and "AI 강도는 그대로 두세요"). I'd like to use one term everywhere. Since those lines tell players which setting to change, they should match LMU's own Korean menu. What does LMU call the "AI Strength" slider in Korean? If it's 난이도, I'll switch all of them. If LMU says something else, I'll use that. And yes, that was me on dcinside 😄 Thanks for the Naver Cafe link too! |
|
I'm not sure where 'AI Strength' is mentioned in the LMU, but if it's under the difficulty settings as 'difficulty' or 'opponent difficulty': difficulty = '난이도' opponent difficulty = '상대 난이도' If 'strength' is actually mentioned in game in LMU AI 'strength' = AI '강도' 
|
|
LMU's built in translation isn't perfect either with each patch, some English text suddenly gets translated into Korean, and mistranslations keep getting fixed. So I think it's totally fine to keep things a bit loose, especially for maintenance. Korean players are pretty used to localizations differing a bit from the original English anyway, so no one really complains about it. |
|
Makes sense, thank you! I'll keep it simple and use AI 난이도 everywhere, same as your fixes. And it's great to hear Korean players will be happy just to have it in Korean 😄 Thanks again for all the help with this. |
Uh oh!
There was an error while loading. Please reload this page.
First of all, thank you for developing Factory Seat! I really enjoy using it.
I'd like to suggest adding multi-language support (localization/i18n) for non-English users.
I understand that maintaining multiple language translations directly in the official build can be a lot of maintenance work for an individual developer. Therefore, rather than bundling every translation yourself, would it be possible to introduce a simple system where the app loads translations from an external file (such as a .json or .csv file)?
If users can simply place a translated file (e.g., mapping English keys/strings to their local language) into a directory or select it in the Settings, the community can easily create and maintain their own localizations without requiring constant updates to the core build.
Additionally, as someone not deeply familiar with programming, I've heard that non-Latin scripts (like Korean, Japanese, and Chinese) often require proper Unicode (UTF-8) handling and appropriate fallback fonts to render cleanly without text overflow or glyph issues. It would be great if this could be taken into consideration as well.
Thank you for your time and consideration!
All reactions