Translator_XH
Moderator: Tata
Translator_XH
Hello community,
I've just released Translator_XH 1beta1. It's available from my website.
Translator_XH is an advanced tool for translating the CMSimple core, pluginloader and individual plugins. It's partcularly useful for translators, so the typical end-user of CMSimple does not have any need for this plugin.
The current version has to be considered Beta software! Use with caution!
Any feedback is welcome -- particularly about missing features, or functionality that could be improved.
Christoph
I've just released Translator_XH 1beta1. It's available from my website.
Translator_XH is an advanced tool for translating the CMSimple core, pluginloader and individual plugins. It's partcularly useful for translators, so the typical end-user of CMSimple does not have any need for this plugin.
The current version has to be considered Beta software! Use with caution!
Any feedback is welcome -- particularly about missing features, or functionality that could be improved.
Christoph
Christoph M. Becker – Plugins for CMSimple_XH
Re: Translator_XH
Seems really excellent. One more idea (as always ). How about to make the output of linkable. I mean, if the translator has all language-files translated and ready for evtl. download, a link to each translated file would be available. Or does it conflict with any security issues?
Code: Select all
.../?&translator&admin=plugin_main&action=plugin_text...
CMSimple.sk
It's no shame to ask for an answer if all efforts failed.
But it's awful to ask without any effort to find the answer yourself.
It's no shame to ask for an answer if all efforts failed.
But it's awful to ask without any effort to find the answer yourself.
Re: Translator_XH
Hi Tata,
But what about this alternative: instead of the download button, a save button is available. When clicking the save button a name for the language pack must be entered, and then the language pack is saved in a configurable folder.
Christoph
Do you mean a download-link for the translator (that's already possible with the "download" button), or for end-users? About the latter case: I'm not quite sure, if that is a good idea. IMO it is better to provide the downloads from another folder than the plugin folders (perhaps downloads/), and with a name including the version number. This can't be done automatically.Tata wrote:I mean, if the translator has all language-files translated and ready for evtl. download, a link to each translated file would be available.
But what about this alternative: instead of the download button, a save button is available. When clicking the save button a name for the language pack must be entered, and then the language pack is saved in a configurable folder.
Christoph
Christoph M. Becker – Plugins for CMSimple_XH
Re: Translator_XH
This would be fine. I just think about some way of standardisation of the translation procedure ending with a standard defined download link. Maybe I miss some point. But I thought about:cmb wrote:...a save button is available. When clicking the save button a name for the language pack must be entered, and then the language pack is saved in a configurable folder.
1. Listing of all installed plugins - solved excellently
2. Two columns source/target languages - solved excellently - I tried to add labels before flags using new variables (not important):
Code: Select all
//***
$plugin_tx['translator']['translate_from']="Translate from";
$plugin_tx['translator']['translate_to']="Translate to";
//***
"As a cherry on the cake top"
4. MakeLanguagePack button to save translated file with its root-relative paths and evtl. ZIP them under the given name. If the "version" variable would become the standard for plugins/addons developers, then the name of the ZIP could be IMHO generated automatically.
5. Code-box with the URL to the language pack to copy/paste on any other place on internet.
CMSimple.sk
It's no shame to ask for an answer if all efforts failed.
But it's awful to ask without any effort to find the answer yourself.
It's no shame to ask for an answer if all efforts failed.
But it's awful to ask without any effort to find the answer yourself.
Re: Translator_XH
Hello Tata,
I will do this for the next version.
Christoph
Change admin.php, line 272ff:Tata wrote:I tried to add labels before flags using new variables (not important):
Code: Select all
$$lang_h = file_exists($fn)
? $$lang.' '.tag('img src="'.$fn.'" alt="'.$$lang.'" title="'.$$lang.'"')
: $$lang;
Indeed that seems to be better than the current solution "download language pack". I'll make it so.Tata wrote:MakeLanguagePack button to save translated file with its root-relative paths and evtl. ZIP them under the given name.
You're right. And even other things could be improved regarding the management of plugins, if a standard would be agreed upon. But one problem remains: how to handle the base language pack (core, pluginloader and default plugins)?Tata wrote:If the "version" variable would become the standard for plugins/addons developers, then the name of the ZIP could be IMHO generated automatically.
This could be easily displayed directly after saving, because the name is known then. But to show it permanently the names of the saved language packs must be stored somewhere.Tata wrote:Code-box with the URL to the language pack to copy/paste on any other place on internet.
Christoph
Christoph M. Becker – Plugins for CMSimple_XH
Re: Translator_XH
I used thiscmb wrote: Change admin.php, line 272ff:Code: Select all
$$lang_h = file_exists($fn) ? $$lang.' '.tag('img src="'.$fn.'" alt="'.$$lang.'" title="'.$$lang.'"') : $$lang;
Code: Select all
$htm .= '<tr><th></th><th>'.$plugin_tx['translator']['translate_from'].': '.$from_h.'</th><th>'.$plugin_tx['translator']['translate_to'].': '.$to_h.'</th></tr>'."\n";
The question is - What would be better/easier for endusers/translators?cmb wrote:...But one problem remains: how to handle the base language pack (core, pluginloader and default plugins)?...
- download LanguagePackCMSimple_XH_xx_yyyymmdd.zip structure with all actual language files and use/upload/install only those needed
- look only for for those needed and download/upload/install them separately
1. The translator may define the folder for storing the ZIPs easily - e.g. userfiles/translations - this can be even be defined in plugin's config.cmb wrote:This could be easily displayed directly after saving, because the name is known then. But to show it permanently the names of the saved language packs must be stored somewhere.
2. The path will be used with "ZIP"-button anyway. Or the button may be extended by an file-name-box and an URL-box appearing after saving as "read-only" with the full URL to the ZIP file.
Before saving:
[ external image ]
after
[ external image ]
CMSimple.sk
It's no shame to ask for an answer if all efforts failed.
But it's awful to ask without any effort to find the answer yourself.
It's no shame to ask for an answer if all efforts failed.
But it's awful to ask without any effort to find the answer yourself.
Re: Translator_XH
Hi Tata,
thanks for the detailed reply and the screenshots, which make things clearer for me.
And I'm currently not sure how to handle the problem of an already existing language pack with the same name. Should it be simply overwritten?
Christoph
thanks for the detailed reply and the screenshots, which make things clearer for me.
Ah, now I understand. That's a good idea.Tata wrote:I used this
IMO the language packs for the base distribution of CMSimple_XH should contain all necessary language files (core + pluginloader + default plugins) for 1 language. I thought, that other plugins should contain all available language files in their download, as it is the case now. But perhaps that should be changed too.Tata wrote:The question is - What would be better/easier for endusers/translators?
That's reasonable.Tata wrote:The translator may define the folder for storing the ZIPs easily - e.g. userfiles/translations - this can be even be defined in plugin's config.
Something like this I had in mind. But I'm not sure, if the full URL is necessary/reasonable, or if the relative path is perhaps better.Tata wrote:Or the button may be extended by an file-name-box and an URL-box appearing after saving as "read-only" with the full URL to the ZIP file.
And I'm currently not sure how to handle the problem of an already existing language pack with the same name. Should it be simply overwritten?
Christoph
Christoph M. Becker – Plugins for CMSimple_XH
Re: Translator_XH
Depends of the way the link will be used. If the link shall be used e.g. here in forum, the relative path won't work. WIll it?...But I'm not sure, if the full URL is necessary/reasonable, or if the relative path is perhaps better...
Again the question: If a file already exist, what is the reason for its new translation/editing? Maybe some additional change, new variable added, some misspelling found... Whatever is the reason, translated/edited file is the last actual version. In this case the overwritten file is OK. Or the name may be generated the same way like the content/pagedata files (name_yyyymmddhhmmss).cmb wrote:And I'm currently not sure how to handle the problem of an already existing language pack with the same name. Should it be simply overwritten?
CMSimple.sk
It's no shame to ask for an answer if all efforts failed.
But it's awful to ask without any effort to find the answer yourself.
It's no shame to ask for an answer if all efforts failed.
But it's awful to ask without any effort to find the answer yourself.
Re: Translator_XH
Hi Tata,
Christoph
I don't know if the link will be used here in the forum, but probably an absolute is better after all. If only the relative URL is needed, the user can only copy this part.Tata wrote:If the link shall be used e.g. here in forum, the relative path won't work. WIll it?
I've thought about different language packs for different versions of CMSimple resp. plugins. But in this case the translator should give a different name to the language pack -- so simply overwriting an already existing file should be okay.Tata wrote:Whatever is the reason, translated/edited file is the last actual version
Christoph
Christoph M. Becker – Plugins for CMSimple_XH
Re: Translator_XH
Now I even think about some hard coded file-name-mask with mandatory language code in it. This way all languagepacks would use the same naming convention.cmb wrote:But in this case the translator should give a different name to the language pack...
The mask example (hard cocded / mandatory / generated):
LanguagePack_CMSimple_XH_xx_SK_20111103_181030.zip
LanguagePack_CMSimple_XH_pluginloader_xx_SK_20111103_181050.zip
CMSimple.sk
It's no shame to ask for an answer if all efforts failed.
But it's awful to ask without any effort to find the answer yourself.
It's no shame to ask for an answer if all efforts failed.
But it's awful to ask without any effort to find the answer yourself.