Pkp-lib: Make wording of editorial team consistent in backend and frontend

[lilients]

I think the different wording for the editorial team page (.../about/editorialTeam) at the backend is confusing.

Backend:

Frontend:

I would propose using the term "Editorial Team" instead of "Masthead" at the backend. This way backend and frontend would be consistent. I would propose to change this in OJS and OMP.

Following keys are relevant: manager.setup.masthead in manager.xml and about.editorialTeam in locale.xml.

I would add the locale manager.setup.editorialTeam and simply copy the string from about.editorialTeam to the new locale (and change all calls of the locale in the code ...). I can do this for all languages (that have the about.editorialTeam locale), this way no new translation work would be needed.

I would also change the storage of the string in the database from masthead to editorialTeam.

I can create pull requests next week. 🌞

[asmecher]

@stranack, any preferences?

[lilients]

I changed the wording of the input for the editorial team at the backend from masthead to editorial team in all languages that have the key manager.setup.masthead (These languages do not have it: ca_ES, cs_CZ, eu_ES, hr_HR, nl_NL, pt_PT, sr_SR, sv_SE, tr_TR, uk_UA, zh_CN) and in the table journal.settings.

Backend:

Frontend:

[bozana]

Thanks @lilients, I'll wait for @stranack to say... then I can take a look at the PR... :-)

[stranack]

This sounds like a sensible change -- go for it!

[bozana]

@lilients, those are the PRs, correct? -- Did I miss something?

[bozana]

Still missing translations:
OJS: eu_ES, hr_HR, nl_NL, tr_TR, zh_CN

[bozana]

PRs:
pkp-lib master: https://github.com/pkp/pkp-lib/pull/2992
ojs master: https://github.com/pkp/ojs/pull/1650
omp master: https://github.com/pkp/omp/pull/459

[lilients]

thanks @bozana!