On Mon, 2017-02-20 at 08:15 +0300, Nikita Shlyapnikov wrote:
> Examples of this are using custom flash RSLs or Flex styles in
> separate flash file.
> In this case the file "SomeStyle.swf" will be internally written by
> PdfFileSpec as "SomeStyle2Eswf" which may break references to it.
Hi,
that 2E is a Unicode variant of a dot and it's understood by an Acrobat
Reader. Why cannot you fix "the other file which references that PDF
attachment"? You already modify it, do you not? You also should use \F
and \UF together, as the ISO says.
I still think that PoDoFo does things according to ISO 32000:2008 (see
the notes at the end of page 101 and the text around).
> This of course can be avoided by ensuring that a PdfFileSpec before
> using it's path, but may not always be desired in the user code.
I'm sorry, I didn't get this part. Why would it be a problem? PoDoFo is
so great that it allows you to do anything there. Either you use a
higher API, like the PdfFileSpec object, or you do the things on your
own, using PdfDictionary, PdfVariant, PdfObject and others. After all,
the higher API classes are just wrappers around these lower level API.
> Another solution could be making the CreateFileSpecification static
> to allow receiving the modified path without the need of creating or
> storing PdfFileSpec instance.
Maybe if you could share an example code or something like that. I feel
dumb, missing your point.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Podofo-users mailing list
Podofo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/podofo-users
