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
Initial work on language-negotiation materials #581
base: gh-pages
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for i18n-drafts ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
I think this needs to include analysis about the potential privacy implications. In particular for minority end users. In some sense, complete customization based on the end user's preferences is rightly an ideal, but that needs to be weighed against websites being largely unvetted applications that might not have the end user's best interests in mind. |
@annevk Thanks for the comment. This material was written from the point of view of a website owner/developer, so, of course, doesn't currently include such considerations. That said, it probably should have already included some admonition about not exposing user preferences to third parties. I agree that privacy implications need to be addressed and will add some text about that shortly. Comments/suggestions welcome. |
The scope of this article seems to have some overlap with our existing article, both covering when language negotiation should be used. The existing article contains more examples. Should we probably introduce the concept of language negotiation in this article, and introduce when we should use language negotiation in our existing article? |
I started to convert some non-prose (powerpoint) presentation materials to prose describing language negotiation. This PR is not ready to merge, as more material needs to be added and the text given a thorough edit. However, it is provided for commentary.