Date: prev next · Thread: first prev next last
January 2015 Archives by date, by thread · List index


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

--- Comment #18 from Simo Kaupinmäki <isokumma@gmail.com> ---
Created attachment 112798
  --> https://bugs.documentfoundation.org/attachment.cgi?id=112798&action=edit
Use of special characters 2.0

Thanks for the comparison table, which certainly helps in seeing the big
picture. However, there seems to be confusion about some Unicode characters, so
I have reordered the table and added background colors in cells as an attempt
to make it a little clearer overall. I have also omitted some of the name
variants (including the German names) and instead added new columns for
line-break behavior, samples and notes. The character list is still not
complete, since Unicode has, for example, many more space characters in
different widths, but most of these allow line breaks in the same way as the
normal space, so I don't regard them as particularly problematic here.

I think the primary concern is to be able to show and identify any character
that behaves differently from what the user is likely to expect. As far as I
can see, exceptional line breaks are the most common case of this. 

(Also take notice of the comments included in the original table by Harald.
These have been omitted from my version.)

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

Context


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.