gimp-print-devel

Re: [Gimp-print-devel] [SPAM] DPD string length for Georgian

[Solomon P. <pi...@sh...>]

On Mon, Jan 20, 2025 at 03:51:33PM +0100, Temuri Doghonadze wrote:
> I've done translation of gutenprint several months ago, but several
> days ago I have noticed that it's disabled. Asked Zdenek Dohnal and I
> was told that several DPD strings are bigger than 80 bytes, which is
> unsupported. 

FYI it is 'PPD' not 'DPD'  :)

(For anyone else that's reading this, the problem is that one Georgian 
"character" typically takes up more than one byte when encoded into 
UTF-8. So even though a translated string may be less than 80 
_characters_ it can take over 80 bytes to store/represent it in the PPD 
file)

> Could you please tell me how can I filter out strings which are 
> breaking this rule? I believe not all strings are under this 
> restriction.

Only strings that can end up in the PPD file are affected, but I'm not 
sure of a simple way to flag the ones that are potentially problematic.

You'll need to re-enable the Georgian language in configure.ac, re-run 
autogen.sh and do a build, generate a buch of PPD files, and pass those 
files through 'cupstestppd'

You can run 'make check-parallel' to do this automatically (after 
running ./autogen.sh first), but it will take a couple of hours to 
complete unless you have a beefy system.  The failures will show up in 
src/cups/test-ppds.log.

 - Solomon
-- 
Solomon Peachy			      pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
Dowling Park, FL                      speachy (libera.chat)

[Gimp-print-devel] DPD string length for Georgian

[Temuri D. <tem...@gm...>]

Hello,
My name is Temuri and I do translations of various software to
Georgian in my free time.
I've done translation of gutenprint several months ago, but several
days ago I have noticed that it's disabled. Asked Zdenek Dohnal and I
was told that several DPD strings are bigger than 80 bytes, which is
unsupported. Could you please tell me how can I filter out strings
which are breaking this rule? I believe not all strings are under this
restriction.

BR, Temuri

[Gimp-print-devel] Support for the epson Sc-P900

[<def...@du...>]

Hi gutenprint team,

I was wondering what is the state of development of gutenprint, (still 
active or not). I have a sc-P900 epson printer, and I would be glad to 
be able to use it with gutenprint. Do you think it is worth trying ? I 
have a spectrophotometer probe, some knowledge about programming. Let 
met know !

Best,
Yann

Re: [Gimp-print-devel] Uninstall the software

[Matt B. <wal...@ma...>]

> On Dec 30, 2024, at 10:26 AM, RICHARD BELL via Gimp-print-devel <gim...@li...> wrote:
> 
> Hi
> 
> I have installed the Gluten Print software on my new Mac book pro M4 with the OS 15.2.
> 
> Sadly it doesn’t allow my Printer to work - it was a long shot……..
> 
> How do I remove the software from my Mac Book?
> 

There is an uninstaller on the disk image that has the installer.
Matt

[Gimp-print-devel] Uninstall the software

[RICHARD B. <be...@ao...>]

Hi

I have installed the Gluten Print software on my new Mac book pro M4 with the OS 15.2.

Sadly it doesn’t allow my Printer to work - it was a long shot……..

How do I remove the software from my Mac Book?

Can you advise please?

Richard

Re: [Gimp-print-devel] 5.3.5 status?

[Solomon P. <pi...@sh...>]

On Fri, Dec 13, 2024 at 10:07:21AM -0500, Erik Beck of Tahoma wrote:
> 1) I can keep doing the tests I can on my printer.

It's all most of us can do!
 
> 2) If you can coach me on how to do this, I can try to help.

I think I figured all of that out; unfortunately the last set of 
checksums I could find are for 5.3.3, and 5.3.4 included some changes 
that affected the output on nearly every model.

I generated a new set, and that'll do for now.

> It seems logical to finalize this release of gutenprint before
> migrating to another hosting site, updating the website, and tackling
> the migration to GIMP 3 and working up the printer application. If
> nothing else, a reasonable way to break the whole shebang into
> reasonable chunks.

At minimum, the existing website needs to be brought up to date.  I've 
sorted the printer list, and made a few essential changes so far.

 - Solomon
-- 
Solomon Peachy			      pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
Dowling Park, FL                      speachy (libera.chat)

Re: [Gimp-print-devel] 5.3.5 status?

[Till K. <til...@gm...>]

On 12/13/24 02:53, Solomon Peachy via Gimp-print-devel wrote:
> 6) Getting off of sourceforge
> 
>   I'm personally partial to sourcehut, if only because they consider
>   mailing lists (and email in general) to be first-class tools.
> 
>   The only things on sourceforge that matter are the mailing list
>   archives and the old release archive.  Both are extractable, though
>   sourceforge now "helpfully" strips out email address.  I don't know if
>   that will prevent re-importing elsewhere.
> 

We could also put it on OpenPrinting's GitHub ...

    Till

Re: [Gimp-print-devel] 5.3.5 status?

[Erik B. of T. <ba...@ta...>]

Hi Solomon, thanks.

1) I can keep doing the tests I can on my printer.

2) If you can coach me on how to do this, I can try to help.


My thoughts on items 3-6:

It seems logical to finalize this release of gutenprint before
migrating to another hosting site, updating the website, and tackling
the migration to GIMP 3 and working up the printer application. If
nothing else, a reasonable way to break the whole shebang into
reasonable chunks.

I can certainly help with website updates once a new home (getting off
sourceforge) is chosen; maybe even do some work before then.

Regards,

Erik


On Thu, 12 Dec 2024 20:53:22 -0500
Solomon Peachy via Gimp-print-devel
<gim...@li...> wrote:

> On Wed, Dec 11, 2024 at 07:07:24PM -0500, Erik Beck of Tahoma wrote:
> > Solomon, how can I and others help?  
> 
> It's those big ticket items.  
> 
> 1) Testing on actual printers
> 
>  Other than my dyesub fleet I have no idea if anything else still
> works on real hardware.  Not that there have been a lot (if any?)
> changes elsewhere...
> 
> 2) Regression testing vs older versions
> 
>  There is the src/testpattern/Checksums directory in the tree; I need
> to figure out how to generate a new batch and compare it to the
> previous release's run.  Then go through the ones that differ and
> make sure they were intentionally changed.
> 
> 3) Update web site and other public documentation
> 
>  * Extract current printer lists for the www site and update
> accordingly
>  * Make it clear everywhere that MacOS is no longer supported
>    (at least outside of MacPorts or Fink or whatever)
>  * (Really, the entire web site should probably be replaced..)
> 
> Longer-term things:
> 
> 4) Port gimp plugin to GEGL and GIMP3
> 
>  Earlier tonight I started getting the basic plumbing in place to
> make a gimp-3 plugin possible. While I don't expect the actual
> gimp-interacing bits will be terribly complicated (beyond handing
> >8bpp image data formats) the real uplift is porting the gutenprintui
> >library from gtk2 
>  to gtk3.
> 
> 5) Picking up the Standalone gutenprint printer application
> 
>  The GSoC project completed the initial phase, but a lot of work
> remains -- general integration and cleanup, the inevitable testing,
> and (particularly important for me) getting the dyesub backend in,
> which is likely to take some serious restructuring of how it is put
> together.
> 
>  This matters because it's realistically going to be the only usable 
>  path forward for gutenprint in the medium term.
>  
> 6) Getting off of sourceforge
> 
>  I'm personally partial to sourcehut, if only because they consider 
>  mailing lists (and email in general) to be first-class tools.
> 
>  The only things on sourceforge that matter are the mailing list 
>  archives and the old release archive.  Both are extractable, though 
>  sourceforge now "helpfully" strips out email address.  I don't know
> if that will prevent re-importing elsewhere.
> 
> That's off the top of my head...
> 
>  - Solomon

Re: [Gimp-print-devel] 5.3.5 status?

[Solomon P. <pi...@sh...>]

On Wed, Dec 11, 2024 at 07:07:24PM -0500, Erik Beck of Tahoma wrote:
> Solomon, how can I and others help?

It's those big ticket items.  

1) Testing on actual printers

 Other than my dyesub fleet I have no idea if anything else still works 
 on real hardware.  Not that there have been a lot (if any?) changes 
 elsewhere...

2) Regression testing vs older versions

 There is the src/testpattern/Checksums directory in the tree; I need to 
 figure out how to generate a new batch and compare it to the previous 
 release's run.  Then go through the ones that differ and make sure they
 were intentionally changed.

3) Update web site and other public documentation

 * Extract current printer lists for the www site and update accordingly
 * Make it clear everywhere that MacOS is no longer supported
   (at least outside of MacPorts or Fink or whatever)
 * (Really, the entire web site should probably be replaced..)

Longer-term things:

4) Port gimp plugin to GEGL and GIMP3

 Earlier tonight I started getting the basic plumbing in place to make a 
 gimp-3 plugin possible. While I don't expect the actual gimp-interacing 
 bits will be terribly complicated (beyond handing >8bpp image data 
 formats) the real uplift is porting the gutenprintui library from gtk2 
 to gtk3.

5) Picking up the Standalone gutenprint printer application

 The GSoC project completed the initial phase, but a lot of work remains 
 -- general integration and cleanup, the inevitable testing, and 
 (particularly important for me) getting the dyesub backend in, which is 
 likely to take some serious restructuring of how it is put together.

 This matters because it's realistically going to be the only usable 
 path forward for gutenprint in the medium term.
 
6) Getting off of sourceforge

 I'm personally partial to sourcehut, if only because they consider 
 mailing lists (and email in general) to be first-class tools.

 The only things on sourceforge that matter are the mailing list 
 archives and the old release archive.  Both are extractable, though 
 sourceforge now "helpfully" strips out email address.  I don't know if 
 that will prevent re-importing elsewhere.

That's off the top of my head...

 - Solomon
-- 
Solomon Peachy			      pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
Dowling Park, FL                      speachy (libera.chat)

Re: [Gimp-print-devel] 5.3.5 status?

[Erik B. of T. <ba...@ta...>]

Solomon, how can I and others help?

On Wed, 11 Dec 2024 18:06:48 -0500
Solomon Peachy via Gimp-print-devel
<gim...@li...> wrote:

> On Fri, Dec 06, 2024 at 10:40:49AM -0500, Greg Troxel wrote:
> > I believe that where we are is that in July 5.3.5-pre1 was
> > released, and we had some discussion about a few minor issues.
> > And that there has been no pre2, alpha, beta, rc or release.  
> 
> Other than some minor fixes, nothing's happened.
> 
> I could just create a new tarball but there's still a lot of other
> stuff that historically has happened for releasees -- updated www
> site and other documentation, running and updating regression test
> suites, and more.  All of that takes time, especially when you have
> to figure it out first!
> 
> Other major stuff looming -- trying to pick up where the GSoC student 
> left off with a native gutenprint Printer Application, and porting
> our GIMP plugin to the 3.0 release.
> 
>  - Solomon

Re: [Gimp-print-devel] 5.3.5 status?

[Solomon P. <pi...@sh...>]

On Fri, Dec 06, 2024 at 10:40:49AM -0500, Greg Troxel wrote:
> I believe that where we are is that in July 5.3.5-pre1 was released, and
> we had some discussion about a few minor issues.   And that there has
> been no pre2, alpha, beta, rc or release.

Other than some minor fixes, nothing's happened.

I could just create a new tarball but there's still a lot of other stuff 
that historically has happened for releasees -- updated www site and 
other documentation, running and updating regression test suites, and 
more.  All of that takes time, especially when you have to figure it out 
first!

Other major stuff looming -- trying to pick up where the GSoC student 
left off with a native gutenprint Printer Application, and porting our 
GIMP plugin to the 3.0 release.

 - Solomon
-- 
Solomon Peachy			      pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
Dowling Park, FL                      speachy (libera.chat)

Re: [Gimp-print-devel] Uninstall Gutenprint-5-3-3 from my Mac 0s 15.1.1

[Matt B. <wal...@ma...>]

> On Dec 10, 2024, at 1:41 AM, N L via Gimp-print-devel <gim...@li...> wrote:
> 
> How do you uninstall all Gutenprint files form my Mac?

The uninstaller is on the same disk image as the installer.  If you do not have the disk image with the installer, you can download it from https://sourceforge.net/projects/gimp-print/files/gutenprint-5.3/5.3.3/gutenprint-5.3.3_rev.dmg/download

Matt

[Gimp-print-devel] Uninstall Gutenprint-5-3-3 from my Mac 0s 15.1.1

[N L <noe...@ya...>]

How do you uninstall all Gutenprint files form my Mac?

Re: [Gimp-print-devel] Printer DRIVER EPSON SC P700

[Matt B. <wal...@ma...>]

> On Dec 6, 2024, at 4:00 AM, albert-malcolm93--- via Gimp-print-devel <gim...@li...> wrote:
> 
> Hello
> 
> Do you have a driver for this Printer:EPSON SC P700
> 
> Couldn‘t find anything.
> 
> For macOS High Sierra 10.13.6
> 
> Best Regards
> Gesendet mit der WEB.DE Mail App

It has been reported that the p600 driver partially works with the p700.  There is a bug in Gutenprint on macos, however, that will prevent you from accessing any of the printer settings in the print window.  If you try the p600 driver and feel there may be enough usefulness, post back and I can provide an amended PPD for the p600 that will get around the bug.

It does appear that Epson does provide macos drivers for macos 10.13.x.

Matt

[Gimp-print-devel] 5.3.5 status?

[Greg T. <gd...@le...>]

I am just making sure I am not missing something, and don't mean to
demand that any person do anything.

I believe that where we are is that in July 5.3.5-pre1 was released, and
we had some discussion about a few minor issues.   And that there has
been no pre2, alpha, beta, rc or release.

(I'm happy to update pkgsrc locally to a new pre/whatever and test, or
to update to a release, when/if that occurs.)

Re: [Gimp-print-devel] Printer DRIVER EPSON SC P700

[Bacon At T. <ba...@ta...>]

The P600 or P800 might be close enough to work. 

I don't use MacOS though, so can't help with that part.
Sent from my iPhone

> On Dec 6, 2024, at 08:01, albert-malcolm93--- via Gimp-print-devel <gim...@li...> wrote:
> 
> Hello
> 
> Do you have a driver for this Printer:EPSON SC P700
> 
> Couldn‘t find anything.
> 
> For macOS High Sierra 10.13.6
> 
> Best Regards
> Gesendet mit der WEB.DE Mail App
> 
> 
> _______________________________________________
> Gimp-print-devel mailing list
> Gim...@li...
> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

[Gimp-print-devel] Printer DRIVER EPSON SC P700

[<alb...@we...>]

Hello

Do you have a driver for this Printer:EPSON SC P700

Couldn‘t find anything.

For macOS High Sierra 10.13.6

Best Regards
Gesendet mit der WEB.DE Mail App

Re: [Gimp-print-devel] Mitsibishi CP90SL

[Solomon P. <pi...@sh...>]

On Thu, Nov 21, 2024 at 04:37:38PM -0500, Solomon Peachy via Gimp-print-devel wrote:
> Historically Mitsubishi has changed the USB IDs and tweaked the "start 
> print" command slightly vs their standard commercial model.  I don't 
> know what they might have done for the CPD90DW-SL.  

This email chain went private, but to follow up here, for the -SL 
variant, Mitsubishi used a unique USB PID and also changed the IEEE1284 
identification string.

Gutenprint has been updated to recognize these, but a week later have 
not heard back if this is sufficient to allow this model to print.

 - Solomon
-- 
Solomon Peachy			      pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
Dowling Park, FL                      speachy (libera.chat)

Re: [Gimp-print-devel] Some fonts produce complete garbage on the printer (OKi MC362DN)

[Solomon P. <pi...@sh...>]

On Thu, Nov 28, 2024 at 12:34:24AM +0100, Shanti-Dominique wrote:
> Is there an option to sanitize fonts before they are sent to the 
> printer, or to force printing as image?

Gutenprint works purely with bitmap data. If the source material is not 
an image then something else has to convert it before it's handed to 
gutenprint.

That "something else" can be the application itself, the framework it's 
using to print stuff, or a filter in the CUPS processing chain (eg 
"pdftoraster").  Since you're seeing wonky fonts, it could be any of 
those layers -- the application (or framework) could be inserting bad 
font data, or the rasterizer could be mis-interpreting said font data.

But either way, by the time Gutenprint is handed the print data, it's 
already been converted to a bitmap.

 - Solomon
-- 
Solomon Peachy			      pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
Dowling Park, FL                      speachy (libera.chat)

[Gimp-print-devel] Some fonts produce complete garbage on the printer (OKi MC362DN)

[Shanti-Dominique <mi...@mi...>]

Hello,

I have an OKi printer that worked fine until a few months back. On some 
fonts, it started producing garbage, I suspect that is because the font 
format evolved and the printer does not recognize it. When upgrading myu 
computer to a newer version of Linux, the fonts included have newer 
freetype features that are not supported.

For example, Libre Baskerville is complete garbage. Some other fonts are 
ok, some have minor issues on some letters.

I know that Chromium has an option to print a PDF as an image, and it 
solves the problem, but I cannot print everything from Chromium.

Is there an option to sanitize fonts before they are sent to the 
printer, or to force printing as image?

Thank you.

Mildred

Re: [Gimp-print-devel] Mitsibishi CP90SL

[Solomon P. <pi...@sh...>]

On Thu, Nov 21, 2024 at 05:21:36PM +0100, Denis Jesse wrote:
> I recently purchased a Mitsubishi CP90DW-SL photo printer.
> It is some special model (SL) and unfortunately it does not work with the
> drivers of from the CP90DW model.

Mitsubishi typically produced special variants of each model, typically 
tied to some vendor's specific kiosk solution (a German company called 
"Silverlab solutions" in this case) *and* additionally being locked to 
vendor-specific media.

> Do you know what the problem could be and how to get the printer to work on
> Linux? I want to connect it to my photo booth via CUPs and AirPrint.

Depends on what you mean by "does not work" -- ie what is the specific 
error?

Historically Mitsubishi has changed the USB IDs and tweaked the "start 
print" command slightly vs their standard commercial model.  I don't 
know what they might have done for the CPD90DW-SL.  

 - Solomon
-- 
Solomon Peachy			      pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
Dowling Park, FL                      speachy (libera.chat)

[Gimp-print-devel] Mitsibishi CP90SL

[Denis J. <jes...@gm...>]

Hello guys,

Hi guys,
I recently purchased a Mitsubishi CP90DW-SL photo printer.
It is some special model (SL) and unfortunately it does not work with the
drivers of from the CP90DW model.

Do you know what the problem could be and how to get the printer to work on
Linux? I want to connect it to my photo booth via CUPs and AirPrint.

Regards,
Denis

Re: [Gimp-print-devel] Gutenprint driver for Sony UP-DR80MD

[Solomon P. <pi...@sh...>]

On Fri, Nov 15, 2024 at 10:11:58AM +0800, 陈和平 wrote:
> We are using Gutenprint software to drive a Sony UP-DR80MD medical 
> printer. We have two printers, one is manufactured in year 2021, the 
> other is in 2014. We found that the Gutenprint worked well for the 
> 2021-produced printer, but did not work for the 2014-produced printer. 
> Both printers are UP-DR80MD. Did you encounter this problem before, 
> and do you have any clues how to sove it?

When you say "did not work" what precisely is the issue or error?

Gutenprint's UP-DR80MD support was written in late 2019 via 
reverse-engineering, ie without any support from Sony.

It is certianly possible that Sony changed something during the 
production run, but one of the points of the "MD" model designation is 
that it's a certified device that doesn't change during its extended 
product lifecycle.

A few other things to check with both the old and new models:

 * What is the 'lsusb' output ?
 * What is the output of 'sudo /usr/lib/cups/backend/gutenprint53+usb' ?
 * What is the output of 'sudo /usr/lib/cups/backend/usb' ?

 - Solomon
-- 
Solomon Peachy			      pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
Dowling Park, FL                      speachy (libera.chat)

[Gimp-print-devel] Gutenprint driver for Sony UP-DR80MD

[陈和平 <ch...@sz...>]

Dear，
We are using Gutenprint software to drive a Sony UP-DR80MD medical printer. We have two printers, one is manufactured in year 2021, the other is in 2014. We found that the Gutenprint worked well for the 2021-produced printer, but did not work for the 2014-produced printer. Both printers are UP-DR80MD. Did you encounter this problem before, and do you have any clues how to sove it?


Sincerely
AcuVu Medical Inc.







陈和平
ch...@sz...

签名由 网易灵犀办公 定制

Re: [Gimp-print-devel] macos patch

[Solomon P. <pi...@sh...>]

On Mon, Oct 28, 2024 at 02:51:02PM -0500, Matt wrote:
> I looked at the files in ./macosx and am attaching a patch to take 
> care of the most important issues. These issues are where the version 
> numbers are hard coded into scripts (5.2 vs 5.3).  The patch also adds 
> provisions for the commandtodyesub filter. The two files that have 
> changes are:

I wanted to apply the patches as-is, but they mostly fail to apply:

$ patch -p5 --dry-run < /tmp/guten_macosx.patch 
checking file macosx/makegutenpkg.sh
Hunk #1 FAILED at 44.
Hunk #2 FAILED at 73.
Hunk #3 FAILED at 107.
Hunk #4 FAILED at 115.
Hunk #5 FAILED at 126.
Hunk #6 FAILED at 177.
6 out of 8 hunks FAILED
checking file macosx/scripts/uninstall-gutenprint.command
Hunk #1 FAILED at 117.
Hunk #2 FAILED at 130.
2 out of 3 hunks FAILED

So... I don't know what you used as the "before", but the files you're 
modifying haven't changed since 2019 and 2017, respectively.  Maybe you 
had non-local commits?

Instead of trying to diff two separate git trees, you could make sure 
you have your local WIP repo up-to-date, and generate a patch with 
something like:

  git diff origin/master

Or, if you have these things committed locally, you could do something like

  git format-patch origin/master

And that will generate one patch file for each commit missing upstream.

(Make sure you do a 'git pull --rebase' first though)

 - Solomon
-- 
Solomon Peachy			      pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
Dowling Park, FL                      speachy (libera.chat)