[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OFFICE-4150) Frames may break between pages in text documents
[ https://issues.oasis-open.org/browse/OFFICE-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=83780#comment-83780 ]
Svante Schubert edited comment on OFFICE-4150 at 11/14/23 2:43 PM:
-------------------------------------------------------------------
As most of us are using the PDF version from [https://standards.iso.org/ittf/PubliclyAvailableStandards/c071691_ISO_IEC_29500-1_2016.zip|https://standards.iso.org/ittf/PubliclyAvailableStandards/c071691_ISO_IEC_29500-1_2016.zip]
I would like to point out that the *page number to jump to within your PDF reader is {color:#172b4d}453{color}*, which is +equivalent to page number 443 written on the page+.
Â
AFAIS there is no explicit attribute for breaking between (or floating over multiple) pages, right?Â
The WordML XML seems "just" describing a floating table:
w_CT_TblPrBase =
element tblStyle \{ w_CT_String }?,
*element tblpPr* \{ w_CT_TblPPr }?,
w_CT_TblPPr =
*attribute w:leftFromText \{ s_ST_TwipsMeasure }?,*
*attribute w:rightFromText \{ s_ST_TwipsMeasure }?,*
*attribute w:topFromText \{ s_ST_TwipsMeasure }?,*
*attribute w:bottomFromText \{ s_ST_TwipsMeasure }?,*
*attribute w:vertAnchor \{ w_ST_VAnchor }?,*
*attribute w:horzAnchor \{ w_ST_HAnchor }?,*
*attribute w:tblpXSpec \{ s_ST_XAlign }?,*
*attribute w:tblpX \{ w_ST_SignedTwipsMeasure }?,*
*attribute w:tblpYSpec \{ s_ST_YAlign }?,*
*attribute w:tblpY \{ w_ST_SignedTwipsMeasure }?*
was (Author: svante.schubert):
As most of us are using the PDF version from [https://standards.iso.org/ittf/PubliclyAvailableStandards/c071691_ISO_IEC_29500-1_2016.zip
]I would like to point out that the *page number to jump to within your PDF reader is {color:#172b4d}453{color}*, which is +equivalent to page number 443 written on the page+.
Â
AFAIS there is no explicit attribute for breaking between (or floating over multiple) pages, right?Â
The WordML XML seems "just" describing a floating table:
w_CT_TblPrBase =
element tblStyle \{ w_CT_String }?,
*element tblpPr* \{ w_CT_TblPPr }?,
w_CT_TblPPr =
*attribute w:leftFromText \{ s_ST_TwipsMeasure }?,*
*attribute w:rightFromText \{ s_ST_TwipsMeasure }?,*
*attribute w:topFromText \{ s_ST_TwipsMeasure }?,*
*attribute w:bottomFromText \{ s_ST_TwipsMeasure }?,*
*attribute w:vertAnchor \{ w_ST_VAnchor }?,*
*attribute w:horzAnchor \{ w_ST_HAnchor }?,*
*attribute w:tblpXSpec \{ s_ST_XAlign }?,*
*attribute w:tblpX \{ w_ST_SignedTwipsMeasure }?,*
*attribute w:tblpYSpec \{ s_ST_YAlign }?,*
*attribute w:tblpY \{ w_ST_SignedTwipsMeasure }?*
> Frames may break between pages in text documents
> ------------------------------------------------
>
> Key: OFFICE-4150
> URL: https://issues.oasis-open.org/browse/OFFICE-4150
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Reporter: Regina Henschel
> Priority: Major
> Attachments: ProposalTextAndRelax.odt
>
>
> Developer contact: Miklos Vajna
> = Rationale =
> Use cases:
> A table inside a text document may be inside a frame, so that content can wrap around it. A table can be also directly in the text document ("inline"), so it can span over multiple pages if there is enough content in it. The proposal is to allow the two use-cases at the same time: a frame containing a table and also spanning over multiple pages.
> Alternatives considered:
> - Don't split tables in frames over multiple pages. This has the downside that it looks like some content is not in the document, while it's just not visible.
> - Never put tables inside frames. This has the downside that content can't wrap around the table, even if there would be space for it. This can lead to more pages than necessary.
> Regina:
> * Use a chain of linked frames. This has the downside that it needs several individual frames each with its own anchor, size and position. It would not allow the author to start with the table because following pages has no text content to anchor a frame to.
> * Limit the new feature to a <table:table> element as child of a <draw:frame> element. This has the downside, that it does not allow additional text to the table like a caption, for example, or allow the page break if a frame has long <draw:object> and <draw:object-ole> child elements.
> Â
> Regina: Addition for interoperability:
> When a floating table spreads over a page break in MS Office, the text content beside the table only starts at the last page. MS Office has the compatSetting extension allowTextAfterFloatingTableBreak to enable that text content beside table is already possible on the first page of the floating table. Such layout is usesful for long smalll tables. Therefore the requested attribute has to be complemented by an attribute to allow such wrap behavior.Â
> = Requested changes to the ODF Standard =
> see attachment
> = 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 attributes is optional.
> Accessibility impact:
> This change will not impact accessibility.
> Interoperability:
> OOXML's wordprocessingML has a <w:tblpPr> markup [17.4.57 tblpPr (Floating Table Positioning), page 443, ISO/IEC 29500-1:2016(E)] to describe a similar feature (multi-page floating table). This proposal allows round-tripping that feature in ODF. LibreOffice 7.6 implements this layout feature in its ODF extension namespace.
> Regina: The attribute allowTextAfterFloatingTableBreak is a document setting in MS Office. I prefer a style attribute for ODF because it is more flexible and therefore suggest style:wrap-text-at-frame-start as graphic property. To get it document wide for round-tripping, it can be set at the root of the styles hierarchy.
> Â
> The topic has been discussed on the LibreOffice mailing list:
> [https://lists.freedesktop.org/archives/libreoffice/2023-July/090610.html]
> The initial proposal is by Miklos, see his attachment in the thread sited above. I have added the attribute style:wrap-text-at-frame-start because otherwise it is not possible to distinguish between a typographically more appealing layout and the way MS Office arrange body text as default.
> Â
--
This message was sent by Atlassian Jira
(v8.3.3#803004)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]