Watermark issue

[marrtn]

Hello,

I have some specification documents with watermarks that ae shown in solid black in SumatraPDF 3.4.6, instead of some transparent grey (in Adobe Reader). Unfortunately, I am not allowed to share these documents.
Below an example:

Whenever there is some background color (the cell with shadow), the watermark seems to be correct, but without background it is solid black making the text below very hard to read.

Is there something I can do about that?
For raising an issue ticket, I'd need some example-PDF which I can't provide right now.

There are some similar discussions/issue to be found, but I couldn't find a solution.

Regards
Martin

[GitHubRulesOK]

Such watermarks are often odded into the existing document after receipt/generation, however since that is (NOT SO) clearly underlay'd it must have been generated by the PDF producer, without sample cant say, but its very easy to remove them so there is no problem with convert to archive format etc., and if desired replace with a different underlay method that could be a whiter image so no interference with the contents when reading aloud (accessibility requires non standard translucent objects be removed) for screen read/printing etc.

Ensure your testing with current pre-release, since only that can be altered if it has not already been fixed ?

[kjk]

See if it still happens in pre-release version: https://www.sumatrapdfreader.org/prerelease

[daysneco]

Hi did you solve this issue, i also have this problem

[marrtn]

Sorry for my late reply...
The current pre-Release fixes the issue for me. Thanks a lot!

[brianrho]

Hi, I'm using Sumatra 3.5.2 (released in October last year) but I still have this issue, the watermark completely obscures any overlapping text. Did the pre-release fix ever go out?

[GitHubRulesOK]

@brianrho
you will need to test most recent e.g. currently August https://www.sumatrapdfreader.org/prerelease
portable should be good enough without re-installing

[brianrho]

Thanks, I dont mind testing with that, but is there a plan to make this fix available as part of the usual releases, so I can eventually return to that?

(I'd assumed that any fixes in the May 2023 prerelease would already be in the later October release.)

[GitHubRulesOK]

@brianrho

There is never a timeframe for a release it may be today or a few years from now. (e.g big time gap from 2016-08 to 2020-03 with lots of pre-releases)

Pre-Release is usually just as stable (and with security fixes) as the release with glitches like watermark problems

The main difference is any known instability or experimental function will be removed from formal official 3.6 release.

[brianrho]

Right, so was this specific fix deemed too unstable / experimental to be cherry-picked for the October release? Or was it simply not considered?

If the latter, it would be nice to include it in the next minor release whenever that happens.

[GitHubRulesOK]

@brianrho
the Feb 2023 problem above and several others were fixed prior to May 2023 (#2934) you clearly must have a different one if the 3.5.2 (2023-10) is still showing an issue.

Several were fixed in more recent MuPDF updates, hence the suggestion to always try latest pre-release or supply a file for testing with a view to fixing if current MuPDF render still has an issue.