Using Joomfish or Falang to translate your Content

In J1.5 we need Joomfish for translating Categories, Fields, Tags, Files, etc

For content, aka for the FLEXIcontent items (=joomla articles with extra fields and capabilities)
we have 2 choices for translating them:

Choice 1:
-- full item translations with
(a) ability to translate all fields, aka the full item ...
(b) associations of translated content (items) and
(c) switching them of the fly via FLEXIcontent Advance Route,
(NOTE: Future version of Joomfish for J2.5 will do (b) and (c) and we will support it, but we recommend that you will use Joomfish for everything, except for items (articles)

Choice 2:
-- Maybe easier approach which
(a) does not translate extra fields, but
(b) you can edit all translations in a single FLEXIcontent item edit form (v1.5.6+) (where you are presented with one tab per language for title, description, meta data).
In this case Falang for J2.5 replaces the translated data when the item / category is presented in the frontend, like Joomfish does in J1.5

It will be possible to use either Joomfish or Falang to translate your content in J2.5

(Joomfish is not yet finished for J2.5 and support for Falang is almost done, and will be 100% in FLEXIcontent v2.0a)

J2.5 user selects on each individual site what he will use:
-- but he must install Falang OR Joomfish, not both to avoid problems and confusion

NOTE:
J2.5 approach of giving a language to each article (=item) , is the approach that FLEXIcontent had from the beginning ...

-- now Joomfish for J2.5 (will) use an approach of (a) associating items together and (b) switching the in the frontend

-- we have both of the above already implemented (not only for J2.5 but for J1.5 too !!!),
meaning one could, with FLEXIcontent v1.5.6 in J1.5 (done via the FLEXIcontent Advanced Route Plugin), do what Joomfish will do in J2.5