GNOME Bugzilla – Bug 502664
Forms: Instead of x sign, $ sign appears in checkboxes
Last modified: 2012-11-05 12:48:26 UTC
Please describe the problem: In some forms, when ticking a checkbox, a $ sign appears instead of a x or a tick. Steps to reproduce: 1. Open http://www.sparda-west.de/lnkcnt.php?et=6pV&url=/pdf/west_fsa2007.pdf&lnkname=PDF+-+Freistellungsauftrag+f%26uuml%3Br+Kapitalertr%26auml%3Bge 2. Tick the box "ledig" 3. Actual results: A dollar sign appears in the checkbox Expected results: A tick or a x should appear in the checkbox Does this happen every time? Yes! Other information:
Looks like a problem with the fonts. I can't reproduce it.
Hm, where can I look up which font I am using? Also could be a problem with the Fedora package, maybe I should report it there, first.
(In reply to comment #2) > Hm, where can I look up which font I am using? Try running: $ fc-match ZapfDingbats More info, here: http://freedesktop.org/wiki/Software/poppler
$ fc-match ZapfDingbats DejaVuLGCSans.ttf: "DejaVu LGC Sans" "Book"
Other problem, but also related to forms, here: http://wuestenrot.de/control/download.php?file=allg_113_2007_freistellungsauftrag_interaktivformular.pdf After entering things to the fields there (for example Vertragsnummer / Kontonummer) and typing in text to the next field, the actual input disappears. And one more thing ;) http://www.redhat.com/f/pdf/CIO_vendor_value_survey_2007.pdf The text is white, the background is, too. You have to mark the text to actually be able to read something.
I retried the first issue with Ubuntu, and it works there. Also, fc-match ZapfDingbats says DejaVu-Sans.ttf: "DejaVu Sans" "Book" but the two other issues that I just posted also appear on Ubuntu. What can I tell the distributor (Red Hat)? What does he have to change in order to fix the first problem?
(In reply to comment #5) > Other problem, but also related to forms, here: > > http://wuestenrot.de/control/download.php?file=allg_113_2007_freistellungsauftrag_interaktivformular.pdf > > After entering things to the fields there (for example Vertragsnummer / > Kontonummer) and typing in text to the next field, the actual input disappears. > yes, I can confirm it. > > And one more thing ;) > > http://www.redhat.com/f/pdf/CIO_vendor_value_survey_2007.pdf > > The text is white, the background is, too. You have to mark the text to > actually be able to read something. > That's a known bug in cairo which is already fixed.
OK, great. But what's about the first issue? What is causing it? I am using Fedora 8.
(In reply to comment #8) > OK, great. But what's about the first issue? What is causing it? I am using > Fedora 8. > I don't know, sorry. It works for me in ubuntu.
right, i am going to report that to the fedora project then. thanks for your help.
Zapf Dingbats is an interesting problem. Some time back — after reading about this issue wrt evince — I modified my setup such that — I thought — it would be guaranteed to work. I guess not: :; fc-match ZapfDingbats LucidaSansRegular.ttf: "Lucida Sans" "Regular" :; fc-match Zapf\ Dingbats Dingbats.ttf: "Dingbats" "Regular" (The former is my first-choice Sans match.) Tests with pango-view verify that the latter works and the former does not. evince or poppler, as applicable, should special-case Zapf Dingbats rather than relying on the underlying libs....
Well I have still the issue :(
Any idea on how to fix this? It's pretty annoying; I can't send forms with $ instead of x to my bank..
Martin, see the Fedora bug https://bugzilla.redhat.com/show_bug.cgi?id=468565 for a workaround.
I filed a bug and plan to fix this in fontconfig http://bugs.freedesktop.org/show_bug.cgi?id=19128
I tried to download the first PDF file but the URL is not pointing onto it anymore. Anyway, the PDF files in the comment 5 are still there. But, I didn't see any problem with the second one and the first one is almost correct now. The only problematic form field is the year (jare) which behave as described by the issue submitter. Confirmed in Evince 2.29.1 (git master), Poppler 0.12.0 (git master).
Created attachment 157382 [details] tax form ... example of the issue I can add just another test case ... http://cds.mfcr.cz/cps/rde/xbcr/cds/Interaktiv5405_16_3AK.pdf is a current Czech tax form for individuals. Font has problems with Zapf Dingbats, but apparently with something else as well (the question mark sign on the scroll down button next to the box nr. 04).
Created attachment 157383 [details] screenshot of the of the first page in Adobe Acrobat 9
still happening for me as well for http://www.bhw.de/content/Service/FormularCenter/D_135_a_%28mL%29.pdf on Ubuntu lucid and with evince 2.30.3-0ubuntu1.1
*** Bug 643553 has been marked as a duplicate of this bug. ***
yeah, another annual tax filing, another PDF from the Czech Ministry of Finance ... http://cds.mfcr.cz/cps/rde/xbcr/cds/Interaktiv_5405_17_4AK.pdf, same bug. No drama, just to have my annual filing (of comment to this bug, that is) done.
In PDFs that provide appearance streams for the X sign, as the one in comment 21, This has been fixed by Carlos in latest poppler git. On other docs, I think we still need to wait for the fix in fontconfig.
(In reply to comment #21) > yeah, another annual tax filing, another PDF from the Czech Ministry of Finance > ... http://cds.mfcr.cz/cps/rde/xbcr/cds/Interaktiv_5405_17_4AK.pdf, same bug. > No drama, just to have my annual filing (of comment to this bug, that is) done. You did not comment this bug in 2012. Also, it seems to me the document in the link is rendered correctly now (evince 3.6.0, cairo master (>0.12.6), poppler master(>0.21)).
(In reply to comment #22) > In PDFs that provide appearance streams for the X sign, as the one in comment > 21, > This has been fixed by Carlos in latest poppler git. On other docs, I think we > still need to wait for the fix in fontconfig. I am closing this bug as fixed given it the bug in fontconfig was fixed on 2012-05-13 20:11:01 UTC. If you still can reproduce the bug, please feel free to re-open it and add more details.
(In reply to comment #23) > You did not comment this bug in 2012. Also, it seems to me the document in > the link is rendered correctly now (evince 3.6.0, cairo master (>0.12.6), > poppler master(>0.21)). Right, it seems to work for me now as well (evince-3.6.1, cairo-1.12.4, poppler-0.20.2).