https://bugs.documentfoundation.org/show_bug.cgi?id=75914
sergio.calleg...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|medium |lowest
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Severity|enhancement |trivial
--- Comment #5 from sergio.calleg...@gmail.com ---
My feeling is that the odf standard should be the rule here.
In principle, if it allows custom properties to contain special characters,
then the UI of LibO should not remove them. According to the standard, a
custom property of type 'string' ('text' in the LibO interface) should allow
#x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF]
(any Unicode character, excluding the surrogate blocks, FFFE, and FFFF).
If LibO decides to remove any of these, the same incident that happened with
texmaths could happen in the future with new extensions, or one might end up
breaking documents made with other production tools compatible with the odf
standard.
In fact, the LibO roundtrip is already OK, because when LibO loads+saves a
file, it preserves these chars. The only issue is that when opening the
document-properties dialogue and editing /any/ custom property, /all/ the
custom properties get deprived of some of the special characters.
So, the whole issue is confined to the management of an interface dialog and
the
point is how to fix it without complicating too much the codebase. IMHO, there
is no need to provide interface elements to let one enter special characters in
the custom properties, and it can even be acceptable to remove special
characters from those entries that are edited. So the only thing that should be
avoided is the cleaning of properties that are not being edited.
It would probably be enough to have a "modified" flag associated to each custom
property row in the interface and to restrict the update of custom properties
inside the document to those that get the "modified" flag set.
Since no known extension currently depends on special chars in custom
properties, this can be a very low priority task. But I would confirm the bug
and keep it open as a reminder of the minor issue with the odf standard (e.g.
Priority -> lowest, Severity -> minor or trivial).
--
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
