Create Use Case Documentation
(DOCU-176)
|
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | content |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Suzanne Deprez | Assignee: | Antti Hietala |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: |
| Description |
|
Create a use case that will provide information and documentation needed in order to create a control for editing a field in multiple languages. This use was raised in the user list forum. This use case will help to fill out the possibilities in the proposed Internationalization section in the use case structure. A skeleton of this use case is provided at http://wiki.magnolia-cms.com/display/DOCU/Multilanguage+dialog+edit+control. |
| Comments |
| Comment by Antti Hietala [ 01/Sep/11 ] |
|
Changed ticket title from "Multilanguage Dialog Edit Control Use Case" to "Multilanguage support in Data and DMS". i18n support is already provided in the website workspace and dialogs reflect this today. What the forum user was asking is extending i18n support to data and dms workspaces and corresponding dialogs. |
| Comment by Antti Hietala [ 25/Feb/14 ] |
|
Obsolete. I18n content entry is supported in workspaces such as dam and contacts in Magnolia 5. Add i18n=true to the field definition. |