Rockbox

  • Status Closed
  • Percent Complete
    100%
  • Task Type Bugs
  • Category Manual
  • Assigned To No-one
  • Operating System All players
  • Severity Low
  • Priority Very Low
  • Reported Version Daily build (which?)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by zagor - 2008-11-14
Last edited by bluebrother - 2008-12-01

FS#9550 - Settings are not searchable in xpdf

Sections of the manual marked \setting{} cannot be searched in xpdf.

Closed by  bluebrother
2008-12-01 21:22
Reason for closing:  Fixed
Additional comments about closing:   Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407

caused by the formerly used default font Palatino. Switched to LaTeX defaults.

added  FS#5721  as related although its not really, but if its going to be fixed anyway it should fix both tasks.

Admin
fg commented on 2008-11-14 09:51

Actually, from looking at  FS#5721  I suspect it’s exactly the same bug

nls commented on 2008-11-24 22:16

In the pdfs it seems that the words in \setting{} macros are searchable if you exclude the first char in the word, so looking for “Playlist” a search for “laylist” would match. Since we use Title Case for settings the first char of every word is in a different font(size) than the others so this may be a limitation in the pdf format or pdflatex.
If we can’t work around this somehow I’d suggest we drop the Title Case, or if we want to keep that, the small caps style for the \setting{} macro and use some other style as searching is imho more important than aesthetics.

I looked in the soul package for fixing this a couple of days back. The results look quite promising, but currently this breaks on a few places, and I haven’t figured out why this happens. Creating small example tex files do work for the cases that break for the manual. Using soul also fixes the html issue and gives the possibility of using a background “marker” color if we find it to be appropriate, thus I’m strongly in favour of figuring why this breaks and fixing that :)

Interesting finding on this: you *can* search for the small caps strings, *if* you put a space after each capital letter – “m anage s ettings” finds the “Manage Settings” string. This works regardless if soul is used for small caps or not. When converting the pdf to txt using pdftotext there is clearly a space shown after captial letters. So it seems LaTeX puts a box between those letters.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing