Opened 5 months ago

Last modified 2 months ago

#368 new defect

Find not working in some cases

Reported by: shmuel Owned by:
Priority: minor Milestone: 1.4.1
Component: Backend Version: 1.4.0
Keywords: Cc:


I am creating a PDF file from a LaTeX file that uses the hyperref package. I compiled the file with the pdflatex option of MiKTeX. The output is annotated with strings of the form {label}, and I am able to copy those to the clipboard. However, a search for those strings fails. The LaTeX source is too large to upload, so I will attempt to reproduce this with a smaller file.

To verify that the problem was in Lucide rather than the file, I opened it in Acrobat and did the same searches, which did find the strings.

Attachments (1)

testpdf.tex (61.8 KB) - added by shmuel 5 months ago.
LaTeX source for the PDF

Download all attachments as: .zip

Change History (7)

Changed 5 months ago by shmuel

LaTeX source for the PDF

comment:1 Changed 5 months ago by shmuel

I created a smaller test case, but the PDF is still too large to upload. I've uploaded the LaTeX source, and will see whether I can cut it down enough to upload the PDF while still showing the problem.

comment:2 Changed 5 months ago by gyoung

Does the file work as expected in QPDFview? The fact that it works in Acrobat doesn't tell me if Poppler (PDF backend for Lucide) supports it appropriately. If it doesn't there isn't much I can do about it. Please email the file directly to me at ygk at qwest dot net.

comment:3 Changed 4 months ago by shmuel

I'm not familiar with QPDFview. I sent an e-mail with the PDF as an attachment.

comment:4 Changed 3 months ago by gyoung

QPDFView is available from the netlabs RPM repository (use ANPM). I tested this with QPDFView and it doesn't find them either. That means it might be a Poppler issue. It seems to relate to the symbols as I find some of the things in the {} and not others. Can you give me an example of what you are searching for and not finding so I can be sure I understand the problem.

It also might be a font/character set/code page issue. This is what I get if I copy the stuff following the very first "{" in the file you sent {(f , o 1 , o 2 ) ∈ M } and this isn't the same as the original in the document. If I search for M the M in this string is found. I am guessing you are using cut and paste to enter the search strings.

comment:5 Changed 2 months ago by shmuel

I am searching for any of the {foo:bar} symbols in the right hand margin, which mark either places where a LaTeX label is defined with \label{foo:bar} or places where the label is refered to by, e.g., \cref{foo:bar}. For instance, in the document that was too large to attach, {part:intro} in the margin of page 1 marks the definition of Part I (Introduction) and {part:lcs} marks a reference to part IX (Local Coordinate Spaces) on page 114.

The same labels appear on page 1 of the test pdf, but the text generated from the reference has question marks because only the beginning of the document is in testpdf.tex, from which I generated testpdf.pdf.

I don't know whether it is related, but if I copy the marginal labels and paste them into another window, I get gibberish.

Last edited 2 months ago by shmuel (previous) (diff)

comment:6 Changed 2 months ago by shmuel

I enter the search string either by keying it in or by copying it from the tex file (ASCII only LaTeX source) from which the PDF was compiled.

Note: See TracTickets for help on using tickets.