You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: