Changes

* Thing is we don't technically do a pdf conversion, CUPS comes with an emulator of the print engine, and prints to the PDF. And we do this because we would like for the teacher to review it.  

* Thing is we don't technically do a pdf conversion, CUPS comes with an emulator of the print engine, and prints to the PDF. And we do this because we would like for the teacher to review it.  

   The pdf is stored in a web folder on the server, and through moodle the teacher goes through them (we provide a webpage), and approves the ones he thinks appropriate for printing.

   The pdf is stored in a web folder on the server, and through moodle the teacher goes through them (we provide a webpage), and approves the ones he thinks appropriate for printing.

   I explained it my explanation

   I explained it my   explanation

   The outcome of my second draft (beta) was that students should be provided as minimal functionality as possible. They shouldn't be given too much flexibility or options. And... you get   

   The outcome of my second draft (beta) was that students should be provided as minimal functionality as possible. They shouldn't be given too much flexibility or options. And... you get   

  WYSIWYG only as we  send the files directly from the journal.

  WYSIWYG only as we  send the files directly from the journal.

   IF the mime type exists in cups mime.type , we are all good to do printing from journal. (that is why we require step 1)

   IF the mime type exists in cups mime.type , we are all good to do printing from journal. (that is why we require step 1)

   There is no reason to read the file, the server handles the necessary post script conversions!

   There is no reason to read the file, the server handles the necessary post script conversions!