You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our other official clients do something similar, trying to determine the language from the user's system if possible, and simply passing it on to the API. Of course this isn't perfect, but it solves most cases. If the language isn't correct, a user can always change the post's language via the API, or in the web app:
Publish a post
Click "edit"
Click the small "i" icon near the top right of the editor
Select a different language
Let me know if I missed something. But I'll close this for now since it doesn't seem to be a bug.
Thanks for the hint.
It's ok for me, but I still think that for average users, a UX during the writing would be better than one after.
But that's your design, I'm fine with the current solution!
Describe the bug
It seems that the language metadata is always "en", even if the text is not obviously.
I checked that with the API
/api/posts/
Steps to reproduce (if necessary)
Steps to reproduce the behavior:
Expected behavior
If no language is specified by the user, use the "und" value specified in ActivityStreams: https://www.w3.org/TR/activitystreams-core/#naturalLanguageValues
As a new feature: offer the UX to the user to specify the post language, on a post or blog basis.
Application configuration
Version or last commit: 0.9.1-104-g541c3a9
The text was updated successfully, but these errors were encountered: