#2769 - Multi-lingual capabilities
-
By PDStig
- Added
- 1 view
| Identifier | #2769 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Multi-lingual capabilities |
| Status | Closed (rejected) |
| Handling member | Chris Graham |
| Addon | core_comcode_pages |
| Description | Add the ability to provide content from comcode pages etc. in multiple translations. That way, site users can easily view page content in the language of their choosing without having to use a translation tool.
For instance, on a comcode page interface, there might be a drop-down to allow you to select a language (when you first go to an edit screen, it will show the content of the language of the website default initially). Whichever language you select, the content for that language will show up in the editor. You can then edit/add content in that language via the editor... and then use the drop down to switch to another language and do the same. Any languages that get saved with no content (blank editor) will be omitted. When someone views the content, they too will then get a language drop-down, which would allow them to choose which language to view the content in. Any languages omitted via. the system above would not be included in the drop down. |
| Steps to reproduce | |
| Additional information | This could get very complex easily. For instance, if a dynamic block is added in the French section of a comcode page, the block will need to be auto-translated to French via. Composr's own language translation. In addition, this could pose challenges with the autosave functionality. |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
We don't do selecting what language to view individual content items in, it's site-wide, but I can't see that being very useful. Besides, using the side_language block would take you back to where you were after changing the language, so it's almost the same.
I think the current solution is more streamlined than keeping setting things per item, and I wouldn't want two ways of handling it all.