this is a known issue. see:
as jrenfrew stated:
"When you rotate a PDF, all you do is set a flag saying 'I am this size and orientation, but please look me this way' The file underneath does NOT change
Some versions of FMP have had problems with correctly interpreting the rotate flag so show the fuel in the original orientation.
To make this stick you have to create a PDF in the orientation you want and then rotate and insert your existing contents. It's not that difficult to write cod ego do it, but it is not a trivial task either."
… and on a side note: It's not FMP to blame
If the flag is saying "please look at me this way"... it means that Filemaker is ignoring the flag... which definitively puts the blame on FMP...
interactive Container fields are based on the web resources of the OS, afaik. For Mac OS, this would be Safari Webkit.
Out of curiosity: If you right-click the file and choose
what orientation will Safari show the PDF?
As one would expect, it shows the correct orientation, exactly as does the interactive PDF in Filemaker.
Again, the interactive part works perfectly.
I'm talking about the case when you want to display just the image part.
Thank you for your posts.
Our Development and Testing departments are aware of this issue. Currently, FileMaker only supports rotation for JPEG and TIFF files. The issue is getting to the PDF metadata. As you discovered, a Container field set for Interactive content is using Preview or Adobe Reader so the document will appear correctly.
This was originally submitted by another customer on the forum: PDF Rotating Upon Insertion into a Container Field
I have attached your posts to the original report. When more information becomes available, I will post again.
Just my 5 cents on this: If you build a formula field which converts the container field into Base64, then use this Base64 string in a WebViewer html protocol, would WV recognize the rotation flag?
=> WV means Safari Webkit / Safari Browser does recognize the rotation flag …
A Web Viewer and an Interactive Container field are identical. They both use Webkit, and the rotation of a PDF is recognized.
I've overseen that "when displaying PDF as Images and not as Interactive object" part.
Though set Option
for container field would be a fair work around