[MAGNOLIA-1431] i18n: basic content support Created: 20/Mar/07 Updated: 23/Jan/13 Resolved: 06/Nov/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | templating |
| Affects Version/s: | 3.0 Final |
| Fix Version/s: | 3.5 RC1 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Template: |
|
||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Description |
|
Currently magnolia does not give any advise how to implement i18n support for content. In cases where you have a single page structure with translations you have to come up with a custom solution. Till now the philosophy was that we can not solve this problem in general and that each setup has other needs. This is still our opinion but we think it is time to deliver basic support for facilitate implementations. More sophisticated all-over approaches may follow in later version. The framework will support
The first very basic implementation will do:
This allows:
|
| Comments |
| Comment by Philipp Bracher [ 27/Apr/07 ] |
|
I commited a first version (so that it goes into the M1 release). It works as such:
|
| Comment by Philipp Bracher [ 11/May/07 ] |
|
| Comment by Vivian Steller [ 20/Sep/07 ] |
|
| Comment by Magnolia International [ 18/Oct/07 ] |
|
Revision #11392 removed the setLocale method from WebContextImpl. Is there any specific reason? This contradicts with |
| Comment by Magnolia International [ 19/Oct/07 ] |
|
Ok - Since r11390-11392 etc, the jstl locale is set through the JspTemplateRenderer. |