Translation: remove support for CiviCRM pre-4.5 l10n file locations #23435
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
When we added support for "native gettext" in CiviCRM 4.5, the file structure for the "mo" translation files (in the
l10n
directory) changed. Since few people used native gettext at the time, and since tooling had to be adjusted, we included a fallback mode so that the older file hierarchy still worked.8 years later, I think we can assume people have fixed their tooling, and use the expected file hierarchy ;)
Before
Fallback mode for
mo
files in the old location.After
Fallback removed.
Comments
I plan on adding an option to load extension
mo
files from the[civicrm.l10n]
directory. It's not directly related, but I saw this old code and wanted to tidy up first.