Ticket #1535 (closed enhancement: fixed)

Opened 14 months ago

Last modified 4 weeks ago

i18n: Namespace support in template translation

Reported by: ischommer Owned by: bfojcapell
Priority: minor Milestone:
Component: i18n Version:
Severity: medium effort / impact Keywords:
Cc: Hours:

Description

currently all template-entities are namespaced with their template-name, even if a different namespace is entered.

MyTemplate?.ss

<% _t('OtherNameSpace.Entity', 'bla') %>
// saved by textcollector as $lang['MyTemplate.ss]['Entity']

this means we're creating a lot of redundancy, and possibliy annoy translators by requiring them to translate the same strings multiple times :)

Change History

Changed 13 months ago by sminnee

  • priority changed from critical to minor

Our translation tools are currently pretty good - I think that we leave this kind of stuff for a wee while and actually wait until translators complain about issues like this. We want to focus the SilverStripe? team's development efforts elsewhere.

Bernat - this kind of thing would be a good thing for you to look at during your studies, as you have time. I don't think there are any time pressures on this.

Changed 13 months ago by ischommer

  • component changed from Sapphire Framework to i18n

Changed 4 weeks ago by ischommer

  • status changed from new to closed
  • resolution set to fixed

Fixed in r65361. In hindsight, we created a lot of (now legacy) implementations that cause us problems now by leaving this off for too long - we basically will have to namespace all includes manually and make sure they retain their "auto-detected" namespace for existing translations.

Note: See TracTickets for help on using tickets.