Differences

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

--- en:entwickler:how_to_make_your_plugin_translatable [2015/12/11 22:05] – Use language files within your plugin fasse
+++ en:entwickler:how_to_make_your_plugin_translatable [2019/08/01 08:29] (current) – [Use language files within your plugin] fasse
@@ Line 2: / Line 2: @@
 ==== Create an xml file with your strings ====
-Admidio uses for translations the [[http://developer.android.com/guide/topics/resources/string-resource.html|Android string resource]]. This is a very compact xml format that should contain every string you use in your plugin.
+Admidio uses for translations the [[https://developer.android.com/guide/topics/resources/string-resource.html|Android string resource]]. This is a very compact xml format that should contain every string you use in your plugin.
 The format looks like this: <code xml><?xml version="1.0" encoding="UTF-8"?>
@@ Line 27: / Line 27: @@
 Also in Plugins own language files can be integrated and accessed to existing Admidio language files. Access to the Admidio language files is done relatively easily over the already used syntax in Admidio itself.
-<code php>$gL10n-> get ('SYS_ALL')</code>\\
+<code php>$gL10n->get('SYS_ALL')</code>\\
-If someone wants to use new unused texts in the plugin, so it must be created an own language file for the plugin. For this, a folder is created in the plugin folder **languages**, where then a newly language file is to be created ,example **de.xml**. The structure of this language file must match from the section **XML language file**. This new folder will be made known via the following call at the beginning of the plugin: <code php> $gL10n-> addLanguagePath (PLUGIN_PATH '/'.$ plugin_folder.'/Languages'.); </code> Now, using the familiar syntax texts from these language files of plugins are accessible. There is no special adaptation necessary. <code php> $ gL10n-> get('PLG_LOGIN_ACTIVE_SINCE') </code>
+If someone wants to use new unused texts in the plugin, so it must be created an own language file for the plugin. For this, a folder is created in the plugin folder **languages**, where then a newly language file is to be created ,example **de.xml**. The structure of this language file must match from the section **XML language file**. This new folder will be automatically loaded if you open Admidio in a new browser session. Now, using the familiar syntax texts from these language files of plugins are accessible. There is no special adaptation necessary. <code php>$gL10n->get('PLG_MY_PLUGIN_HOUSE')</code>
 ==== Find translators for your language file ====
-Now that you have created a language file it's possible to translate these strings to several other languages. You can do that by yourself or search for people who will do this but it's also possible to add your file to the [[https://www.transifex.com/admidio/admidio/dashboard/|Admidio Project]] at [[http://www.transifex.com|Transifex]]. We have already people who translate Admidio into another language and maybe they could also translate the strings of your plugin.
+Now that you have created a language file it's possible to translate these strings to several other languages. You can do that by yourself or search for people who will do this but it's also possible to add your file to the [[https://www.transifex.com/admidio/admidio/dashboard/|Admidio Project]] at [[https://www.transifex.com|Transifex]]. We have already people who translate Admidio into another language and maybe they could also translate the strings of your plugin.