first of all, :derisive: for your time explaining this all :)
Secondly, am I save to translate both "invalid" and "broken" "nodes" and points as "broken point" (according to the MSTS AE use)? Also, in the German MSTS AE, broken points are actually called "disconnected points" - is that more accurate to what the term actually describes?
Dangling in this case means "not reconnected", right?
As for the localization problems shown in the pictures above, I fear I was not quite clear on them: Most of the strings already are contained in the translation files and (at least in German) are already translated. However, instead of the proper translation, the source string is shown (all above pictures were taken with TrackViewer set to German).
Yes, changing translatable strings in the code will change other people´s translations, in ways depending on the type of change. Fortunately, the *.POT / *.PO system, used with POedit is very flexible in this regard, so that adverse effects are kept to a minimum.
- If a string is removed from the source, it will also be removed from the translation files, if the same translation is not use in another place in the code.
- If a string is changed in the source, but not removed, the translation will be marked as "fuzzy", because it might no longer reflect the meaning of the original string. However, a string that has already had a complete, non-fuzzy translation will always be considered "translated" by launchpad´s translation statistics. The string will only need another look by the translator to check if the translation is still correct (in the last such cases, this was always true, because these changes only dealt with typos).
- If a string is added in the source, it will also be added to the translations as a new, untranslated entry.
Cheers, Markus