![]() We invite you to install and test bioPDF for yourself today at no obligation. As large enterprise clients began to show interest, we developed bioPDF to match the requirements of businesses on any scale. Many more have simply used the application and reported their enjoyment. Over time, countless dedicated Bullzip fans have tested almost any conceivable combination of application and platform. When all users can and do print to PDF, fewer potentially harmful or unreadable file formats are distributed and paper use is greatly reduced throughout the organization.Įnterprise-level robustness at SMB pricesīioPDF takes highly praised community software Bullzip PDF Printer to the professional level. This leads to swift adoption and low support requirements. I'm really disappointed in you guys.For admins, bioPDF is simple and flexible to adapt and deploy, with support for unattended setup scripts, Citrix Metaframe, and more.Įnd-users find the PDF writer fast and intuitive to use, emboldened by the fact that the interface is localized into multiple languages. I, like the others here, am going to delete Firefox right now, and download another browser (as I still hate IE). The bug isn't with it, you're simply choosing not to support it any longer. Why don't you guys just take your thumbs out and actually be pro-active to create a patch integrated with Firefox to make this work? My company has no desire to waste hundreds of dollars on a newer version of Acrobat, and quite frankly shouldn't be strong-armed into it because you're too lazy to develop your browser with a fix for the issue. Distiller, and all other writers, do not compare to the simplicity of PDF Writer. Every other app I use supports PDF Writer, and I NEED the writer for my work, as I compile hundreds of different documents into PDF. I switched to Firefox because I felt like you guys really cared about your users. I understand how you're attempting to spin this, and it's honestly wrong. I was so confused for the last handful of months why my PDF Writer wasn't working properly, and just found out today that it is due to Firefox. This issue is most definitely NOT resolved. THAT is going to be the downfall of such a wonderful OS like Linux, and it will be because of programmers attitudes like this one here. But their attitude, like yours, is not to give your best and support it to be clean and efficient. It's like many of the Linux-based software utilities that have come to the forefront, and Linux itself. to consider going to something that is so poorly supported. I will not encourage folks I deal with, work with, and support. I would assume that future problems with Firefox will be met with the same lack of fervor to resolve issues.Ĭonsider me an abandoned FIREFOX user, supporter, and most of all. But I can see that your resolve is to argue this rather than fix it. Your programmers didn't address this situation and are now reluctant to go back and fix it, as they should do. Guess what did? THAT is the answer to "who" is at fault. If someone comes up with a patch for the latin text issue, it would be considered, but as of right now noone is working on such a patch. So, as of right now, this is a bug in PDF Writer that happens to be exposed by Firefox. If we "fixed" it, we would only have a chance of fixing it for printing latin text, and doing so would cause other problems (layout differences between print and screen). IE and Firefox 2 don't do the more complex text layout that Firefox 3 does for latin text, so it can print without using glyph indices. Well, except that PDF Writer doesn't work in "everything" - in IE (and, presumably, Firefox 2), it only works for latin text, and doesn't work in many other apps (e.g. ![]() Even your application worked fine before you released the > you blame the application? And to recommend an alternative applications is > That's a cop-out! PDF Writer works in "everything" EXCEPT Firefox. find the two consecutive nightlies where one yields normal body text and the next yields gibberish body text? (It'd be between and the FF3 release, according to comment 30) > as of the offical release, all text appears as 'corrupt' gibberish throughoutĬould someone could narrow down the date range for when this changed? i.e. ("Make gfxTextRun be a single shared class for all platforms") That sounds like a regression from bug 370588. > 20-03-05-04-trunk/ where text in the head/foot is suddenly 'corrupt' > the real font 'corruption' begins to appear in the 03-05-04 build from That's very likely due to the patch for bug 177805, which was very wide-reaching and touched a bunch of printing-related files. > where all text in body frame is output as highlighted in black
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |