https://issues.apache.org/ooo/show_bug.cgi?id=121855
--- Comment #11 from crxssi <[email protected]> --- (In reply to comment #9) > PSLevel=0 > > This bug is fixed on trunk (where the development towards 4.0 takes place), > you can try a build from [...] My interpretation of what you said is: Download a development version and run it just to create a working psprint.conf file which I can then remove from that configuration and copy to the users' directories on the 3.4.1 installation. If that is correct, I don't think I can use that as a workaround because I have over 150 users on the machine. I have need to set up a global psprint.conf, instead, that will affect all users at once. I might be able to somehow copy a model directory to each user, but just adding one new printer on my system would become a nightmare of complexity. * I have proven that the global/system-wide psprint.conf file is being honored and can be edited. It just has that problem where I can't set PS level 2 or "default". * The psprint.conf file is just a text file. Can you tell me what about the "trunk" version file is different from the 3.4.1 file? Knowing that, I should be able to edit the global file to obtain the same results without having to install a "trunk" version, right? NEW INFORMATION..... I also discovered that I don't have to specify any printers AT ALL in the globalbasis-link/share/psprint/psprint.conf file! There is a variable under "[__Global_Printer_Defaults__]" called "PSLevel" and that will automatically change EVERY printer for OpenOffice, even when none are listed in the psprint.conf file :) Only problem- it has the same bug, 0 = PDF, and 3 = <blank> :( But to make matters even more interesting, I tested printing to a file with this "blank" entry (with PSLevel=3) and guess what.... it is creating postscript level 3, identical [checked with diff] to a file created to "print to file" with it manually set to "postscript level 3" :) But that leads to another concern- if I try to use this as a workaround, any new documents created would have a print language set to <blank> saved in them and I am not sure how future versions of Open/Libre Office will deal with that (or older versions even). I will have to test more. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
