-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Accept BCP 47 language tags in the statuses API #23541
Comments
I wonder if this is an adoptable solution, and if so, whether there is anything I can help with. |
I guess we could bring this issue on IRC? There must be a primary discussion space for Mastodon devs, and we’ll need some attention before even convincing the merge. |
@rschiang Hi, I'm not very familiar with the actual ecosystem of Mastodon development. I am definitely ready to make a some kind of pitch if you can help me into a right place to do. |
Just from my other comment:
|
Pitch
Currently, I see three parameters that take an ISO 639 string in the statuses API.
POST /api/v1/statuses
:language
POST /api/v1/statuses/:id/translate
:lang
PUT /api/v1/statuses/:id
:language
I suggest that we should expand them to accept a well-formed BCP 47 string, or if any compatibility concerns, make another parameter (such as
locale
?) that can store them. The ActivityPub content property readily accepts BCP 47, so I think this is just a Mastodon API restriction.Motivation
ISO 639 alone is not a "practical" approximation of concrete languages people perceive
en-US
) vs BrE (en-GB
) and Brazillian Portuguese (pt-BR
) vs Portuguese Portuguese (pt-PT
), which Mastodon API cannot accept (edit: it was already reported in Consider the country when translating with DeepL #22707).it affects wider audience than Mastodon
The text was updated successfully, but these errors were encountered: