med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

361
active users

#lcms2

0 posts0 participants0 posts today
Martin Owens :inkscape:<p>Bit stuck on this <a href="https://floss.social/tags/lcms2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lcms2</span></a> <a href="https://floss.social/tags/LittleCMS2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LittleCMS2</span></a> profile conversion.</p><p>Here's the thing, I should be able to transform an xyz d65 color into an sRGB d65 color using relative calorimetric intent as the <a href="https://floss.social/tags/w3c" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>w3c</span></a> CSS Color Module 4 says.</p><p>But I keep getting different results for some of the inputs. Some of them come out the same though.</p><p>Clipping? Anyone done this before?</p>
Martin Owens :inkscape:<p>I don't understand why some print shops ask for sRGB source documents *without* providing a gamut limiting icc profile so you can see what the hell you are doing.</p><p>I get taking in sRGB files for non-vector printing. But without that gamut limiter you're guessing what kind of gamut narrowing will happen so you should still have access to an icc profile.</p><p>At least, in my opinion as a self-made expert 😅 </p><p><a href="https://floss.social/tags/inkscape" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>inkscape</span></a> <a href="https://floss.social/tags/printing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>printing</span></a> <a href="https://floss.social/tags/cmyk" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cmyk</span></a> <a href="https://floss.social/tags/lcms2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lcms2</span></a> <a href="https://floss.social/tags/icc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>icc</span></a></p>
Jeff Fortin T. (風の庭園のNekohayo)<p><a href="https://mastodon.social/tags/Poppler" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Poppler</span></a>, the <a href="https://mastodon.social/tags/FreeDesktop" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeDesktop</span></a> <a href="https://mastodon.social/tags/PDF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PDF</span></a> library used by <a href="https://mastodon.social/tags/Evince" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Evince</span></a> / <a href="https://mastodon.social/tags/Okular" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Okular</span></a> / <a href="https://mastodon.social/tags/GNOME" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNOME</span></a> <a href="https://mastodon.social/tags/Papers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Papers</span></a> &amp; pretty much every floss PDF reader app on <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a>, has always been slow at searching text. As in, "3 to 5 minutes to search through 5000 pages"…</p><p>Beyond the fact that it's single-threaded, there's an issue that has remained mysterious for 11 years (possibly more): "Why is TextOutputDev slow?"</p><p>Today I profiled the hell out of it.<br>Result: it's <a href="https://mastodon.social/tags/LCMS2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LCMS2</span></a> ❓<br>Why is color management involved?! 🤯</p><p><a href="https://gitlab.freedesktop.org/poppler/poppler/-/issues/1472" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gitlab.freedesktop.org/poppler</span><span class="invisible">/poppler/-/issues/1472</span></a></p>