Inverted text prints as solid black squares when "Minimum Contrast" set to "High"
By n...@noah.org on April 08, 2014 21:03 (imported from Google Code)
Color preset set to "Light Background". If the "Minimum Contrast" is set "High", all the way to the right, then most colors appear normal until inverted text is printed (light on dark background). Inverse text will appear as solid black illegible squares. Since inverse text is not printed often I had long since forgotten that I had changed the "Minimum Contrast" so it took me forever to trace this back to the cause of setting "Minimum Contrast" to "High". I think iterm2 should either handle inverse text so that it is at least somewhat legible in all contrast settings (black on black is clearly never going to be legible), or warn the user that while some contrast settings may render some text illegible in certain circumstances, or display a few samples of text demonstrating reasonable edge cases for legible text so that the user can see the consequences of different contrast settings.
The attached plist shows my configuration with "Minimum Contrast" set full right, "High".
For the attached debug log I started with "Minimum Contrast" set a bit lower than "High". Then I started the log. I switched the contrast to full right, "High". I started a program that uses inverted text (the Color preset set to "Light Background". If the "Minimum Contrast" is set "High", all the way to the right, then most colors appear normal until inverted text is printed (light on dark background). Inverse text will appear as solid black illegible squares. Since inverse text is not printed often I had long since forgotten that I had changed the "Minimum Contrast" so it took me forever to trace this back to the cause of setting "Minimum Contrast" to "High". I think iterm2 should either handle inverse text so that it is at least somewhat legible in all contrast settings (black on black is clearly never going to be legible), or warn the user that while some contrast settings may render some text illegible in certain circumstances, or display a few samples of text demonstrating reasonable edge cases for legible text so that the user can see the consequences of different contrast settings.
The attached plist shows my configuration with "Minimum Contrast" set full right, "High".
For the attached debug log I started with "Minimum Contrast" set a bit lower than "High". Then I started the log. I switched the contrast to full right, "High". I started a program that uses inverted text (the watchColor preset set to "Light Background". If the "Minimum Contrast" is set "High", all the way to the right, then most colors appear normal until inverted text is printed (light on dark background). Inverse text will appear as solid black illegible squares. Since inverse text is not printed often I had long since forgotten that I had changed the "Minimum Contrast" so it took me forever to trace this back to the cause of setting "Minimum Contrast" to "High". I think iterm2 should either handle inverse text so that it is at least somewhat legible in all contrast settings (black on black is clearly never going to be legible), or warn the user that while some contrast settings may render some text illegible in certain circumstances, or display a few samples of text demonstrating reasonable edge cases for legible text so that the user can see the consequences of different contrast settings.
The attached plist shows my configuration with "Minimum Contrast" set full right, "High".
For the attached debug log I started with "Minimum Contrast" set a bit lower than "High". Then I started the log. I switched the contrast to full right, "High". I started a program that uses inverted text (the `watch command in diff mode). I observed that I could not read the black on black text in the black squares, I set the contrast back to a legible level. I turned off the log.
Thanks!
Noah Spurrier