Thanks much for the mail. See my comments inlined. Pl. view this request as an EOF announcement for print filter consolidation similar to we did for PSARC/2001/754.
James Carlson wrote: > Suresh Chandrasekharan writes: > >>> is the actual presentation forms. This is no longer used as >>> conversion from logical to visual representation is done at >>> runtime now and we are not interested in storing presentation >>> forms output by ctlconvert_txt which is not portable. The original >>> purpose this filter was to provide glyph input into non-PS >>> printers. mp(1) do have -D/-P option for creating non-PS output >>> so this is not useful at all now. >>> > > Are there any users potentially still using these utilities? > No, these are quite antique tools. While there are no guarantees that people aren't using this, I will be quite surprised if we find any users, With fixing the mp(1) utility to work in native Arabic/Hebrew locale, (we already have the fix ready to be integrated for the bug "4771193 Native Arabic/Hebrew locale does not print correctly using mp") this utility may be replaced by mp(1). So if at all any customers are using this, they can use mp(1) instead. > If so, then what must they do on upgrade to a Nevada-based release? > Does the upgrade process itself automatically adjust the print filters > to the new mechanism, or is there a document that explains the > necessary customer action? > The following is the mechanism used for alerting the customers about the EOF. The EOF notice a message "ctlmp: This utility will be removed from next Solaris Major release. Please use mp(1) print filter or another suitable printing mechanism instead" will output to stderr for each invocation of ctlmp. Pl. see the reasons for EOFing ctlconvert-txt in the OVERVIEW section of the fasttrack one pager submitted. "ctlconvert-txt: This utility will be removed from next Solaris Major release. Please use mp(1) print filter or another suitable printing mechanism instead". > If there's customer action required, is this something that customers > can do (prior to upgrade) on existing S10 and S9 systems when the EOF > notice is released? Or is it an upgrade-break-fix cycle? > > >>> There is no notable imported interfaces. The following are the exported >>> interfaces: >>> >>> Interface Stability Reference >>> >>> /usr/openwin/bin/ctlmp obsolete >>> /usr/openwin/bin/ctlconvert_txt obsolete >>> > > Looks like this is: > > EOF Notice - Patch/Micro release binding > Actual EOF - Minor release binding > Yes, you're right. Regards, Suresh
