Also moving form joomfish isn't a big effort (ther's a tutorial on the developer page).
First difference is: Falang does not support frontend edition!
Second difference - and that's the reason I'm not using it so far: sef url functionality is not supported. While joomfish used the translated menu alias to build the url in falang the url always is in the default language. Like that
-If I move from Joomla 1.5 my content isn't available under the same url -> very bad!!!
-my url is always in the same language -> not good for search engines
A hack in the core files lets you fix that (translating the url) but then the language switcher module doesn't work anymore (and that's definitely not what I'm looking for). Also I have to translate the whole url instead of only the menu alias.
If you don't care about seo or if you do seo with an additional tool falang may be great. No - it is great. And I'm quite sure the developer will add the functionality with the menu alias and then this extension is even better.
Localise has a very large functionality.
Even compared with missingT Localise get's some advantages:
-Autotranslation lets you choose which entries you'd like to translatees.
-text editor available to fix corupt files.
Compared with missingT there is just one small disadvantage: Theher is no export function.
Like in missingT there is no possibility to create a missing file.
Also it's not possible to create a override file, so updating joomla can overwrite the changes. Override files aren't even recoginesed.
I'd like Localise even more, if there would be a functionality to create an manage override files.
joomla own has edit override functions
but in localise you can edit override files too by filter select type to override
-Poor filter options
-no overview of the translation state outside the file.
-no auto translation (google/ bing)
-simple text editor without any layout
But (and it's a big but) j!Language Editor supports language overrides! Changes are not saved in the orignal file, so after an update they are still there.
Compared with the j!Language Editor missingT has a very large functionality.
Compared with Localise there are some disadvantages:
Autotranslation translates all entries. I prefer to choose which entries I'd like to autotranslate.
No text editor available to fix corupt files.
But there is also an advantage: The export function.
Like in Localise there is no possibility to create a missing file.
Also it's not possible to create a override file, so updating joomla can overwrite the changes. Override files aren't even recoginesed. But here in MissingT the export function may help.
All in all I prefer Localise. I'd change to missingT if there would be a functionality to create an manage override files.