i18n: sprintf-support for template-translation

[ischommer]

this is basically stopping us from translating some template-parts now (if we don't want to heavily fragment the entities). not very many cases, but would be handy anyway.

[sminnee]

I'm deprioritising this, but Bernat, it would be good if you could have a look at it as time permits.

[ischommer]

sam, this shouldn't be marked as "minor" - it prevents people from completing a translation. Especially with the currently high level of active translators we should solve this soon - it will be a lot harder to get people to complete their work later on than provide the opportunity now.

[sminnee]

Should we try and put this into 2.2.2, then? Bernat, would you be able to get this fix, and the translated entities that sprintf support would allow, completed by 18 Jan 2008?

[severin.schols]

since i'm working on making the ecommerce-module translatable for the google highly open participation contest, i created a patch to enable sprintf-support in tempatlates so use for translation. it's used like this (_t function inside of sprintf): <% sprintf(_t(...),$argument) %> it simply translates into the php function, but currently only supports one argument.

[severin.schols]

apply to sapphire/core/SSViewer.php

[ischommer]

patched in r46162 - thanks heaps severin! i've added an enhancement ticket to support more than one argument for sprintf: http://open.silverstripe.com/ticket/1952, but thats minor priority for now :)