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
Add notranslate class to addresses #348
Add notranslate class to addresses #348
Conversation
Tied to Issue: code4recovery/12-step-meeting-list#1092 Wrap display of addresses with "notranslate" to deny Google Translate from translating native language addresses
✅ Deploy Preview for tsml-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks awesome, thanks! mind taking the console.info
out though?
@joshreisner updated the two things. Not sure if you want commits squashed in PR, some repos ask for that. Let me know if anything else is outstanding. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
thanks @gkovats ! i have to merge it because the tests aren't passing - we haven't refactored those from the last pr yet i'll 'squash & merge' - no need to squash PRs before the merge though |
Tied to Issue:
code4recovery/12-step-meeting-list#1092
First PR, could be missing some steps, glad to adjust and fix. The issue was Google Translate goes nuts and translates native language addresses to the target language, but this obfuscates addresses. GPS / map tools drive off native language addresses.
Wrapping display of addresses with "notranslate" to deny Google Translate from translating native language addresses. This comes from the Issue, assuming this is sufficient - hard to test locally as Google Translate requires a public site.