Hi there,
on Tue Sep 27 20:34:56 UTC 2016, Albert Astals Cid wrote:
> The discussion about C++11 was in my opinion not concluded, i.e. noone
> contacted the people that [wrongly] use core library about if they can use C+
> +11, i'd prefer if you revert the change that needs C++11.
note that
Dear Jannick,
> please find attached - and copied below - a proposed patch for your
> consideration to include annotation author information to poppler.
thanks for the patch. Can you please open a report at
https://bugs.freedesktop.org/
and attach the patch there? It will make reviewing it
> In pdfinfo is easier since we don't have to build lots of classes around it,
> but that means that for example I would have to do the same code in Okular
> which is not particularly great.
That does not sound like a good idea to me.
smime.p7s
Description: S/MIME Cryptographic Signature
Hmm. Doesn't that sound more like a bug in hasht.h? In any case,
the file hasht.h on my machine (Debian testing) starts with
#include "prtypes.h".
Best,
Oliver
On 21.12.2017 08:56, suzuki toshiya wrote:
> Hi,
>
> For signature calculation, poppler can use Mozilla's NSS3 library
> optionally.
Hi Alexey,
can you please open a bugreport for this at https://bugs.freedesktop.org/ ?
Otherwise your issue may just fall through the cracks. Please attach your
patch and an example document that shows the problem.
Your patch isn't easily recognizable as such. Can you please post the
output of
Hi Tobias,
> -maybe the pdfcomment TeX package? No idea how complete the standard is
> implemented there...
the pdfcomment package is not a bad option. I don't know about completeness,
but it does
implement a lot of things. It's documentation comes with an example file,
which I have
found
rted then simply applying your patch is much easier. But that
>> is not on me to decide.
>>
>> Regards,
>> Oliver
>>
>>> Regards,
>>> mpsuzuki
>>>
>>>
>>> Oliver Sander wrote:
>>>> Hmm. Doesn't that sound more like a bug in hash
Hi Albert,
that's great news. I was really hoping for this migration to happen soon.
I'm eager to try a merge request, but I think you have to add me to the project
and explicitly give me the right to do so. Could you, please? My login is
'sander'.
Best,
Oliver
On 20.08.2018 19:48, Albert
> As this GitLab instance is the same as GitHub or commercial GitLab, you
> should just create a fork and work off of that. You should not need
> permissions to the main repo to create a MR.
Ah, true. I was used to the dev model where potential contributors need to be
added to the 'project
Hi Leonard, thanks for answering,
> Is there a sample PDF that demonstrates the difference? I didn't see it in
> that long thread.
I think Tobias accidentally posted the wrong link. He meant
https://gitlab.freedesktop.org/poppler/poppler/issues/6
An example file is posted there. For your
Hi Nara,
I can't really comment on whether your approach is a good one. In any case
you may want to try find out at which step in your pipeline the problem
gets introduced. Is the output of printTopdf still correct? If yes,
is the output of renderToImage still correct? And it would help if
Hi Dileep,
I think I can answer most of your questions.
> 1. What does Okular use - the core poppler or poppler Qt5 interface library?
Okular uses the poppler Qt5 interface library exclusively. That library in turn
calls core poppler, which does most of the real work.
>
> 2. There is partial
On 21.02.2018 00:31, Albert Astals Cid wrote:
>
> I'd really appreciate other people's comments on this.
I am generally in favour of changes like this, provided there is no significant
increase in run-time or binary code size. I think such changes do decrease
long-term maintenance costs, and
Hi Allan,
> Where do I find the step-by-step instructions on how to compile poppler on
> Linux (x64)?
in the file INSTALL that is part of the poppler sources.
> Or if there is a place I can download an already compiled executable that
> would be even better...
Pre-compiled poppler binaries
> Ok, I see a bit there. Unfortunately my knowledge on compiling is very
> limited so I don't know how to deal with the errors I get. I install cmake
> and make on my Debian installation but get the error "No CMAKE_CXX_COMPILER
> could be found." Even if I knew how to fix that
For that you
Hi Albert, hi all,
On 06.12.19 12:50, Albert Astals Cid wrote:
> Someone needs to go over them, i've not much idea about cairo nor glib nor
> time to learn them.
given this understandable situation, wouldn't it be consequent to grant full
write access
to (at least) a second person? Currently
Hi Nathanael,
> I'm willing to do some or most of the work to be honest but if
> someone was able to do it faster and for a decent price I'd love that
> even more. I am relatively new to the PDF spec so if I'm doing I'd pay
> for 'rapid response help' so I'm not sitting staring at the same code
I think that this is a worthy goal, but out priority should be guided by
the APIs that downstream users actually need right now. For example,
LibreOffice has its own OutputDev implementation, and would benefit from a
standardization of that interface.
Best,
Oliver
>> We have asked third party uses of non public headers to come forward and
>> describe their needs multiple times, we've always got a big silence as
>> answer.
>
> Not completely true ;-)
Indeed. As mentioned I have also received descriptions of what the LibreOffice
folks do.
In order to
Hi Ken,
can you open an actual bug report at
https://gitlab.freedesktop.org/poppler/poppler
and attach the file? Helping is a lot easier with the problematic file.
Best,
Oliver
On 18.05.20 16:31, Ken Sands wrote:
> Hello all, I tried to run a pdf through pdftocairo in order to embed some
Dear poppler devs,
would the upcoming switch to Qt6 be a good occasion to rename ArthurOutputDev
to something like QtOutputDev, Qt6OutputDev, or QPainterOutputDev? The name
'Arthur' may have historically been associated to Qt, but very few traces
of that remain in the archives (even I don't
Dear Shinichi,
I don't know of any such limits, and I don't see an error message string "out
of memory"
anywhere in the poppler source code. Could it be the python library that
enforces the
limit? Do you have access to its source code? What are you trying to do with
that
library?
Best
Hi Jon,
thanks for reaching out---what you have sounds like an interesting project.
In order to get your code reviewed for inclusion into poppler you need to get
an account for the freedesktop/poppler GitLab instance:
https://gitlab.freedesktop.org/poppler/poppler
Afterwards please open a
defines
the order in which rendering and hit testing is performed. However, there is
nothing that precludes you doing what you're doing with the multiple click
choices as well.
Leonard
On 12/14/20, 2:28 AM, "poppler on behalf of Oliver Sander"
wrote:
Dear Leonard,
Dear Leonard,
please allow me to ask about a detail of the PDF spec. In
https://bugs.kde.org/show_bug.cgi?id=429635
we have received a pdf document with two link actions in the
very same position. Unfortunately, the spec doesn't seem
to say what to do in this case. Treat only the first
Hi Thomas,
aller Anfang ist schwer. Stick to it and it will seem easier
after a while. You may want to look at Leonard Rosenthol's
book about pdf, but the standard itself is actually quite
readable (compared to, say, the C++ standard).
Best,
Oliver
On 13.06.21 11:51, thomas.huxh...@web.de
Hi Rob,
2. After writing a bit of code to add an outline and save the
resulting PDF, the file had a trailer section which referred to the
new Catalog dictionary as expected. However, the new Catalog
dictionary had the same object and generation numbers as the old one.
So there were now two
No objections besides the one mentioned by Leonard.
It would also allow to replace Object by std::variant.
Best,
Oliver
On 27.09.21 00:10, Leonard Rosenthol wrote:
The only downside is that it will prevent the use of Poppler on some Unix/Linux
distros due to older GCCs being present…
I do not understand well your question. But I know that a pdf document contains
pages.
I have pdf documents in memory (read from a database) and I need to merge these
documents in memory to write them back in a database...
You need to give a few more details about what you mean by "I have
John's answer below quite exactly reflects my own opinion about this.
Best,
Oliver
On 03.03.22 09:59, jcup...@gmail.com wrote:
gcc at least (clang too I think) will warn for misleading indentation,
so I think forcing braces probably won't add much extra safety.
Braces for single lines adds
CI: make the libcpp build use C++23
It will help us make sure we don't do things like std::string s = nullptr; (since that is not possible on C++23)
Very nice move! The std::string s = nullptr pitfall was very easy to fall into.
Best,
Oliver
smime.p7s
Description: S/MIME
On 19.08.22 23:23, Albert Astals Cid wrote:
I ran the SonarCloud analizer on the poppler_mirror github mirror
https://sonarcloud.io/project/overview?id=tsdgeos_poppler_mirror
I'm not super convinced the analizer is super smart but if someone has time i
guess it wouldn't hurt to try to make it
32 matches
Mail list logo
