• FOR J1.5 you will need to install and Enable Joom!Fish, or Falang for J2.5
• For J1.7/J2.5 you will need to configure multi-language menus and enable language switcher module, see joomla documentation.

NOTE: (Joom!Fish will be available for J2.5 soon, see here, BUT we do not support joomfish YET, final version will be supported)

PART 2: For everything but not for FLEXIcontent items:

-- Translate category, tags, fields (the titles not values) and files with Joom!Fish
-- Important usability feature: To quickly open the corresponding translations for all the above. You can use the back-end direct translation module (comes with Joom!Fish):
See: How can I expand the Joomfish support?

PART 3: For FLEXIcontent items (Your site content) you have 2 solutions:

(a). Use Joom!Fish (or Falanf in J2.5) to translate items,
-- This will translate only title, description, meta keywords and meta description
-- Disadvantage: All other fields can not be translated, since they are not part of the joomla #__content table.
-- Possible advantage: Item hits/voting are shared since you have a single item item for all
translations
-- Possible advantage: You have multiple items for the same original content
-- Important usability feature: (See above) Use the back-end direct translation module, to quickly open item translations

(b). Use one item per translation  e.g. 3 items for every translation of the "Original Content Item"
NOTE: this associates the items together and automatically switches them in the frontend
-- This way you can translate the item fully, --all field values--.
-- Possible disadvantage: Item hits/voting are not shared since items are different (sharing may be implemented in v1.5.6 final or in v1.5.7)

-- Important usability feature: You can quickly duplicate many items and change language via Item TRANSLATE Task in items manager TAB
 This task has 3 options:
-- i.  Copy original content without any change
-- ii.  Import Joomfish Data (J1.5 only, since in J2.5 there is no such content, since Joomfish associates items in J2.5 instead of storing translations)
-- iii. Automatic google translation of original content before saving the item (THIS is implemented but not yet enable because we must use a free Google API translate interface) (possibly v1.5.6 final or v1.5.7)

CONFIGURING

For alternative (a) (J1.5 ONLY)
we use Joom!Fish language selection module OR in (J1.7/J2.5) you use the language switcher module to select language in the front-end.
In FLEXIcontent Global Configuration
-- YES :: Activate Joom!Fish support
-- NO :: Disable language selector
-- NO :: Enable translation groups
-- YES :: Edit Joomfish Translations
-- NO :: Filter category views AND Filter tag views

ALTERNATIVE (b) for both J1.5 / J2.5,
In FLEXIcontent Global Configuration
-- YES :: "Filter category views" and "Filter tag views"
-- YES :: Enable translation groups

WARNING: FLEXIcontent does not delete Joom!Fish translations of items, so for example