https://bugs.documentfoundation.org/show_bug.cgi?id=102249
Yousuf Philips (jay) changed:
What|Removed |Added
Keywords|needsUXEval |
CC|libreoffice-ux-advise@lists |
|.freedesktop.org|
Blocks||102345
--- Comment #15 from Yousuf Philips (jay) ---
(In reply to Armin Le Grand (CIB) from comment #9)
> I personally use non-printing characters as blanks and CR in my code editor,
> and it would be possible to do this for EditEngine, too, but - the question
> is - where is the win?
I would assume that it would be a win in writer for a setting that affects all
text of the document to also affect text in shapes and textboxes, else it feels
like broken functionality.
> Of course one glance on the EditView compared with
> klicking in it and using the cursor keys to travel over the parts in
> question, but really quite some work to be done to do this and to guarantee
> that this is only shown in the EditViews.
Well using the cursor key wont tell you if a space is a regular space or a
non-breaking space, or with soft hyphens appearing as if something is between
the two characters, but a user unfamiliar with it wouldnt know what it was and
possibly would delete it.
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.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
