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


Caolán McNamara wrote (21-12-10 21:17)
On Tue, 2010-12-21 at 19:59 +0000, Wols Lists wrote:
Seeing as LO is based on XML as the document format it should be easy -
all "reveal codes" is is a window with text and all the markup visible.

The thing is that, while the file format is XML, the file format doesn't
bear that much relationship to how the application actually
store/applies properties. There aren't actual codes embedded in the
strings whose display can be toggled on or off, so something like that
would require faking it all up.

On the other hand there's definitely a lot to be said for something like
a "format inspector" which describes from where and why something is
formatted like it is.

I do not so much believe in the old WP-style of 'reveal formatting' since I know OOo. As a style addict, and knowing where to find Ctrl-M, it's easy to tackle most...
Said that, indeed a (new style) pop-up to show
 - para style
 - char. style
 - direct (hard) formatting
would be useful, at least for many users.

Making this as an extension is not that difficult. (It might even exist already?) Thinking about adding it to the core code (which is way beyond my competences) I would say the the format paintbrush will have some interesting code to re-use ;-)

Best,
Cor


--
 - giving openoffice.org its foundation :: The Document Foundation -


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.