While I’m doing the translation in Finnish, there is few moments when I really have think how I can translate the meaning and not just the words. There is two that are giving me extra hard time and those are “From” and “To”.
From can be understood in Finnish as “Starting” or “Sender”, depending where it is used and To can be used as “Ending” or “Receiver” depending where it is used.
Is it possible to add two more definitions and tags, that we can translate the definitions properly. I believe that this might help some other translations too.
Same happened in the Dutch translation. Also Back is an example. Could be the side of the body you can’t see, but also a link to the last screen options.
Brady found a solution, but it was beyond my comprehension and started to live with “double translations”. Rug and Terug… both translated in Rug/Terug, or in your example: Start/Sender and End/Receive (in Finnish of course).
There is a WiKI page explaining what Brady intended to do. Look for Language translation instructions. With special coding for International problems…
It will require changes in the actual codebase. So, for the “to” example, there is a constant to{{range}} and to{{salutation}} in the google doc to translate different meanings of “to”.
I did find to{{range}} not the other one. But reading your message it might be needed to make changes in the software i.e. Github…
to is translated.
Now the different “to” can be made with the addition of {{salution}} and other {xxx}} or is this thinking to simple and need to do more?
My question looks like the answer is to simple, {{xxx}} will not be translated but will show in the translation-spreadsheet whenever it is included in the software…
Need to modify it in the codebase (ie. github), which then gets placed into the spreadsheet via the pipeline. Can not directly modify the constants in google docs spreadsheet or it will all break. You are correct, that all the stuff within {{}} is ignored when displayed in OpenEMR.