<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Jun 7, 2007, at 6:39 PM, Ian Goldberg wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">I agree that the otrl_message_* routines blur the line between library</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">stuff and app stuff.<SPAN class="Apple-converted-space"> </SPAN>That's where the English HTML messages all live,</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">for example.<SPAN class="Apple-converted-space"> </SPAN>The reason we moved them from gaim-otr to libotr is that</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">we thought they may be useful to other apps.<SPAN class="Apple-converted-space"> </SPAN>But I totally agree that</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">some refactoring may be useful there.</FONT></P> </BLOCKQUOTE></DIV><BR><DIV><SPAN class="Apple-style-span">Optimally, these messages would be available in the library but not in their current form. It'd be awesome if the library passed back defined error codes which could <I>then</I>, at the application's discretion, either be used to generate its own messages <I>or</I> passed to something like<B></B></SPAN></DIV><DIV><SPAN class="Apple-style-span"><B>const </B><B>char *</B><B>otr_get_error(otr_error errno)</B></SPAN></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>-Evan</DIV></BODY></HTML>