Generall update on i18n pages (DOCU-729)

[DOCU-697] Document the i18n key generators and best practices Created: 16/Mar/16  Updated: 16/Jun/16  Resolved: 04/May/16

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Martin DrĂ¡pela
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to DOCU-729 Generall update on i18n pages Closed
Template:
Date of First Response:
Sprint: Docu Sprint 10

 Description   

We need a list of all of the implemented key generators.
We need a description of why there are so many.
The advantages and recommendation to use the less specific ones in most cases.
The need to use more specific ones sometimes.

For internal and external audiences.
We want to encourage the less specific keys so that we dont have so much duplication i the language files.



 Comments   
Comment by Martin DrĂ¡pela [ 04/May/16 ]

The context of i18n key generators will be described here:
https://documentation.magnolia-cms.com/display/DOCS/Internationalization#Internationalization-i18nmessagekeys

A new i18n best practices page is here:
https://documentation.magnolia-cms.com/display/DOCS/i18n+best+practices

Comment by Christoph Meier [ 16/Jun/16 ]

We have now the page Generic i18n keys and their list and we are also explaining a bit how to create a custom Keygenerator (etc pp), see I18nable and I18nText annotations ...
...
however, to list the existing keygenerators is not really needed (imho).

Generated at Mon Feb 12 01:11:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.