Re: [Gimp-print-devel] Mac OS X issue

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

> On May 8, 2021, at 4:52 PM, Solomon Peachy <pi...@sh...> wrote:
> 
> On Sat, May 08, 2021 at 05:05:41PM -0400, Robert Krawitz wrote:
>> I'm sort of leaning toward simply changing the base unit for the PPD 
>> files to 0.5 point.  That will still make for a lot of option choices 
>> and we'll need to test to make sure that that doesn't cause additional 
>> problems.  What do people think?
> 
> I think this is the least worst option..
> 
> (And I say that as someone whose use cases aren't affected one way or 
> another)
> 
> - Solomon

I think I agree with Solomon here.  I do have some other thoughts/concerns,
1.  Is changing the base unit going to cause problems with cupstestppd ?

2.  We have had the messiness of 'mm' 'points' and 'inches' for quite some time.  We saw how ugly it is when this macos bug emerged.  The  bug first appeared with v3.x.  Robert, I know you *really* don't like making big changes even if it the right thing to do.

2a  What problems might this cause with cups-genppdupdate?  There are going to be users that already have modified their PPD defaults through the CUPS web interface or command line.  Also, at least in macos, users can create Custom Presets either for one printer or for all printers in the standard Print Window.  I think this is going to get very messy and problematic very, very quickly.  I may not be thinking correctly on these point or overanalyzing.

While the current bug in macos only affects those printers that print on CDs/DVDs, it is still a nasty bug. My immediate concern is to get something out for macos users that won't crash applications when they try to look at and set Printer Features.  I think Steve is having problems getting the ARM binaries to work and to make a fat binary. He will have to let us know where he is.  At this point, I would settle for a x86_64 only release.  I is easier to fend off complaints of not not having native code for the M1 chipset than deal with drivers that can crash applications. As I recall the last patch Robert has us try solved the problem.

Matt