On Jan 27, 1:06 pm, Rossko <[email protected]> wrote: > I still see the difficulty in that you cannot (I think?) construct a > PDF to be fed to a remote end-user, without breaking the terms by way > of handling the actual static image outside of a browser.
But you can--_if_ you consider the Adobe Reader plugin to be within the browser. You just feed the PDF to the Reader plugin with a link to the static image as the image source, and the Reader plugin inserts the image when it's viewed. Now, I'm not sure how you could ensure that the PDF gets sent to the plugin and not just saved as a file, and that might be required to follow the terms. Since that way the image is actually downloaded by the plugin in a web browser instead of by another PDF viewing program like Adobe Reader (or evince for example on Ubuntu Linux). I'm sure a good faith effort to ensure that would be enough--you can't keep a user from breaking the terms himself. I could make a PDF with a link to a Google Static Map image easily and open it, and I'm sure it wouldn't be hard to get around any attempt to ensure it is opened in the plugin. But again, that's the user breaking the terms, not the site. -Brian -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
