<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body>Krzysztof Kowalczyk wrote:<br>> Is there interest among poppler developers to maintain win32 portability?<br><br>I am interested, having ported Poppler over to VC/Win32 myself.<br><br>> I just started working on a PDF viewer for Windows<br>> (http://blog.kowalczyk.info/software/sumatrapdf). Initially I used<br>> xpdf but just ported it to poppler and would much rather stick with<br>> poppler since it has more open and more active development so that I<br>> can benefit from fixes made to poppler and others can benefit from<br>> fixes that I make.<br><br>I have made similar fixes while looking at Poppler.<br><br>NOTE: you need to be careful when removing unused variables that<br>they are not actually being used inside a #ifdef...#endif block!<br><br>> I would be happy to maintain win32 portability. I've opened a bug and<br>> attached a patch to bring the latest cvs version of poppler to compile<br>> on Windows under Visual Studio 2005<br>> (https://bugs.freedesktop.org/show_bug.cgi?id=7107).<br><br>I have updated that to include my alternative patch.<br><br>> Is that the best way to submit patches in order to get them into main<br>> tree or should I use some other way (e.g. send the patches to mailing<br>> list)?<br><br>I assume that this would be the best approach, then they don't get lost<br>like my VC patch did!<br><br>- Reece<br><br /><hr />Express yourself instantly with MSN Messenger! <a href='http://clk.atdmt.com/AVE/go/onm00200471ave/direct/01/' target='_new'>MSN Messenger</a></body>
</html>