View Issue Details

IDProjectCategoryView StatusLast Update
0014175ScribusStory Editor / Text Framespublic2020-04-24 02:56
ReporterJuan Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status confirmedResolutionopen 
Platformx86_64OSWindowsOS Version10
Product Version1.5.3.svn 
Target VersionFuture Release - High PriorityFixed in Version 
Summary0014175: Error in page number (“Reference to Mark”) when anchors are in linked text frames
DescriptionReferences to marks (anchors) work correctly, inserting the number of the page where the anchor is, but as soon as the text frame containing the anchors is linked to another text frame, the page number changes to that of the first text frame.
Steps To ReproduceCreate a new file.
Add several pages (three or more).
Add a text frame in each of the pages.
In each text frame except the first, insert anchors (Insert > Marks > Anchor Mark).
In the text frame of the first page, insert references to these anchors (Insert > Marks > Reference to Mark): page numbers are correct.
Then, link the text frames containing the anchors: all page numbers in the first frame change to that of the first linked text frame.
Then, unlink the text frames containing the anchors: all page numbers in the first frame change to reflect the correct page number.
Tagsmarks
PatchNo

Relationships

related to 0014181 closedjghali Deleting text with anchor marks triggers crash 
related to 0011812 closedcbradney reference to item marks dont respect the secttion's defined offset for page numbers 
child of 0012496 acknowledged Metabug: Marks & Footnotes & Weld (1.5.0.svn) 

Activities

Juan

2016-06-24 13:24

reporter   ~0041708

Last edited: 2016-06-25 12:05

View 2 revisions

Seems related to 0011812, but this has been closed (?).

PeterBenedek

2016-06-24 14:39

developer   ~0041709

Juan, please upload sample file! Thanks!

Juan

2016-06-24 15:30

reporter  

References to anchors - Unlinked Frames.sla (21,564 bytes)

Juan

2016-06-24 15:31

reporter  

References to anchors - Linked Frames without Frame Breaks.sla (22,588 bytes)

Juan

2016-06-24 15:31

reporter  

References to anchors - Linked Frames with Frame Breaks.sla (21,400 bytes)

Juan

2016-06-24 15:45

reporter   ~0041710

Thanks for your attention, Peter. Here you have three files, created as follows:

1. Create file “References to anchors - Unlinked Frames.sla”, composed of four pages with one text frame each, containing two anchors at the beginning of two lines, then create a kind of TOC in the first page by inserting references to each anchor. Result: Page numbers (Insert > Reference to Mark) are correctly displayed and updated automatically (e.g.: add a page in the middle, delete it…).

2. Copy the file and name it “References to anchors - Linked Frames without Frame Breaks.sla”. Proceed to link frames on pages 2, 3 and 4 (which leads often to a crash, but that is another story…). After this, reflow the text between pages as it was before by adding paragraphs until all anchors are in their original page. Result: Page numbers in TOC change to 2 (the first linked frame) for all references to anchors, disregarding their real position.

3. In the file “References to anchors - Linked Frames with Frame Breaks.sla”, reflowing of the anchors is done by inserting frame breaks instead of paragraphs. Result: same issue with page numbers.

Hope it helps!

PeterBenedek

2016-06-25 12:12

developer   ~0041711

Tested: Linux Mint 18; Qt5.5.1; Qt5.6.1; r21386

I can reproduce this. And this: 0014181

Juan

2016-12-19 10:23

reporter   ~0043102

Is there any chance of these two issues being addressed in the forthcoming 1.5.3 version? They break important functionality. Thanks in advance!

jghali

2020-04-23 23:39

administrator   ~0047556

I had a look at this issue and fixing it will be a bit difficult in the context of Scribus. In order to know the proper page number corresponding to each anchor, we basically need to perform the layout of the frame where anchors are located before layout of the frame where the reference marks are located. In the use case presented here, the frame where the reference marks are inserted are positioned logically before the frames where anchor marks have been inserted. So frames where references marks are inserted will be layouted before frames on following pages. So layouting text in such case would need at least multiple passes. Possible in software such as Latex, hardly in Scribus for obvious performance reasons. If reference marks are located in the same text chain as the anchors, this even leads to a chicken and egg problem : to know the text to insert for reference marks, we need to layout the text located afterwards, but to perform the layout of the portion of text containing anchor marks, we need to perform layout of the preceding portion of text containing the reference marks.

xavid

2020-04-24 02:56

reporter   ~0047559

Would it make sense to have some manual operation one could trigger to update page references based on the current layout? That'd avoid the performance impact of doing two passes all the time while allowing someone to get the correct page references before printing without needing to unlink everything.

Issue History

Date Modified Username Field Change
2016-06-23 14:17 Juan New Issue
2016-06-24 13:24 Juan Note Added: 0041708
2016-06-24 14:39 PeterBenedek Note Added: 0041709
2016-06-24 15:30 Juan File Added: References to anchors - Unlinked Frames.sla
2016-06-24 15:31 Juan File Added: References to anchors - Linked Frames without Frame Breaks.sla
2016-06-24 15:31 Juan File Added: References to anchors - Linked Frames with Frame Breaks.sla
2016-06-24 15:45 Juan Note Added: 0041710
2016-06-25 12:05 PeterBenedek Note Edited: 0041708 View Revisions
2016-06-25 12:12 PeterBenedek Note Added: 0041711
2016-12-19 10:23 Juan Note Added: 0043102
2016-12-19 13:29 Kunda Relationship added related to 0014181
2016-12-19 13:30 Kunda Tag Attached: marks
2016-12-19 13:32 Kunda Status new => confirmed
2016-12-19 13:32 Kunda Target Version => Future Release - High Priority
2016-12-19 13:33 Kunda Relationship added related to 0011812
2016-12-19 13:37 Kunda Relationship added child of 0012496
2020-04-23 23:39 jghali Note Added: 0047556
2020-04-24 02:56 xavid Note Added: 0047559