Hallo and thanks for a great program.
At my work we have previously been using another program (Rednotebook) for our lab journals, but now we wish to migrate to elog because it is more configurable and because it runs in a browser.
We would off course like to move all of our old log entries with us. Luckily Rednotebook uses a standard module (YAML) for data storage, so I can easily access the data (e.g. with python) and I have already done do, and I have exchanged the native markup with html.
Now I would prefer it if I can make the elog data files directly, in stead of using the elog command, because that makes it possible and easy to revert the change, and also to not have to handle escaping html string before feeding them to elog on the commandline. I have actually already written the program that produces the elog data files, but now I have a few questions:
1) Is there an overall way of validating the datafiles, to make sure elog doesn't choke on them at some point in the future when I try to open one of the old entries. Along the same lines, does elog parse all the files when the demon is started, so if it starts then I'm ok?
2) What exactly are the requirements for the HTML content
2a) Will any valid html do, or are there some speciel requirements (e.g. like at blank lines)
2b) Does it require a particular version of html, because then I could at least validate it against that doctype beforehand
3) Is there a log from elog where I can see if it encounters something it doesn't like?
I hope the you can answer some of my questions.
Regards Kenneth |