I very often switch between English and German and realized that some translation items do not work - user defined fields and view scheme names. So those names make a rather ugly appearance (What about a field "Entstehungsjahr" in English?).
This is due to the fact that they are not part of the official translation file as they are provided by the user. Of course I could add them to the translation file (can I?), but then each time a new translation file is being deployed, they will overridden.
My suggestion would be to have an include option in the translation file to include a separate user defined translation file like a statement such as: #include mytranslation.txt. The file would be in the same folder as language.txt. Or even simpler: If there is a custom.txt in the same folder, it would also be read. This could include the possibility to override some translations of the official file one would like to change.