Updated printer definitions

[QORTEC]

Added the following printer definitions

Pulled #107 Brother DCP-7070DW Thanks @musinsky

Closes #141 Brother DCP-7020 Closes #172 Brother DCP-8065DN Closes #66 Brother DCP-L2510D series Closes #87 Brother DCP-L2537DW Closes #102 Brother DCP-L2550DW series Closes #63 Brother HL-2130 series Closes #147 Brother HL-2230 series Closes #121 Brother HL-2240D series Closes #101 Brother HL-2250DN series Closes #128 Brother HL-2280DW Closes #94 Brother HL-5040 series Closes #112 Brother HL-L2305 series Closes #108 Brother HL-L2310D series Closes #103 Brother HL-L2350DW series Closes #162 Brother HL-L2370DN series Closes #90 Brother HL-L2380DW series Closes #156 Brother HL-L5000D series Closes #109 Brother MFC-1810 series Closes #115 Brother MFC-7320 Closes #77 Brother MFC-7340 Closes #144 Brother MFC-7440N Closes #50 Brother MFC-8710DW Closes #129 Brother MFC-8860DN Closes #134 Brother MFC-L2700DW series Closes #114 Brother MFC-L2700DN series Closes #130 Brother MFC-L2710DN series Closes #57 Brother MFC-L2750DW series Closes #83 Brother MFC-L3750CDW series Closes #142 Lenovo LJ2650DN Closes #150 Fuji Xerox DocuPrint P265 dw

[QORTEC]

Added the following printer definitions

Closes #173 Brother DCP-1610W series Closes #176 Brother FAX-2820 Closes #189 Brother FAX-2840 Closes #185 Brother HL-2260 Closes #190 Brother HL-L2335D series Closes #187 Brother MFC-7860DW Closes #182 Brother MFC-9160

[qwertychouskie]

@pdewacht Any chance of this getting merged soonish and a new release tagged? This would greatly benefit the owners of a variety of printers (including me).

[qwertychouskie]

(Also @QORTEC this PR shows merge conflicts for some reason, perhaps a bad rebase?)

[QORTEC]

@qwertychouskie your correct; when I rebased I apparently accidentally "recommitted" f3de875079e0544e91eb9992bf308a78545b23c5 (which was already in pdewacht/brlaser) which seems to be source of the conflict.

I'll fix that later on when I have more time, though "functionally" it shouldn't matter, and that commit can be ignored when pulling the changes from my fork.

While its important to resolve this conflict, I consider it to be "low priority" since @pdewacht doesn't seam to have time to maintain brlaser at the moment and a quick resolution doesn't have a functional benefit. Package maintainers will probably ether use vanilla brlaser found here or a release on Owl-Maintain/brlaser with the patches already applied.

[hifron]

Currently package printer-driver-brlaser is installed in Ubuntu but also there is driver from Brother which should be more beneficial to Brother users who wants to print something as it seems as Rust is preferred language for @pdewacht now but also Brother for older printer seems not so interested for Linux(but other systems seems not so)...

What about transfer this repo to Brother organization or OpenPrinting and let help maintain them with not so overhead for currently Linux drivers with some support from Brother for fixing bugs? And maybe make OpenPrinting App which would somehow work with nowadays/3.0 CUPS and maybe make it more official with Brother. @michaelrsweet ?

But one huge problem(for Brother organization) could be that some printers also have scanners and Scanner application is not installed by default either(but SANE app installable) or possible with current CUPS(but planned) and Brother have builtin combined drivers(but maybe outdated)...

But if faulty installed package printer-driver-brlaser is problematic and not maintained, its disaster for some users.

[michaelrsweet]

@hifron I can't speak for the OpenPrinting organization, but I know for me that I don't have the time or resources (printers, documentation, etc.) to support such an effort directly. The best I can do is advise developers when they have questions, either for CUPS driver developer or migration to a printer application using PAPPL.