https://bugs.documentfoundation.org/show_bug.cgi?id=121182
V Stuart Foote <vstuart.foote@utsa.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|NOTABUG |WORKSFORME
Blocks| |102345
See Also| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=58
| |434
CC| |vstuart.foote@utsa.edu
--- Comment #8 from V Stuart Foote <vstuart.foote@utsa.edu> ---
IMHO believe => WFM is the more appropriate resolution.
Input is correctly handled by applying the U+200E LEFT-TO-RIGHT MARK [LRM]
with Insert -> formating mark, or Alt+X toggle provides expected typographical
behavior.
The same Left-to-right mark/Right-to-left mark UNO commands are available to
assign to menu, toolbar button, context menu, or Keyboard shortcuts.
Though establishing a default keyboard shortcut _might_ be appealing for some
locales.
Otherwise enhancements of see also bug 58434 for showing formatting marks when
displaying non-printing characters remains to be implemented, still mostly as
in table of attachment 112798, would improve the UX by exposing use of the
Unicode control.
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=102345
[Bug 102345] [META] Formatting marks (aka Non-printing characters) bugs and
enhancements
--
You are receiving this mail because:
You are on the CC list for the bug.
Context
- [Libreoffice-ux-advise] [Bug 121182] Western acronyms not correctly formatted in RTL context · bugzilla-daemon
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.