Search Page Maker

[Marcelo Vitoria]

Hello friends

I purchased the Search Page Maker plugin, and when generating searches, it does not accompany the translation file, (I use Portuguese), leaving buttons and the page text in English.

Is this normal or is there a problem with my Pugin?

Will I have to translate the text and buttons on the screen manually every time I generate a search screen?

Thank you

[a.gneady]

SPM generates a custom filter page for each table in the hooks folder named like tablename_filter.php. The language strings are hard-coded in that file currently, so it can be translated directly in that file, but I plan to implement standard translation in future releases of the plugin.

[Marcelo Vitoria]

SPM generates a custom filter page for each table in the hooks folder named like tablename_filter.php. The language strings are hard-coded in that file currently, so it can be translated directly in that file, but I plan to implement standard translation in future releases of the plugin.

Another question:

Are the other Plugins also like this?

[a.gneady]

Here is a detailed list of language support for each plugin:

• Summary Reports plugin: hooks/language-summary-reports.php can be used to translate generated reports.
• Calendar plugin: plugins/calendar/app-resources/plugin-calendar/language/en.js can be used to translate generated calendars. Copy that file, renaming the copy to the 2-character abbreviation of the desired language, for example it.js for Italian.
• Messages plugin: plugins/messages/language/en.js can be used to translate the interface. Copy that file, renaming the copy to the 2-character abbreviation of the desired language, for example de.js for German.
• Mass Update plugin: plugins/mass_update/app-resources/language-mass-update.js can be translated.
• DataTalk: No support for translation yet.
• Search Page Maker plugin: No support for translation yet.

So, currently each plugin has its own way of applying translations, rather than a standardized way of translating all plugins. But this is something that I plan to work on in future releases.

[Marcelo Vitoria]

Here is a detailed list of language support for each plugin:

• Summary Reports plugin: hooks/language-summary-reports.php can be used to translate generated reports.
• Calendar plugin: plugins/calendar/app-resources/plugin-calendar/language/en.js can be used to translate generated calendars. Copy that file, renaming the copy to the 2-character abbreviation of the desired language, for example it.js for Italian.
• Messages plugin: plugins/messages/language/en.js can be used to translate the interface. Copy that file, renaming the copy to the 2-character abbreviation of the desired language, for example de.js for German.
• Mass Update plugin: plugins/mass_update/app-resources/language-mass-update.js can be translated.
• DataTalk: No support for translation yet.
• Search Page Maker plugin: No support for translation yet.

So, currently each plugin has its own way of applying translations, rather than a standardized way of translating all plugins. But this is something that I plan to work on in future releases.

Hello Ahmad

Thanks for the clarifications.

I believe it would be simpler for you to add the translation of the Plugins directly to the AppGini translation file, so when users purchase the plugins, when configuring the Plugins, they would already be displayed translated in the language of the translation file.

[a.gneady]

Will consider this option, though it creates some inter-dependencies in development, but it would indeed be easier for users to manage translations.

[onoehring]

Hi Ahmed,

I think

I believe it would be simpler for you to add the translation of the Plugins directly to the AppGini translation file, so when users purchase the plugins, when configuring the Plugins, they would already be displayed translated in the language of the translation file.

is a very good idea.

The interdependencies should not be Thus I suggest using a prefix for the plugin texts. This should prevent interdependencies I suppose (like: pg_spm_OriginalEnglishText for "Plugin", "SearchPageMaker" ...

PS: Having translation in the AG file might also trigger sales of those plugins. Just might be

Olaf