1. RATIONALE
1.1 Use cases:
Borders around pages and paragraphs are already supported by
ODF. It's a natural request from the user to be able to have
borders around a few characters inside a paragraph as well. This
also improves interoperability with HTML or Office Open XML, as
both markups have a notion of character borders.
1.2 Alternatives considered:
None.
2. REQUESTED CHANGES TO THE ODF STANDARD
2.1 Text changes/additions:
Add the appropriate text properties for borders to 16.27.28 <style:text-properties> as following:
16.27.28 <style:text-properties>
...
The <style:text-properties> element has the following attributes:
... fo:border 20.176.2, fo:border-bottom 20.176.3 fo:border-left 20.176.4, fo:border-right 20.176.5, fo:border-top 20.176.6, fo:padding 20.210, fo:padding-bottom 20.211,fo:padding-left 20.212, fo:padding-right 20.213, fo:padding-top 20.214, style:border-line-width 20.241, style:border-line-width-bottom 20.242, style:border-line-width-left 20.243, style:border-line-width-right 20.244, style:border-line-width-top 20.245, style:shadow 20.349.
Update the reference information accordingly in sections:
20.176.2 fo:border, 20.176.3 fo:border-bottom, 20.176.4 fo:border-left, 20.176.5 fo:border-right, 20.176.6 fo:border-top, 20.211 fo:padding, 20.212 fo:padding-bottom, 20.212 fo:padding-left, 20.213 fo:padding-right, 20.214 fo:padding-top, 20.241 style:border-line-width, 20.242 style:border-line-width-bottom, 20.243 style:border-line-width-left, 20.244 style:border-line-width-right, 20.245 style:border-line-width-top and 20.349 style:shadow.
For example, 20.176.2 fo:border
The fo:border attribute is usable with the following elements: <style:graphic-properties> 17.21, ..., <style:text-properties> 16.27.28.
2.2 Schema changes/additions:
<define name="style-text-properties-attlist">
<interleave>
...
<optional>
<ref name="common-border-attlist"/>
<ref name="common-border-line-width-attlist"/>
<ref name="common-padding-attlist"/>
<ref name="common-shadow-attlist"/>
</optional>
...
</interleave>
</define>
3. IMPACTS
3.1 Conformance:
This proposal will not add any mandatory features or behaviors.
3.2 Backwards compatibility:
This element was not available in previous versions and is
optional. Existing ODF processors may ignore it.
3.3 Accessibility impact:
None.