Localised prototype data #58
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 7 commits
November 25, 2020 13:30
Takes a series of CSV files with replacement text for the various names and strings in the prototype data, plus a locale to write them to
I've moved the existing en and es prototype data into subfolders and updated the management/fixture loading commands to include the current LANGUAGE_CODE setting in the path they look for prototype data. This allows us to load different prototype data with moving data around manually.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Related to #57 - this is additional localisation work we've been doing at Open Ownership to make the following sites:
We've sketched out a spreadsheet-based substitution method for localising the prototype data, where we've got some folks with locale-specific expertise to adapt the data to their contexts and then created duplicates of the BODS/OCDS files with these modifications made to them. There's a new management command to actually make the changes, plus some modifications to the data loading scripts so that if you've set a
LANGUAGE_CODEsetting, it'll look for the appropriate prototype data.I think this is probably a bit too rough and ready for inclusion as-is, but in the spirit of sharing, I'll let you be the judge! There's no documentation as yet, but I can add some and tidy this up if it's interesting - it's still a bit of a manual process.