-
-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different behavior for .mps and .eps #928
Comments
Perhaps also mention https://tex.stackexchange.com/questions/659801/different-behavior-for-mps-and-eps, where Ulrike already gave the explanation for the difference. Personally I can see the usefulness in both (either no effect from color or getting the effect from coloring) |
Yes, Ulrike describes the cause correctly. However, the problem remains that different engines deliver different results. |
Well at first handling of graphics is something that is engine specific. If you want the best result for more than one engine you often have to provide more than one version of the same graphic. Apart from this I don't see what latex or graphics-def can do here. We can not add a Imho it could only work if you find a ghostscript option (or convince them to add one) for the pdfwriter device so that it doesn't add the black. Then epstopdf could perhaps be changed. |
|
This issue has been automatically marked as stale because it has not had recent activity. |
@FrankMittelbach suggests using a key to define the behaviour: I might look at |
A key here would be able to enforce the standard colour as black across all engines: I guess what I need is a suggestion on a key name. I suppose |
Thinking a bit more, I guess we should be talking about |
Perhaps Btw: you have the same problem with xform/xobjects: pdflatex and lualatex allow color injection but not the other backend. |
I guess it should produce "normalcolor" by default but is there a usecase that it should be anyhting other than that, ie a different color? If so the key could by default use normalcolor but could explicitly set via key=color to something else? So I would not put "normal" in the key name but perhaps |
OK, so we think |
I would say
(and if people really define a color with the name false they can probably use |
sounds good, except that I wouldn't bother with |
well |
Well if the user is forcing CMYK they won't, but otherwise the standard setting for |
Keys always have a value, even if it's empty ... I guess you mean that we initialise with an empty stored value, and that we set the default to (I favour |
Well we can only fix stuff to some extent, and we likely don't want to break existing usage. (Perhaps |
Just to throw another hat in the ring: |
that doesn't seem to fit the bill if I understand the problem. It is not a fallback color, it is a color that is explicitly set at the beginning of the graphic, for some workflow paths it is set unconditionally (without any key) and for others it is not set at all and with this key we can force pdftex and luatex to also explicitly set a color at this point |
Well, it's a fallback in the sense that it is the colour used if the graphic file doesn't explicitly set a colour. |
true enough as an interpretation, but when I read fallback I would think more about something is failing and then I get a fallbackcolor but not expect that "fallback color" to apply if I explicitly set "red" on the outside, whereas with init-color I can immediately see why my "red" does no longer apply. |
This issue has been automatically marked as stale because it has not had recent activity. |
This issue has been automatically marked as stale because it has not had recent activity. |
Brief outline of the bug
The following example document loads two identical graphics files as .mps and .eps via \includegraphics. Both are valid eps files. I get different results depending on the TeX compiler:
pdflatex & lualatex: first square is red, second square is black
xelatex: Both squares are black
latex+dvips+ps2pdf: Both squares are black
From the user's point of view, it seems advantageous to me if graphics that do not themselves cause color settings can be colored from the outside. In any case, different behavior is unfavorable.
Minimal example showing the bug
grf-test2.log
The text was updated successfully, but these errors were encountered: