#English localization issues
1 messages · Page 1 of 1 (latest)
I’ll also tag @hexed pasture in here, in case they've come across anything during the French translation
(And in case you missed it, feel free to PR your French i18n to the system, looks like Andrew's ready for translation PRs. Will be a shame to lose Le Crucible's art though)
We took a lot of liberties with the translation for this type of key, because French rarely works well with English translations anyway, our sentences are sometimes twice as long, lol.
Yep, I saw it! (And got a PM!) But I think it's better to keep the translation .json files in their compendium module. 🤔 That way, we don’t have to go through a back-and-forth if there are changes, it lets us update on the fly, and the system developer doesn’t have to wait for us to make updates. Personally, I only see advantages to keeping it in the compendium module.
Actually, now that I think about it, I remember that the Russian translation module for Foundry has a bunch of translations for systems. Dunno if I should maybe be contributing to that instead.
Meh, I am more involved with the Crucible community than with the Russian FVTT community so I'll keep it in the system unless someone else with the desire to do the translation and a strong opinion on the matter comes around.
yeah, this is less about how things should be translated and more about the fact translation requires reading the text carefully, which naturally means finding inaccuracies.
a very minor nitpick but the phrase "iconic spells" is capitalized in "No unlocked Iconic Spell slots." not not in "Add iconic spells by browsing the provided Crucible system compendium pack."
so now I'm not sure if I should treat this as a proper noun or not for translation
@flat drift do you have thoughts on this?
I'd treat it as a proper noun and log the mistreatment
I think this tooltip is misleading. It's not the number of enemies engaged, it's the number of enemies that can be engaged without being flanked.
English localization issues
renamed the thread to emphesize that it's about mistakes in en.json, and differentiate it from #1497311484706029730