Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
localization [2015-01-29 17:46] – [User localization] natalia.martinezlocalization [2024-02-10 09:52] (current) – external edit 127.0.0.1
Line 61: Line 61:
 </PHP> </PHP>
 The left part is the translation key, which is used on Feng Office's source code. The right part is the translation string, which is displayed on Feng Office's interface. The localization files are loaded according to the localization preferences chosen by the user. If the user selects the 'pt_br' localization on his user preferences, then the files in the 'pt_br' folder will be loaded and so all text will be displayed in Portuguese. The left part is the translation key, which is used on Feng Office's source code. The right part is the translation string, which is displayed on Feng Office's interface. The localization files are loaded according to the localization preferences chosen by the user. If the user selects the 'pt_br' localization on his user preferences, then the files in the 'pt_br' folder will be loaded and so all text will be displayed in Portuguese.
 +
 +For on-premise:  
  
 To translate Feng Office to your own localization you could just copy the **en_us** folder, rename it to your localization's name, and translate the right part of all files in that folder, but there's an easier and safer way. Feng Office includes a translation tool that will take care of all the nifty details, and allow you to focus on just translating the text. If you were to manually translate all files you would have to be careful to use UTF-8 character encoding and respect the file format, comma positions, etc, otherwise text could be wrongly displayed or it could break the interface altogether. For example, PHP translation files can have a trailing comma on the last translation string, but Javascript files should not end with a comma, or it won't work in IE. When using Feng Office's translation tool this is handled for you. To use it browse to http://feng_root/public/tools (change **feng_root** for your installation's root, e.g., localhost/feng) of any installation and choose **Translate Feng Office**. This tool can also be used to update existing translations. To translate Feng Office to your own localization you could just copy the **en_us** folder, rename it to your localization's name, and translate the right part of all files in that folder, but there's an easier and safer way. Feng Office includes a translation tool that will take care of all the nifty details, and allow you to focus on just translating the text. If you were to manually translate all files you would have to be careful to use UTF-8 character encoding and respect the file format, comma positions, etc, otherwise text could be wrongly displayed or it could break the interface altogether. For example, PHP translation files can have a trailing comma on the last translation string, but Javascript files should not end with a comma, or it won't work in IE. When using Feng Office's translation tool this is handled for you. To use it browse to http://feng_root/public/tools (change **feng_root** for your installation's root, e.g., localhost/feng) of any installation and choose **Translate Feng Office**. This tool can also be used to update existing translations.
 +
 +For cloud clients:  
 +
 +Contact our support team at support@fengoffice.com and request a user for our web translation tool.
 +
 {{ :localization2.png | Feng Office's translation tool}} {{ :localization2.png | Feng Office's translation tool}}
  
 Once you have finished translating Feng Office you can share your translation files at the [[http://forums.opengoo.org|Feng Office forums]]. Once you have finished translating Feng Office you can share your translation files at the [[http://forums.opengoo.org|Feng Office forums]].