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


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vstuart.foote@utsa.edu

--- Comment #10 from V Stuart Foote <vstuart.foote@utsa.edu> ---
Samuel's suggestions in OP ( comment 0 )of pulling text from  specific Style
are fine--certainly better than grabbing the first string encountered.

Suggest also the File -> Properties dialog: Description tab any entries made to
the Title, Subject, Comments or Keywords fields (given a hierarchical
preference in that order).  These fields are always picked up and incorporated
into the ODF  meta.xml as "Dublin Core" DCMI (ANSI/NISO Z39.85 and ISO
15386-2009) values, i.e. dc:title, dc:subject, dc:description, and meta:keyword

Seems reasonable to parse them first as potential for automated file naming
ahead of content from the document styles listed.

Also, can see some utility in improving the GUI (status bar/dialog/navigator)
related to metadata manipulated via the File -> Properties dialog, especially
with ongoing addition of CMIS and other "Cloud" formats.

Naming a file on initial save to ODF is just the facet here.

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