Mercurial > pidgin.yaz
view README.CVS @ 9222:316b1afb5974
[gaim-migrate @ 10018]
nosnilmot make autolinkification work even better.
This patch improves the way we auto-linkify detected
URLs and email addresses:
- if a URL is enclosed in parenthesis eg
(http://www.google.com/), the closing parenthesis will
not be included as part of the link
- email addresses inside parenthesis or <>'s will
correctly be linked
- either whitespace or non-ascii characters are
recognized as boundaries for email addresses, which
will allow auto linking of email addresses for Chinese
conversations which don't use whitespace:
<stu|laptop> wing: you know you mentioned being able to
auto-linkify email addresses in Chinese text (without
whitespace), do you want to try
a patch out for me?
<wing> stu|laptop: eh, actually i found that gaim cannot
<stu|laptop> cannot? at all?
<wing> stu|laptop: it seems so
stu|laptop> even with this? <link to patch>
<wing> stu|laptop: i'll check it out then :)
... ...
<wing> stu|laptop: it works perfectly with the patch :)
committer: Tailor Script <tailor@pidgin.im>
author | Tim Ringenbach <marv@pidgin.im> |
---|---|
date | Sun, 06 Jun 2004 19:06:22 +0000 |
parents | 17a446f5e99b |
children | e4a27c9aec4c |
line wrap: on
line source
If you plan to use gaim CVS, PLEASE read this message in its entirety! Gaim is a fast-moving project with a somewhat regular release schedule. Due to the rate of gaim development, CVS undergoes frequent bursts of massive changes, often leaving behind brokenness and partial functionality while the responsible developers rewrite some portion of code or seek to add new features. What this all boils down to is that CVS _WILL_ sometimes be broken. Because of this, we ask that users who are not interested in personally tracking down bugs and fixing them (without a lot of assistance from the developers!) avoid CVS and use releases. Since releases will be made often, this should not prevent anyone from using the newest, shiniest features -- but it will prevent users from having to deal with ugly development bugs that we already know about but haven't gotten around to fixing. If you are interested in hacking on gaim, please read README and HACKING, and take note of the issues in PROGRAMMING_NOTES. (Note that they may be somewhat out of date at times.) Win32 developers, please read README.mingw. By far the best documentation, however, is the documented code. Not all parts of gaim have yet been documented, but the major subsystems are falling fast. If you have doxygen, you can use the Doxyfile in the toplevel directory to generate pretty documentation. Otherwise (or even if you do!), the header files for each subsystem contain documentation for the functions they contain. For instance, conversation.h contains documentation for the entire gaim_conversation_* API, and account.h contains documentation for the gaim_account_* API. If you have questions, please feel free to contact the gaim developers by email at gaim-devel@lists.sourceforge.net, on IRC at irc.freenode.net in #gaim, or via the sourceforge forums at http://www.sourceforge.net/projects/gaim. Please do as much homework as you can before contacting us; the more you know about your question, the faster and more effectively we can help you! Send patches to gaim-devel@lists.sourceforge.net or post them in the Sourceforge forums at http://www.sourceforge.net/projects/gaim.