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


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |erack@redhat.com,
                   |                            |libreoffice@kohei.us,
                   |                            |vstuart.foote@utsa.edu

--- Comment #23 from V Stuart Foote <vstuart.foote@utsa.edu> ---
I'd like dev input, but believe a parsing filter set from the CSV input dialog
will always be necessary to assure correct data type handling. End of story.

However, the nuisance to users is that there is no means to capture/reapply the
CSV filter, and they must repeatedly work through the dialog, even if defaults
are correct. More so if they have a fairly complex CSV file that requires data
type settings on multiple columns.

Seems there should be a means to capture the parsing/formatting filter for
reuse against _recurring_ CSV files, even in multiple LO sessions--so filter(s)
would need to be held in user profile. 

Then adding an option to by-pass the dialog popup (for GUI use) when applying
that filter from profile would be reasonable. And probably would want something
for use with CLI conversions.

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