ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

ვრცლად

pdf labels not printing barcodes

  • 4 პასუხი
  • 2 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 17 ნახვა
  • ბოლოს გამოეხმაურა mourningstar625

When I create FedEx labels through eBay and print them with the default PDF viewer in Firefox none of the bar codes print out. I believe it is an error with the PDF viewer in Firefox, when I save it and print out in any other viewer it works just fine. I would like to just use the built in pdf viewer in firefox because I would rather not install adobe software with all of the problems that come with that. Could Mozilla look into this PDF viewer bug ?

When I create FedEx labels through eBay and print them with the default PDF viewer in Firefox none of the bar codes print out. I believe it is an error with the PDF viewer in Firefox, when I save it and print out in any other viewer it works just fine. I would like to just use the built in pdf viewer in firefox because I would rather not install adobe software with all of the problems that come with that. Could Mozilla look into this PDF viewer bug ?

გადაწყვეტა შერჩეულია

Sounds like they identified the problem and are fixing it in the next release of Firefox, yay devs!

პასუხის ნახვა სრულად 👍 0

ყველა პასუხი (4)

You can file a Bug report about that "bar code" issue with PDF.js.. https://bugzilla.mozilla.org/ https://developer.mozilla.org/en/Bug_writing_guidelines

I did do a search of Bugzilla for "bar code" Bugs already filed and didn't find one specific to your condition; only one where an airline boarding pass bar code printout was 'blurred' and couldn't be read by a scanner - https://bugzilla.mozilla.org/show_bug.cgi?id=1012700 . The fault was found to be an unsupported font among other errors and that Bug is still open.

შერჩეული გადაწყვეტა

Sounds like they identified the problem and are fixing it in the next release of Firefox, yay devs!