Re: [Podofo-users] PDF FileSpec

2017-02-26 Thread zyx
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


Re: [Podofo-users] Font object duplication

2017-02-26 Thread zyx
On Wed, 2017-02-22 at 23:41 +, Leonard Rosenthol wrote:
> The PDF 1.7 specification was superseded in 2008(!!) by ISO 32000-1
> as the official PDF standard.

Hi,
pity the 1.7 reference was not updated with any such information (I
have a download from the Adobe site from 2012 or so). That would make
sense, from my point of view. Anyway, thanks for correcting me.
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


Re: [Podofo-users] BUG: Erase method from PdfOutlineItem sometimes segfaults

2017-02-26 Thread zyx
On Sat, 2016-07-16 at 20:44 +0200, zyx wrote:
> On Thu, 2016-07-14 at 23:58 +, Matthew Brincke wrote:
> > I haven't changed the check, but documented it can't be deleted at
> > its source anymore. If that's too impractical (which it may be),
> > please say so and I'll change the check.
> 
> thanks for the update. I committed it as revision 1775:
> http://sourceforge.net/p/podofo/code/1775

Hi,
I realized, when testing PoDoFo 0.9.5, that this change caused
a regression, one is not able to create new outlines using
PdfOutlineItem::CreateChild(), because it ends with an exception due to
the added check. I fixed it with revision 1827:
http://sourceforge.net/p/podofo/code/1827

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


Re: [Podofo-users] 0.9.5 regression, pdfImage.GetObject()->GetDictionary() throws exception

2017-02-26 Thread zyx
On Fri, 2017-02-17 at 17:24 +, Mark Rogers wrote:
> The only changes needed after reverting are

Hi,
I did something like that and as it works fine here I also committed it
as revision 1825:
http://sourceforge.net/p/podofo/code/1825

I also committed a change which stops forcing c++98 standard for gcc
compiler. There should not be any reason to do it only there, but not
elsewhere. It's revision 1826:
http://sourceforge.net/p/podofo/code/1826

It causes, for me and gcc 6.2.1 to claim a warning about an exception
being thrown in PoDoFo::PdfPainter::~PdfPainter(), about which we spoke
in a not so distant past.

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