@Pewpew!, and thank you for a second and all together more important reason, Good Sir. :bow:
Here's to a a Healthier and ever more Vibrant BATTLETECH Community. : )
Here's to a a Healthier and ever more Vibrant BATTLETECH Community. : )
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
- Status
Hello dear developers! Thank you for your detailed answer, we have been waiting for specific actions in this topic for a long time and at least now we know what the problem was and we have the release date of beta localization. I have questions about this.
1. When the beta version of localization comes out, do we have to manually download it as beta patches?
2. Error correction will be carried out by yourself or we in this thread can write wishes?
3. Names battlemechs and weapons will be in the original language, that is, in English or also translated?
4. How long will it take to finalize the beta version of localization? By December time? Thanks in advance!
1. When the beta version of localization comes out, do we have to manually download it as beta patches?
2. Error correction will be carried out by yourself or we in this thread can write wishes?
3. Names battlemechs and weapons will be in the original language, that is, in English or also translated?
4. How long will it take to finalize the beta version of localization? By December time? Thanks in advance!
As translator for another kickstarter game, I deeply feel HBS, PDX and translators' pain.
Localization is one of those things that:
1) must be considered when you create the first source file and implemented perfectly from the very start,
2) cannot be done well the first time, so no matter how much effort you put in 1), you'll hit the dreaded "refactor most strings" sooner rather than later.
Sort of catch-22.
Thanks for the update, keep your discipline high (having devs conform to a string style guide is akin to herding cats - been there, done that), and learn from your experience.
Good things come to those who wait.
Localization is one of those things that:
1) must be considered when you create the first source file and implemented perfectly from the very start,
2) cannot be done well the first time, so no matter how much effort you put in 1), you'll hit the dreaded "refactor most strings" sooner rather than later.
Sort of catch-22.
Thanks for the update, keep your discipline high (having devs conform to a string style guide is akin to herding cats - been there, done that), and learn from your experience.
Good things come to those who wait.
As a professional programmer, there's only one thing I dread more than localisation, and that is the absolute horror that is properly programming for time zones.
Yes, we will give download and beta branch location instructions as we have for every beta update so far. Exactly the same process.
Both - we will continue to bug fix, error correct, and update as appropriate. In the beta update thread, you are welcome to submit requests for changes or error corrections that you see.
We will follow what we have seen as the historical usage trend in other BT games and books that have been translated, which is that proper names in the universe remain in English.
Very difficult to say right now, including taking into account that it's possible all languages may not go to beta or "finalize" at the same time. I put finalize in quotes because there will be ongoing translation work. When we release core game translations in relation to Flashpoint translation, for example, is still under discussion.
There were german names for some 'Mechs (and other vehicles) in the localized books. The oldschool 50+ yo members of my MWO unit still call 'Mechs with the german name (which can be confusing at times but is also kinda cool). Many germans that read "Endscheidung am Thunder Rift" probably remember the "Dunkelfalke" (Shadow Hawk) and the "Marodeur" (Marauder).
That said, I think games like MW4 had english names and they should be more familiar for younger players so that's ok too. Also some translations are quite janky. Like the Axman - the signature 'Mech of the upcoming Flashpoint expansion - which is called "Kriegsbeil" (lit. Waraxe) which sounds wrong for a giant robot - even for germans ^^.
Here's a list (which someone created for old and confused german MWO players
):https://mwomercs.com/forums/topic/7415-deutsche-mech-bezeichnungen-german-mech-names-is-clan/
Last edited:
Yeah. 4 Names for Clan Mechs was just bad…
English IS / Clan - German IS / Clan. "So, what are we using today?"
MadCat, Timberwolf, Katamaran or Waldwolf?
English IS / Clan - German IS / Clan. "So, what are we using today?"
MadCat, Timberwolf, Katamaran or Waldwolf?
Minor correction: It's the Hatchetman (German name "Tomahawk") that is the signature 'Mech for Flashpoint, not Axman. The Hatchetman is a 45-ton medium introduced in 3023, the Axman is a 65-ton heavy that isn't introduced until 3048 (which means it is out of timeline for this game).
Indeed. German Translators back at the time had a habit of translating absolutely everythign including names. Sometimes this works very well, but the Battletech universe has IMHO suffered from it. Because everyting that has been given a "foreign" flavour in the original has lost that flavour in the process.There were german names for some 'Mechs (and other vehicles) in the localized books. The oldschool 50+ yo members of my MWO unit still call 'Mechs with the german name (which can be confusing at times but is also kinda cool). Many germans that read "Endscheidung am Thunder Rift" probably remember the "Dunkelfalke" (Shadow Hawk) and the "Marodeur" (Marauder).
That said, I think games like MW4 had english names and they should be more familiar for younger players so that's ok too. Also some translations are quite janky. Like the Axman - the signature 'Mech of the upcoming Flashpoint expansion - which is called "Kriegsbeil" (lit. Waraxe) which sounds wrong for a giant robot - even for germans ^^.
Here's a list (which someone created for old and confused german MWO players
https://mwomercs.com/forums/topic/7415-deutsche-mech-bezeichnungen-german-mech-names-is-clan/
"A notable change implemented by Ulisses is that the names of BattleMechs, Aerospace Fighters and other combat units are not translated into German anymore. The original English designations are now used across the board even where German translations have been established for a long time (for example, the HBK-4G Hunchback is now referred by this designation in Ulisses' German edition of the boxed set, whereas it was previously referred to as QSM-4G Quasimodo in Germany ever since FanPro published the German edition of CityTech and the Hardware-Handbuch: 3025 in 1990)."
- sarna.net, Ulisses Medien & Spiel Distribution GmbH
Ulisses Spiele holds the license to produce the German line of BattleTech since 2011.
- sarna.net, Ulisses Medien & Spiel Distribution GmbH
Ulisses Spiele holds the license to produce the German line of BattleTech since 2011.
I quite like that Clan OmniMechs in BattleTech (and, hopefully in the fullness of time, BATTLETECH too) have both a Clan Designation as well as an Inner Sphere Designation.
Such dual-naming has happened in conflicts throughout history, as one side does not necessarily already know the other’s weapon designation of newly appearing Machines of War.
And this is quite authentically the case in the BattleTech universe and franchise during the CLAN INVASION.
Such dual-naming has happened in conflicts throughout history, as one side does not necessarily already know the other’s weapon designation of newly appearing Machines of War.
And this is quite authentically the case in the BattleTech universe and franchise during the CLAN INVASION.
Thank you very much for the answer! I hope in the Russian localization you leave the original names of mechs, weapons, equipment. Description can be translated, and the names leave as is. These are the wishes of our community. Even if we take as the Armada publishing translated books we have, for example, was a translation: Shadow Hawk translated as Eagle (Беркут). But in the books it was still tolerable, but in games often break the language while you read. Translated literally, Hunchback the Горбун.
Last edited:
With all due respect to your honest explanation and I am British so this is not a problem for me, I have had a translation company and have personally or with the help of a few colleagues translated large complex books, technical manuals and other complex materials which are fair greater in terms of complexity or size than all the text in Battletech to various European languages. I would be rather miffed if were German as I know that while the great majority of them understand English up to an almost Scandinavian level, they clearly love Battletech and I'd imagine as such a lot of them were Backers. Anyway as one professional to another if your translation company claims there was a bug in their translation software they are talking rubbish, TRADOS is so simple a child of 5 could use it, bugs or not. Keep up the good work.
As I understood the OP, the bug was in HBS' code, not in the translation program - as in, the HBS code that parsed the source code for text strings to translate missed about a third of all text strings due to how those strings were constructed/tagged.
Agreed. No doubt computer-assisted translation software suites like SDL Trados Studio are as powerful as they are nuanced and accurate...
...but there still must be a complete data-harvest of all elements requiring translation. Without that, and that looks to be the case here, such programs as Trados can only accomplish so much, at least until a proper data-harvest is available.
@Shrike - to confirm what others have said and understood to be the case, the issues have been on the HBS side in the collection of strings within the game, not on the translation company's end. Our translators have been and continue to be fine and professional.
Eh. Timezones aren't that bad. I spent 7 years working on software where we had to get it right because it was relevant user facing info.
This is definitely a virtue of HBS. They don't BS us about how things are going.
Last edited:
@HBS_Comanche
Is it your first developed game with localisation? If not, then i don't understand how experienced developers can miss (or not tested) the things they promised when raised funds.
Not blame you, simple don't understand it.
Is it your first developed game with localisation? If not, then i don't understand how experienced developers can miss (or not tested) the things they promised when raised funds.
Not blame you, simple don't understand it.
Last edited:
They have not missed what is promised. The time frame for the release of localized versions has always been an estimate. The localizations are still coming (currently estimated to be mid-late October), but they are taking longer because of an unfortunate issue on HBS's end in how the informarion was collected for the translators.
Again, estimates are not promises.
- Status