> Hello,
> 
>    Thank you for such a great piece of software!
> 
>    When displaying the entries in a log book with Summary view, ELCode is not processed in 'Text'. I know 
there
> is an option called 'Allow HTML", but is there something similar for decoding ELCode in the Summary 'Text' 
field?
> 
> Thank you again,
>    - Dan

Decoding HTML (or ELCode which translates to HTML) in the summary field is difficult, since the text is 
truncated. 
Assume you have some code like

Text
<b>Text
  <i>Text
----- cut here
</i>
</b>

Sot he bold <b> and italics <i> tags are opened, but closed after the cutting line. In that case the whole page 
might render wrongly, because everything after the summary text will be displayed in bold and italics. To fix this I 
would have to scan the HTML code and close all open tags "by hand". But since there are very many possibilities, 
especially if one used multi-column tables, this is almost impossible without writing my own HTML parser which is 
beyond the scope of elog. So the only clean solution I have found so far is to strip off all HTML formatting and 
just showing plain text there.

That would be a lot of effort for very little gain. I appreciate your detailed response. 

Thank you,
   - Dan

> > Hello,
> > 
> >    Thank you for such a great piece of software!
> > 
> >    When displaying the entries in a log book with Summary view, ELCode is not processed in 'Text'. I know 
> there
> > is an option called 'Allow HTML", but is there something similar for decoding ELCode in the Summary 'Text' 
> field?
> > 
> > Thank you again,
> >    - Dan
> 
> Decoding HTML (or ELCode which translates to HTML) in the summary field is difficult, since the text is 
> truncated. 
> Assume you have some code like
> 
> Text
> <b>Text
>   <i>Text
> ----- cut here
> </i>
> </b>
> 
> Sot he bold <b> and italics <i> tags are opened, but closed after the cutting line. In that case the whole page 
> might render wrongly, because everything after the summary text will be displayed in bold and italics. To fix this I 
> would have to scan the HTML code and close all open tags "by hand". But since there are very many possibilities, 
> especially if one used multi-column tables, this is almost impossible without writing my own HTML parser which is 
> beyond the scope of elog. So the only clean solution I have found so far is to strip off all HTML formatting and 
> just showing plain text there.

'Date' attributes can only be between 1970 and 2037, since I use internally the
unix time format. I added a test so future versions will complain and not crash
when the date is outside that range.

If you need dates before 1970, don't use the 'Date' format, simply use strings.

That bug has been fixed recently, please update to the newest version.