Wikipedia:Featured article candidates/Common Unix Printing System/archive1

Common Unix Printing System
Self-nomination Have done quite a bit of work on it as it's my focus article. I have placed it on peer review for quite a while with no comment and as I've recently finished the architecture diagram I think this is pretty much complete. Any suggestions, however, I would love to hear and I'll attempt to sort them out! - Ta bu shi da yu 03:00, 14 Jan 2005 (UTC)
 * I've not read the article fully yet, but before I do that the only pointer I have is to break the paragraphs into more paragraphs for easier reading. &#8211;&#8211; Constafrequent (talk page) 09:29, 14 Jan 2005 (UTC)
 * Support but yes, it would be nice if there was a little more white space in there. CUPS is a complicated beast, so getting away from that might be tough. iMeowbot~Mw 09:53, 14 Jan 2005 (UTC)
 * I've broken the paragraphs into smaller ones; Will read the actual article now. :-) &#8211;&#8211; Constafrequent (talk page) 10:12, 14 Jan 2005 (UTC)


 * Support: On the qualities of article structure. It's such a technological article that after sleep deprivation I can't focus sufficiently to absorb the knowledge, and it's not my field so can't vouch for accuracy or omissions. &#8211;&#8211; Constafrequent (talk page) 10:23, 14 Jan 2005 (UTC)4
 * Suggestion: A section with definitions of terms used, so in the context of the article by itself the acronyms and terms used make enough sense for the lay person to grasp the information enough for them to have some level of understanding without having to venture into other articles. &#8211;&#8211; Constafrequent (talk page) 10:32, 14 Jan 2005 (UTC)
 * I'd prefer to work in the definitions into the article. I'm working at this now. - Ta bu shi da yu 11:47, 14 Jan 2005 (UTC)
 * Support, article has improved. silsor 14:39, Feb 1, 2005 (UTC)
 * OK, I'm happy to do this. Do you have any suggestions though? My overview states the following:
 * CUPS provides a standard API to allow print jobs to be sent to printers. The API sends the data to a scheduler which then sends jobs to a filter system that converts the print job into a format the printer will understand. The filter system then passes the data on to a backend—a special filter that sends print data to a device or network connection. The system makes extensive use of PostScript and rasterization of data in order to convert the data into a language that the printer will understand. The primary advantage of CUPS is that it is a standard and modularised printing system that can process numerous data formats on the print server. Previously, it was difficult to find a solution that was standardised that would allow for the numerous printers that are on the market that use their own printer languages and formats. With CUPS, it is far easier for printer manufacturers and printer driver developers to create drivers that work natively on the print server. As the processing is done on the server, it is also far more easy to allow for network based printing than it was previously with other Unix printing system. One advantage is that when used with Samba printers can be used on remote Windows computers and in fact generic PostScript drivers can be used to print across the network.
 * I thought that was pretty good, what should I say to tighten it up? - Ta bu shi da yu 09:04, 15 Jan 2005 (UTC)


 * Support. Very well-written. utcursch 09:08, Jan 15, 2005 (UTC)
 * Support. Concur with  utcursch. JuntungWu 11:13, 15 Jan 2005 (UTC)
 * Object. I am a relative Luddite compared to many people here, and so my position on this may be unpopular.  I believe that all technical articles should start off with a lead section that is comprehensible to someone totally unfamiliar with the topic.  For starters, although I am usually not annoyed by red links, the print server link in the opening paragraph must be filled in with a substantive article (I have only a fuzzy idea of what it is, and I'm probably in the top 10% of the general population for understanding computers).  Wikipedia is an encyclopedia, not a technical reference work.  At the very least, this means that the lead sections of good articles should be informative to the casual reader and introductory in scope.  Under those criteria, the second sentence is a little early for the phrase "uniform rasterized data format", which frankly made my eyes glaze over and head hurt.  Bantman 23:28, Jan 17, 2005 (UTC)
 * Well, I've filled in that article with a stub (whether it is a stub or not should not reflect on my article), I have given a very brief sentence of what a print server is and I have clarified why CUPS is important. I have removed the "uniform rasterized data format" info also. I hope that the lead section is a lot clearer now. - Ta bu shi da yu 02:45, 18 Jan 2005 (UTC)
 * Much better &mdash; I can now get as far as the table of contents before wishing I paid more attention in CS lectures. I withdraw my objection and, lacking any ability to comprehend the rest of the article, will abstain (not the bad kind, the "pretend I wasn't here" kind). Bantman 19:07, Jan 18, 2005 (UTC)
 * I added another diagram to try to clarify the process a bit. Does this help in understanding? - Ta bu shi da yu 02:03, 19 Jan 2005 (UTC)