https://bugs.documentfoundation.org/show_bug.cgi?id=75914
--- Comment #6 from sergio.calleg...@gmail.com --- A couple of side notes: 1) A regression test for this can be easily implemented, there is no need to test against an old extension. It is enough to define a LibO macro that puts a string in containing the line termination char in a custom property. 2) IMHO custom properties should be used for tasks where properties need to be stored by the user and there is no other obvious interface for the user to enter them. In the case of extensions such as texmaths that need to store big chunks of data that is 'private' to the extension and for which the extension offers its own user interface, custom properties seem not very appropriate to me. In fact, big chunks of data tend to clutter the document custom properties significantly (think of an extension that decides to use 1000 custom properties for which it is the only user... this would make the custom property dialog very polluted and difficult to search). If I read the odf standard properly, there is the possibility to store "Text content being used as RDF metadata. Sec. 4.2.1" see http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#InContentMetadata. Now, I wonder if LibO provides an API to macro writers for this. If this is the case, extension writers could be incouraged to use this option when they have relatively large chunks of data to store. If currently there is no API for this, it may be worth providing it. Custom metadata (custom XML elements within meta.xml). Sec. 4.3.1 http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#CustomMetadataElements could be an alternative, but I see it is in being deprecated. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
