[MAGNOLIA-3210] i18n content support for separate hierarchies Created: 21/May/10 Updated: 09/Apr/21 Resolved: 03/Jun/10 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | i18n |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.2 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Federico Grilli | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Description |
|
Add support for i18n also when the locale content is in separate hierarchies. |
| Comments |
| Comment by Federico Grilli [ 03/Jun/10 ] |
|
Following yesterday's meeting at Namics, a new requirement has come up: the locale should also be determined from the last URI part, typically a page (e.g. /foo/bar/baz/de.html). When we parse the URI and get to the last element we should strip it from what follows the dot (if one is there and see if a valid locale can be inferred from it) |