|
· Föderation EN Mo 17.06.2024 00:29:10 @libreoffice ... but it gets worse. Because it turns out, the Accessibility Check was faulting *every single paragraph* for the same thing, even for the majority that had no direct formatting, or even character styles, in them at all that could be revealed by the user interface. So basically, that's useless. Useless false positives unless it can explain to me what's wrong. |
|
Föderation EN Mo 17.06.2024 00:37:24 @libreoffice I mean, it would mark a whole paragraph and say "there's direct formatting in here" and I'd be thinking "no there bloody isn't; nothing that I've done, and nothing visible” But if I do a manual clear direct formatting, the warning disappears, so there *was* something. But it was nothing *I* did. So wtf? *Any* manual fix for this is unscalable. The default action should be correct. |
|
Föderation EN Mo 17.06.2024 00:39:00 @libreoffice accessibility check faulting every single damn paragraph when all you've been doing is typing, is useless. the only sane reaction is, "sod that then”. |
|
Föderation EN Mo 17.06.2024 00:54:12 @libreoffice ok, maybe I've wrangled the cmd-I, cmd-B to toggle emphasis and strong-emphasis respectively (it being necessary to restart the app for the toggle to work). Let's try living with that for a bit. It's customary to also use italic text for certain foreign or out-of-context words. Semantically I wonder what that should be called? Emphasis seems wrong. |
|
Föderation EN Mo 17.06.2024 08:42:58 @StrangeNoises Hi! It's hard for us to help without any details about your setup (LibreOffice version, operating system etc.) If you think it's a bug, please let our QA community know at https://bugs.documentfoundation.org with some details about your setup, so that they can investigate. Thanks! |
