t needed and it's not thread safe. Also, the ref-
count should always start at 1, not at 0, but I didn't test the patch
yet, thus my patch-reading-opinion can be wrong.
Hope it helps,
zyx
--
http://www.litePDF.cz
to a library.
PNG_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libpng.so
//Path to a file.
PNG_PNG_INCLUDE_DIR:PATH=/usr/include
Thus I'd hesitate to commit a change for an old cmake, when the newer
doesn't have any issue. (Or I didn't notice the issue he
idthArray() inline into PdfFontSimple::Init()
b) forced the widths array to start with a space (ASCII 32)
c) made the widths array not referenced by a reference
Otherwise the arrays should be the same, if I read the code properly.
Bye,
zyx
--
http://www.litePDF.cz
ay
"backward compatible", then it's a better option then the patch split.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Find and fix application perfo
ofo/code/1721
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides dee
On Tue, 2016-05-03 at 10:26 +0200, zyx wrote:
> My personal opinion on the patch itself is that the pseudo-reference-
> counting added is not needed and it's not thread safe. Also, the ref-
> count should always start at 1, not at 0, but I didn't test the patch
> yet, thus my
ing, if you can make a very simple and
small example PDF which fails for you, with no confidential data, then
there's no problem to send it to this mailing list, I believe.
Bye,
zyx
--
http://www.litePDF.cz
hich is used in the
code (I know, rc.exe is used for the resource compiling only, but
anyway). When the symbol (__FILE__) is not defined in the code-compiler
too, then the code might not build.
There is a PODOFO_COMPILE_RC, which seems suitable for the issue you
are trying to address.
ceforge.net/p/podofo/code/1722
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Find and fix application performance issues faster with Applications Manager
Applicati
On Fri, 2016-05-06 at 12:20 +, Matthew Brincke wrote:
> > a) place GetWidthArray() inline into PdfFontSimple::Init()
>
> your (zyx') point a) is wrong, because (as Josef has posted already) the
> method PdfFontMetricsFreetype::GetWidthArray calls FT_Load_Char which
> us
with a certain PDF file content, or by
creating the PdfString instance in a code from scratch?
Thanks and bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Find a
On Tue, 2016-05-10 at 18:07 +0200, F. E. wrote:
> Is there a reason the INCLUDE_DIRECTORIES are not set for OpenSSL or
> is it just a bug?
Hi,
I believe it's just a bug. Could you share your change in a form of a
patch, please? (If you are not having a svn checkout, then have a file
before
issing from
> SVN (running create_forward_headers.sh should fix this)
I see the PdfExtension.h file there:
https://sourceforge.net/p/podofo/code/HEAD/tree/podofo/trunk/podofo/base/
It's there since 2014-04-06, according to svn.
Bye,
zyx
--
http://www.litePDF.cz
API change to make methods name "nicer"/more-
accurate and an API change which fixes a bad bug.)
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Mobile securit
non-PoDoFo code broke the "tree"
structure of the outlines.
Yan, what are you trying to achieve with that code with the outlines?
You see that the manipulation of the tree structure assigns the nodes,
it doesn&
other
compilers/linkers), but it still feels like a bad practice for me.
I would skip this change altogether, personally.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
n object with an empty destination array.
Hi,
thanks for the updated patch. I've a problem that I'm unsure how to
properly test this. I'm sorry.
Bye,
zyx
--
http://www.litePDF.cz
ode/1723
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work a
rray uses
rounded values with your patch, which might be for good. I committed it
as revision 1724:
https://sourceforge.net/p/podofo/code/1724
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
blem with the way you made the previous patch, it
was fine for read-review. I meant that I do not know how to test
the change at all, like I do not have a PDF file which would show
an improvement after the patch is applied and other similar tests.
Bye,
zyx
--
http
tch, please?
As you noted above, the patch changes PdfImage.h only, because the
PdfImage.cpp is covered by the base/PdfDefinesPrivate.h, which includes
the winsock2.h when needed, but cannot be used in the (public) header
files.
Thanks and bye,
zyx
--
http://www.litePDF.cz
On Thu, 2016-05-12 at 12:31 +0200, zyx wrote:
> As you noted above, the patch changes PdfImage.h only, because the
> PdfImage.cpp is covered by the base/PdfDefinesPrivate.h, which
> includes
> the winsock2.h when needed, but cannot be used in the (public) header
> files.
es for the project.
I think you can get some inspiration on this code:
https://sourceforge.net/p/podofo/code/HEAD/tree/podofo/trunk/test/SignatureTest/
and tune it for your platform and use case.
Bye,
zyx
--
http://www.litePDF.cz i...@lite
On Thu, 2016-05-12 at 12:49 +0200, zyx wrote:
> the tiffio.h is not needed in the PdfImage.h, thus
> dropping it from the header file is even better solution.
Hi,
I committed this change as revision 1728:
http://sourceforge.net/p/podofo/code/1728
Please let me know if it didn
the version check and the include. Or do the version check from the
CMake. There are several options how to keep before-r1728 behaviour.
Nonetheless, as I said, the new behaviour is fine with me too.
Thanks and bye,
zyx
--
http://www.litePDF.cz
th my previous commit. I'm sorry for that. I committed your
fix as revision 1745:
https://sourceforge.net/p/podofo/code/1745
Thanks and bye,
zyx
--
http://www.litePDF.cz
F
or in PoDoFo, I currently do not know where it is). As it's not a
feature, I suppose it won't be a problem to fix it within the "feature
freeze" period.
Bye,
zyx
--
http://www.litePDF.cz
de PdfPainter::DrawText for me).
This looks like a typo and if no objection is given, I'll revert this
chunk at the beginning of the next week.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
---
nk, but more of them.
If there is no objection, then I'll commit it at the end of this week.
The change itself will not fix the crash from the reporter, such thing
needs new method(s) added into the PdfOutlineItem, to move/copy
the items in the "tree", rather than only crea
nction to determine
whether the glyph is available in the font or not. If not, then draw
that particular glyph with a different font. The PdfFontMetricsFreetype
implementation of the GetGlyphWidth() function returns 0.0, when it
cannot load the glyph from the font.
Bye,
zyx
On Sun, 2016-05-22 at 14:39 +0200, zyx wrote:
> This looks like a typo and if no objection is given, I'll revert
> this chunk at the beginning of the next week.
Hi,
I did the revert as revision 1757:
http://sourceforge.net/p/podofo/code/1757
Bye,
zy
he whole of my
> patch.
Naturally. I committed the partial patch as revision 1758:
http://sourceforge.net/p/podofo/code/1758
It fixed unlinking of the freed item in a simple case, which is a good
thing to do, from my point of view.
Thanks and bye,
zyx
uring the weekend, but
please do not hold the release only due to me.
Thanks and bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
What NetFlow Analyzer can do for
oworld.pdf
doesn't do any such transformations, the added text looks properly.
There can be other aspects involved, this is only one I could think of
right now.
Bye,
zyx
--
http://www.litePDF.cz
On 25.5.2016 23:21, zyx wrote:
> On Sun, 2016-05-22 at 14:39 +0200, zyx wrote:
>> This looks like a typo and if no objection is given, I'll revert
>> this chunk at the beginning of the next week.
>
> I did the revert as revision 1757:
> http://sourceforge.net/p/po
wait for you
due this. Just my opinion.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patter
ners of the PoDoFo.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level.
nssl/ossl_typ.h,
both are defining OCSP_RESPONSE. The wincrypt.h has it as a #define,
while the openssl as a structure type name.
Try to define (globally) NOCRYPT, which will avoid inclusion of the
wincrypt.h from the windows.h. The 'globally' can be as a CFLAGS
option, like -DNOCRYPT, or
I'd be able to commit to PoDoFo repository.
Bye,
zyx
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, a
but I do not know for sure.
Bye,
zyx
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming
On Wed, 2016-07-13 at 19:14 +0200, zyx wrote:
> I'll remove the variable declaration once the SourceForge site is
> fully online and I'd be able to commit to PoDoFo repository.
Hi,
committed as revision 1772:
http://sourceforge.net/p/podofo/code/1772
htmare to clean up the patch from unnecessary
white-space and other changes, limit it to only relevant changes. I'll
appreciate if you could be more careful with your patches in the
future. Thanks in advance.
Bye,
//sourceforge.net/p/podofo/code/1774
Bye,
zyx
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
co
, because it's an improvement.
Bye,
zyx
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
cons
as attachments, different mail applications can
garble "patches" sent inline;
b) I would create the .pc file always personally;
c) does the patch expect any
gnInc*.cpp/.h files and structures in the base/ and doc/
directories.
I guess it answered both your questions/parts.
Bye,
zyx
--
___
Podofo-users mailing list
Podofo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/podofo-users
> on a new page, but I don’t want to create a whole new page containing
> nothing else than a signature.
It's only an example, there is no need to create a new page for the
visual representation of the digital signature. [1]
Bye,
zyx
[1] see the 'annotation'-rela
rticular reason
using that old cmake (you claimed you use cmake 2.8)?
Thanks and bye,
zyx
--
--
___
Podofo-users mailing list
Podofo-users@lists.sourceforge.net
htt
+", but I
do not know "Visual Basic C++".
In any case, if you compile all the requirements [1], then it should be
built fine.
Bye,
zyx
[1] See the list of dependencies at
http://podofo.sourceforge.net/about.html#requ
and add to it openssl and eventually oth
mail was held because of mail length" and then one on Thu, 4
Aug 2016 16:28:18 + stating "Resending" [1].
I didn't check the attachment myself, because the change is targeted to
Dennis for review, which I agree with.
Bye,
zyx
[1] https://sourceforge.net/p/pod
t line 37:
https://sourceforge.net/p/podofo/code/HEAD/tree/podofo/branches/PODOFO_0_9_4_BRANCH/src/base/PdfMemoryManagement.cpp#l37
and remove that #ifdef _WIN32 with its corresponding #endif, which
means delete line 45 and 37.
Bye,
e from the system for testing purposes.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
p
ture).
When you fix that, then it'll build. Basically, STLPORT wasn't found,
which is an optional dependency, thus no big deal, but also freetype
wasn't found, which is required.
Bye,
zyx
--
http://www.litePDF.cz
do not know off head).
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
___
Podofo-users mailing list
Podofo-users@lists.
usual signing and it uses Windows Crypto API.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz#include
#include
#include
#include
#include
#include
#include "podofo.h"
using namespace PoDoFo;
// Link with the crypt32.lib file
#pra
te out of my hands at the moment. As
I wrote above, maybe I'll commit both changes for the time being, thus
the PoDoFo will be usable, until someone brave will implement the full
incremental editing.
Bye,
zyx
P.S.: with the attached patch I can sign your simple.pdf
--
exStrings so I’m stuck…any idea how to deal
> with this issue?
Hi,
did you look into the podofotxtextract tool? That may cover what you
are looking for:
https://sourceforge.net/p/podofo/code/HEAD/tree/podofo/trunk/tools/podofotxtextract/
Bye,
zyx
--
http:/
, your replies break threading for some reason.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
___
Podofo-users mailing lis
http://www.litePDF.cz i...@litepdf.cz
--
zyx
Bye,
file. Thanks in advance.
I have some, but they are odd, thus I'd like to have a real-life PDF
would it be possible to share a test PDF with a form to sign, please?
Hi,
>
> the a
On Mon, 2016-09-19 at 10:11 +0200, zyx wrote:
> You can find the workaround attached. I hesitate to commit it to
> PoDoFo sources, but maybe I'll just do it for the time being.
Hi,
I decided to commit that change as a temporary workaround. It's better
this way than the cr
urrently at revision 1785), which partially addresses the
issue. It's partially, because it still fails for linearized PDF files.
That part requires more thinking.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.czIndex: src/doc/PdfSigIncMe
ocument (excluding the Index), and its description references only
'Variable Text' fields, which is not a Sig, right?).
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
he field, which is sort of funny (focused-
>shown, unfocused->hidden). Note that I have basically no control on
the input PDF file, I only sign it and that's all.
Bye,
zyx
P.S.: I may also note that I use pretty ancient Acrobat reader (9.5.5),
though I think it doesn&#x
ignature panel in this case.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
___
Podofo-users mailing list
s some other
changes, all committed as revision 1791:
http://sourceforge.net/p/podofo/code/1791
It would be good to give it a try, maybe I removed too much (it worked
fine locally though).
Thanks and bye,
zyx
--
http://www.litePDF.cz i...@lite
rld-base14.cpp#l276
Also, how do you draw the text, using the PdfPainter::DrawText(), just
like in the example above, or differently?
Bye,
zyx
--
http://www.litePDF.cz
just before
the "%%EOF" token (quotes for clarity only). Also check what was read
into the pszBuff after the Read() call and whether m_device.Device()-
>Eof() returns true.
It's quite unlikely that the stream search handling would be broken in
iOS 10.0, but who knows.
r change also makes those following
lines useless. It needs some testing, though.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
_
sometimes helps to ask and the answer comes
later on its own (it happens to me from time to time too). :-)
Bye,
zyx
--
http://www.litePDF.cz i...@l
y correct;
The "weird" behaviour you see isn't influenced by your changes in the
PoDoFo.
Hope it helps,
zyx
--
http://www.litePDF.cz
makes it very easy to break other things (unintentionally).
Thanks and bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
__
alue is wchar_t, not any other PdfString() constructor. It
depends on the actual system for which you compile, though.
By the way, mentioning your PoDoFo version would be also a good idea.
Bye,
zyx
--
http://www.litePDF.cz
On Thu, 2016-11-17 at 09:59 +0100, zyx wrote:
> I'm afraid I still miss here some important detail(s), I'm sorry.
Hi,
just as a follow up, after some playing with it and with help from some
other folks, it's just as you said, Leonard. Unfortunately trying to
parse
On Sun, 2016-12-11 at 10:34 +0300, Sergey Shambir wrote:
> This patch fixes issues with linking PdfError when PoDoFo built as
> DLL.
Hi,
thanks for the patch, I committed it as revision 1802:
http://sourceforge.net/p/podofo/code/1802
Bye,
zyx
--
http://www.lite
ble
Error Description: Changing values on immutable objects is not allowed.
Callstack:
#0 Error Source: /src/base/PdfDataType.h:148
What am I missing, please?
Bye,
zyx
--
http://www.litePDF.cz
sooner the better, the code freeze is approaching
quickly.
Thanks and bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Check out the vibrant tech community on one o
preferred, somehow.
Thanks again and bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi proces
and bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With
it would take care of itself
transparently, without a need to any management, like when and where to
free it, thus it would not grow ad infinity.
What do you think?
Bye,
zyx
--
http://www.litePDF.cz i...@li
at I had on my mind, involving PdfMutex, thus fully
depending on the build options (-DPODOFO_MULTI_THREAD). I can write a
functional code to express in detail, if you'd like to.
Bye,
zyx
--
http://www.litePDF.cz
application, which is not
good.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based
st for it, then that's for bonus points.
Thank you for your understanding.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Check out the vibrant tech community on o
anges than just re-ordering members. I’ll look
> at that for next release.
That sounds pretty interesting.
Thanks and bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
em will be able to provide the patch as soon as possible.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Check out the vibrant tech community on one of the world's m
On Thu, 2017-01-19 at 13:17 +, Jaseem Ali K T wrote:
> For now I am sending only the fix, which is just an one line change.
Hi,
thanks for the patch. I committed it as revision 1814:
http://sourceforge.net/p/podofo/code/1814
Bye,
zyx
--
http://www.litePDF
ruction:
SET(PODOFO_BUILD_STATIC NOT ${PODOFO_BUILD_SHARED})
didn't result to set the opposite value of PODOFO_BUILD_SHARED, but to
populate the PODOFO_BUILD_STATIC as a list with two values, one being
'NOT' and the other the actual value of the PODOFO_BUILD_SHARED. Hence
such awkward if-ing the
e.
Alternatively, if you face this in any of the PoDoFo examples or tools,
then they are supposed to be fixed.
In other words, I believe that this error is valid and should not be
muted for non-debug builds.
Bye,
zyx
--
http://www.litePDF.cz
e decision up to Dom.
Bye,
zyx
P.S.: By the way, no need to write to me, I do read the list messages,
thus there is no need to CC me in your replies (as I currently receive
the message twice).
--
http://www.litePDF.cz
lps,
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/
ur PDF file, or you copy&pasted some portions
of the tool to your own code? In case you didn't try the tool itself, I
suggest to do it. Otherwise it would be interesting to have the PDF,
which causes the tool to that access violation.
Bye,
zyx
-
h it. It would be
useful to try to reproduce and eventually fix it, or at least to verify
whether the issue is with the build or with the tool or with PoDoFo or
with the PDF file itself or...
Thanks and bye,
zyx
--
http://www.litePDF.cz i
On Tue, 2017-01-31 at 11:59 +0100, zyx wrote:
> > I can give my pdf file here if needed.
>
> As long as you'll not expose any private data with it.
Hi,
as there had been private data involved, Fryderyk sent the file to me
privately and I see that with the svn trunk at
at's all.
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.or
they are known,
nobody replied to them yet. See the mails from Agostino. Thus it's good,
after all, the originator found a way to contact the PoDoFo project
upstream.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
---
not have time currently. If you can come up with a patch,
then it'll be highly appreciated. And having there a unit test for it
would be the best.
Thanks and bye,
zyx
--
http://www.litePDF.cz i.
ls Clear(), which sets the m_bDelayedLoadDone to true.
Does the same code work properly with PoDoFo 0.9.4 for you?
By the way, you should include "podofo.h", not each header separately.
Bye,
zyx
--
http://www.litePDF.cz
t be miscompiling).
Hi,
I made my build with gcc 6.2.1. I cannot test with 7.0.1 at the moment,
the machine doesn't want to connect anywhere. I do not know why. I'll
let you know if I find anything.
Bye,
zyx
--
http://www.litePDF.cz
Etienne said, the problem is
in the ConvertToUnicode() call.
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Check out the vibrant tech community on one of the world
wrong?
Bye,
zyx
--
http://www.litePDF.cz i...@litepdf.cz/* Configure in /home/zyx/podofo-0.9.5/build/
$ cmake -G "Unix Makefiles" -DCMAKE_INSTALL_PREFIX=/tmp/podofo -DCMAKE_BUILD_TYPE=Debug -DWANT_BOOST=ON -DPODOFO_BUILD_SHARED=ON ..
Build
tween versions
(and in general).
Thanks and bye.
zyx
--
http://www.litePDF.cz i...@litepdf.cz
--
Check out the vibrant tech community on one of the world's most
engaging tec
201 - 300 of 729 matches
Mail list logo
