+1 to improve this..thks for contributing. I also would like to make feeds imports languageaware

This is an interesting idea. Is this the only benefits of using Falang where it has a fallback "item"?

The way I use Falang with EB is like this:

- Select the language
- Select the type to translate (EB post)
- Click button "copy" original post to translation box (all EB code is copied)
- Translate the post content only (leave EB code in place)

That is not an easy way of translating but it does the job.
If you want you can connect to admin of my website and have a look inside Falang component...

If we could have an option like described in my request above that would be so much more convenient

EDIT:
It has always been said the advantage of Falang is that it does not create "duplicated content".
A text "There is no translation available" can also be displayed with the use of a plugin (personally do not use it)
Falang is mainly used to translate components that can not be translated natively by joomla AND to NOT create duplicated content (No need to create copies of menus or categories in every languages - simply translate them in Falang)

Hm, based on what you are describing on the usage of Falang, it seems like what you are trying to achieve is probably "duplicate" a post to a different language rather than typing from scratch, am I understanding this point correctly?

What about Joomla articles itself? Is there any benefits of using Falang on Joomla articles considering that Joomla already has a built-in translation integrated?

Hm, based on what you are describing on the usage of Falang, it seems like what you are trying to achieve is probably "duplicate" a post to a different language rather than typing from scratch, am I understanding this point correctly?

What is important are time and fallback:
Time:
Not waste time in building again the complete layout of different blocks and their content. So yes, basically we are duplicating the content to modify some blocks, translate the texts, translate the captions etc. etc.
Fallback:
If we do not have a translation for one or more languages it does not matter, a fallback displays the post in the original language.

With Falang:
- No 404, always a fallback to original language
- Optional message on item page : "There is no translation available"
In EasyBlog:
- We possibly can duplicate a post and translate the blocks when needed and assign a language (mostly like Falang)
- We can not create relationship with original post (standard in Falang)
- We can not set a fallback to the original post language (standard in Falang)
- If there is no translation in a language EB does not display anything... we would like to display the post in the original language (it is important to display the news even without translation - close to 50% of world population is bilingual)

What about Joomla articles itself? Is there any benefits of using Falang on Joomla articles considering that Joomla already has a built-in translation integrated?

- There is no fallback in the joomla built-in multilingual.
- You are forced to create an item in ALL languages and then make the language associations.
- This mean if you did not duplicate an item AND assign a relationship in any language you get a 404

How to implement the concept in EasyBlog:
- Write a post
- Select a specific language or "ALL Languages"
- If a language is selected : Set (or not) this post as fallback post (you can write an original post in German as a german native but want the fallback in English to make the post accessible to a wider audience) - Better than Falang !
- Make a translation relationship by selecting other posts in other languages

Ah okay, after re-reading this many times I finally understand what do you mean here and I think it is very confusing for us, because we seldom or never really deal with multi lingual content and never really experience the pain or hassle of building such contents.

I will discuss with the team to see if there's anything we can simplify from what I gather here as there are also quite a number of tasks which we are still working on and not sure if we have the time to push this

Hi

I agree with supporter and good you start analysing/planning bcs the most annyoing for me with a Joomla site with many modules and languages is when you only need to change the module title for same module type.

You should have something like tabs for the module for different languages where you change the title for different language modules instead of the need to create one module per language.

Dont know if you can solve this differently but you dont want to go into the language .ini file everytime and fiddle.

Here is attachedrf examples of another Joomla comp that uses tabs for different titles in a directory component and also how you directly change language in the component itself.

You see a similar solution here 1:54 into this video https://www.youtube.com/watch?v=gx37_Lyg3vo ( description)

Hm, what I am seeing on your screen shots is actually very different than what we are discussing here. In your screen shots, you are directly translating the items and it doesn't make sense to implement this in EasyBlog because I can foresee this will only confuse your authors and scare them from even starting to write anything

Hello Mark,

Do you have any update about a possible "fallback" option ?

Thank you

Up ....