2
Self-hosting version need i18n support
Source: supabase/supabase#11128 · opened by @forkpath
Feature request
> Self-hosting version need i18n support
Is your feature request related to a problem? Please describe.
> None
Describe the solution you'd like
> Extract the hard-encoded English description string originally located in the render template into the language package file and use the third-party i18n library to make the studio multilingual
Describe alternatives you've considered
> None
Additional context
> I really like supabase, the usability has been greatly enhanced when the Edge-Function come online. However, without the internationalized version, non-native english speaking developers will still have misunderstandings in using it.
> Self-hosting version need i18n support
Is your feature request related to a problem? Please describe.
> None
Describe the solution you'd like
> Extract the hard-encoded English description string originally located in the render template into the language package file and use the third-party i18n library to make the studio multilingual
Describe alternatives you've considered
> None
Additional context
> I really like supabase, the usability has been greatly enhanced when the Edge-Function come online. However, without the internationalized version, non-native english speaking developers will still have misunderstandings in using it.
No pledges yet. Be the first to back this.
Comments
Similar requests
Internationalization (i18n) Architecture for Supabase Studio
1 vote · 0 comments
Request: Internationalization for Authentication Email Templates
58 votes · 0 comments
Enable email Llanguage change based on frontend language
2 votes · 0 comments
Email Templates API
4 votes · 0 comments
Questions and Issues Regarding Local Deployment of Supabase
5 votes · 0 comments
No comments yet.