Page MenuHomePhabricator

Allow CentralNotice banner variables to be marked as non translated
Open, MediumPublic


Currently any central banner variable (added as {{{name}}} ) is added into the translate extension automatically. This is because the most common use case for the variables is translatable text. However, there are many occasions (especially for shared code) where you may want to use that variable as a 'variable' setting something for the whole banner. When this is the case you do not want to allow it to be translatable as it may make the code malfunction or behave in unexpected ways.

You should be able to mark something so that it does not get added into the translation system.

Version: master
Severity: normal



Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 2:04 AM
bzimport set Reference to bz51470.
bzimport added a subscriber: Unknown Object (MLST).
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 21 2015, 7:21 AM
awight added a comment.EditedOct 21 2015, 7:22 AM

Definitely--and we should call the untranslated parameters "variables" as you said!

DStrine set Security to None.
Restricted Application added a subscriber: TerraCodes. · View Herald TranscriptApr 19 2016, 8:21 PM

To clarify why I set T116235 as a dependency, if we managed to migrate banners to translatable pages, then this task would be unnecessary.

Base added a subscriber: Base.Feb 19 2017, 1:48 PM
mmodell removed a subscriber: awight.Jun 22 2017, 9:39 PM