TOPIC:

Well, yes, I know, it will be a while until the documentation has to be created, but I am willing to help.
I've been doing some documentation and helpfiles before, so I think this is a good place for me in the development team.
But: I am German, so I would need some native speaker to read through all my texts so that is not embarrassing to publish - neither for me nor for JEM itself

Hi there Silberchen,

Thanks a lot for offering! I wouldn't mind reading through you work before it's published. There seem to be some tools that convert HTML help files into (PFD) documentation. Do you have any experience with that?

@Ernst,.

There are indeed some tools for converting documentation to PDF. And you've probably noticed that there are also websites offering to convert a page from html to pdf. Such a thing is probably a thing we can make ourselfs (offline). If it's really needed we could try something like code.google.com/p/dompdf/. Ofcourse it will take time testing/trying.

Something else is a program called "HTML to PDF converter", available over here .

Is there a reason you want to have a pdf? You have to recreate it every time you change something.

Things can be automated, but it has to be setup nontheless.

JEM is a web project, so why not leave the documentation as HTML?

Well, I was actually thinking of a PDF as helpfile/installation guide.

After all you need a reference before you have the software running.
An online guide on our website could be an alternative. It only means we have to guarantee to be up-and running 24/7...

ernst67 wrote: It only means we have to guarantee to be up-and running 24/7...

Usually, the web server is not switched off at night, I think