[MGNLDEMO-36] German translation for content Created: 18/May/15  Updated: 24/Jun/15  Resolved: 19/Jun/15

Status: Closed
Project: Magnolia Demo Projects
Component/s: None
Affects Version/s: None
Fix Version/s: 0.5

Type: Task Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Christopher Zimmermann
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLDEMO-67 When I browse the demo I can switch t... Closed
dependency
depends upon MGNLDEMO-66 Tour page only displays english Closed
depends upon MGNLDEMO-35 Final page content Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Site must have a second language for all page content and for at least the titles and descriptions of the category and tour content.
German is the natural choice as Magnolia is headquartered in Basel.



 Comments   
Comment by Christopher Zimmermann [ 02/Jun/15 ]

Website & Tour content has been sent out for translation

Comment by Christopher Zimmermann [ 19/Jun/15 ]

Note: Depends on linked ticket for displaying the tour page in a different language.

Added german language content. Implemented in:
website content, tours content, categories content, language files.

TourServices modifications to support multi-language.
Additional footer area "lastLinks" added. (Was previously hardcoded links which did not play nice with multilanguage.)

Changed tourCarousel to pass the nodeName of the category to the tourTypeIcon macro so that it would be language independent.

Changed link.ftl so that it does not add an extra space after the link (which looks bad on rollover.)

Personalization variations recreated in order to get latest version of footer and german language.

Comment by Federico Grilli [ 23/Jun/15 ]

Only small improvement maybe is to use freemarker special variable .now in travel-demo/templates/areas/footer.ftl so not have to update the current year manually every year, eg.

${.now?string['yyyy']}

even though starting from 2016 it will have to be changed to something like this

2015-${.now?string['yyyy']}
Generated at Mon Feb 12 05:15:39 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.