Hello, I have a website that is maintained by people from several languages, among which en and fr are prevalent over the others. Both fr and en create the entities in their own language, they roughly create 50% each. People with other languages create nothing, they just translate in their own language what is created by fr and en.
I would not like to force fr people to give an en translation, as well as I would not like to force en people to give an fr translation. Then I refuse to give any required_locales.
What I would like is that, when either an en or fr creates an entity, with his own language, all the other communities see the en or fr text given, whichever it is:
An entity created with fr translation (only) is displayed for all in fr...
An entity created with en translation (only) is displayed for all in en...
... until anyone sees that, and enters the translation for its own language: then, after that italians see it instead of the fr or en that was entered at creation.
This looks like having several default_locale instead of one. No problem if giving many would likely result in having an order, such as:
"if my language is not present, then look for translation en, then if not present, look for translation fr, else empty string."
or:
"if my language is not present, then look for default_locale 1, then if not present, look for default_locale 2, (etc. for any other default_locale[]) else empty string."
I hope that's clear enough, please tell me your feeling about this.
Hello, I have a website that is maintained by people from several languages, among which en and fr are prevalent over the others. Both fr and en create the entities in their own language, they roughly create 50% each. People with other languages create nothing, they just translate in their own language what is created by fr and en.
I would not like to force fr people to give an en translation, as well as I would not like to force en people to give an fr translation. Then I refuse to give any
required_locales.What I would like is that, when either an en or fr creates an entity, with his own language, all the other communities see the en or fr text given, whichever it is:
This looks like having several
default_localeinstead of one. No problem if giving many would likely result in having an order, such as:"if my language is not present, then look for translation en, then if not present, look for translation fr, else empty string."
or:
"if my language is not present, then look for default_locale 1, then if not present, look for default_locale 2, (etc. for any other default_locale[]) else empty string."
I hope that's clear enough, please tell me your feeling about this.
Best,