Translator_XH
Moderator: Tata
Re: Translator_XH
Hi Tata,
I don't know, if it's reasonable to define a standard for names of language packs now. Perhaps we should wait until the update availability check for plugins makes progress. So the conventions and necessities could be discussed then.
Christoph
I don't know, if it's reasonable to define a standard for names of language packs now. Perhaps we should wait until the update availability check for plugins makes progress. So the conventions and necessities could be discussed then.
Christoph
Christoph M. Becker – Plugins for CMSimple_XH
Re: Translator_XH
It was just an idea. I often think a step in advance .
OT:
I installed all latest XH_plugins to start checking/editing/completing translations. As the debug mode is active, there are too many NOTICEs almost with each plugin. Now, I am not sure how serious they are or if they may be simply ignored.
OT:
I installed all latest XH_plugins to start checking/editing/completing translations. As the debug mode is active, there are too many NOTICEs almost with each plugin. Now, I am not sure how serious they are or if they may be simply ignored.
and many others.NOTICE: Undefined offset: -1
F:\CMSimple_XH_15RC2_20101023\plugins\hi_fancybox\index.php:93
NOTICE: Undefined variable: vars
F:\CMSimple_XH_15RC2_20101023\plugins\hi_pd_scripting\languages\en.php:13
NOTICE: Undefined index: hi_pd_scripting_active1
F:\CMSimple_XH_15RC2_20101023\plugins\hi_pd_scripting\index.php:55
NOTICE: Undefined index: title
F:\CMSimple_XH_15RC2_20101023\plugins\meta_tags\index.php:45
NOTICE: Undefined index: description
F:\CMSimple_XH_15RC2_20101023\plugins\meta_tags\index.php:48
NOTICE: Undefined index: keywords
F:\CMSimple_XH_15RC2_20101023\plugins\meta_tags\index.php:51
NOTICE: Undefined index: robots
F:\CMSimple_XH_15RC2_20101023\plugins\meta_tags\index.php:54
NOTICE: Undefined index: show_heading
F:\CMSimple_XH_15RC2_20101023\plugins\page_params\index.php:67
NOTICE: Undefined index: show_last_edit
F:\CMSimple_XH_15RC2_20101023\plugins\page_params\index.php:74
NOTICE: A session had already been started - ignoring session_start()
F:\CMSimple_XH_15RC2_20101023\plugins\advancedform\captcha.php:19
NOTICE: Undefined index: admin
F:\CMSimple_XH_15RC2_20101023\plugins\hi_backup\admin.php:30
NOTICE: Undefined index: action
F:\CMSimple_XH_15RC2_20101023\plugins\hi_backup\admin.php:31
NOTICE: Undefined index: downloadnow
F:\CMSimple_XH_15RC2_20101023\plugins\hi_backup\admin.php:33
NOTICE: Undefined variable: newsrotator
F:\CMSimple_XH_15RC2_20101023\plugins\newsrotator\admin.php:14
NOTICE: Undefined variable: menumanager
F:\CMSimple_XH_15RC2_20101023\plugins\sitemapper\admin.php:219
NOTICE: Undefined variable: pagemanager
F:\CMSimple_XH_15RC2_20101023\plugins\sitemapper\admin.php:220
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
PS: I've just seen, that you have posted a list. The two notices caused by sitemapper are already fixed in 1beta5. The notice from advancedform will be fixed in 1beta9. The "NOTICE: Undefined variable: vars" caused by hi_pd_scripting is caused by $plugin_tx['hi_pd_scripting']['hint_code']. Just open en.php in an external editor and replace ($vars) by (\$vars), before translating further.
And that's good!Tata wrote:I often think a step in advance
Usually notices, deprecated reports and even warnings are no problem. You can compare them to HTML validation errors: if everythings works fine, no need to be worried. But IMO it's better to get rid of them, just to be on the safe side. BTW: if there are too many of them so you have to scroll down half a mile , you should turn off the debug mode.Tata wrote:As the debug mode is active, there are too many NOTICEs almost with each plugin. Now, I am not sure how serious they are or if they may be simply ignored.
Christoph
PS: I've just seen, that you have posted a list. The two notices caused by sitemapper are already fixed in 1beta5. The notice from advancedform will be fixed in 1beta9. The "NOTICE: Undefined variable: vars" caused by hi_pd_scripting is caused by $plugin_tx['hi_pd_scripting']['hint_code']. Just open en.php in an external editor and replace ($vars) by (\$vars), before translating further.
Christoph M. Becker – Plugins for CMSimple_XH
Re: Translator_XH
Thanks for explaining. WIll do. But first next Thuesday after return from Dubai. I leave tomorrow.
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,
have a nice trip. And perhaps you'll return with a souvenier: LanguagePack_CMSimple_XH_AR
Christoph
have a nice trip. And perhaps you'll return with a souvenier: LanguagePack_CMSimple_XH_AR
Christoph
Christoph M. Becker – Plugins for CMSimple_XH
Re: Translator_XH
Hello community,
I've just released Translator_XH 1beta2. 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!
From the changelog:
changed download language pack to save language pack and display URL for copy&paste (suggested by Tata)
updated manual accordingly
made some minor enhancements
Any feedback is welcome -- particularly about missing features, or functionality that could be improved.
Christoph
I've just released Translator_XH 1beta2. 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!
From the changelog:
changed download language pack to save language pack and display URL for copy&paste (suggested by Tata)
updated manual accordingly
made some minor enhancements
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
Hello community,
I've just released Translator_XH 1beta3. 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!
From the changelog:
fixed bug regarding translation-hints for the core
Any feedback is welcome -- particularly about missing features, or functionality that could be improved.
Christoph
I've just released Translator_XH 1beta3. 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!
From the changelog:
fixed bug regarding translation-hints for the core
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
Hi Christoph,
one thing I don't understand:
If I don't translate certain items, the plugin will add the item nevertheless with an empty string, e.g.:
$plugin_tx['calendar']['cf_calendar-popup']="";
However now the plugin cannot get the English text any more, it remains simply empty in my translated language.
I understand, I can set the plugin "use defaults" to 1 to put the English text into my translation.
What I want is that the plugin doesn't change the items which I do not translate. (So that even the next day I would see the yellow background of the items which are not translated.) How do I do this?
svasti aka Frank
one thing I don't understand:
If I don't translate certain items, the plugin will add the item nevertheless with an empty string, e.g.:
$plugin_tx['calendar']['cf_calendar-popup']="";
However now the plugin cannot get the English text any more, it remains simply empty in my translated language.
I understand, I can set the plugin "use defaults" to 1 to put the English text into my translation.
What I want is that the plugin doesn't change the items which I do not translate. (So that even the next day I would see the yellow background of the items which are not translated.) How do I do this?
svasti aka Frank
Re: Translator_XH
Hi Frank,
yes, I'm aware of this inconvenience (and probably should have stated it in the manual). I wanted to do it the way you prefer, but then I've stumbled across empty language strings (e.g. urichar_org). If the plugin won't save empty strings, the urichar_org will be missing in the translation, what wouldn't be a problem for CMSimple_XH 1.5, but the plugin should even be useful for older versions.
But on rethinking the problem, I found a solution. In case of new language strings I have to output a unique string (say "*** NOT YET TRANSLATED ***), and if this isn't changed when saving, the plugin should not write any language string for this key. This won't work though, if use_defaults=1.
So I guess it's time for 1beta4 ASAP.
Christoph
yes, I'm aware of this inconvenience (and probably should have stated it in the manual). I wanted to do it the way you prefer, but then I've stumbled across empty language strings (e.g. urichar_org). If the plugin won't save empty strings, the urichar_org will be missing in the translation, what wouldn't be a problem for CMSimple_XH 1.5, but the plugin should even be useful for older versions.
But on rethinking the problem, I found a solution. In case of new language strings I have to output a unique string (say "*** NOT YET TRANSLATED ***), and if this isn't changed when saving, the plugin should not write any language string for this key. This won't work though, if use_defaults=1.
So I guess it's time for 1beta4 ASAP.
Christoph
Last edited by cmb on Fri Nov 04, 2011 4:24 pm, edited 1 time in total.
Christoph M. Becker – Plugins for CMSimple_XH
Re: Translator_XH
Hello community,
I've just released Translator_XH 1beta4. 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!
The only change to 1beta3 was inspired by the latest two posts above. Have a look at the hint for default_translation in the plugin config.
Any feedback is welcome -- particularly about missing features, or functionality that could be improved.
Christoph
I've just released Translator_XH 1beta4. 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!
The only change to 1beta3 was inspired by the latest two posts above. Have a look at the hint for default_translation in the plugin config.
Any feedback is welcome -- particularly about missing features, or functionality that could be improved.
Christoph
Christoph M. Becker – Plugins for CMSimple_XH