elkuku wrote:

quote BEAT(can someone tell me how to quote ¿¿)

Nick's solution has the big advantage that replies are the same independantly of language.

if you refer to "systemmails in multilanguage environments" you are damn right... this is a big headache at present point.

btw.. let me kiss your feet for the quick fixes you made for several componets to let them run without joomlas register_globals emulation.

EXCELLENT WORK !

- Quoting multiple posts: Just press "quote", open it in other window, copy content, paste in your post.

- Thanks. Just simply shared the solutions found for making Joomlapolis and other sites run with register_globals off. Actually i got many testers-feedbacks back, which allowed me to quickly complete the fixes... ...power of community & open-source

- Yes, system-mails, and many other things are not yet treated by the fish. We have been postponing all language-related work in CB until the new, better, languages API and UTF-8 standard of Joomla 1.5 comes into effect. So yes, we need to live in a world of compromises. I hope that Fish 2.0 for Joomla 1.5 will also hook into that API. Does somebody have a thread URL for that discussion ? if not, maybe worthwile to ask in 1.5 dev forum.

mikko wrote:

nant wrote:

I would setup all selectable or multi-selectable field values as language strings.
So, if for example you have a multiselect field for languages you should setup the allowable values (when defining the CB field) as _UE_LANG_1, _UE_LANG_2, etc. Then just add these values with the correct translations to your language files.

This is a solution, but for my use (and perhaps many other) joomfish translation would be much better. The reason for this is that I have select fields which that can accept new values entered by users. For some selects there is an option called "new.." and selecting that option triggers a prompt asking for a new value. These values then go to aproval and translation work flow where the administrator needs to do a bit of work for them. For the people that do this work on one of my sites, it is much easier to translate with joomfish than hardcode each translation to a language file every time someone enters a new value.

It would be possible to make a component which cretes translations to the language file, but this would be a potential security risk and much more work than making the fields work with ids rather than titles.

-Mikko

- Agree that JoomFish allows centralization of translations management in one place, which is desirable.

- Actually, why wouldn't you implement your own multi-select field type in your plugin instead of relying on CB's, so the translations would be handled by JoomFish ? would take another 2 hours for you . But keep in mind to store unique ids or keywords for answers, to be able to treat them independantly of language