You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two issues here:
* The hue angles need adjusting to work with the palette library
* The resultant RGB color had the wrong gamma level, resulting in
an overly bright image.
refs: #775
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
I was testing sixels in the HLS color space in several terminal emulators and noticed that wezterm doesn't handle them correctly:
Environment
To Reproduce
Run
img2sixel -t hls <image>
. Compare withimg2sixel -t rgb <same image>
.Expected behavior
Additional context
In Sixels, the primary color hues are:
I suspect wezterm uses
See https://archive.org/details/bitsavers_decstandar0VideoSystemsReferenceManualDec91_74264381/page/n927/mode/2up, or/and https://vt100.net/docs/vt3xx-gp/chapter2.html#S2.4.2 (scroll down to "Table 2-3 VT340 Default Color Map")
Also worth noting is that XTerm's implementation has issues too, but e.g. mlterm works as expected.
The text was updated successfully, but these errors were encountered: