okular | annotate documents of various formats | Document Editor library

You'd need to know the name that is currently used in the resources, so check these with resources.getFontNames()

2. To replace a standard 14 font, use this font object:

You are missing extra-cmake-modules, a package from KDE Frameworks 5. This package is available in every linux distro that ships KDE. You'll need more -devel/-dev packages other than ECM.

Take a look at http://www.linuxfromscratch.org/blfs/view/svn/kde/extra-cmake-modules.html for details, and chapter 30 too.

The okular site (https://okular.kde.org) will also guide you to build from source.

Use pdfedit . You can install it in Linux from here (it worked in ubuntu 18.04 LTS bionic beaver).

Type pdfedit in terminal to open the program and load your pdf file .

In the right side of the window you will see a tree . Open outlines . Then find each node of the pdf outline you want to be always display wrapped . Open that node and left click on it and choose add item to dictionary. This item should have property name Count be of int type and value equal to the negative of the already existing Count property (left click on the count property and choose show string representation , look at left down window and you will see the value that is has) . Replace the already existing Count property and that node will always be wrapped when you open the pdf .

I still do not know a faster way to do that in linux .

Edit : A somewhat faster solution is to use jPdfTweak . Download it from here and read the README.txt file on how to run it via terminal .

You are not supposed to edit these files using vi, just write values using echo. Vim will try to create a file in the same directory and rename it over the latency_timer file which does not work in /sys

Instead, use something like:

Thanks to this answer I have deduced a solution: https://serverfault.com/questions/414074/mount-cifs-host-is-down/929331#929331

Not sure why but I suspect an upgrade in my computer of SMB has meant I am no longer compatible with their (older?) version.

This now works if I do it manually in the terminal and specify vers = 1.0:

In short: The (original) PDF does not contain the information required for regular text extraction as described in the PDF specification. Depending on the exact nature of your task, you might try to add the required information to the existing text objects and fonts or you might go for OCR.

The PDF specification ISO 32000-1 (and similarly ISO 32000-2, too) describes an algorithm for mapping character codes to Unicode values using information available directly inside the PDF.

It has been quoted very often in other stack overflow answers (see here, here, here, here, here, or here), so I won't quote it here again.

Essentially this is the algorithm used by Adobe Acrobat during copy&paste and also by many other text extractors.

In PDFs which don't contain the information required for text extraction, you eventually get to this point in the algorithm:

If these methods fail to produce a Unicode value, there is no way to determine what the character code represents in which case a conforming reader may choose a character code of their choosing.

This is where the text extraction implementations differ, they try to determine the matching Unicode value by using heuristics or information from beyond the PDF or applying OCR to the glyph in question.

That the different programs you tried returned so different results shows that

1. your PDF does not contain the information required for the algorithm above from the PDF specification and

2. the heuristics used by those programs differ relevantly and Okular's heuristics work best for your document.

There are multiple options, more or less feasible depending on your concrete case:

1. Ask the source of the PDF for a version that contains proper information for text extraction.

   Unless you have a contract with that source that requires them to supply the PDFs in a machine readable form or the source is otherwise obligated to do so, they usually will decline, though...

2. Apply OCR to the PDF in question.

   Depending on the quality of the OCR software and the glyphs in the PDF, the results can be of a questionable quality; e.g. in your "PDF copy text issue-Text layer workaround.pdf" the header "Chapter 1: Derivative Securities" has been recognized as "Chapter1: Deratve Securites"...

3. You can try to interactively add manually created ToUnicode maps to the PDF, e.g. as described by Tilman Hausherr in his answer to "how to add unicode in truetype0font on pdfbox 2.0.0".

   Depending on the number of different fonts you have to create the mappings for, this approach might easily require way too much time and effort...

The problem is caused by the command

After a lot of digging I came across these posts: post1 post2 from which the following solution emerged:

It's simply a comment starting symbol. That's also why it's chosen as the default symbol for the superuser shell, because someone mistakenly pasted a dangerous command intended for superusers will be safe