Comment 9 for bug 838432

On Thursday 01 September 2011, you wrote:
> Hello Xrg.
>
> Can you give us the branch to see if it is the same?
>

It's the 'trunk-xrg' branch on Sourceforge or Igloo:

http://git.hellug.gr/?p=xrg/openobject-addons
http://openerp-addons.git.sourceforge.net/git/gitweb.cgi?p=openerp-
addons/openerp-addons;a=summary

About the discussion: let's both agree that we give 2 possible solutions to
the same issue. For the Greek market, it is true that the fiscal printer is
connected to the cash box too (it must provide the "key" to print on the
invoice, although the fiscal device may be separate from the printer that we
use for the customer's "receipt").

My consideration is that I define a "protected area" of software and hardware
installation. The fiscal printer, the driver and the business logic must be
_audited by authorities_, to ensure that no receipt can be printed w/o getting
through the complete flow. So, I wanted this "protected area" to be outside of
OpenERP's software management (versions, installations, hacks). Since the
client and the server might change at any point, I made a clear separation of
the OpenERP's invoicing logic and the "fiscal printing". And put most of that
protected stuff in the server, because the server is more closely administered
than the client machines.

It is still doable to work through CUPS. I wrote a special wrapper for that,
talking to the serial port, too. I could provide you with full design plans
etc. And the benefit of the CUPS logic is that it can easily be networked, so
that it is physically placed where the fiscal printer needs to be installed.

(to be continued.. - I hope :] )