I attach the example of my html log. I hide all private information in it but the structure of log is unchanged.
I think that using QRegExp is better because the result parser is much simpler and clear to understand. I hope you have one message per line format too. The speed is not important because import of logs is operation that user performs only one time.
The RegExp parser is simple to adapt to your message format. For example, in your log <font color="#A82F2F"><font size="2">(22:12:33)</font> <b>Nick:</b></font> <font sml="AIM/ICQ">[MessageText]</font><br/> you need to correct beginMessage to "</b></font> " and replace text <font sml="AIM/ICQ"> and </font><br/> with "".
There is a problem with html links in the text body such as <a href='mailto:<email address hidden>'><email address hidden></a> but it can be solved with a regexp too.
I attach the example of my html log. I hide all private information in it but the structure of log is unchanged. #A82F2F" ><font size="2" >(22:12: 33)</font> <b>Nick:</b></font> <font sml="AIM/ ICQ">[MessageTe xt]</font> <br/> you need to correct beginMessage to "</b></font> " and replace text <font sml="AIM/ICQ"> and </font><br/> with "".
I think that using QRegExp is better because the result parser is much simpler and clear to understand. I hope you have one message per line format too. The speed is not important because import of logs is operation that user performs only one time.
The RegExp parser is simple to adapt to your message format. For example, in your log <font color="
There is a problem with html links in the text body such as <a href='mailto:<email address hidden>'><email address hidden></a> but it can be solved with a regexp too.