Post by Dimitri Stamatiadis on Apr 2, 2016 12:21:28 GMT
Dear all,
I have had some interesting discussions lately about PDF rendering with one of our members. The question is "should an EDMS tailored for small companies, necessarily include PDF rendering capability?". The argument was that this is beyond document management and adds a cost (server-based rendering is more expensive than local machine functionality which is embedded in MS word and in the printing functions). On the other hand, PDF rendering has always been a functionality included in traditional EDMS (and admittedly a practical one).
We would very much like to hear from the group if we should maintain the requirement in the Pocket EDMS URS. For information there are currently two requirements. The first mandates that PDFs must comply with specifications provided by the FDA and other agencies and the second prohibits font substitution (as this could create problems with displaying special characters or change the pagination).
I have had some interesting discussions lately about PDF rendering with one of our members. The question is "should an EDMS tailored for small companies, necessarily include PDF rendering capability?". The argument was that this is beyond document management and adds a cost (server-based rendering is more expensive than local machine functionality which is embedded in MS word and in the printing functions). On the other hand, PDF rendering has always been a functionality included in traditional EDMS (and admittedly a practical one).
We would very much like to hear from the group if we should maintain the requirement in the Pocket EDMS URS. For information there are currently two requirements. The first mandates that PDFs must comply with specifications provided by the FDA and other agencies and the second prohibits font substitution (as this could create problems with displaying special characters or change the pagination).
