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


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

V Stuart Foote <vstuart.foote@utsa.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |libreoffice-ux-advise@lists
                   |                            |.freedesktop.org,
                   |                            |vstuart.foote@utsa.edu
          Component|Writer                      |ux-advise
            Summary|EDITING Feature request:    |EDITING: Add code window to
                   |Add code window for editing |expose and directly edit
                   |                            |XML with validation
           Severity|normal                      |enhancement

--- Comment #7 from V Stuart Foote <vstuart.foote@utsa.edu> ---
A bit beyond idea of Reveal Codes being exposed during WYSIWYG editing in
Writer, as proposed bug 34002 

But it sure would be handy to have direct cursor focused access to the XML
components (at least content.xml and styles.xml), that would be generated on
document save, available during editing to be able to make document changes 
with validation there.

Could see this being a useful UI for all LO modules.

-- 
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.