[Libreoffice-ux-advise] [Bug 154766] management of ellipsis variants

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=154766

--- Comment #6 from toddwarner at duck.com ---
Note: This bugzilla is not asking how to insert a U+2026. That's not the issue.
It's that the U+2026 is an APA-styled ellipsis (three dots, no spacing
between). Most other styles require and ellipsis formatted as three dots,
spaced between. I hope that wasn't confused. Anyway . . .

Can someone comment who has written for traditional publication, please? Maybe
that is no one. Dunno.

What you shared is 100% a workaround. Well, except for this, which doesn't even
rise to that level: "Not seeing an issue. U+2026 with OpenType stylistic
alternative for the opened spacing of the ellipsis is already supported--UI is
the Character dialog." That only works if you use a typeface that will support
it (none do that I know of, and not Times New Roman) and only if you know how
to trigger it. 99.999% of the users do not.

I have long had LibreOffice autocorrect to .[NBSP].[NBSP].. That is definitely
a workaround and not an end solution. That is also what everyone largely does,
or they just use three spaced-out dots and individually deal with the resulting
word wrap and formatting issues. This is fine-ish. But it is a brute-force,
non-ideal solution. Plus, it breaks the grammar-checker and other things since
LibreOffice doesn't see an ellipsis.

Whatever. My RFE was a stab in the dark. I expected this response pretty much
since no one from the word-processing world has resolved it. It'll take the
Unicode community to make it a reality, I am sure.

In the meantime, I hope I triggered someone to think about it.

Cheers. -t

P.S. The two dashes '--' that you used above instead of an emdash '—' is also
no longer a "workaround" if you are publishing professionally. An actual emdash
is expected. Thank goodness that's available. Maybe someday the
Chicago/MLA/etc-style ellipsis will be as well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.