Try file:///full_path_of_file#page=3 in your regular web browser and see if it works.
Edit: Nevermind, look at the note under. I don’t think this can work:
Note: If you use UNC server locations (\servername\folder) in a link, set the link to open to a set destination using the procedure in the following section. If you use URLs containing local hard drive addresses (c:\folder), you cannot link to page numbers or set destinations. With Adobe Acrobat 7.0 products, a link to a page number works only if you use HTTP or HTTPS locations. UNC server locations will only work if you use the set destinations method outlined in the following section of this document.
Today Logseq can jump to locations in a PDF.
My assumption is it uses what it has previously stored in the “assets/pdf_name.edn” to know where to jump.
Wouldn’t it be just a matter of parsting the prefix #page= to achieve the same?
Regards,
Philippe
Yes that would be possible. But I think it is sort of not possible with external PDF reader like acrobat, because the external PDF reader must support it and each reader will likely work differently so each would need to be supported individually.
That being said, I don’t know if it is supported currently in Logseq. It would totally make sens since the mechanism is already there.