Q: A few questions regarding XOD files and the publisher SilverDox SDK
(http://www.pdftron.com/silverdox):
• What happens with links inside of a PDF (such as external sites and
internal bookmarks)? Will they still work in the XOD and in the
viewer?
• Is XOD your creation, or is this a standard file used by people
other than PDFTron?
• Is the PDFTron evaluation watermark created at publishing, or is it
added in the viewer? I may want to add a watermark like this to my
docs and want to know the best place to do it. I have also converted
a few thousand documents and need to know if I need to re-convert them
once I have a valid license.
• I’m currently using PDFNet to convert my PDFs in a multi-threaded
environment. So far it seems to work well with multiple threads, but
I want to find out if there is anything I need to be cautious of. Is
everything thread-safe?
• Is there any CPU or license restrictions on how and where I use the
publisher?
Support questions:
• How does your support work? Do I just email support@pdftron.com, or
do you use a ticket-based system?
• How often do updates to SilverDox (and other SDKs) come out?
• Are you able to let your customers know ahead of time what’s
coming? For example, you mentioned improving the optimization of the
XOD files at a later date. Will you be able to keep me up to date on
your roadmap – even at a high level?
Thanks, and I look forward to your reply…
---------------------
A:
➢ What happens with links inside of a PDF (such as external sites and
internal bookmarks)?
➢ Will they still work in the XOD and in the viewer?
Yes, all links will be preserved.
➢ Is XOD your creation, or is this a standard file used by people
other than PDFTron?
XOD is a subset of Open XPS document that is optimized for viewing on
the Web. For example, to view/print a XOD file in Windows 7/Vista,
simply change the extension to XPS and double-click the file.
The only reason why we call these XPS files 'XOD' is to differentiate
files web optimized files from non-optimized files (such as print
spool files, files with huge images, etc).
For more info please see:
A really cool thing about SilverDox XOD-s is that you can use .NET
Framework (http://msdn.microsoft.com/en-us/library/
system.windows.documents.fixeddocument.aspx,
http://msdn.microsoft.com/en-us/library/ms748388.aspx) to perfoms
additional processing (e.g. content extraction, stamping, etc) or any
third-party API out of the box.
➢ Is the PDFTron evaluation watermark created at publishing, or is it
added in the viewer? I may
➢ want to add a watermark like this to my docs and want to know the
best place to do it.
The watermark is added as part of publishing process. The best place
to add your own watermark is by stamping the source PDF (e.g. using
pdftron.PDF.Stamper - http://www.pdftron.com/pdfnet/samplecode.html#Stamper).
➢ I have also converted a few thousand documents and need to know if I
need to re-convert them
Yes, you would need to reconvert the files.
• I’m currently using PDFNet to convert my PDFs in a multi-threaded
environment. So far it seems to work well with multiple threads, but
I want to find out if there is anything I need to be cautious of. Is
everything thread-safe?
Yes, everything is thread safe. Please keep in mind that some
conversions may be memory or CPU hungry, so there is a limit on the
maximum number of concurrent conversions (especially on 32-bit systems
with 2 GB per process address space).
• Is there any CPU or license restrictions on how and where I use the
publisher?
This is governed by the license agreement (Web or Enterprise). One CPU
license covers the use of publisher on machines with up-to two (2)
cores. A quad-core machine would require 2 CPU licenses, etc. The
license can be only used by a given legal entity etc.
➢ How does your support work? Do I just email support@pdftron.com, or
do you use a ticket-based system?
At the moment, you would contact support@pdftron.com, but we are in
the process adding on the customer log-in page and a ticket-based
system (http://www.pdftron.com/login.html).
➢ How often do updates to SilverDox (and other SDKs) come out?
We are releasing an update every 2-3 months. We are planning the next
major update in early fall.
➢ Are you able to let your customers know ahead of time what’s
coming? For example,
➢ you mentioned improving the optimization of the XOD files at a later
date. Will you be able
➢ to keep me up to date on your roadmap – even at a high level?
Yes, we are quite open and keep interested existing clients up-to date
regarding the roadmap. All of the features are driven by our clients.