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

Localization of user-facing strings #31

Open
rrix opened this issue Nov 2, 2021 · 2 comments
Open

Localization of user-facing strings #31

rrix opened this issue Nov 2, 2021 · 2 comments
Labels
Future Consider this further in the implementation phase
Milestone

Comments

@rrix
Copy link
Collaborator

rrix commented Nov 2, 2021

I've put a big "ugh" field around this during protocol development, but there is a simple issue: some strings in the requests and metadata will be necessarily presented to users and not all of them speak English or tech-ese

Cataloging these and then thinking about how to localize them is gonna be a "fun time"

@rrix
Copy link
Collaborator Author

rrix commented Nov 2, 2021

it's obvious that some of these things can be inferred at load-time (check browser localization headers, use localization settings from verified account) but for things like a list of access categories or possible relationship hints, those could even vary by locale..

@rrix rrix added the Future Consider this further in the implementation phase label Nov 2, 2021
@rrix
Copy link
Collaborator Author

rrix commented Sep 16, 2022

mark strings which may be visible to consumer, ask the content to respect Accept-Language headers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Future Consider this further in the implementation phase
Projects
None yet
Development

No branches or pull requests

1 participant