Translations:Crowdin Administration/18/en

If you notice a string in the FreeCAD UI that is not translated do the following:
 * 1) If you are not sure to which workbench the string belongs, first locate it in the FreeCAD source code. On Linux you can use.
 * 2) For example, if the string is  you will find this file:, and you will know that the string belongs to the FEM workbench.
 * 3) Now search for this string on Crowdin. If your language is French visit https://crowdin.com/project/freecad/fr, go to the FEM workbench, and check if it is there and translated.
 * 4) There two possibilities:
 * 5) The string is not on Crowdin because it has not been picked up by the script that gathers strings from the FreeCAD source code and packs them into  files. There can be two reasons for this:
 * 6) * The string is not properly handled by code (or  code for special cases like command names), that means there is a problem that must be solved in the source code.
 * 7) * Everything seems normal, but the gathering script has a problem with that specific string, which can happen as it has many bugs.
 * 8) The string is on Crowdin. There are several possibilities then:
 * 9) * It might be that the latest Crowdin strings have not yet been merged. You can check if that's the case by searching for the string (see above), and check if it appears in the translated files. In our example  would then be found in . This indicates that the translated string is in the FreeCAD source and everything should be fine in the next build.
 * 10) * If the string is still missing in the next build, the problem is more complex and we'll need to do some debugging:
 * 11) *# Check in the source file if the original string is handled by or.
 * 12) *# Verify that the context matches what is on Crowdin.
 * 13) *# In case of, there are several particular cases. For commands, the context must be the exact command name, the same as used in . For properties it must be . For the names of menus and toolbars it must be.