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


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |108479
                 CC|                            |libreoffice-ux-advise@lists
                   |                            |.freedesktop.org,
                   |                            |vstuart.foote@utsa.edu
           Keywords|                            |needsUXEval

--- Comment #1 from V Stuart Foote <vstuart.foote@utsa.edu> ---
There would rarely, if ever, be a 1-to-1 mapping so we would have to provide a
UI to manually make the style assignments. 

Or if done more simply, i.e. import into target document with template
default(s) for the element type(s), could ask user to validate the import to
that style--or choose to make it unformatted text. More involved would be to
offer import to a different style than template default(s).

But at least it could clear out the source document style(s) and not bloat the
target document.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108479
[Bug 108479] [META] Paste special bugs and enhancements
-- 
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.