From Fedora Project Wiki
(Created page with '= Installazione automatica dei driver di stampante = == Sommario == <!-- A sentence or two summarizing what this feature is and what it will do. This information is used for t...')
 
m (Obbiettivo->Obiettivo)
 
(8 intermediate revisions by one other user not shown)
Line 3: Line 3:
== Sommario ==
== Sommario ==
<!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
<!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
Packages like gutenprint-cups, hpijs, and pbm2l2030 should be installed on-demand when hardware requiring those drivers is detected.
Pacchetti come gutenprint-cups, hpijs, e foomatic dovrebbero potersi installare su richiesta dell'hardware.


== Progettista ==
== Progettista ==
<!--This should link to your home wiki page so we know who you are-->
<!--This should link to your home wiki page so we know who you are-->
* Name: [[User:twaugh| Tim Waugh]]
* Nome: [[User:twaugh| Tim Waugh]]


<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
* email: twaugh@redhat.com
* Email: [mailto:twaugh@redhat.com twaugh@redhat.com]


== Current status ==
== Stato attuale ==
* Rilascio: [[Releases/13|  Fedora 13]]
* Per informazioni aggiornate sullo stato del progetto consultare la [[Features/AutomaticPrintDriverInstallation#Current_status | pagina originale]] di questo documento.


* Targeted release: [[Releases/13 | Fedora 13]]
== Descrizione dettagliata ==
* Last Updated: 2010-01-25
* Percentage of completion: 80%
 
== Detailed Description ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
All printers, whether connected by parallel port, USB, bluetooth or network, identify themselves using an IEEE 1284 Device ID string. This is a sequence of key:value pairs with, among others, fields for the manufacturer, the model, the command sets supported by the printer.
Tutte le stampanti, connesse alla porta parallela, o UBS, Bluetooth o di rete, vengono individuate dal S.O. usando una stringa di identificazione secondo quanto stabilito da IEEE 1284. Essa è una sequenza di coppie chiave:valore, con tra gli altri, campi per il produttore, il modello, l'insieme dei comandi supportati dalla stampante.


The idea behind this feature is to add RPM tags to printer driver packages to match up with the manufacturer and model fields used by printers to identify themselves. Once this is done system-config-printer can use PackageKit to install the driver required for a printer when it is connected, or when a queue is set up for it interactively.
L'idea di questo progetto è di aggiungere dei tag RPM ai pacchetti driver della stampante coincidenti con quelli usati per l'identificazione della stampante stessa. In tal modo system-config-printer può usare PackageKit per installare il driver necessario quando la stampante viene collegata, o quando si imposta per essa interattivamente una coda.


The way these RPM tags can be added automatically to printer driver packages is by using a "provides" script. This will look for PPD files, read through them to find a "1284DeviceID" PPD attribute, and parse the IEEE 1284 Device ID string to extract the "MFG" and "MDL" fields. Here is an example of a snippet of a PPD that contains a 1284DeviceID attribute:
I tag RPM possono essere aggiunti automaticamente ai pacchetti driver della stampante usando degli script. Il compito dello script sarà di cercare il file PPD appropriato, trovare all'interno di esso un attributo PPD ''1284DeviceID'', e analizzare la stringa d'identificazione IEEE 1284 estraendone i campi ''MFG e MDL''. Di seguito si riporta un estratto di file PPD che evidenzia l'attributo 1284DeviceID:


<pre>
<pre>
Line 41: Line 39:
*1284DeviceID: "MFG:Brother;MDL:HL-5250DN series;CMD:PJL,PCL,PCLXL,POSTSCRIPT;"
*1284DeviceID: "MFG:Brother;MDL:HL-5250DN series;CMD:PJL,PCL,PCLXL,POSTSCRIPT;"
</pre>
</pre>
I file PPD sono il modo più semplice per un driver di rendersi disponibile attraverso CUPS.<BR>Un'alternativa è di fornire un [http://www.cups.org/documentation.php/doc-1.4/ppd-compiler.html driver information file], ed analogamente ai file PPD essi dovranno includere un attributo 1284DeviceID per ogni PPD che definiscono affinchè l'installazione automatica del driver possa funzionare.<BR> Il driver ''hpcups'' del pacchetto ''hplip'' è un esempio di questo tipo.


PPD files are the simplest way for a driver to make itself available through CUPS.  Another way is to provide a [http://www.cups.org/documentation.php/doc-1.4/ppd-compiler.html driver information file], and similarly to PPD files these must include a 1284DeviceID attribute for each PPD they define in order for automatic printer driver installation to work.  The hpcups driver from the hplip package is an example of this type.
Un altro modo ancora è di fornire un [http://www.cups.org/documentation.php/doc-1.4/man-cups-driverd.html CUPS driver]. Questo è un programma che genera su richiesta file PPD. Qunado CUPS manda in esecuzione il programma con l'opzione ''list'', esso compila una lista con tutti i PPD in grado di generare. Per poter confrontare automaticamente il produttore ed il modello con i tag presenti nel pacchetto RPM, anche questa lista deve contenere le appropriate stringhe d'identificazione.<BR> I pacchetti ''gutenprint-cups'' e ''foomatic'' sono esempi di questo tipo di driver.
 
Yet another way for a driver to integrate with CUPS is for it to provide a [http://www.cups.org/documentation.php/doc-1.4/man-cups-driverd.html CUPS driver]. This is a program that generates PPD files on demand. When CUPS runs the program with "list" as its argument, it must write out a list of all the PPDs it is prepared to generate. In order for the manufacturers and models to be automatically tagged in the RPM package, this list must contain the appropriate Device ID strings. The gutenprint-cups and foomatic packages have examples of this type of driver.


== Benefit to Fedora ==
== Vantaggi per Fedora ==
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
Very often the wrong driver is used and bugs are reported about "the" driver not working, when the answer was to install another package. Of course it is also easy to be misled into thinking that there is no driver for a particular model simply because that model does not show in the CUPS model list (that list is built from the information provided by the installed drivers).
Molto spesso vengono usati i driver sbagliati e di conseguenza si riportano bug del tipo il driver non funziona, qunado invece busterebbe installare il pacchetto giusto. Altre volte invece si è portati a credere che non ci sia alcun driver per un particolare modello semplicemente perchè quel modello non è presente nella lista fornita da CUPS (tale lista è generata dalle informazioni fornite dai driver installati!).
 
== Scope ==
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
* All the printer drivers need to report IEEE 1284 Device IDs, including at least the MFG and MDL fields, for the majority of the printers they support.
** HPLIP and gutenprint (DONE)
** Still needed for others such as pbm2l2030 and other small drivers like that
* PackageKit needs support for the new tag type (DONE)
* RPM needs to be able to add the tags. Patch ready.
* system-config-printer needs to be able to install packages for automatically-detected USB printers
* system-config-printer needs to be able to install packages for printers when manually adding a queue


== How To Test ==
== Note di rilascio ==
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  
I driver delle stampanti ora si installano automaticamente, quando la stampante viene collegata.


Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
== Altre informazioni ==
Per:
* Obiettivi
* Test Plan
* Esperienza Utente
* Dipendenze
* Progetto corrente
* Documentazione
* Commenti e Discussioni


A good "how to test" should answer these four questions:
consultare la [[Features/AutomaticPrintDriverInstallation | pagina originale]] di questo documento.


0. What special hardware / data / etc. is needed (if any)?
[[Category:Italiano]]
1. How do I prepare my system to test this feature? What packages
[[Category:F-13 Features IT|{{SUBPAGENAME}}]]
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the feature is
working like it's supposed to?
3. What are the expected results of those actions?
 
-->
=== Connecting a USB printer ===
Start with the relevant driver package for your printer *not* installed and the printer disconnected.
 
Connect the printer and power it on.
 
You may be asked for authentication to install packages.
 
You should be asked to print a test page.
 
You must be able to print to the printer.
 
=== Adding a queue manually ===
Start with the relevant driver package for your printer *not* installed.
 
Select System->Administration->Printing.
 
Select a network printer (can be 'Internet Printing Protocol' for another CUPS server).
 
You may be asked for authentication to install packages.
 
If a list of drivers is shown, the correct driver should already be selected in the list.
 
You should be asked to print a test page.
 
You must be able to print to the printer.
 
== User Experience ==
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
Plugging in a printer just works, whenever this is possible.  The LiveCD does not have to ship with printer drivers on it.
 
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
* rpm ([https://bugzilla.redhat.com/show_bug.cgi?id=538101 bug #538101])
* gnome-packagekit ([https://bugzilla.redhat.com/show_bug.cgi?id=558450 bug #558450])
 
== Contingency Plan ==
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
Revert to previous behaviour.
 
Add foomatic-db-ppds to comps.
 
== Documentation ==
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
This is it.
 
== Release Notes ==
Printer drivers are now installed automatically when a printer is connected.
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
 
== Comments and Discussion ==
* See [[Talk:Features/AutomaticPrintDriverInstallation]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->


[[Category:FeatureAcceptedF13]]
[[Category:FeatureAcceptedF13]]
<!-- When your feature page is completed and ready for review -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
<!-- Note that the current Feature guidelines require useful Scope and Test Plans at certain milestones; QA is responsible for checking these, and will change this category as needed. -->

Latest revision as of 22:56, 29 August 2010

Installazione automatica dei driver di stampante

Sommario

Pacchetti come gutenprint-cups, hpijs, e foomatic dovrebbero potersi installare su richiesta dell'hardware.

Progettista

Stato attuale

Descrizione dettagliata

Tutte le stampanti, connesse alla porta parallela, o UBS, Bluetooth o di rete, vengono individuate dal S.O. usando una stringa di identificazione secondo quanto stabilito da IEEE 1284. Essa è una sequenza di coppie chiave:valore, con tra gli altri, campi per il produttore, il modello, l'insieme dei comandi supportati dalla stampante.

L'idea di questo progetto è di aggiungere dei tag RPM ai pacchetti driver della stampante coincidenti con quelli usati per l'identificazione della stampante stessa. In tal modo system-config-printer può usare PackageKit per installare il driver necessario quando la stampante viene collegata, o quando si imposta per essa interattivamente una coda.

I tag RPM possono essere aggiunti automaticamente ai pacchetti driver della stampante usando degli script. Il compito dello script sarà di cercare il file PPD appropriato, trovare all'interno di esso un attributo PPD 1284DeviceID, e analizzare la stringa d'identificazione IEEE 1284 estraendone i campi MFG e MDL. Di seguito si riporta un estratto di file PPD che evidenzia l'attributo 1284DeviceID: 

*%==== General Information Keywords ========================
*FormatVersion: "4.3"
*FileVersion: "1.03"
*LanguageEncoding: ISOLatin1
*LanguageVersion: English
*Manufacturer: "Brother"
*PCFileName: "BR5250_2.PPD"
*Product: "(Brother HL-5250DN series)"
*PSVersion: "(3010.106) 5"
*ShortNickName: "Brother HL-5250DN BR-Script3"
*ModelName: "Brother HL-5250DN BR-Script3"
*NickName: "Brother HL-5250DN BR-Script3"
*1284DeviceID: "MFG:Brother;MDL:HL-5250DN series;CMD:PJL,PCL,PCLXL,POSTSCRIPT;"

I file PPD sono il modo più semplice per un driver di rendersi disponibile attraverso CUPS.
Un'alternativa è di fornire un driver information file, ed analogamente ai file PPD essi dovranno includere un attributo 1284DeviceID per ogni PPD che definiscono affinchè l'installazione automatica del driver possa funzionare.
Il driver hpcups del pacchetto hplip è un esempio di questo tipo.

Un altro modo ancora è di fornire un CUPS driver. Questo è un programma che genera su richiesta file PPD. Qunado CUPS manda in esecuzione il programma con l'opzione list, esso compila una lista con tutti i PPD in grado di generare. Per poter confrontare automaticamente il produttore ed il modello con i tag presenti nel pacchetto RPM, anche questa lista deve contenere le appropriate stringhe d'identificazione.
I pacchetti gutenprint-cups e foomatic sono esempi di questo tipo di driver.

Vantaggi per Fedora

Molto spesso vengono usati i driver sbagliati e di conseguenza si riportano bug del tipo il driver non funziona, qunado invece busterebbe installare il pacchetto giusto. Altre volte invece si è portati a credere che non ci sia alcun driver per un particolare modello semplicemente perchè quel modello non è presente nella lista fornita da CUPS (tale lista è generata dalle informazioni fornite dai driver installati!).

Note di rilascio

I driver delle stampanti ora si installano automaticamente, quando la stampante viene collegata.

Altre informazioni

Per:

  • Obiettivi
  • Test Plan
  • Esperienza Utente
  • Dipendenze
  • Progetto corrente
  • Documentazione
  • Commenti e Discussioni

consultare la pagina originale di questo documento.

Retrieved from "https://fedoraproject.org/w/index.php?title=It_IT/Releases/13/Features/AutomaticPrintDriverInstallation&oldid=194784"