3 ms·
> Page turning would change two numbers, one of them would always increment by 1 I don't think most end-users will like that. > But the same issues exist toda
by wolverine876 3y ago
> Page turning would change two numbers, one of them would always increment by 1
I don't think most end-users will like that.
> But the same issues exist today with PDF since you have page count (more visible since it's usually permanently visible in the app) and page labels
Yes, not a good situation, so why duplicate it elsewhere? Anyway, if I say 'page 545', IME people understand it's the document's page number and not the PDF page count.
- eviks 3y agoIf you have such understating people they'd have no issues understanding that there are two systems of coordinates in the new format just like in PDF (reader page vs writer page / absolute page vs writer page) But you don't need to duplicate it, all I was saying is PDF as exists has no benefits here. Also, speaking of columns, when you reflow page to fit the narrow screen, you can simply make the same page longer instead of splitying, then you can have your same single writer page number. Basically, it's a non-issue for format comparison purposes, you can make UI whatever you like (unless it's PDF where nothing can reflow)
- wolverine876 3y agoPagination is preserved in PDFs, even if the page numbering is complicated. > when you reflow page to fit the narrow screen, you can simply make the same page longer instead of splitying, then you can have your same single writer page number. You could do that, but IME, formats/apps besides PDF don't preserve pagination. Consistency across platforms, applications, etc. is hard.