Yes, it seems you _will_ be penalized for creating a website that is Mobile Friendly:- use plain HTML where the presentation is strictly up to the browser, and the Google check tool uses a default tiny, tiny font and then complains that your website has fonts that are too small !
Ironically, Chrome (on Android at least) doesn't have this problem - plain HTML websites are perfectly readable, making a mockery of Googles check tool.
You're not far wrong in your estimate of the amount of effort needed (Argyll has taken about 7 years effort so far), but you're wrong in assuming that nothing is happening in the open source area. A couple of us seem to be making fair color scientists out of ourselves by writing color management systems from scratch.
One of the reasons Argyll is open source is that I figured, yes I can write another proprietary color management package, and be like the other dozen companies scratching for a living in this area, or I can do something new, and write the first open source CMS. As someone working for a competitor to EFI, you'll have to forgive me for thinking that working for EFI is not much of a credential when it comes to talking about color:-)
For the couple of areas that Argyll is being actively used, it is being used in preference to
commercial CMS. One area is in creating monitor to film recorder links for a (very well known) animation studio. The other area is in creating color profiles and links for extremely critical print system proofing. In the latter area, Argyll is giving results that are very clearly superior to Kodak's KCMS, and Gretag-Macbeths ProfileMaker.
For things it is not being actively used with (such as the sort of RGB -> pseudo CMY profiling that Raph
is having a go at), then there is still a lot of fine tuning to do, and it is not (nor does it claim to be) an end user tool.
As for GIMP, Argyll provides all the bits needed to incorporate ICC profile support, including RGB CMYK.
It's rather up to the developers of GIMP to pick it up and use it though !
Slashdot Mirror
Yes, it seems you _will_ be penalized for creating a website that is Mobile Friendly :- use plain HTML where the presentation is strictly up to the browser, and the Google check tool uses a default tiny, tiny font and then complains that your website has fonts that are too small !
Ironically, Chrome (on Android at least) doesn't have this problem - plain HTML websites are perfectly readable, making a mockery of Googles check tool.
You're not far wrong in your estimate of the amount of effort needed (Argyll has taken about 7 years effort so far), but you're wrong in assuming that nothing is happening in the open source area. A couple of us seem to be making fair color scientists out of ourselves by writing color management systems from scratch. One of the reasons Argyll is open source is that I figured, yes I can write another proprietary color management package, and be like the other dozen companies scratching for a living in this area, or I can do something new, and write the first open source CMS. As someone working for a competitor to EFI, you'll have to forgive me for thinking that working for EFI is not much of a credential when it comes to talking about color :-)
For the couple of areas that Argyll is being actively used, it is being used in preference to commercial CMS. One area is in creating monitor to film recorder links for a (very well known) animation studio. The other area is in creating color profiles and links for extremely critical print system proofing. In the latter area, Argyll is giving results that are very clearly superior to Kodak's KCMS, and Gretag-Macbeths ProfileMaker. For things it is not being actively used with (such as the sort of RGB -> pseudo CMY profiling that Raph is having a go at), then there is still a lot of fine tuning to do, and it is not (nor does it claim to be) an end user tool. As for GIMP, Argyll provides all the bits needed to incorporate ICC profile support, including RGB CMYK. It's rather up to the developers of GIMP to pick it up and use it though !