Reset an array at the end of the frill processing

Question

Hi, 
 I have a question with the array resetting after the end of the frill processing. 
 Originally, I planned to use an array to store texts on each page for indexing. The result is perfect when composing only one page. Unfortunately, when composing more than a page (compose range(+)), the array on each page has changed. I wonder if this is caused by the variables from the next page moved to the previous page for pagination checking. 
 I have undef the array at the end of the frill processing but the issue still exists. Can anyone point me in the right direction? 
 Regards, 
 Terrence

Bart Terryn · Accepted Answer

Terrence, Not sure. I think the danger is bigger when the tag is glued against the previous word. A thing which you can prevent by using the '!' preprocess operator. (not sure if that can still be combined with a /Pb macro in 'i' mode). I guess Jonathan is in a better position to give you a correct answer. I also wonder what you will do when 2 index terms fall on the same line. As you get only 1 flag but you need to output 2 index terms. Let me guess: Initially you simply tried by pushing the index term onto the px;;0 text register. But then you ran into the problem of what happens when there are 2 index terms on the same line as there is only 1 instance of the px;;0 register per line. Hence you decided to go the perl array route... If you really want to solve this multiple occurrence on the same line, then you better switch to the following way of working: We are going to use a number register to set a unique index number for each index term. So you first get hold of the current value of the (lets say) number register 10, increment it and store the content into the array at that index number. Something along the following lines: sub capture { local $/; my $term = ; my $X = XPPcompo->new(); my $number = $X->get_reg('#10'); $number++; $index[$number] = $term; $X->ns(10,$number); $X->fg(); } Then during the frills processing loop, when you encounter a flagged line, you read out the current instance of the same main number register using: my $number = $X->get_main_numreg(10, 't'); This will give you the array index of the last term for the current line. (the current instance is the value of the number register at the end of the line) If you keep track of the previous value that you read, you know how many and which terms you need to read from the array. Oh and before you start the frills processing loop, you read the first previous instance of the same number register, so that you have an initial value to start with. Well that is what I would do. There are probably other ways to solve the same problem...

Jonathan Dagresta · Answer

Let's back up a bit. Terrence Chu said: I wonder if this is caused by the variables from the next page moved to the previous page for pagination checking. Now I'm wondering if fundamentally you're process is not accounting for how XPP composition works (as I now understand that you might have been asking about in your original post), in that (when there is sufficient text) composition first oversets the bottom of blocks (by some twenty or so lines) in order to determine where it is going to vertically break (to account for any keeps and/or widow/orphan rules and/or VJ squeeze rules). So, if there are any ... occurrences within that "overset" text that then gets pushed to the next page then I can see that your saved array for a page might include index entries that end up on the next page. If that's what is happening, then you'll have to figure out a way to account for that. Jonathan Dagresta SDL XPP Engineering

XPP > XPP

Reset an array at the end of the frill processing

Top Replies