Bug#754463: RFS: pdf2htmlex/0.11+ds-1
Hi,
Quoting Jakub Wilk (2014-08-04 23:03:54)
> * Johannes Schauer <j.schauer@email.de>, 2014-08-02, 09:33:
> >I'm not familiar enough with the kind of disaster that may
> >happen when linking C++11 compiled code to C++98 libraries
>
> Crashes, I suppose.
>
> >I also do not see any advised fix or how to prevent the situation.
>
> There's not much that can be done, other than:
> - porting pdf2htmlEX to C++98 (unlikely to be feasible);
> - not uploading the package yet;
> - keeping your fingers crossed that nothing bad will happen.
I would suggest going for the last option and handle problems once they appear
in practice.
> >I uploaded the new version.
>
> There's a new typo:
> comparision -> comparison
I created a new patch "fix-spelling". But since this is the only correction we
have so far I guess we wait with forwarding it to upstream until there are more
changes than just a single letter?
> >I also noticed that the software allows to set ENABLE_SVG=ON which enables
> >generating SVG backgrounds and converting type-3 fonts. But this feature
> >requires CairoFontEngine, CairoRescaleBox and CairoOutputDev from the
> >poppler sources. Should I integrate the required files into the upstream
> >tarball so that we can build with ENABLE_SVG=ON?
>
> Embedding a copy of (a part of) Poppler doesn't seem appealing to me.
> :-(
>
> It would be ideal if Poppler provided the required headers files, and
> perhaps moved Cairo*.o to a separate library (they are currently part of
> libpoppler-glib). But I have a hunch Poppler maintainers won't like this
> idea...
Just in case I filed wishlist bug #757055
> >I also noticed that the required files are shipped by the emscripten binary
> >package. But it'd be quite messy to depend on that binary package for the
> >sources it ships for a different purpose.
>
> Yeah, let's not go that way.
Agreed. In case #757055 gets resolved we can revisit this feature.
I uploaded a new version that fixes the spelling mistake you found.
cheers, josch
Reply to: