An Idea for better Translation-Support
In my opinion, even if you can translate individual texts and exchange ideas, FG has a small design flaw. The hard link to coding and description, and the use of terms in coding. I was thinking about how to make the translation easier with as few changes to the software as possible, as well as existing rulesets, modules and extensions. Mixing translated and untranslated content would probably also be possible.
Two approaches to split internal and external representation of an Element:
1. Give all Elements an optional link to a Translated version. If the link exists, use if for displaying. The internal (english) need no additional changes (only the link) and is used for Coding.
2. Use the english fields as internal, and allow an optional external field as external representation (e.g. with specified additional suffix or prefix). For displaying use the optional field, if it exists.