I found that the easiest way to make your pdf compliant with the IEEE requirements is to just print your pdf to another pdf! This works like a charm. I had a few problems, which are enumerated in the table below. I tried removing the urls, I even tried these hacks: http://mohamednabeel.blogspot.com/2009/10/fixing-font-not-embedded-issue-to-pass.html. However, the only thing that you have to do is to grab the document generated by latex, go to File->Print...->Print to file (choose another location/name) and voila, it works! :)
If
the report says: |
Possible
cause(s) |
Solution |
|
---|---|---|---|
(1) |
Bookmarks found in document |
(1)
User inserted bookmarks into the PDF. |
Click |
(2) |
Document
contains security |
(2a)
User applied security to some or all elements of the
PDF |
Click |
(2b)
If source is Microsoft Word— PDFMaker is
set to apply security to all PDFs |
Click |
||
(3) |
Font
### is not embedded |
(3a)
The font file does not exist on the system that created
the PDF |
Click |
(3b)
The font is not being found by Distiller |
Click |
||
(3c)
The font is not embeddable |
Click |
||
(3d)
Using Office 2003 or 2007 |
Click |
||
(4) |
Font
### is not subsetted |
(4a)
PDF conversion options are not set correctly |
Click |
(4b)
Headers/footers were added using Acrobat 6 function
(or other application) |
Click |
||
(4c)
Using Office 2003 or 2007 |
Click |
||
(5) |
Document contains link annotations |
(5)
User has applied a link to text in the document. |
Click |
(6) |
Document contains form fields
|
(6)
User has used form fields in the document. |
Click |
I found this is easiest way to find IEEE compliance. Thanks for sharing such an informative post. We are providing the best services click on below links to visit our website.
ReplyDeleteOracle Fusion HCM Training
Workday Training
Okta Training
Palo Alto Training
Adobe Analytics Training