Summary
Proposal owner: Miklos Vajna
Proposal short name: Page-content-bottom vertical relation
Rationale
Use cases
Users sometimes want to specify the vertical position of their shapes in text documents in a way that is relative from the bottom of the page content area.
Also, this improves consistency, specifying a position that is relative from the top of the page content area is already possible.
Alternatives considered
It is possible to have the same calculated position when positioning from the top of the page content area. The downside of this approach is that the position changes when the page height changes. So if the user intention is to position a shape 2 cm above the bottom of the page content area and the page height changes, the shape has to be manually re-positioned. This manual re-positioning is not needed with the proposed markup.
For example, if a shape has a height of 10 cm and a 2 cm spacing is wanted between the bottom of the shape and the bottom of the page content area, the position can be set to -12 cm, and then the 2 cm spacing will be maintained, even after the page height changes.
Requested changes to the ODF Standard
Text changes/additions (compared to ODF 1.2)
20.388 <style:vertical-rel> (existing section)
Append to the end of defined values for the style:vertical-rel attribute list:
page-content-bottom: vertical position of frame positioned relative to the
bottom of page content.
Append to the end of style:vertical-rel attribute value list:
page-content-bottom.
Table 23 - Vertical Relation Values:
page-content-bottom is allowed for page, paragraph and char text:anchor-type
values.
Schema changes/additions
<rng:define name="common-vertical-rel-attlist" combine="interleave">
{{ <rng:optional>}}
{{ <rng:attribute name="loext:vertical-rel">}}
{{ <rng:choice>}}
{{ <rng:value>page-content-bottom</rng:value>}}
{{ </rng:choice>}}
{{ </rng:attribute>}}
{{ </rng:optional>}}
{{ </rng:define>}}
In other words, allow page-content-bottom as a new value of the
style:vertical-rel attribute.
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 attribute value is optional.
Accessibility impact
This change will not impact accessibility.
Interoperability
OOXML's wordprocessingML has a <wp:positionV relativeFrom="bottomMargin"> markup to describe the same, this proposal allows roundtripping that feature in ODF. LibreOffice 7.0 implements this layout feature in its ODF extension namespace.