8000 Internationalization support for the nunjucks templates · Issue #55 · perfood/couch-auth · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
8000

Internationalization support for the nunjucks templates #55

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.

Sign up for GitHub

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

Jump to bottom
Open
fynnlyte opened this issue Sep 7, 2022 · 2 comments
Open

Internationalization support for the nunjucks templates #55

fynnlyte opened this issue Sep 7, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@fynnlyte
Copy link
Contributor
fynnlyte commented Sep 7, 2022
  • use header information from the requests to determine the current language
  • use some configurable folder structure or whatever nunjucks offers to send out a localized template based on the language header
@fynnlyte fynnlyte added the enhancement New feature or request label Jan 24, 2023
@suchyjan
Copy link

It is great idea :) It should be able to send a header to local.confirmEmailRedirectURL too or using parameter to callback ?success=true&lang=en or "error=...lang=en" for example to be able to display correct localized html page to the user.. The language can be also set on registration as field and saved in sl-users, but if someone wants to change the language on that user, that should be than possible by another api call for example. Or better approach can be the custom header for every API call.. And of course some change to nunjucks folder structure templates/[lang]/email with some default lang (as en) fe. I vote for this enhancement :) Thank you.

@fynnlyte
Copy link
Contributor Author

It should be able to send a header to local 60C1 .confirmEmailRedirectURL too or using parameter to callback ?success=true&lang=en or "error=...lang=en" for example to be able to display correct localized html page to the user.

Yeah, that makes sense.

The language can be also set on registration as field and saved in sl-users, but if someone wants to change the language on that user, that should be than possible by another api call for example. Or better approach can be the custom header for every API call.

Or maybe just use the Accept-Language Header. I don't think I want to add setting a language via sl-users in couch-auth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fynnlyte @suchyjan
0