Policy on custom fields translations

RT Developers
1

I’ve received the following answer about translating CF in this ticket:

As a general rule of RT, we don’t translate Custom Field names.

It’s not consistent, I mean, CF can’t be translated while all other fields can be translated in local po files. Is there any reason?

Searching for this topic in the forum, I see that it’s demanded since 2010. So I’ve added loc() functions in some files (RT 5.0.7 and FormTools plugin):

  • /opt/rt5/local/share/html/Elements/EditCustomFields
    • Line 68: <span class="<% $CustomField->EntryHint ? 'prev-icon-helper' : '' %>"><% loc($CustomField->Name) %>:</span>\
  • /opt/rt5/local/share/html/Search/Elements/PickCFs
    • Line 62: $line{'Field'} = loc($CustomField->Name);
  • /opt/rt5/local/plugins/RT-Extension-FormTools/html/FormTools/Field
    • Line 58: $field_label ||= loc($cf->Name)
    • Line 172: <div data-name="<% $cf ? loc($cf->Name) : '' %>"
  • /opt/rt5/local/plugins/RT-Extension-FormTools/html/Admin/FormTools/Modify.html
    • Line 187: <span class="content"><% loc($item) %> <span class="label"></span></span>

I hope this changes help someone. If someone find other files to update (articles, assets, etc.) please, paste your code here (or file name and the line number).

1 Like