It’s not code-related, but I’ve just read that images should have the sRGB color profile attached, or no profile at all. Adobe RGB, which works just fine for print, will wash out on Windows monitors.
Not quite the case; Windows is perfectly capable of showing Adobe RGB (1998) colour-tagged images correctly. Perhaps it is the Windows browsers that assume sRGB? I know most browser plugins do that with Adobe RGB (1998)-tagged images (on Mac as well as Windows), rendering colours weaker than they should be.
I don’t know of any Windows browser that will actually read or do
anything with ColorSync profiles on images they display. (Well, except
for Safari, but that’s hardly a /Windows/ browser, is it?) They just
show the raw image data, without performing any color-matching to
account for local display foibles.
What you might find is that since your images are being displayed
without any color correction whatsoever, and at a higher than normal
gamma, they may appear quite different than you intended, or could
predict.
Walter
On Mar 12, 2010, at 1:53 PM, Keith Martin wrote:
It’s not code-related, but I’ve just read that images should have
the sRGB color profile attached, or no profile at all. Adobe RGB,
which works just fine for print, will wash out on Windows monitors.
Not quite the case; Windows is perfectly capable of showing Adobe
RGB (1998) colour-tagged images correctly. Perhaps it is the Windows
browsers that assume sRGB? I know most browser plugins do that with
Adobe RGB (1998)-tagged images (on Mac as well as Windows),
rendering colours weaker than they should be.
Speaking of color management — and for my own and others’ future reference — Keith provides an epic amount of information, he even expounds on cmyk profiles, here:
A pay-wall. I can’t be giving my work away for free Walt like I used too. It just wasn’t fair and balanced nor are my prices ridiculous either. I mean my WebYep series, episode 2 and 3 are an hour long and are each $5 bucks. All the money goes strictly to the web hosting and the site, not into my pocket, as I’ve stated to my customers.
I remember, so long ago, 11 totally free screencasts were out there on FreewayCast.com when it first got started but the site just failed to develop anywhere. There was no way to customize the site or edit any of the comments.
In the next few days I’ll be making an announcement that will change that.
The first is about editing the body tag, which I haven’t needed to do…yet. And the second is a detailed thread about those pesky style1s, style2s, etc. that pop up.
Where possible try to apply text styles to html items, rather than selected text. This will help keep FW from styling text via s and keep the code efficient.
