My translation is not working

[ceemjay]

Hi

Cant see a way to enter a person's "preferred name" as well as "given name" so thinking of using the Suffix field instead (almost never used in my English world)

I have tried changing the en_GB/LC_MESSAGES/messages.po file to add a translation and editing /locale/js/en_GB.js too but nothing changes. (I have set language to en_GB in Localization too!)

What am I missing? Is there a compilation phase?

Many thanks

[ceemjay]

Despite adding entries in BOLD
in locale/textdomain/en_GB/LC_MESSAGES/messages.po

#:
msgid "Suffix"
msgstr "Informal Name"

#:
msgid "State"
msgstr "County"

and in locale/js/en_GB.js
try {window.CRM.i18keys = {
"Suffix": "Pref Name",
"State": "County",

nothing seems to have changed on the data entry screens.

PS I changed the title as the original didn't elicit any response

[DAcodedBEAT]

@ceemjay Please don't update these translations manually. If you'd like to make any changes, feel free to do it here: https://poeditor.com/join/project/RABdnDSqAt

[ceemjay]

@ceemjay Please don't update these translations manually. If you'd like to make any changes, feel free to do it here: https://poeditor.com/join/project/RABdnDSqAt

Hi - thanks for the response. I came across that but assumed it was to modify common translations not a translation uniquely for our own system. Was I right in that?

To clarify I need another field for "Informal Name" (or aka) as we dont use the Suffix field so I was planning to use that as it appears in the right place in forms

The easiest way I can think of to do that is to change the legend on the form to say Informal Name instead of Suffix by using a translation for that one field name.

I realise this may break on updates but that's a risk we'll take.

Are you able help me to achieve my goal or do you have a better suggestion.

Thanks

[DAcodedBEAT]

@DawoudIO Again another reason for #6651 (#7185)

[ceemjay]

Was my question clear enough or did I omit to do or provide something else? Or is everyone too busy to answer what I hoped was a simple question?

[MrClever]

@DawoudIO Again another reason for #6651 (#7185)

As @DawoudIO stated in #6651 and I mentioned in the dev chat; that feature can be trivially implemented using a custom field. I still don't see any compelling and pervasive use case that warrants the code changing to implement it.