poppler issueshttps://gitlab.freedesktop.org/poppler/poppler/-/issues2018-09-02T11:34:14Zhttps://gitlab.freedesktop.org/poppler/poppler/-/issues/88pdftotext only outputs first page content with -bbox-layout option2018-09-02T11:34:14ZBugzilla Migration Userpdftotext only outputs first page content with -bbox-layout option## Submitted by Jonathan Marchand
Assigned to **poppler-bugs**
**[Link to original bug (#93344)](https://bugs.freedesktop.org/show_bug.cgi?id=93344)**
## Description
The new -bbox-layout option introduced in 911d9fc8d85b776418039b...## Submitted by Jonathan Marchand
Assigned to **poppler-bugs**
**[Link to original bug (#93344)](https://bugs.freedesktop.org/show_bug.cgi?id=93344)**
## Description
The new -bbox-layout option introduced in 911d9fc8d85b776418039b4eebb37200a0987554 adds extra bounding box info. However it only displays the first page content, other pages are shown empty.
The -bbox option still works as intended.
By browsing the code, my guess is that comes from textOut->takeText() (line 528 from utils/pdftotext.cc) who get the TextPage content only in its first invocation.https://gitlab.freedesktop.org/poppler/poppler/-/issues/83Expose poppler-cairo2020-11-07T23:03:59ZBugzilla Migration UserExpose poppler-cairo## Submitted by Lu Wang
Assigned to **poppler-bugs**
**[Link to original bug (#55540)](https://bugs.freedesktop.org/show_bug.cgi?id=55540)**
## Description
Created attachment 67993
Install CairoOutputDev.h
Not sure why it has bee...## Submitted by Lu Wang
Assigned to **poppler-bugs**
**[Link to original bug (#55540)](https://bugs.freedesktop.org/show_bug.cgi?id=55540)**
## Description
Created attachment 67993
Install CairoOutputDev.h
Not sure why it has been hidden (not installed even with --enable-xpdf-headers)
Guess not harmful to expose it for hacking.
~~**Attachment 67993**~~, "Install CairoOutputDev.h":
[cairo_outputdev.patch](/uploads/89552739b0cc13fe5bfc81f52cc8e4ac/cairo_outputdev.patch)https://gitlab.freedesktop.org/poppler/poppler/-/issues/53RTL: Copy/Paste Arabic results in reverse order of Arabic phrases after pasting2021-03-12T22:43:03ZBugzilla Migration UserRTL: Copy/Paste Arabic results in reverse order of Arabic phrases after pasting## Submitted by Germán Poo-Caamaño
Assigned to **poppler-bugs**
**[Link to original bug (#106805)](https://bugs.freedesktop.org/show_bug.cgi?id=106805)**
## Description
As reported in https://gitlab.gnome.org/GNOME/evince/issues/4...## Submitted by Germán Poo-Caamaño
Assigned to **poppler-bugs**
**[Link to original bug (#106805)](https://bugs.freedesktop.org/show_bug.cgi?id=106805)**
## Description
As reported in https://gitlab.gnome.org/GNOME/evince/issues/489
```
Hello,
When I copy phrases from Arabic PDFs and then past it anywhere , the order of words becomes reverse.For example when I copy
" بسم الله الرحمن الرحيم "
then past it anywhere it becomes
" الرحيم الرحمن الله بسم "
For more explaining - in English - If I copy "Hello Ali" the result after pasting is "Ali Hello" .
Contrary to English, Arabic is written from right to left.
You can download a document which has the same Arabic phrase
"بسم الله الرحمن الرحيم" from the following link
http://www.gulfup.com/?tCcbsP
And If you like in the following link you can find several Arabic PDFs
http://librebooks.org/
```
The first link does not work. However, I tried with a random book from the the second one (http://librebooks.org/) and it is reproducible.
It may be related to [Bug 105015](https://bugs.freedesktop.org/show_bug.cgi?id=105015), although the reverse text in that report is per character. Selecting/Copy/Paste is per word.
At last but not least, I tested it with poppler-glib-demo, but I am filing this issue to general as I notice the RTL support is lacking across frontends.https://gitlab.freedesktop.org/poppler/poppler/-/issues/34Add support for pdf tooltip!2021-02-11T23:02:14ZBugzilla Migration UserAdd support for pdf tooltip!## Submitted by 9u0..@..il.com
Assigned to **poppler-bugs**
**[Link to original bug (#105326)](https://bugs.freedesktop.org/show_bug.cgi?id=105326)**
## Description
Some PDf files have 'tooltip' feature on them. For an example doc...## Submitted by 9u0..@..il.com
Assigned to **poppler-bugs**
**[Link to original bug (#105326)](https://bugs.freedesktop.org/show_bug.cgi?id=105326)**
## Description
Some PDf files have 'tooltip' feature on them. For an example document, see the section 3.2 (\pdftooltip command) of the 'package documentation' file on this website (https://www.ctan.org/pkg/pdfcomment).
I tested this using the aformentioned .pdf file and various PDF readers. It worked perfectly with Microsoft Edge (Windows), SumatraPDF (Windows, Wine on Linux and macOS), Adobe Acrobat Reader (Windows and macOS), and Foxit reader (Windows, Linux, and macOS). But not with Evince. (Actually I couldn't find any Linux-native reader that support this tooltip feature.) An Evince developer told me that this is because Poppler doesn't support API for tooltips (https://bugzilla.gnome.org/show_bug.cgi?id=793986).https://gitlab.freedesktop.org/poppler/poppler/-/issues/1469Help using text decorations like overlines2024-02-29T22:19:26ZAaron LinHelp using text decorations like overlinesIn some PDFs there is an "overline" text decoration (like an underline, but directly above the text). It seems most PDF utilities represent this as a text decoration, not just a line, so I assume Poppler has some support for it. I don't ...In some PDFs there is an "overline" text decoration (like an underline, but directly above the text). It seems most PDF utilities represent this as a text decoration, not just a line, so I assume Poppler has some support for it. I don't see this anywhere in Poppler's TextAnnotations - can someone please point me in the right direction?https://gitlab.freedesktop.org/poppler/poppler/-/issues/1467'Mu' symbol becomes 'alpha' using poppler2024-02-20T13:15:13ZBruno Lopes'Mu' symbol becomes 'alpha' using popplerThe greek symbol 'mu' in PDF files read by poppler becomes alpha (right after `log[(` in the screenshots). This happens in many programs that depends on poppler.
See the original file: [plot2005_-_2009Jan_0.pdf](/uploads/5ef29338ccbd0bc...The greek symbol 'mu' in PDF files read by poppler becomes alpha (right after `log[(` in the screenshots). This happens in many programs that depends on poppler.
See the original file: [plot2005_-_2009Jan_0.pdf](/uploads/5ef29338ccbd0bcf6ad0e33d81815539/plot2005_-_2009Jan_0.pdf)
This was first reported in GIMP: https://gitlab.gnome.org/GNOME/gimp/-/issues/4287
In Inkscape the same bug can be see:
![image](/uploads/6026088ea4e9761adb2d647dbc4f125b/image.png)
And in Evince:
![image](/uploads/330b96eb04a9210d6e08b9b291607a47/image.png)
---
This seem to only happen in Windows but [no specific patch](https://github.com/msys2/MINGW-packages/tree/master/mingw-w64-poppler) is being applied by the MSYS2 folks. Maybe [NSS3](https://github.com/msys2/MINGW-packages/blob/c73984859915349a637686d7ceb96a27398ef2f2/mingw-w64-poppler/PKGBUILD#L80) build option?https://gitlab.freedesktop.org/poppler/poppler/-/issues/1447Poppler fails to open some password encrypted PDF which other readers can ope...2024-02-22T08:15:37ZNelson Benítez LeónPoppler fails to open some password encrypted PDF which other readers can open (after repairing)In this [downstream Evince issue](https://gitlab.gnome.org/GNOME/evince/-/issues/1889), a reporter mailed me a Password protected PDF document generated by his turkish online bank which he could not attach to gitlab as it contained perso...In this [downstream Evince issue](https://gitlab.gnome.org/GNOME/evince/-/issues/1889), a reporter mailed me a Password protected PDF document generated by his turkish online bank which he could not attach to gitlab as it contained personal data.
The PDF metadata shows it was created by `JasperReports Library version 6.9.0` and the PDF opens fine in Acrobat Reader, Firefox, and in `Xpdf 4.04`.
`Xpdf 4.04` shows the PDF had to be reconstructed to be opened, the Xpdf error window shows:
```
Syntax Error: Couldn't read xref table
Syntax Warning: PDF file is damaged -attempting to reconstruct xref table...
```
`Xpdf 4.04` is able to open this file because it has an updated "repairing code", my assumption comes from the fact that `Poppler`'s `XRef.cc` has the [comment shown below](https://gitlab.freedesktop.org/poppler/poppler/-/blob/poppler-23.06.0/poppler/XRef.cc#L857) while `XRef.cc` in `Xpdf 4.04` does not have that comment anymore, and the code seems refactored to support the aforementioned repairing from inside object streams.
```cpp
// Attempt to construct an xref table for a damaged file.
// Warning: Reconstruction of files where last XRef section is a stream
// or where some objects are defined inside an object stream is not yet supported.
// Existing data in XRef::entries may get corrupted if applied anyway.
bool XRef::constructXRef(bool *wasReconstructed, bool needCatalogDict)
{
//bla bla
}
```
We found where Firefox `PDF.js` fixed this same bug:
- https://github.com/mozilla/pdf.js/issues/15893
- https://github.com/mozilla/pdf.js/pull/15897
and good news they had a testcase pdf file which we could use publicly:
- [issue15893_reduced.pdf](/uploads/53917879af696462740484498756021d/issue15893_reduced.pdf) password is `test`
Anyway, I'm sure our Evince user Sabri Ünal would mail privatly the bank PDF file to any Poppler developer interested in trying that too.
------------
So, I went ahead and took the time to locate the involved Xpdf 4.04 code and migrate it to Poppler, with sucessful results in opening the problematic password encrypted files. I'll be sending MR's.https://gitlab.freedesktop.org/poppler/poppler/-/issues/1445'Symbol' font on Windows not found2023-12-10T22:38:46ZHakan Usakli'Symbol' font on Windows not foundAfter updating poppler to version 23.11 on Windows an issue started happening that seems to be documented but I am still unsure how to deal with it properly. I would appreciate any help.
Older versions of poppler did not complain about ...After updating poppler to version 23.11 on Windows an issue started happening that seems to be documented but I am still unsure how to deal with it properly. I would appreciate any help.
Older versions of poppler did not complain about this: Syntax Error: No display font for 'Symbol' when using
`pdffonts -subst input.pdf `
or
`pdftocairo.exe -pdf input.pdf output.pdf`
What I checked and tried so far:
-File 'symbol.ttf' is available in Windows/Fonts directory. Copying it into the binary folder of the poppler executable makes no difference.
-I have read Issue #1174 - Invalid mathematical (cryptographic) symbols rendered in some PDF's (needs symbol.ttf) but that issue is on Linux, not Windows.
The Changelog from Version 23.06 reads:
```
Windows: Look for fonts in both windows font dir and poppler fonts dir
Windows: symbol.ttf is not a good Symbol font
```
I did not understand why 'symbol.ttf' is not considered a good symbol font. Windows users use it because it comes with the system.
My question: what is the recommended way on Windows systems, starting with release 23.06 and higher so that symbol.ttf is not reported as a syntax error or missing. Would an entry in a configuration file help to point poppler to the symbol.ttf file ? How would that config file need to look like and where does it need to be placed. A sample would be appreciated.
If required I can supply a sample file that is looking for 'symbol'
Best Regards
PS:
I am upgrading from version 21.11 and there is significant performance improvement on some files for pdfcairo -pdf (rewriting pdfs). Processing speed is much faster. Great work.https://gitlab.freedesktop.org/poppler/poppler/-/issues/1442PDF incorrectly cropped when converted to eps with pdftocairo2023-10-12T22:21:36ZMarkus JohnssonPDF incorrectly cropped when converted to eps with pdftocairoThe content gets incorrectly cropped when converting this pdf to eps using pdftocairo.
Instead of the expected size (as per pdfinfo) of `563.04 x 450 pts` I get (with whatever parameters I try) this cropped bounding box: `%%BoundingBox:...The content gets incorrectly cropped when converting this pdf to eps using pdftocairo.
Instead of the expected size (as per pdfinfo) of `563.04 x 450 pts` I get (with whatever parameters I try) this cropped bounding box: `%%BoundingBox: 7 137 450 551` in the eps file.
SVG, png and jpeg all works fine. (svg: ` width="563.03998" height="450" viewBox="0 0 563.03998 450"`)
[example.pdf](/uploads/2772d4a29be466addc3494685e020139/example.pdf)
[output.eps](/uploads/885f37c40713bcf68a61e592db73bc24/output.eps)
I'm using Poppler 23.10.0 on Macos. I got the same result with 23.08.0 on Windows. And 22.02.0 on linux mint.https://gitlab.freedesktop.org/poppler/poppler/-/issues/1439Poppler 23.09 and Qt 6.5.2 - #include "poppler-export.h" <--- File not found.2023-09-27T11:21:46ZOnevoidPoppler 23.09 and Qt 6.5.2 - #include "poppler-export.h" <--- File not found.While trying to build **Poppler 23.09** on **Qt 6.5.2**, there's the following critical error in **qt6/src/poppler-annotation.h**, line #45.
**#include "poppler-export.h"** <--- File not found.
This critical file **"poppler-export.h"...While trying to build **Poppler 23.09** on **Qt 6.5.2**, there's the following critical error in **qt6/src/poppler-annotation.h**, line #45.
**#include "poppler-export.h"** <--- File not found.
This critical file **"poppler-export.h"** is nowhere to be found in the Poppler file system structure.
Thanks in advance.https://gitlab.freedesktop.org/poppler/poppler/-/issues/1438Poppler-23.09.0 fails to build on Solaris2023-10-02T07:15:26ZMartin ŘehákPoppler-23.09.0 fails to build on Solarispoppler-23.09.0 fails to build with following error on Solaris:
```
[ 48%] Linking CXX shared library libpoppler.so
ld: fatal: option --version-script requires option -z gnu-version-script-compat to be specified
collect2: error: ld retur...poppler-23.09.0 fails to build with following error on Solaris:
```
[ 48%] Linking CXX shared library libpoppler.so
ld: fatal: option --version-script requires option -z gnu-version-script-compat to be specified
collect2: error: ld returned 1 exit status
```
CMakeLists.txt contains this:
```
if(UNIX AND (NOT APPLE))
set_target_properties(poppler PROPERTIES LINK_OPTIONS LINKER:--version-script=${LINKER_SCRIPT})
endif()
```
I tried to use `-z gnu-version-script-compat` as suggested, but it is failing with following error:
```
[ 64%] Linking CXX executable pdfseparate
Undefined first referenced
symbol in file
__iob CMakeFiles/pdfseparate.dir/parseargs.cc.o (symbol belongs to unavailable version ../libpoppler.so.131.0.0 ((null)))
ld: fatal: symbol referencing errors
collect2: error: ld returned 1 exit status
```
To be honest I don't understand the latter issue at all, so the only way I was able to workaround that was to ifdef it this way:
```
-if(UNIX AND (NOT APPLE))
+if(UNIX AND (NOT APPLE AND NOT CMAKE_HOST_SOLARIS))
```
Solaris has specific ld which tries to be compatible with GNU ld, but for some reason doesn't behave in the same way here.
Is this linker setting important or is it just fine to merge the change above to make it build, please?
Thank you,
Martinhttps://gitlab.freedesktop.org/poppler/poppler/-/issues/1436Too big png and jpg are not displayed2023-10-22T15:00:36ZRiccardo GagliarducciToo big png and jpg are not displayedSome files, a pdf with embedded graphic and the exported images (pdfimages -j ...), does not display.
They can be opened in Gimp and partially Krita without problems.
The source is public Italian cartography.
Files are quite big so here...Some files, a pdf with embedded graphic and the exported images (pdfimages -j ...), does not display.
They can be opened in Gimp and partially Krita without problems.
The source is public Italian cartography.
Files are quite big so here a WeTransfer link: https://we.tl/t-kokvgUrNME
Thank you,
Riccardohttps://gitlab.freedesktop.org/poppler/poppler/-/issues/1433Pdfseparate: A type error occurred while calling the object2023-09-11T21:37:56Z刘文Pdfseparate: A type error occurred while calling the objectversion:23.08.0<br>
My system OS:Ubuntu 20.04<br>
reproduce: pdfseparate poc.pdf output-%d.pdf<br>
Final error message prompt“Internal Error (0): Call to Object where the object was type 10, not the expected type 7”<br>
I reinstalled and...version:23.08.0<br>
My system OS:Ubuntu 20.04<br>
reproduce: pdfseparate poc.pdf output-%d.pdf<br>
Final error message prompt“Internal Error (0): Call to Object where the object was type 10, not the expected type 7”<br>
I reinstalled and compiled the poppler that fixed the issue with issues/1428, and the poc.pdf in issues/1428 no longer triggers crashes. But I found a new PDF file that seems to have triggered the same issue<br>
The stack information is as follows:<br>
Program received signal SIGABRT, Aborted.<br>
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50<br>
50 ../sysdeps/unix/sysv/linux/raise.c: 没有那个文件或目录.<br>
(gdb) bt<br>
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50<br>
#1 0x00007ffff7593859 in __GI_abort () at abort.c:79<br>
#2 0x00007ffff7c28796 in Object::getDict (this=this@entry=0x7fffffffd888) at /Oscar01/liujiahao/poppler-master/poppler/Object.h:435<br>
#3 0x00007ffff7d437ab in PDFDoc::savePageAs (this=0x653fe0, name=..., pageNo=1) at /Oscar01/liujiahao/poppler-master/poppler/PDFDoc.cc:927<br>
#4 0x00000000004055ad in extractPages (srcFileName=<optimized out>, destFileName=0x7fffffffed1e "out/put-%d.pdf")
at /Oscar01/liujiahao/poppler-master/utils/pdfseparate.cc:123<br>
#5 main (argc=<optimized out>, argv=<optimized out>) at /Oscar01/liujiahao/poppler-master/utils/pdfseparate.cc:156<br>[poc.pdf](/uploads/9d5e293105ec15bdf00d48272bac2f87/poc.pdf)https://gitlab.freedesktop.org/poppler/poppler/-/issues/1432Rendering issue with literata variable font2023-09-12T06:10:28ZMara MRendering issue with literata variable fontThe right-pointing double angle quotation mark (U+00BB) is rendered wrongly in Literata (variable font). In the static version there is no problem.
![image](/uploads/b6119e867533c11e971aa9520e91b2cf/image.png)
[Test3-varmodern.pdf](/up...The right-pointing double angle quotation mark (U+00BB) is rendered wrongly in Literata (variable font). In the static version there is no problem.
![image](/uploads/b6119e867533c11e971aa9520e91b2cf/image.png)
[Test3-varmodern.pdf](/uploads/4b6b2df9ec88b9429302ed58ef780962/Test3-varmodern.pdf)https://gitlab.freedesktop.org/poppler/poppler/-/issues/1431The program seems to have fallen into a loop2023-09-06T20:18:48Z刘文The program seems to have fallen into a loopversion:23.08.0
My system OS:Ubuntu 20.04
reproduce: pdfsig poc.pdf
[1.pdf](/uploads/78f7e55de28a7571d32b528142a84818/1.pdf)
[2.pdf](/uploads/ff9da01eddb6d4f96c8c362edb1aef65/2.pdf)
[3.pdf](/uploads/f5ae01c0ba61b264ca5f84af79b21a24/3...version:23.08.0
My system OS:Ubuntu 20.04
reproduce: pdfsig poc.pdf
[1.pdf](/uploads/78f7e55de28a7571d32b528142a84818/1.pdf)
[2.pdf](/uploads/ff9da01eddb6d4f96c8c362edb1aef65/2.pdf)
[3.pdf](/uploads/f5ae01c0ba61b264ca5f84af79b21a24/3.pdf)https://gitlab.freedesktop.org/poppler/poppler/-/issues/1430The program seems to have fallen into a loop in DCTStream.cc2023-09-19T22:37:25Z刘文The program seems to have fallen into a loop in DCTStream.ccversion:23.08.0
My system OS:Ubuntu 20.04
reproduce: pdfunite 1.pdf poc.pdf output.pdf
[1.pdf](/uploads/d93654243413abef9a0321e925019550/1.pdf)
[poc.pdf](/uploads/59ef1836587e3d9e10f1b7a65f3bd639/poc.pdf)
reproduce: pdfseparate poc...version:23.08.0
My system OS:Ubuntu 20.04
reproduce: pdfunite 1.pdf poc.pdf output.pdf
[1.pdf](/uploads/d93654243413abef9a0321e925019550/1.pdf)
[poc.pdf](/uploads/59ef1836587e3d9e10f1b7a65f3bd639/poc.pdf)
reproduce: pdfseparate poc2.pdf out/put-%d.pdf
[poc2.pdf](/uploads/e7795393163ef4b3bef0e81dcf4f193f/poc2.pdf)https://gitlab.freedesktop.org/poppler/poppler/-/issues/1428Pdfseparate: A type error occurred while calling the object2023-09-04T22:50:56Z刘文Pdfseparate: A type error occurred while calling the objectversion:23.08.0
My system OS:Ubuntu 20.04
reproduce: pdfseparate poc.pdf output-%d.pdf
Final error message prompt“Internal Error (0): Call to Object where the object was type 5, not the expected type 7”
The stack information is as fo...version:23.08.0
My system OS:Ubuntu 20.04
reproduce: pdfseparate poc.pdf output-%d.pdf
Final error message prompt“Internal Error (0): Call to Object where the object was type 5, not the expected type 7”
The stack information is as follows:
Program received signal SIGABRT, Aborted.<br>
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50<br>
50 ../sysdeps/unix/sysv/linux/raise.c: 没有那个文件或目录.<br>
(gdb) bt<br>
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50<br>
#1 0x00007ffff7594859 in __GI_abort () at abort.c:79<br>
#2 0x00007ffff7d44a22 in PDFDoc::savePageAs (this=0x654560, name=..., pageNo=1) at /Oscar01/liujiahao/poppler/poppler/Object.h:435<br>
#3 0x00000000004055ad in extractPages (srcFileName=<optimized out>, destFileName=0x7fffffffed26 "output-%d.pdf") at /Oscar01/liujiahao/poppler/utils/pdfseparate.cc:123<br>
#4 main (argc=<optimized out>, argv=<optimized out>) at /Oscar01/liujiahao/poppler/utils/pdfseparate.cc:156<br>
Attach the poc file. If this is not an error or if it has already been discovered, we apologize for wasting your time. thank you very much indeed
[poc.pdf](/uploads/b425f436a6911615474db5418c7501cd/poc.pdf)https://gitlab.freedesktop.org/poppler/poppler/-/issues/1427Failed conversion, file attached as requested ...2023-09-05T19:20:57ZAndrew TealFailed conversion, file attached as requested ...[RAFA_Sud-Ouest_France_History_2021_ENG.pdf](/uploads/1f983c25717ddc41d808e257881b4776/RAFA_Sud-Ouest_France_History_2021_ENG.pdf)[RAFA_Sud-Ouest_France_History_2021_ENG.pdf](/uploads/1f983c25717ddc41d808e257881b4776/RAFA_Sud-Ouest_France_History_2021_ENG.pdf)https://gitlab.freedesktop.org/poppler/poppler/-/issues/1423vector anti-aliasing: pdftoppm produces different result (darker, more black)...2023-08-25T18:49:57ZMilan Hauthvector anti-aliasing: pdftoppm produces different result (darker, more black) than chromium PDF readeri want to render PDF vector graphics to high quality raster graphics
for this job im using pdftoppm, but surprisingly, it creates a slightly different result than the chromium pdf renderer:
with pdftoppm, fine black lines are darker, s...i want to render PDF vector graphics to high quality raster graphics
for this job im using pdftoppm, but surprisingly, it creates a slightly different result than the chromium pdf renderer:
with pdftoppm, fine black lines are darker, so overall, the graphic looks darker
https://github.com/milahu/pdf-rendering-chromium-versus-pdftoppm
![pdf-rendering-chromium-versus-pdftoppm-png-720dpi](/uploads/68cbd034a5ccbe198e1f4dcfb6c3a3bd/pdf-rendering-chromium-versus-pdftoppm-png-720dpi.png)
[page-061.input-vectors.pdf](/uploads/311dd53f2f836e75ce6e75ecde96fb53/page-061.input-vectors.pdf)
the screenshot is with chromium PDF reader at full zoom (500%) which gives the same size as a 720dpi resolution image
i have tried running pdftoppm with different options, and only `-aaVector no` makes the result worse. so i guess im looking for a PDF rendering engine with more vector anti-aliasing, or with higher-precision anti-aliasing
| `pdftoppm` | `pdftoppm -aaVector no` |
| ------ | ------ |
| ![page-061.input-vectors.pdf.720dpi.png.trim](/uploads/4d9dfe2a36fecc5b97e80e2d78cebbd5/page-061.input-vectors.pdf.720dpi.png.trim.png) | ![page-061.input-vectors.pdf.720dpi.aaVector-no.png.trim](/uploads/bdea830a3ef2c11cdf2c669eb5fb1d76/page-061.input-vectors.pdf.720dpi.aaVector-no.png.trim.png) |https://gitlab.freedesktop.org/poppler/poppler/-/issues/1422Missing Mathematical Symbols2023-11-09T23:19:26ZBalbir ThomasMissing Mathematical SymbolsKindly see [linked PDF](https://download.e-bookshelf.de/download/0010/9228/27/L-G-0010922827-0027094516.pdf) ( [also attached](https://gitlab.freedesktop.org/poppler/poppler/uploads/b475669657c2214505026852f57ca4be/L-G-0010922827-0027094...Kindly see [linked PDF](https://download.e-bookshelf.de/download/0010/9228/27/L-G-0010922827-0027094516.pdf) ( [also attached](https://gitlab.freedesktop.org/poppler/poppler/uploads/b475669657c2214505026852f57ca4be/L-G-0010922827-0027094516.pdf) ) with the missing symbols problem. `pdffonts` shows that all fonts are embedded. It may be pertinent to note that these symbols are shown in the PDF viewer shipped with modern browsers (Firefox and Chrome) on the same platform that libpoppler is being used. Compare for example rendering of page 27 using Evince or XPDF with the same page rendered in the browser PDF viewer.
PS: I am aware this issue may duplicate #1253 but I am re-filing it just in case. Kindly feel free to close if you think this is a duplicate. I have also put a comment in the original issue. The problem is not specific to Okular and happens with all PDF readers using libpoppler.