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

Translation Script Follow-up #575

Open
ColinBuyck opened this issue Dec 19, 2022 · 1 comment
Open

Translation Script Follow-up #575

ColinBuyck opened this issue Dec 19, 2022 · 1 comment

Comments

@ColinBuyck
Copy link
Collaborator

Following the missing translation script (#572), it was discovered that there are a bunch of jurisdiction translations missing that are already translated in ui-components. For example the ones listed in San Mateo for the footers is the same wording as the one in ui-components. We want to do a follow up script to remove the duplicate translations before we send the missing translations to the clients so they don't have to translate strings we have already translated

@ColinBuyck ColinBuyck self-assigned this Dec 19, 2022
@sarahlazarich
Copy link
Collaborator

Related to this, I took a pass at cataloging fields that weren't picked up by the script & fields that were picked up by the script but ended up being translated for all jurisdictions. There aren't a ton of either of those, but thought it would be useful to have broken out for when we go through this process in the future. I also included a tab in this document for potential improvements, or fields that I filtered out manually that maybe could be handled by the script.

https://docs.google.com/spreadsheets/d/1D0U8QKVn7K5SF6kSJJ_Dtg05uMeshrvxV3wnuwPWGI8/edit#gid=2099708733

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

No branches or pull requests

2 participants