[MGNLSTK-221] A module-wide i18nBasename would be nice Created: 14/Oct/08  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MAGNOLIA-1519 i18n should be definable at module level Closed
relation
is related to MAGNOLIA-2748 i18n: bundles should be chainable in ... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

It's quite cumbersome to set the i18n property for each and every paragraph, template, dialog, ... It seems a single value shared across a complete module would be sufficient.



 Comments   
Comment by Jan Haderka [ 26/May/09 ]

not only module wide, but also site wide i18nBasename would be nice. It would be also nice if such value exists, if it can be used as a fallback for properties not found in the message bundle that was specified.
Useful for extra stk templates added by other modules (e.g. newsletter). Currently, either messages for such template (title and description) have to either be added to the stk template bundle, or the other messages used in the template page (extras.newLabel, basename.newLabel, etc. ) have to be copied to the module specific message bundle used by the template.

Comment by Magnolia International [ 26/May/09 ]

Funny, I'd already reported that 18months before: MAGNOLIA-1519

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 07:24:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.