https://bugs.documentfoundation.org/show_bug.cgi?id=160249
--- Comment #6 from Eyal Rozenberg <[email protected]> --- (In reply to Eyal Rozenberg from comment #4) Sorry, I messed up that reply by confusing arbitrary and undetermined. Let me take that back and reply again. (In reply to Stéphane Guillou (stragu) from comment #2) > Seems to me like very niche use case. It is a somewhat a niche case, but then - there quite a lot of highly-obscure, probably-not-spoken languages that we support. I mean, this would have wildly more usage than runic ancient Hungraian... > We already have "no language" Do we have "no language"? Where? And - it's important to have "arbitrary"; but I agree it's not as important as having "no language" or "undetermined language". > It's not a label that you assign to some text Why not? And remember, we're mostly focused on a post-151920 situation. > Ultimately there is no use case that you solve. Like with any language code, the use case is telling the app/the reader what is known and not known about the language of a piece of text. That's both a use case for automated tools and for manual editing. -- You are receiving this mail because: You are the assignee for the bug.
