Re: [poppler] user-defined output device & private functions in libpoppler

2016-12-02 Thread Carlos Garcia Campos
Adam Reichold writes: > Hello, > > I am obviously not a maintainer, but here a my two cents anyway: Just > from reading this and hence assuming that OPVP is to become generally > relevant, I think upstreaming the OPVPOutputDevice and possibly even > making pdftoopvp part of poppler-utils sounds l

Re: [poppler] user-defined output device & private functions in libpoppler

2016-12-02 Thread Albert Astals Cid
El divendres, 2 de desembre de 2016, a les 9:37:48 CET, suzuki toshiya va escriure: > Dear Poppler maintainers, > > I would like to hear your comments about the possibility > of the disclosure of functions used "in" libpoppler, like, > Goo, Fofi and Splash (if there was some discussion in the > p

Re: [poppler] user-defined output device & private functions in libpoppler

2016-12-01 Thread suzuki toshiya
Dear Adam, Thank you for encouraging comment! Regards, mpsuzuki Adam Reichold wrote: > Hello, > > I am obviously not a maintainer, but here a my two cents anyway: Just > from reading this and hence assuming that OPVP is to become generally > relevant, I think upstreaming the OPVPOutputDevice an

Re: [poppler] user-defined output device & private functions in libpoppler

2016-12-01 Thread Adam Reichold
Hello, I am obviously not a maintainer, but here a my two cents anyway: Just from reading this and hence assuming that OPVP is to become generally relevant, I think upstreaming the OPVPOutputDevice and possibly even making pdftoopvp part of poppler-utils sounds like the most reasonable course of a

[poppler] user-defined output device & private functions in libpoppler

2016-12-01 Thread suzuki toshiya
Dear Poppler maintainers, I would like to hear your comments about the possibility of the disclosure of functions used "in" libpoppler, like, Goo, Fofi and Splash (if there was some discussion in the past, please give me the pointer to there). It could be useful for the developers who want to mak