"number of pages" metaTag "$n" increases cumulatively for each part in export PDF of Score+Parts
If I either download PDF including parts and view *-parts.pdf or if I locally export parts as PDF and view *_Score_and_Parts.pdf, then I notice that the value of "number of pages" metaTag "$n" increases depending of on total accumlated number of parts that exist so far into PDF generation.
Here is how $P/$n page tags are displayed when exported as PDF of Score+Parts both generated locally (e.g. attached) or generated online (temporary secret link: http://mus.cr/1HqNG1h) of a SATB example containing 2 pages for score and 2 pages for each part:
So you can figure out that pattern. $n seems to be equal to the total number of pages of the current amount of parts that have been encountered so far into the pdf generation. I don't know what "expected behavior" should be, but I would expect that for a particular PDF file, the value of $n would be a constant equal to the total number of pages in that PDF. So in this example, I would expect $n should equal 10.
(Note: when generating *individual* PDFs of each part, I would expect $n to always equal the number of pages in each part, which in this example always equals 2, which musescore does handle correctly.)
|test_number_of_pages_n_on_all_pages_on_all_parts-parts (1).pdf||25.13 KB|