[OASIS Issue Tracker] (OFFICE-4131) Inline content controls for text documents

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OFFICE-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=81581#comment-81581 ] 

Regina Henschel commented on OFFICE-4131:
-----------------------------------------

More information about this new feature are given by Miklos Vajna in

[https://vmiklos.hu/blog/sw-content-controls.html]

[https://vmiklos.hu/blog/sw-content-controls2.html]

Â

> Inline content controls for text documents
> ------------------------------------------
>
>                 Key: OFFICE-4131
>                 URL: https://issues.oasis-open.org/browse/OFFICE-4131
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Improvement
>            Reporter: Regina Henschel
>            Priority: Major
>         Attachments: demo.docx, demo.odt
>
>
> Proposal from Miklos Vajna:
> h2. Use cases
> A content control is one way of adding fill-able pieces to a text document. It has the following properties:
>  * inline content controls always start and end inside the same paragraph, unlike bookmarks
>  * content controls are well-formed XML elements: this allows nesting, but intentionally doesn't allow bookmark-style random start/end positions in the document
>  * content controls have a set of properties, allowing the user to interact with them
>  * content controls can contain rich text, similar to {{<text:meta>}}
> h2. proposed types (can be extended later)
> *Rich text content control:* this is similar to {{<text:text-input>}}, but it can host formatted text, not just a string.
>  *Checkbox content control:* interacting with this type alters if the checkbox is ticked or not
>  *Dropdown:* this allows choosing one value from a list of choices.
>  *Picture:* this is similar to {{<text:placeholder text:placeholder-type="image">}}, but a placeholder image is already part of the document, so a template author can set its properties before providing the actual picture.
>  *Date:* this allows selecting a day from a calendar, provided a wanted language and date format.
> h2. Alternatives considered
>  * bookmarks also allow marking a range of formatted text, but they can start and end in different paragraphs and they don't support convenient interaction (e.g. checkbox, date, etc.)
>  * fields also support hosting some special content, but can't be nested
>  * form controls also support e.g. choosing one item from a list, but they can't be part of the document text to have formatting, breaking to multiple lines, etc. language and date format.
> h2. Impacts
> *Conformance:* This proposal will not add any mandatory features or behaviors.
>  *Backwards compatibility:* This change will not impact existing ODF processors, the usage of the new element is optional.
>  *Accessibility impact:* This change will not impact accessibility.
>  *Interoperability:*
>  OOXML's wordprocessingML has a {{<w:sdt>}} markup to describe a similar feature, this proposal allows roundtripping that feature in ODF. LibreOffice 7.4 implements this layout feature in its ODF extension namespace.
>  Note that this proposal introduces markup for inline content control, {{<w:sdt>}} can also represent block/row/cell content controls as well, while this proposal focuses on inline content controls.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)