• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
PDF Page Number Customization or Page Number Shift
I recently added a few Fake Books (PDF's) to my library as multi page documents to have for a back-up for songs I don’t have entered as individual sheets.
What I immediately noticed is when attempting to find a song from the Fake Book index by the referenced page number, I end up somewhere else because MobleSheets counts the first page in the PDF as number 1 while the Fake Book considers page 1 the first page of music, disregarding covers, indexes and other pages.
For example, when viewed in Acrobat an example PDF Fake Book I have refers to the cover page as C1 while the six pages of indexes are referred to as i – vi, however when brought into MobileSheets, C1 becomes page 1 while indexes i - vi become pages 2 – 7.
That means if I try to enter the page number for a song that according to the index is supposed to be on page 7, I actually have to enter page number 14 in MobileSheets. While that may seem like a minor hassle, I have 12 different Fake Books in my library, all with a different number of index and other pages before what the Fake Book considers as page 1 for index look-up purposes. Doing the math in addition to the look-up of the song in the index wastes even more time.
Splitting up the multipage documents into individual pages is of course an option, but I really don’t want to clutter up my library with a bunch of sheets I may already have or never use.
What would be nice is if MobileSheets imported the PDF with the same page numbers as Acrobat, meaning having something other than numbers, (like C1 for covers and i - x for index pages).
Another suggestion would be to add a method to renumber/rename individual pages for an individual multi-page item in your MobileSheets library to accomplish the same thing if it can’t be done easily during the import of the PDF. Or, possibly some way to change the range of page number while still having pages you don’t want in the page count to appear during page turns.
Presently, if you change the range of page numbers from 1 -100 to 6 – 100, you no longer see pages 1 -5 which defeats the purpose of having an index if you can't view it.
Hopefully you understand what I am talking about and thanks in advance for any consideration you give to this suggestion.
I like it. 

Mike, how about a negative number for exclusion of some pages, like (oh drat, can't use the '-', let's take the '!') !5-100 if the first 6 (counting the '0' as well, I guess) should be excluded from the MSP numbering?
Or what about a way of using, say, a CSV file to generate an index rather than individual songs. Then you could use this to jump to the song in the multi-page PDF.

Maybe these indexes could live in a new tab a bit like set lists, which might make handling them easier and they wouldn't "pollute" the song list.

I can look into supporting other page numbering displays. I researched this and it involves having to look up fields in the PDF that indicates how certain pages are numbered. Apparently these types are supported:

(Optional) The numbering style to be used for the numeric portion of each page label:
    D      Decimal arabic numerals
    R      Uppercase roman numerals
    r      Lowercase roman numerals
    A      Uppercase letters (A to Z for the first 26 pages, AA to ZZ for the next 26, and so on)
    a      Lowercase letters (a to z for the first 26 pages, aa to zz for the next 26, and so on)

A prefix can also be specified (which is how the cover pages start with "C") as well as the starting page for a given range (so you could start on page 3 instead of page 1 if there was a reason to). So this definitely adds a lot of complexity in displaying the page numbers, which is something that is very simple in nature right now. I'll have a lot of code changes to make so that values entered by the user can support these page ranges and be mapped correctly back to the actual PDF page numbers. For example, if the document starts with C1 through C5 and i-v for indices, the user should be able to have a page range such as "C1-C3,i-iv,1-15". This is much more complex than what I'm doing now, as I'll have to ignore custom prefixes before numbers and convert roman numerals to digits (no idea if that's internally supported in Java and C# but I'll find out). 

So I definitely want to help support this to make your life easier with these PDFs. I don't know if I can justify working on this before the annotations rework or iOS version though as far more people will benefit from the availability of those over better page numbering for large PDFs. If you can wait fora while, then I should be able to get to it after the iOS version is released. If you need something sooner, we will have to brainstorm something that fits within the current design that doesn't require a lot of design and UI changes to support. Nothing comes to mind though that doesn't require a lot of complexity in the implementation. BRX's idea is interesting but I don't really understand how the user would reference the "ignored" pages though for things like bookmarks, link points, etc, or how those pages would be displayed to the user.


As much as I hate to admit it, I can wait...

Right now my workaround is to add to the title of the multi-page document the "fudge factor" (+2, +7, etc) needed to get to the page indicated in the index. Hardly a slick solution and a challenge to do the math after a long night, Wink but it works for now.

It seems to my limited brain that supporting other page numbering displays in PDF may make the most sense as a first step if all the MS user would have to do is import the PDF. I also assume that if finding a page number when the first pages in a PDF have a different system works in Acrobat or Acrobat Reader, it can work elsewhere...


Regardless, thanks for the interest in the problem and of course thanks for MobileSheets.

We all anxiously await your full-time efforts!
Preparing (or finding) a CSV file for each of your fakebooks is imho the way to go.
It's not necessary to import the whole fakebook. On the CSV import dialog you can easily select by song title.
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 1803
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de

(10-22-2019, 07:01 AM)itsme Wrote: Preparing (or finding) a CSV file for each of your fakebooks is imho the way to go.
It's not necessary to import the whole fakebook. On the CSV import dialog you can easily select by song title.

I tend to agree, but. Like Scherzo I have a number of fakebooks that I use as a "backup" and I would prefer that their songs didn't appear in my main list. I know I can filter things with the various fields, but I think it would be nice to have what I originally suggested. A single entry for the fakebook that opens an index like a set list. This would list all the songs in the fakebook and let you select/open them like any other song.

I would be happy to have a new tab for these "index" entries if that makes it easier and there is no rush (I have several friends wedded to iOS who would love to have MSP Smile )

Even though I am totally ignorant on CSV files and how to create them from PDF's, in this case the PDF's are scanned documents meaning no OCR and represent over 4700 individual scanned pages.

Even the master index I have for all 12 books is 69 pages long with over 3700 entries. On that I could tweak the page numbers to match how the song numbers appear when I enter them in MobileSheets, but exporting that PDF to anything else creates a jumbled list that would take days to weeks of full time work to sort out and clean-up just so I could create formulas to tweak the page numbers. Besides, I still would want the individual indexes to be accurate as well so we would be talking about 7400 entries to correct.

Having the 12 books AS books in my library with the ability to be able to look up and use the page numbers in ether the master index or the individual indexes to find the song is what I was hoping to accomplish without spending a massive amount of time to tweak data for something I only want as a back-up when I don't have a particular song in my library as an individual sheet. That's how most people I play with use Fake Books.

If I am missing something that makes creating and using CSV files a snap from scanned documents, enlighten me but in my mind, having MobileSheets use the same page format as Acrobat so things match up when the imported PDF uses other page numbering displays is the way to go for a lot of reasons.

Thanks for the input!
"... I am totally ignorant on CSV files and how to create them from PDF's ..."
I recommend changing that. Using CSV files is less difficult as you might think.

"...Even the master index I have for all 12 books is 69 pages long with over 3700 entries..."
This statement makes me assume that you already have a digital table of content of all the songs in your books.
Creating CSV files from that list sounds doable. How does this master index look like? Is it an Excel / LibreOffice Calc file?

Opening a PDF book as a whole and turning pages up to the song you are looking for is not what MSP is designed for. You can do that but there are more convenient ways to handle fakebooks in MSP.
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 1803
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de

I don't use MSP in this way - I much prefer to have individual charts.  

However, reading through the messages above, it seems to me that a possible solution is to crop the pages at the beginning of the Fakebook PDF up to the first chart.   That would mean the MSP page count would be the same as the modified Fakebook.

Or have I missed something?

1: Samsung 12.2" SM-P900: Android 5.0.2 
2: eSTAR GRAND HD Quad-Core 4G 10.2": Android 5.1 
3: Home-built BT pedal

Some of my music here

Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  

Users browsing this thread:
1 Guest(s)

  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2019 MyBB Group.