On Mon, Nov 12, 2012 at 6:16 PM, Michael Meeks <michael.meeks@suse.com>wrote:
Hi guys,
On Fri, 2012-11-09 at 10:54 +0000, Michael Meeks wrote:
On Thu, 2012-11-08 at 12:23 +0100, Michael Stahl wrote:
this patch appears to change the default format for printing via CUPS
from PDF to PostScript.  this was changed from PostScript to PDF in
OOo 3.3.
      Urk ! - right, reverting that is not a good fix.
        So - in fact; having consulted internally and read a few bugzilla
bugs
- I think it is perhaps quite a good fix; we have things like:
        https://bugzilla.novell.com/show_bug.cgi?id=732442#c5
        Which look scary; Johannes maintains CUPS at SUSE, and his view is
that
we should be careful here; he suggested having an IMHO un-usable option
in the print dialog to select which meta-file-format (hmm).
        So - (I guess) perhaps (reluctantly) turning this back to generate
.PS
output is the right answer cf.
        https://bugs.freedesktop.org/show_bug.cgi?id=44664
        Having said that - it's clearly nice to help out with improving
CUPS -
so I recommend we default to PS, unless we're in "Experimental mode"
where we use PDF instead (?).
        How does that sound ? Any chance of tweaking the patch to do that
Lior
- and thanks for the catch ! :-)
I can try, but I need hints/pointers for this experimental mode (let me
remind you I'm not a programmer).
CCing Jaroslav Krejci who provided the patch in the first place.
Kaplan
Context
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.