Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Localisation of built-in content types #5995

Closed
aro opened this issue Jan 23, 2018 · 0 comments
Closed

Localisation of built-in content types #5995

aro opened this issue Jan 23, 2018 · 0 comments
Assignees
@aro
Labels
Improvement

Comments

@aro
Copy link
Contributor

aro commented Jan 23, 2018

Set localisation keys in the built-in content types:

  • displayName
  • description
  • input labels
  • input help-text

Add the i18n properties files with the keys for 2 languages, and empty files with placeholders for the other languages supported in xp-apps.

Research how to resolve the bundles, since the appKey for built-in types is a "virtual" name (e.g. "base", "portal", "media")
@aro aro self-assigned this Jan 23, 2018
aro pushed a commit that referenced this issue Jan 25, 2018
Localisation of built-in content types (#5995)
368f553
GlennRicaud added a commit that referenced this issue Jan 26, 2018
@GlennRicaud
Merge pull request #6009 from enonic/issue-5995
4932034 
Localisation of built-in content types (#5995)
aro pushed a commit that referenced this issue Feb 28, 2018
Localisation of built-in content types (#5995)
f1dd1c7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aro aro

Labels
Improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aro @alansemenov