Multi-lingual support for extensions ..... more

[over]

The thread "Joomla GPL Extensions and Removal of Backlinks" was "hijacked" by "Multi-lingual support for extensions"

You can use this thread if you want to comment further on the "Multi-lingual....."

Here a related question about modules.
Not Multilingual but a general problem: I add a titel-field to the module parameters as I see a difference between the module title in the backend module list and the module title in frontend. Of course not all modules need a title in the frontend
Multi-lingual problem: How do I get a translated module title in frontend if I have say 5 languages? Make 5 copies of the same module? Hurra! the site manager has something to do if he/she wants to change a single module parameter.

Any idea? I'll test my own sugestion to use JText with a variable $MyModuleTitle and add the translation to the Joomla language overrides. It might work. I suppose the variable has to be language .ini compatible.

Do you see a better way?

regards
Ove


 

[Niels Braczek]

Am 26.07.2012 16:41, schrieb over:

> Multi-lingual problem: How do I get a translated module title in frontend
> if I have say 5 languages? Make 5 copies of the same module? Hurra! the
> site manager has something to do if he/she wants to change a single module
> parameter.

Use FaLang (Joom!Fish port to 2.5), if you want to have the same
structure for all languages. The core system does not really support
that, because the same item gets different IDs depending on language.
Due to that, you have to copy the complete structure, even if it were
not necessary for untranslatable items. FaLang/Joom!Fish avoids this
problem.

Regards,
Niels

--
| http://barcamp-wk.de · 2. Barcamp Westküste Frühjahr 2013 |
| http://www.bsds.de · BSDS Braczek Software- und DatenSysteme |
| Webdesign · Webhosting · e-Commerce · Joomla! Content Management |
------------------------------------------------------------------

[Ove]

Yes Niels I know,
but I try to use Joomlas built in multi-lingual support without any 3.d
party extras. There are some lomg term disadvantages with the
translations. i.e. I prefer to store content as articles and other items
in each language. There are some ideas how to get a reference between
those items.

Regards
Ove

[JM Simonet]

As of today and until someone proposes a patch to fully allow any
Items associations (Volunteers welcome!) -and not only menu items
associations-, we have already one way to link to articles in other
languages by using the Article link button at bottom of the Editor.
This will correctly switch to the right language UI and drilldowns
when clicking on the article link in the original article.
One can create a span css for that link to display, for example, a
Flag included in the link.
Example:
LTR: .en-flag { background:
url(../../../media/mod_languages/images/en.gif) no-repeat;
padding-left:20px;}
RTL: .ar-flag { background:
url(../../../media/mod_languages/images/ar.gif) no-repeat;
padding-right:20px;}

JM

>--
>You received this message because you are subscribed to the Google
>Groups "Joomla! General Development" group.
>To post to this group, send an email to joomla-de...@googlegroups.com.
>To unsubscribe from this group, send email to
>joomla-dev-gene...@googlegroups.com.
>For more options, visit this group at
>http://groups.google.com/group/joomla-dev-general?hl=en-GB.


--
>Please keep the Subject wording in your answers
This e-mail and any attachments may be confidential. You must not
disclose or use the information contained in this e-mail if you are
not the
intended recipient. If you have received this e-mail in error, please
notify us immediately and delete the e-mail and all copies.
-----------------------------------------------------------
Jean-Marie Simonet / infograf768
Joomla Production Working group
Joomla! Translation Coordination Team

[Ove]

@Niels, The translations are per default duplicates. No difference if
you store them in the original table or in separate table(s). As I a
long time ago wrote a JoomFish "scheme" for a component I did not
include all fields but in a general solution you probably would also
need fields as publish-up and publish-down i.e all fields available for
"translation". The problem is that there are no general solutions on
item associations.

@JM, thanks for the tip on articles. I did not come to this idea myself.
I sure will test it. As long as you have a limited number of
articles/translations this would be a solution. I do not have the
technical skills to come up with a general solution on the associations.
What i have done is to add a reference field in the components main
table. This reference points to the main-language item. I also have a
copy2language task to create a translation from the original item. Using
an extra table for the associations might be better.

Back to my original question about modules and freetext as parameter and
duplicating the modules. In a module like log-in I would remove the free
texts (pre- and post-texts) and use a text in the module .ini file to
make it translatable. You wouldn't use more than one copy of the log-in
module on a page. Probably not even possible as it is a form. The module
title could be translated in the same way. The problem is that you might
want to use more than one copy of the module with different titles on a
page.