UI: Re-label anchoring to page to anchoring to page number
I assumed anchoring to page being anchored to page (bug 135829). So moving with page break. To page actually means it fixed to a certain page number
However the label should be adjusted to what actually does to reduce this misunderstanding. I would propose: Anchor to page number, instead of the general 'anchoring to page'. At minimum this will confuse people, so looking it up in the first place :-).
Steps to Reproduce:
1. Open Writer
2. Insert an image
3. Anchor it to page
Anchoring to page
Anchoring to page number (to generate 'confusion' and to make it more specific)
User Profile Reset: No
Version: 22.214.171.124.beta1+ (x86)
Build ID: 5cfac16dbd4af456a7fb6d52c8953c69a72ba2ba
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win;
Locale: nl-NL (nl_NL); UI-Language: en-US
See bug 135829 and https://ask.libreoffice.org/en/question/199971/multiple-captioned-images/#post-id-199989 for the motivation
The documentation team will love this
and if I change any numbering in my document? what will happen?
-1 from me
(In reply to Roman Kuznetsov from comment #3)
> and if I change any numbering in my document? what will happen?
> -1 from me
Feel free for a suggestion for alternative. Not attached to the description as such. To Page is also really confusing. Look at STR of bug 135829. I really expect the image to go to new page with the page break, not stick around. It's not simply 'to page'. It's to, and only THIS specific page.
So alternative might be anchoring to "to this (specific) page". Specific doesn't fit well, I think in they UI and also dubious. Other alternative might be "Lock to page". "Bind to page" (but losing the 'anchor' description here)
FWIW, It's not really clear to me how to interpret: "and if I change any numbering in my document? what will happen?" Not sure what you're referring to exactly. Changing page numbering, heading numbering? Adding pages?
I do get there is some 'issue' with number as volatile factor, so might be misleading too. However it surely not 'evident' description. To page seems to have some obvious meaning; which doesn't apply.
At least for me to page doesn't mean to this, and only this specific page. I won't move anywhere, any time. Maybe 'because it's called anchor" and anchors tend to be dynamic (paragraph/to character/ to frame').
FWIW: this is will become more trivial if bug 135836 is honored :-). So happy to stick with 'to p[age' if there are objections from documentation/ and or/ a risk of user confusion as the setting is hidden as much as possible already.
However it should be changed if the decision is to have that setting present all over the place, IMHO.
Disagree with renaming. It might be more precise but adds confusion since To Page is well known. No objection, however, to add a footnote to the help what To Page actually means.
(In reply to Heiko Tietze from comment #5)
I also don't think that renaming is good; mostly because of consideration from comment 3. For user, a page number is mainly associated with user-visible/defined page numbering; and that's not what counts here, where just "Nth page of the document, no matter which number was assigned by user". And no, I don't have an idea what would be the best. A lengthy description in help? definitely needed, but wouldn't be read my most ;-)
Also tdf#135836 seems questionable ... at least definitely its scope must be limited to most prominent UI, without removing it from e.g. dialogs, and by no means removing the function at all.
(In reply to Telesto from comment #4)
> I really expect the image to go to new page with the page break, not stick
> around. It's not simply 'to page'. It's to, and only THIS specific page.
Here's a problem of user's perception, when user imagines there's something like "THIS" page, while in reality, from the model PoV, there's only THIS text, and all pages are just dynamically appearing/disappearing depending on viewing mode/formatting/whatever ... pages are ephemeral.
Created attachment 164912 [details]
Bug 135836 and this bug are interconnected. So it's more 'or' 'or' approach
The problems I personally have with 'to page' are
1) What's described in bug 135829
2) And whats happening in attachment 164912 [details] (change the anchor on page 13 to 'to character'
This is from model PoV fine. However a potential source for confusion. And I do see people use To page, where it probably shouldn't be used.
As said I assumed 'to page' meaning 'to this page' in dynamic sense. So if pages are deleted before, it moves. Not To Page as exactly this page (including page position) shown under 2. Where plenty of empty inaccessible pages created to being able to hold the image on page 13. You could say those are 'virtual pages'; and should be visualized differently. Because those are not 'real' pages in some sense.
I prefer self-explaining options, instead of pointing to manual/documentation. Especially if it initially does what you think it should do. The surprise is occurring mostly at different point in time.
Point to the manual/help/documentation is always second best, IMHO. And should be avoided as far as possible. The need for lengthy documentation shows something not to obvious and might need improvement.
So would like to list the options, before jumping to improving documentation as last resort.
1) So renaming: some suggestions in comment 1 and comment 4
2) Making To page less prominent. [Removal was only a try out; to check the response]
3) Add here the alternative I didn't think of: ....
There is no point in discouraging the use neither renaming the function. It is just one of the features that require to learn the usage. To Page is known as that in all major text processors, so dropping it would be a serious regression.
And ultimately it's also a bit nitpicking to me. Even when it's unclear how exactly this works you may try and see what goes on. Everything beyond needs to be addressed in the help (CC'ing Olivier).