Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(NFC) Fix typo - no hyphen in 'override' #16571

Merged
merged 1 commit into from
Feb 17, 2020

Conversation

wmortada
Copy link
Contributor

Overview

Very minor change to fix a typo. There is no hyphen in the word 'override'.

Before

Incorrect spelling: 'over-ride'

image

After

Correct spelling: 'override'.

image

Technical Details

None.

Comments

None.

@civibot
Copy link

civibot bot commented Feb 17, 2020

(Standard links)

@civibot civibot bot added the master label Feb 17, 2020
@wmortada wmortada changed the title Fix typo - no hyphen in 'override' (NFC) Fix typo - no hyphen in 'override' Feb 17, 2020
@demeritcowboy
Copy link
Contributor

I'm not trying to block this and obviously technically it's correct and this makes it look more professional, but this is a good example of what I was trying to get clarification on in https://github.com/civicrm/civicrm-dev-docs/pull/754/files. When does the benefit outweigh the downside of having to retranslate this string in all languages which can take a couple release cycles during which time it goes back to being untranslated. I don't know the exact answer - maybe spelling mistakes should always be fixed all the time, as opposed to when it's something more technical. If so, it would be good to get that clarification.

@eileenmcnaughton
Copy link
Contributor

That's a tough one @demeritcowboy - I've understood it to be 'change it once & change it right'

For now I'm merging this - even though I kinda like the hyphen I accept google didn't support me in that

@eileenmcnaughton eileenmcnaughton merged commit e585012 into civicrm:master Feb 17, 2020
@demeritcowboy
Copy link
Contributor

Ok I'll see if I can add something to the docs PR.

@wmortada
Copy link
Contributor Author

@eileenmcnaughton thanks for merging

@demeritcowboy I think you raise a good point here and it would be good to clarify best practice. My inclination would be to fix spelling mistakes (particularly when it is inconsistent on the same page as in this case). However, I don't think I fully appreciate the impact that this has on the translations so it is certainly helpful to be mindful of this.

In this particular case is there a way of keeping the translations as they are currently? i.e. could the translation strings be copied so that the existing translations apply to this slightly modified string? (Apologies for my ignorance about how the translation system works.)

@wmortada wmortada deleted the over-ride branch February 21, 2020 10:56
@demeritcowboy
Copy link
Contributor

It's an interesting thought about keeping the current translations/copying them over, but it's hard to say when you do and don't want that. For example the particular string in this PR is also spelled wrong in some translations, e.g. en_GB (https://lab.civicrm.org/dev/translation/blob/master/po/en_GB/member.po#L1627), so you don't want to keep it.

The process is described at https://lab.civicrm.org/dev/translation/-/wikis/Pushing-new-strings-to-transifex and related documents on that wiki https://lab.civicrm.org/dev/translation/-/wikis/home. But a complication is that it's not fully automated because some of it needs to be manually weeded by someone - see the 3rd paragraph in the description at https://lab.civicrm.org/infra/ops/issues/931. So anyway if you're curious those are some docs to read.

@wmortada
Copy link
Contributor Author

Good point!
Thanks for the links. Helpful to understand how the process works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants