Digital BW, The Print

If the GrayLab profile was accepted as a "colorspace" profile
then it would function with Qimage's CM as well in my opinion.
Grayscale files loaded will be converted to RGB in the process
to the "printfile". Including the printer profile selected.
The RGB file it delivers should be converted back to grayscale
but QTRgui takes care of that as far as I know. Like PS Qimage
doesn't accept the Graylab profile as a "Colorspace" and it
doesn't have the grayscale management that PS has.

Which colorspace profile has the same effect as the graylab 
profile on a grayscale image or B&W RGB file ? Keeping L and 
throwing a and b out shouldn't be different from setting a and 
b to zero. Or an AdobeRGB profile with all the saturation per 
rendering taken out in an editor. Where's the flaw in my 
thoughts ?
Qimage loads the gray etc printer profile but not the graylab 
profile. All dry trials though so I don't know what results  I 
can get right now.

I have asked MIke not so long ago where on the list the 
grayscale engine for Qimage is, it is very low on the priority
list he wrote. I think it would be faster to add another 
GrayLab "colorspace"profile etc that would enable us to use 
the adapted profiles in Qimage's CM system.

I wonder how the CM parts in the workflow interact with the 
interpolation, sharpening routines of Qimage if they are 
applied in a different order to one another. For example: PS 
total CM first>Qimage's sharpening etc>no Qimage CM 
activity>RGB print file, PS grayscale to RGB conversion + 
Graylab (color version)>RGB file to Qimage> Qimage's 
sharpening + interpolation>gray printer profile (color 
version)>RGB print file.

Ernst