11-04-2023, 03:20 AM
I'm with BRX in not having MS update the pdfs. In particular, this means the files can't be corrupted if something goes wrong (something that is likely to happen with all the cross platform code, multitude of device models and the 3rd party libraries being used)
Embedding in the pdf is possible but MS isn't/wasn't designed as a pdf editor; Mike is just trying to add features that users have requested (and doing a brilliant job). There is always a trade-off in doing this - it takes almost no time to update an extremely small pdf but could lead to unacceptable delays for a several hundred page file.
Keeping the annotations separately eliminates these variations in performance.
A purpose built pdf editor is always going to do a better job at handling annotations. To my mind, MS should just do the basic operations (I suppose it all depends what each user classes as basic).
Adding extra pdf features means that Mike will have less time for customer support and designing/creating new features like song versioning.
Geoff
Embedding in the pdf is possible but MS isn't/wasn't designed as a pdf editor; Mike is just trying to add features that users have requested (and doing a brilliant job). There is always a trade-off in doing this - it takes almost no time to update an extremely small pdf but could lead to unacceptable delays for a several hundred page file.
Keeping the annotations separately eliminates these variations in performance.
A purpose built pdf editor is always going to do a better job at handling annotations. To my mind, MS should just do the basic operations (I suppose it all depends what each user classes as basic).
Adding extra pdf features means that Mike will have less time for customer support and designing/creating new features like song versioning.
Geoff
Samsung Galaxy Tab A6