Open alesf opened 9 years ago
Do you have any examples of ways other CMSes implement localization in a user friendly way for content editors?
As far as localization for the admin UI -- I'd be happy to add that into a future release provided a native speaker provides translation strings!
That is exactly what is missing in most content management systems - user friendly localization. It's hard to give an example of a good one as they are either too complex or to basic.
You can look at Typo3 localization, but considering great UX of BigTree you would have to come up with something flexible and usable. The easiest implementation could be versioning of the same content (could be a problem if you want a different structure for different languages, but most websites have the same or just pruned versions of localizations). Best way to translate is usually side by side, so you might pick a default language to translate from that is shown beside the translation. Localization of other content like images and documents is done in similar fashion.
If you set up the translation files for administration and put them on Github, I'm sure many people will create PR with translated files.
Localisation of content is a must for non English developers, since websites are usually developed on the local language and English. This is probably the main reason why I'm not using BigTree in client work.
One option would be to have a global setting where you could change the language, and edit only content on that language.
Another option, would be to have a multilingual option when creating a field, and when editing content this field would be repeated as many times as languages are configured.
What kind of programmatic interface would you guys suggest for pulling languages into front end templates (and via module classes)? Do you think just a different output format when running a multi-lingual site?
I.e. in a template you'd have $en for your full array of English template resources and $fr for your full array of French template resources?
I.e. in a template you'd have $en for your full array of English template resources and $fr for your full array of French template resources?
Yeah, that would be great.
Hey @timbuckingham any news about multilingual support? Is it something you are working on?
No news at the moment -- I haven't had the bandwidth for it juggling client work. I do have localization of the admin interface on my radar after I finish up the 4.3 extension updates, though.
I'm not sure if multi-lingual content is going to make it into 4.3 -- I really want to have a Fall release and haven't had the time to dedicate to all the things I was hoping would make it.
Having no multi-language support makes the CMS useless for us :( We are currently deciding to go away from the long-time player ModX and try some new CMS. And we need multilanguage support, see http://stackoverflow.com/a/38902608/1066234
As soon as there is such a feature implemented in Big Tree, we will consider testing and using it. Now we do not touch it, since this is one of the most essential features for us.
Admin localization is baked into BigTree 4.3 -- we don't currently have any localized strings but as we get closer to a beta release we will begin soliciting translations for all the needed strings.
I can do it for Brazilian Portuguese. I just discovered BigTree and would like to use it for a client. I don't know how much far away you are guys are from a beta release, since I was not following it 'til now. So let me know when it's time.
Localization of content into different languages.
This is widely used feature and a deal breaker if you need it.
Requesting for localization of administration UI would be pushing it I guess :)