Looking a bit through the extensive discussion, I noticed Ian
Laurenson's RevealCodes macro [2] from 2004. This seems to be the
closest to an implementation and could be used as an inspiration.
How about we open a bug?
Regards,
Philipp
[2] http://homepages.paradise.net.nz/hillview/OOo/ "RevealCodes3.sxw"
On 23 December 2010 01:30, Wols Lists <antlists@youngman.org.uk> wrote:
On 23/12/10 00:07, Philipp Weissenbacher wrote:
May I point you to the crazy idea "Add WordPerfect features like
RevealCodes and HiddenText" [1]
Actually, it was me that added that to the wiki page :-)
Also see the therein referenced OOo bug. It's been requested in 2002
and always dismissed with the answer "learn to use styles" *sigh*.
But I didn't know about that OOo bug. I'll need to learn styles, but yes,
*me* learning styles is totally useless when it's *someone* *else* who's
messed up *their* document (and expects me to fix it for them).
I think that's *exactly* *the* use case: fixing broken formatting.
Plus, I expect I may well soon be teaching people to word process. I shall
almost certainly be running WordPerfect under Wine, and making them use
reveal codes. Yep - WordPerfect 6.1 for Win 3.1, but imho the
pre-Corel-rewrite versions of WP are pretty much the best word processor
ever :-)
Just my 2 cents.
And my tuppence.
Cheers,
Wol
Context
- Re: [Libreoffice] sw: numbering misbehaviour (continued)
Re: [Libreoffice] sw: numbering misbehaviour · Caolán McNamara
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.