Hi All,
On some francophone communities, ou friend @Camus@lemmy.blahaj.zone has run a couple of tests to understand how does language tag work in community with a default language. See that thread (En Français) for details.
The interesting part is that the behaviour changes based on which instance you post from (I believe all the tests have been done /c hosted by jlai.lu ) To summarize if the community default language is french a post from Lemmy.ca or Blahaj would be automatically tagged as in french while a post from SJW and lemmy.ml won’t get automatically a language tag.
I haven’t run all the test by myself and just agreed to be the messenger as someone using SJW. No idea whether it’s just about setting a flag user-side, or whether it’s a very specific lemmy version which enable this discussion.
A short note on language tags too. Not only, they avoid to deal with that frustrated person downvoting content they don’t understand. But I’ve read a nice Mastodon thread about how they matter for visually impaired user who need their screen-reader to know which language they read. So they’re very relevant.
Finally, while I’m complaining to our beloved great admins. I’ve seen that I tried to write that post in French first, but was blocked due to language setting, c’est dommage pour une instance bilingue
The automatic language tag should only depend on the community language settings and user language settings. Specifically it will build the intersection of both, and if the result only contains one item (excluding “undetermined”), that is used as the post language. The instance doesnt matter at all. And there havent been any changes in this area in a while, so there should be no difference between 0.19.x versions.
I thought maybe the community language isnt federated properly but its identical on all mentioned instances. Also @Camus@sh.itjust.works mentioned that French is enabled in user settings. There is clearly a bug but I cant think what else might be causing it.
Anyway please report such bugs directly on the issue tracker, otherwise I might not find out about it at all.
Hey, Thanks for coming here. My concern before going tot the issue tracker is that it seems to work on some instance and not on some other. so it was not clear whether it’s an instance specific problem or a software issue. hence firstly a discussion here.
If necessary I can try to open a ticket on the github.