On Wed, 2012-12-05 at 10:52 +0000, Jack Leigh wrote:
I wonder - could we not provide some compile-time lint tool for this to
catch & warn/fail on bad strings ? presumably that would solve the
problem permanently in a way that doens't require lots of ongoing
care ? :-)
Also are they 3 stops or unicode ellipsis? This would also catch that.
Might force LibreOffice into glyph fallback in a lot of cases I suspect.
C.
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.