Created attachment 169931 [details] Document with single landscape page inbetween portrait pages with gutter The feature 'page gutter' was implemented with bug 91920. It allows the user to distinguish in the margins between an area, which will be consumed by binding and an area, which gives a visible margin. The drop-down-list 'gutter position' has the items "Top" and "Left". The option "Top" works only on a whole document and it is not saved as page layout property but is save in the propriety "settings.xml". This way of implementing mimics the way a "Top" gutter is handled in OOXML. But it does not cover all use cases and LibreOffice should be better here. Imagine a user has a document in portrait orientation with a left page gutter. Now he needs some pages in landscape e.g for wide tables or maps. He sets the page style 'landscape' for them. But he is not able to use gutter position "Top", because that is only possible for a whole document. He is forced to increase the top margin manually and the information, that part of this area is consumed by binding is not available in contrast to the intension of the new feature. [The 90deg rotation of the landscape page can be done by the printing algorithm, e.g. Acrobat Reader handles this nicely.] Enhancement request: Implement page gutter position 'Top' so, that it is usable as property in page styles, so that it can be applied to individual pages.
Wouldn't it be better automatically consider page orientation instead and properly display gutter? With per-page setting available, will user have to separately set different position of the gutter for differently oriented pages? (Sounds to me like a good opportunity for errors). Btw, does "left" option for gutter becomes "right" for documents with RTL text?
(In reply to Valek Filippov from comment #1) > Btw, does "left" option for gutter becomes "right" for documents with RTL > text? The case RTL text is not yet implemented, see bug 140343. > Wouldn't it be better automatically consider page orientation instead and > properly display gutter? > > With per-page setting available, will user have to separately set different > position of the gutter for differently oriented pages? (Sounds to me like a > good opportunity for errors). You need to assign a different page style, when switching between portrait and landscape in the same document. And as we have no inheritance for page styles, you have no common "parent" to set the page gutter value and position but need to do it in each page style individually.
The reason I didn't implement this so far is that this way we have no interop problems when saving/loading Word formats. Word only supports only a single per-doc setting for the gutter position. If we allow multiple gutter positions, then which one would you write to the export result for Word formats? Whatever you write, somebody will be upset that we lost formatting when not writing the rest of the positions. What do you think?
ODF and OOXML are incompatible in many aspects. So loosing something from ODF to OOXML happens already and users should know about that. There exists a long standing wish, to not only have a warning, that something might be lost on export to a different format, but have a list, what is actually lost for the current document. https://bz.apache.org/ooo/show_bug.cgi?id=75255 But in case you have customers which use LibreOffice only for working in OOXML formats, it might be a solution to use 'top edge gutter for entire document' only in case the current opened file has an OOXML file format, and allow 'top edge gutter for single page formats' in case of ODF file format? (I admit, that I don't know, whether that is easily possible.) Any solution here must take into account the UI deficiencies listed in bug 140575.
Miklos, what do you think about Regina's answer?
(In reply to Dieter from comment #5) > Miklos, what do you think about Regina's answer? Sorry, Miklos, I've just seen, that you wasn't in cc
I'm not objecting; if somebody wants to implement this per-page-style setting, go ahead. I commented above on why I wouldn't do this myself. :-)