Hello<br><br>I think we should keep foomatic-* as is, if only to avoid user confusion. <br><br>Overall openprinting-cups-filters is a good name and can be extended to an optional package easily, e.g. openprinting-cups-filters-extra, cannot really go wrong with it.<br>
<br>The only downsides I can think of is that it is verbose and just a bit, plain.<br><br>There is another source of options, in line with CUPS, CPD, CMPD we could call it CFS* ( Common Filter Set ) or CPF ( Common Printing Filters ) or CCUPSFS (Common Common Unix Printing Spooler Filter Set).<br>
<br>But perhaps my favourite: CUFS ( Common Unix Filter Set), it may not mention the cups specific nature of the filters but what we lose in description we make up for in branding, it is a pronounceable word!**<br><br>Daniel<br>
<br>*Already taken =\<br>**In English at least.<br><br><br><br><div class="gmail_quote">2011/10/27 Till Kamppeter <span dir="ltr"><<a href="mailto:till.kamppeter@gmail.com">till.kamppeter@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<br>
Mike Sweet intends to remove the filters which are not used by Mac OS X from the CUPS upstream package:<br>
<br>
<a href="http://www.cups.org/str.php?L3930" target="_blank">http://www.cups.org/str.php?<u></u>L3930</a><br>
<br>
We have agreed on this on the last OpenPrinting Summit and the filters will be continued and hosted by OpenPrinting. In addition, the filters for the PDF printing workflow will not be adopted by CUPS but joined with the CUPS filters we overtake.<br>
<br>
All Linux distributions would have to include this new CUPS filters package then to get CUPS continuing to work and have the same feature set as before.<br>
<br>
Due to the fact that this package will use the PDF workflow by default and that all major desktop applications send their print jobs already in PDF, this will complete the implementation of PDF as standard print job format. See also my updated web page:<br>
<br>
<a href="https://www.linuxfoundation.org/collaborate/workgroups/openprinting/pdfasstandardprintjobformat" target="_blank">https://www.linuxfoundation.<u></u>org/collaborate/workgroups/<u></u>openprinting/<u></u>pdfasstandardprintjobformat</a><br>
<br>
By this, we also do not need to get a copyright/license agreement between the developers of the PDF filters and Apple.<br>
<br>
We can start hosting the CUPS filters as soon as our BZR repositories for OpenPrinting will be back. In the CUPS project these filters are already separated into their own branch, we only need to import them from their SVN into our BZR.<br>
<br>
We also need a name for the package. Should we call it simply "cups-filters"? Or "op-cups-filters"? Or do we rename Foomatic to openprinting and have the packages<br>
<br>
- openprinting-db<br>
- openprinting-db-nonfree<br>
- openprinting-db-engine<br>
- openprinting-rip<br>
- openprinting-cups-filters<br>
<br>
Note that we keep foomatic-rip/openprinting-rip separate from the CUPS filters as this filter is a universal filter which also works with many other printing systems.<br>
<br>
Another decision to make is whether we really should maintain all the filters which get over to us from CUPS or whether we should discontinue some. The filter set will contain "imageto..." and "textto..." filters which are not made use of by the usual desktop applications, they send all PDF (and some send PostScript). Alternatively, these filters could be made optional.<br>
<br>
Till<br>
______________________________<u></u>_________________<br>
Printing-architecture mailing list<br>
<a href="mailto:Printing-architecture@lists.linux-foundation.org" target="_blank">Printing-architecture@lists.<u></u>linux-foundation.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/printing-architecture" target="_blank">https://lists.linuxfoundation.<u></u>org/mailman/listinfo/printing-<u></u>architecture</a><br>
</blockquote></div><br>