In Russian there is no good translation of "Go To" which will mean "Go To" for train, road vehicle, aircraft and ship at the same time. The current translation is quite irregular. And in English it may be replaced with "Fly to", "Sail to", "Drive to" for non-train transport types too to be more exact.
Doing so means duplicating a lot of strings because it arguably isn't just STR_ORDER_GO_TO, but also STR_ORDER_GO_NON_STOP_TO, STR_ORDER_GO_VIA, STR_ORDER_GO_NON_STOP_VIA, STR_ORDERS_GO_TO_NEAREST_DEPOT, STR_ORDERS_GO_TO_BUTTON (after all, the button should say the same, right?), STR_ORDERS_GO_TO_WAYPOINT, STR_ORDERS_GO_NON_STOP_TO_WAYPOINT. Then probably the STR_ORDER_SERVICE_AT and STR_ORDER_SERVICE_NON_STOP_AT strings as well.
You make it seem like there is no translation for "Go to Paris" if you do not know the means of transportation. That's something I can't quite believe.
I'm quite hesistant to adding 30 strings that are a copy of some other string. It only adds to the translator's burden.
People always know the means of transportation when they refer to transport, not a person (you can say "Go to Paris" about the person in Russian). There are some translations, but none of them are applied both good for land, sea and air ways of transportation. Just see a number of translations for a word "go" http://lingvo.yandex.ru/go/с%20английского/ . (it BTW doesn't include those which I think the most suitable) Adding those strings could also make an English and other variants of game richer as well.
Persuaded to reopen by Perk and Eddi. I don't see splitting translations as bad, it's copy-paste for translators in some languages, and provides a better result in other languages where the context changes the required word(s).
Fully agree with Eddit and Perk, and disagree with Rubidium (sorry). We did often a few things so translations fit. And I agree, 30 copies is annoying .. but we either support other languages or we don't :D (we also have this insane system for numbers and their plural form).
What I do wonder, if this can be done smart with sub-strings or something? Or some other clever solution to make it a bit easier?
Outside of making 3x, 4x, or 5x the number of every "Go (non-stop) to/via" string, which will be pointless in most translations, perhaps a new string formatting feature for optional case-parameterised strings would be relevant.
This issue has been automatically marked as stale because it has not had any activity in the last two months.
If you believe the issue is still relevant, please test on the latest nightly and report back.
It will be closed if no further activity occurs within 7 days.
Thank you for your contributions.