This is one of the reasons I plan to avoid using OO.ui.BookletLayout in one of my scripts and switch to OO.ui.IndexLayout. Or hack into OO.ui.MenuLayout. For me, this has nothing to do with specific languages. The worst part is that you can't even see the full name on hover. Basically, you are left to guess what's in the part after the ellipsis.

We are sort of already tracking this in T337865, although that's specific to buttons and it sounds like you're request general guidelines on truncation (as opposed to a specific solution for one type of use case).

I think button wrapping is valid to handle separately from general truncation. Since in the buttons, there can be some instances where you cannot put entire button text on the available screen space (e. g. the button in the example screenshot above). Though I would argue that in the ideal world even such cases should be handled by adapting design in the languages where the button gets truncated, or fixing the word usage, etc., and not cutting off text that can be valuable to understanding what the button in question does.

I agree there are two components to this:

• Providing best practices in the guidelines to avoid situations where truncation happens at all.
• Providing good built-in tooling for truncation when it is used. There should always be some way to see the entirety of the text being truncated, like through a tooltip as suggested in T337865.

It is strange to me to close the older task as a duplcate of the newer one, but alright.