initial commit

git-svn-id: http://svn.miranda-ng.org/main/trunk@2 1316c22d-e87f-b044-9b9b-93d7a3e3ba9c

8 files changed, 918 insertions, 0 deletions

diff --git a/plugins/IEView/docs/chat.css b/plugins/IEView/docs/chat.css
new file mode 100644
index 0000000000..5741e47996
--- /dev/null
+++ b/plugins/IEView/docs/chat.css
@@ -0,0 +1,37 @@
+/* this changes the way main window background looks like */

+.body {margin: 0px; text-align: left; background-color: #E6E8E6; overflow: auto;}

+/* this changes the way your links look like */

+.link {color: #0000FF; text-decoration: underline;}

+/* this changes the way smileys and log icons look like */

+.img {vertical-align: middle;}

+/* this changes the way incoming (received) events look like including timestamp, name, etc. */

+.divIn {padding-left: 2px; padding-right: 2px; word-wrap: break-word; background-color: #E6E8E6;}

+/* this changes the way outgoing (sent) events look like including timestamp, name, etc. */

+.divOut {padding-left: 2px; padding-right: 2px; word-wrap: break-word; background-color: #E6E8E6;}

+.divUserJoined {padding-left: 2px; padding-right: 2px; word-wrap: break-word; background-color: #E6E8E6;}

+.divUserLeft {padding-left: 2px; padding-right: 2px; word-wrap: break-word; background-color: #E6E8E6;}

+.divUserKicked {padding-left: 2px; padding-right: 2px; word-wrap: break-word; background-color: #E6E8E6;}

+.divUserDisconnected {padding-left: 2px; padding-right: 2px; word-wrap: break-word; background-color: #E6E8E6;}

+.divNickChange {padding-left: 2px; padding-right: 2px; word-wrap: break-word; background-color: #E6E8E6;}

+.divTopicChange {padding-left: 2px; padding-right: 2px; word-wrap: break-word; background-color: #E6E8E6;}

+.divNotice {padding-left: 2px; padding-right: 2px; word-wrap: break-word; background-color: #E6E8E6;}

+.divInformation {padding-left: 2px; padding-right: 2px; word-wrap: break-word; background-color: #E6E8E6;}

+.divError {padding-left: 2px; padding-right: 2px; word-wrap: break-word; background-color: #E6E8E6;}

+.timestamp {font-family: Verdana; font-size: 6pt; font-weight: bold; color: #000000;  }

+.nameIn {font-family: Verdana; font-size: 10pt; font-weight: normal; color: #323772;  }

+.nameOut {font-family: Verdana; font-size: 10pt; font-weight: bold; color: #A45344;  }

+.messageIn {font-family: Verdana; font-size: 10pt; font-weight: normal; color: #000000;  }

+.messageOut {font-family: Verdana; font-size: 10pt; font-weight: normal; color: #805050; font-style: italic; }

+.userJoined {font-family: Verdana; font-size: 8pt; font-weight: normal; color: #0F880F; font-style: italic; }

+.userLeft {font-family: Verdana; font-size: 8pt; font-weight: normal; color: #B91313; font-style: italic; }

+.userDisconnected {font-family: Verdana; font-size: 8pt; font-weight: normal; color: #0F880F; font-style: italic; }

+.userKicked {font-family: Verdana; font-size: 8pt; font-weight: normal; color: #0F880F; font-style: italic; }

+.nickChange {font-family: Verdana; font-size: 8pt; font-weight: normal; color: #0F880F; font-style: italic; }

+.topicChange {font-family: Verdana; font-size: 10pt; font-weight: normal; color: #531A99; font-style: italic; }

+.notice {font-family: Verdana; font-size: 8pt; font-weight: normal; color: #0F880F; font-style: italic; }

+.information {font-family: Verdana; font-size: 8pt; font-weight: normal; color: #0F880F; font-style: italic; }

+.statusEnable {font-family: Verdana; font-size: 8pt; font-weight: normal; color: #0F880F; font-style: italic; }

+.statusDisable {font-family: Verdana; font-size: 8pt; font-weight: normal; color: #0F880F; font-style: italic; }

+.action {font-family: Verdana; font-size: 8pt; font-weight: normal; color: #0F880F; font-style: italic; }

+.highlight {font-family: Verdana; font-size: 8pt; font-weight: normal; color: #0F880F; font-style: italic; }

+.error {font-family: Verdana; font-size: 10pt; font-weight: bold; color: #D01010;  }

diff --git a/plugins/IEView/docs/ieview-license.txt b/plugins/IEView/docs/ieview-license.txt
new file mode 100644
index 0000000000..ca3fe8d547
--- /dev/null
+++ b/plugins/IEView/docs/ieview-license.txt
@@ -0,0 +1,340 @@
+                    GNU GENERAL PUBLIC LICENSE

+                       Version 2, June 1991

+

+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.

+                       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

+ Everyone is permitted to copy and distribute verbatim copies

+ of this license document, but changing it is not allowed.

+

+                            Preamble

+

+  The licenses for most software are designed to take away your

+freedom to share and change it.  By contrast, the GNU General Public

+License is intended to guarantee your freedom to share and change free

+software--to make sure the software is free for all its users.  This

+General Public License applies to most of the Free Software

+Foundation's software and to any other program whose authors commit to

+using it.  (Some other Free Software Foundation software is covered by

+the GNU Library General Public License instead.)  You can apply it to

+your programs, too.

+

+  When we speak of free software, we are referring to freedom, not

+price.  Our General Public Licenses are designed to make sure that you

+have the freedom to distribute copies of free software (and charge for

+this service if you wish), that you receive source code or can get it

+if you want it, that you can change the software or use pieces of it

+in new free programs; and that you know you can do these things.

+

+  To protect your rights, we need to make restrictions that forbid

+anyone to deny you these rights or to ask you to surrender the rights.

+These restrictions translate to certain responsibilities for you if you

+distribute copies of the software, or if you modify it.

+

+  For example, if you distribute copies of such a program, whether

+gratis or for a fee, you must give the recipients all the rights that

+you have.  You must make sure that they, too, receive or can get the

+source code.  And you must show them these terms so they know their

+rights.

+

+  We protect your rights with two steps: (1) copyright the software, and

+(2) offer you this license which gives you legal permission to copy,

+distribute and/or modify the software.

+

+  Also, for each author's protection and ours, we want to make certain

+that everyone understands that there is no warranty for this free

+software.  If the software is modified by someone else and passed on, we

+want its recipients to know that what they have is not the original, so

+that any problems introduced by others will not reflect on the original

+authors' reputations.

+

+  Finally, any free program is threatened constantly by software

+patents.  We wish to avoid the danger that redistributors of a free

+program will individually obtain patent licenses, in effect making the

+program proprietary.  To prevent this, we have made it clear that any

+patent must be licensed for everyone's free use or not licensed at all.

+

+  The precise terms and conditions for copying, distribution and

+modification follow.

+

+                    GNU GENERAL PUBLIC LICENSE

+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

+

+  0. This License applies to any program or other work which contains

+a notice placed by the copyright holder saying it may be distributed

+under the terms of this General Public License.  The "Program", below,

+refers to any such program or work, and a "work based on the Program"

+means either the Program or any derivative work under copyright law:

+that is to say, a work containing the Program or a portion of it,

+either verbatim or with modifications and/or translated into another

+language.  (Hereinafter, translation is included without limitation in

+the term "modification".)  Each licensee is addressed as "you".

+

+Activities other than copying, distribution and modification are not

+covered by this License; they are outside its scope.  The act of

+running the Program is not restricted, and the output from the Program

+is covered only if its contents constitute a work based on the

+Program (independent of having been made by running the Program).

+Whether that is true depends on what the Program does.

+

+  1. You may copy and distribute verbatim copies of the Program's

+source code as you receive it, in any medium, provided that you

+conspicuously and appropriately publish on each copy an appropriate

+copyright notice and disclaimer of warranty; keep intact all the

+notices that refer to this License and to the absence of any warranty;

+and give any other recipients of the Program a copy of this License

+along with the Program.

+

+You may charge a fee for the physical act of transferring a copy, and

+you may at your option offer warranty protection in exchange for a fee.

+

+  2. You may modify your copy or copies of the Program or any portion

+of it, thus forming a work based on the Program, and copy and

+distribute such modifications or work under the terms of Section 1

+above, provided that you also meet all of these conditions:

+

+    a) You must cause the modified files to carry prominent notices

+    stating that you changed the files and the date of any change.

+

+    b) You must cause any work that you distribute or publish, that in

+    whole or in part contains or is derived from the Program or any

+    part thereof, to be licensed as a whole at no charge to all third

+    parties under the terms of this License.

+

+    c) If the modified program normally reads commands interactively

+    when run, you must cause it, when started running for such

+    interactive use in the most ordinary way, to print or display an

+    announcement including an appropriate copyright notice and a

+    notice that there is no warranty (or else, saying that you provide

+    a warranty) and that users may redistribute the program under

+    these conditions, and telling the user how to view a copy of this

+    License.  (Exception: if the Program itself is interactive but

+    does not normally print such an announcement, your work based on

+    the Program is not required to print an announcement.)

+

+These requirements apply to the modified work as a whole.  If

+identifiable sections of that work are not derived from the Program,

+and can be reasonably considered independent and separate works in

+themselves, then this License, and its terms, do not apply to those

+sections when you distribute them as separate works.  But when you

+distribute the same sections as part of a whole which is a work based

+on the Program, the distribution of the whole must be on the terms of

+this License, whose permissions for other licensees extend to the

+entire whole, and thus to each and every part regardless of who wrote it.

+

+Thus, it is not the intent of this section to claim rights or contest

+your rights to work written entirely by you; rather, the intent is to

+exercise the right to control the distribution of derivative or

+collective works based on the Program.

+

+In addition, mere aggregation of another work not based on the Program

+with the Program (or with a work based on the Program) on a volume of

+a storage or distribution medium does not bring the other work under

+the scope of this License.

+

+  3. You may copy and distribute the Program (or a work based on it,

+under Section 2) in object code or executable form under the terms of

+Sections 1 and 2 above provided that you also do one of the following:

+

+    a) Accompany it with the complete corresponding machine-readable

+    source code, which must be distributed under the terms of Sections

+    1 and 2 above on a medium customarily used for software interchange; or,

+

+    b) Accompany it with a written offer, valid for at least three

+    years, to give any third party, for a charge no more than your

+    cost of physically performing source distribution, a complete

+    machine-readable copy of the corresponding source code, to be

+    distributed under the terms of Sections 1 and 2 above on a medium

+    customarily used for software interchange; or,

+

+    c) Accompany it with the information you received as to the offer

+    to distribute corresponding source code.  (This alternative is

+    allowed only for noncommercial distribution and only if you

+    received the program in object code or executable form with such

+    an offer, in accord with Subsection b above.)

+

+The source code for a work means the preferred form of the work for

+making modifications to it.  For an executable work, complete source

+code means all the source code for all modules it contains, plus any

+associated interface definition files, plus the scripts used to

+control compilation and installation of the executable.  However, as a

+special exception, the source code distributed need not include

+anything that is normally distributed (in either source or binary

+form) with the major components (compiler, kernel, and so on) of the

+operating system on which the executable runs, unless that component

+itself accompanies the executable.

+

+If distribution of executable or object code is made by offering

+access to copy from a designated place, then offering equivalent

+access to copy the source code from the same place counts as

+distribution of the source code, even though third parties are not

+compelled to copy the source along with the object code.

+

+  4. You may not copy, modify, sublicense, or distribute the Program

+except as expressly provided under this License.  Any attempt

+otherwise to copy, modify, sublicense or distribute the Program is

+void, and will automatically terminate your rights under this License.

+However, parties who have received copies, or rights, from you under

+this License will not have their licenses terminated so long as such

+parties remain in full compliance.

+

+  5. You are not required to accept this License, since you have not

+signed it.  However, nothing else grants you permission to modify or

+distribute the Program or its derivative works.  These actions are

+prohibited by law if you do not accept this License.  Therefore, by

+modifying or distributing the Program (or any work based on the

+Program), you indicate your acceptance of this License to do so, and

+all its terms and conditions for copying, distributing or modifying

+the Program or works based on it.

+

+  6. Each time you redistribute the Program (or any work based on the

+Program), the recipient automatically receives a license from the

+original licensor to copy, distribute or modify the Program subject to

+these terms and conditions.  You may not impose any further

+restrictions on the recipients' exercise of the rights granted herein.

+You are not responsible for enforcing compliance by third parties to

+this License.

+

+  7. If, as a consequence of a court judgment or allegation of patent

+infringement or for any other reason (not limited to patent issues),

+conditions are imposed on you (whether by court order, agreement or

+otherwise) that contradict the conditions of this License, they do not

+excuse you from the conditions of this License.  If you cannot

+distribute so as to satisfy simultaneously your obligations under this

+License and any other pertinent obligations, then as a consequence you

+may not distribute the Program at all.  For example, if a patent

+license would not permit royalty-free redistribution of the Program by

+all those who receive copies directly or indirectly through you, then

+the only way you could satisfy both it and this License would be to

+refrain entirely from distribution of the Program.

+

+If any portion of this section is held invalid or unenforceable under

+any particular circumstance, the balance of the section is intended to

+apply and the section as a whole is intended to apply in other

+circumstances.

+

+It is not the purpose of this section to induce you to infringe any

+patents or other property right claims or to contest validity of any

+such claims; this section has the sole purpose of protecting the

+integrity of the free software distribution system, which is

+implemented by public license practices.  Many people have made

+generous contributions to the wide range of software distributed

+through that system in reliance on consistent application of that

+system; it is up to the author/donor to decide if he or she is willing

+to distribute software through any other system and a licensee cannot

+impose that choice.

+

+This section is intended to make thoroughly clear what is believed to

+be a consequence of the rest of this License.

+

+  8. If the distribution and/or use of the Program is restricted in

+certain countries either by patents or by copyrighted interfaces, the

+original copyright holder who places the Program under this License

+may add an explicit geographical distribution limitation excluding

+those countries, so that distribution is permitted only in or among

+countries not thus excluded.  In such case, this License incorporates

+the limitation as if written in the body of this License.

+

+  9. The Free Software Foundation may publish revised and/or new versions

+of the General Public License from time to time.  Such new versions will

+be similar in spirit to the present version, but may differ in detail to

+address new problems or concerns.

+

+Each version is given a distinguishing version number.  If the Program

+specifies a version number of this License which applies to it and "any

+later version", you have the option of following the terms and conditions

+either of that version or of any later version published by the Free

+Software Foundation.  If the Program does not specify a version number of

+this License, you may choose any version ever published by the Free Software

+Foundation.

+

+  10. If you wish to incorporate parts of the Program into other free

+programs whose distribution conditions are different, write to the author

+to ask for permission.  For software which is copyrighted by the Free

+Software Foundation, write to the Free Software Foundation; we sometimes

+make exceptions for this.  Our decision will be guided by the two goals

+of preserving the free status of all derivatives of our free software and

+of promoting the sharing and reuse of software generally.

+

+                            NO WARRANTY

+

+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY

+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN

+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES

+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED

+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS

+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE

+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,

+REPAIR OR CORRECTION.

+

+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING

+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR

+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,

+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING

+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED

+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY

+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER

+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE

+POSSIBILITY OF SUCH DAMAGES.

+

+                     END OF TERMS AND CONDITIONS

+

+            How to Apply These Terms to Your New Programs

+

+  If you develop a new program, and you want it to be of the greatest

+possible use to the public, the best way to achieve this is to make it

+free software which everyone can redistribute and change under these terms.

+

+  To do so, attach the following notices to the program.  It is safest

+to attach them to the start of each source file to most effectively

+convey the exclusion of warranty; and each file should have at least

+the "copyright" line and a pointer to where the full notice is found.

+

+    <one line to give the program's name and a brief idea of what it does.>

+    Copyright (C) 19yy  <name of author>

+

+    This program is free software; you can redistribute it and/or modify

+    it under the terms of the GNU General Public License as published by

+    the Free Software Foundation; either version 2 of the License, or

+    (at your option) any later version.

+

+    This program is distributed in the hope that it will be useful,

+    but WITHOUT ANY WARRANTY; without even the implied warranty of

+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the

+    GNU General Public License for more details.

+

+    You should have received a copy of the GNU General Public License

+    along with this program; if not, write to the Free Software

+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

+

+

+Also add information on how to contact you by electronic and paper mail.

+

+If the program is interactive, make it output a short notice like this

+when it starts in an interactive mode:

+

+    Gnomovision version 69, Copyright (C) 19yy name of author

+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.

+    This is free software, and you are welcome to redistribute it

+    under certain conditions; type `show c' for details.

+

+The hypothetical commands `show w' and `show c' should show the appropriate

+parts of the General Public License.  Of course, the commands you use may

+be called something other than `show w' and `show c'; they could even be

+mouse-clicks or menu items--whatever suits your program.

+

+You should also get your employer (if you work as a programmer) or your

+school, if any, to sign a "copyright disclaimer" for the program, if

+necessary.  Here is a sample; alter the names:

+

+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program

+  `Gnomovision' (which makes passes at compilers) written by James Hacker.

+

+  <signature of Ty Coon>, 1 April 1989

+  Ty Coon, President of Vice

+

+This General Public License does not permit incorporating your program into

+proprietary programs.  If your program is a subroutine library, you may

+consider it more useful to permit linking proprietary applications with the

+library.  If this is what you want to do, use the GNU Library General

+Public License instead of this License.

diff --git a/plugins/IEView/docs/ieview-readme.txt b/plugins/IEView/docs/ieview-readme.txt
new file mode 100644
index 0000000000..a51893239e
--- /dev/null
+++ b/plugins/IEView/docs/ieview-readme.txt
@@ -0,0 +1,263 @@
+IEView user's manual & FAQ v1.0

+-------------------------------

+

+1. Overview

+-----------

+

+IEView is a replacement for RichEdit-based log window available in SRMM

+or TabSRMM. It cannot be used as a standalone plugin. It provides new features

+not achievable with RichEdit like:

+- animated emoticons,

+- background images,

+- customization of log appearance with CSS files,

+- look of log window may be built from scratch with HTML templates

+

+IEView works in 3 modes:

+

+A) compatibility mode (either Scriver or TabSRMM)

+It tries to mimic original look of Scriver or TabSRMM, but in addition

+animated emoticons and wallpapers are available. Text formatting and

+other options are taken directly from Scriver or TabSRMM settings.

+Some of TabSRMM features are not supported, for example text indentation.

+Both HTML and CSS styles are automatically generated by IEView.

+

+B) compatibility mode with external CSS

+

+IEView follows SRMM or TabSRMM log formatting settings, but you can change more than

+just colours, because an external, manually adjusted CSS file is used along with computer

+generated HTML code. More information on CSS classes used by IEView are available in included

+CSS examples.

+

+C) template-based mode

+

+IEView does not generate either CSS or HTML, but it uses HTML templates provided

+by the user instead. You can use several variable in templates including message text, date,

+nicknames etc. This part of IEView is still changing, so more information on templates is

+included in a separate file called templates_info.txt.

+

+2. Installation

+---------------

+

+To install IEView please copy ieview.dll and ieview folder into your

+Miranda's plugins directory. Ohter folders included in the pack are as

+follows:

+css        - examples of CSS files for tabsrmm, scriver and srmm

+docs	   - information about templates, translations etc.

+

+In order to use IEView you need Scriver or TabSRMM. Scriver project page is located here:

+http://developer.berlios.de/projects/mgoodies. Scriver v2.2.2.9 or later is recommended.

+If IEVIew is among avtive plugins it will be automatically used by Scriver for message log rendering,

+otherwise regular RichEdit control is used.

+

+In order to use IEView with TabSRMM you need at least TabSRMM 0.9.9.96. Moreover it is necessary

+to turn on support for IEView in TabSRMM configuration.

+Please go to Window Sessions -> Message Window -> Message log options page, locate and

+check "Activate support for external".

+

+3. Configuration

+----------------

+

+Wallpaper - select any image format supported by Internet Explorer (JPG, GIF etc.)

+

+4. FAQ

+------

+Q: Where can I find new versions of IEView, report bugs or request new features ?

+A: http://developer.berlios.de/projects/mgoodies.

+

+Q: Is SmileyAdd required in order to use animated emoticons ?

+A: SmileyAdd is NOT required to see animated emoticons in the log, however,

+   IEView does not provide any button for smiley selection, so no SmileyAdd means no such button.

+

+Q: Does IEView support Unicode ?

+A: Yes, it does.

+

+Q: Does IEView support RTL ?

+A: Yes, it does.

+

+Q: What version of Miranda is required to run IEView ?

+A: IEView DOES require Miranda IM 0.4.

+   It may work with older releases, but there is no guarantee !

+

+Q: I use TabSRMM, why IEView does not work ?

+A: Make sure Window Sessions -> Message Window -> Message log -> Activate support of external log

+   is turned on.

+

+5. Known Issues

+---------------

+

+A) Unicode

+Unicode support in Miranda is rather poor. IEView tries to determin if a message contains Unicode part or not,

+but this may fail sometimes and you will need to switch Unicode off in such cases. There is a possibility to turn

+Unicode off manually in Scriver.

+

+B) Avatars

+Unfortunately each Miranda plugin tends to store avatars in a different way. I am not going to add support

+for all of these possibilities to IEView, because I believe there should be only one standard. As a result

+IEView ALWAYS takes avatars stored in ContactPhoto/File DB entry. TabSRMM, Scriver and mToolTip use this field

+properly and I think authors of other plugins should consider changing their programs in order to use it.

+Alternatively, you may install AvatarService plugin and IEView will automatically detect and use AvatarService.

+

+6. Change Log

+-------------

+1.1.0.0

++ initial support for group chats (compatibility mode)

++ new BBCode - [code]

+* improvements in SmileAdd support

+* improved URL detection

+* improved Jabber chat states handling (patch by Andrey Balaguta)

+* fix for random crash (buffer overflow)

+1.0.9.10

+* support for UTF-8 encoded messages (required by Miranda 0.7 build #30)

+* critical changes in RTL templates (existing template files should be modified and they SHOULD provide HTMLStartRTL, MessageInRTL and MessageOutRTL templates to be recognized as RTL-compliant in the future IEView releases, 

+whole layout (including heading - HTMLStartRTL) will change when switching between LTR and RTL contacts, some changes in both TabSRMM and Scriver will be provided in Miranda 0.7 build #31 to improve RTL support in IEView as well)

+* RTL/Grouping info icons

+* removed some redundant reqources

+* other bugfixes

+1.0.9.9

+* bugfixes: TabSRMM compatibility mode, crash on file transfer

+1.0.9.8

+* a lot of bugfixes

+1.0.9.7

+* workaround for Win2k + IE6

+1.0.9.6

+* workaround for IE7 RC1 security issues

+* better support for flash avatars

+* some fixes related to RTL support

+1.0.9.5

++ web browser functionality exposed to other plugins

++ experimental support for Flash avatars

+* RTL support completely changed (see example css and template files)

+* bugfix: #007914 (wrong CP conversion)

+1.0.9.4

++ option to hide window border

+* bugfix: duplicate messages when incorrect smiley pack is used

+1.0.9.3

+* bugfixes: characters allowed in bbcode arguments, incorrect nick name, smiley replacement

+* improved compatibility with Mozilla ActiveX conrol

+1.0.9.2

+* bugfixes

+1.0.9.1

++ [url] bbcode

+* bugfixes

+1.0.9.0

++ flexible, per-protocol settings

++ support for Avatar Service

++ option to replace smileys in nick names

++ support for IEView-based history plugins

+* smileys will not be replaced with "red X" when incompatible emoticon set is used

+* a lot of bugfixes including endless loop when focus was lost

+1.0.5.2

+* bugfix: [bimg]

+1.0.5.1

++ new API for direct event logging (no need to store events in the DB)

++ on-the-fly switching between template and regular mode

++ [bimg] BBCode for showing images with relative paths

+* fixed bug #005790 (Unknown Contact displayed instead of user's id)

+- removed some obsolete options

+1.0.5.0

+- Removed internal support for emoticons (SmileyAdd v0.1.10.1 or higher is now required)

++ option to turn on/off workaround for PNG transparency

++ new BBCode: [s] (strikethrough)

+* workaround for weird bug in _vswnprintf()

+1.0.4.0

++ ME_IEVIEW_OPTIONSCHANGED event

+* improved compatibility with Scriver

+* bugfixes: metacontacts' nicknames, GUI fixes

+1.0.3.9

++ support for Unicode nick names

++ support for png emoticons (thanks to Alex Krivospitsky !)

++ support for drag&drop file transfer

++ possibility to choose smiley selector background color

++ new divUserJoined, divUserLeft, divUserKicked etc. styles (see chat.css)

++ translation file by Raq

+* bugfixes

+1.0.3.8

++ nickOut variable and improved compatibility with metacontacts (patch by Tweety)

++ SHIFT+click opens links and closes message window at the same time

++ option to print log in context menu

++ new smiley configuration page

+* fixed handling of URLs in links

+* fixed some other minor bugs

+1.0.3.7

+* some links were not handled properly

+* fixed Updater compatibility

+1.0.3.6

+* fixed compatibility with TabSRMM

+* bugfix: memory leaks

+1.0.3.5

++ new templates: fileIn, fileOut, hFileIn, hFileOut, URLIn, URLOut, hURLIn, hURLOut

++ new variables: %statusMsg%, %nickIn%, %fileDesc%

++ escaped variables: %\name% %\text% etc.

+* midnight-split message grouping

+* improved Scriver compatibility

+* bugfixes: swf support, memory leaks

+1.0.3.4

++ smileys are now properly copied/quoted (patch by Tweety and Vasilich)

++ uin, uinIn and uinOut variables

+* respective real protocol smileys are used for metacontacts

+* bugfix: message grouping

+* fixed %base% variable encoding

+1.0.3.3

++ support for MathModule (requires MathModule.dll v0.3.1.5 or later)

++ support for Macromedia Flash (.swf) files in smileys and [img] BBCode

++ closing messaging window with ESC key

+* proper handling of "unevenly" aligned BBCodes

+* fixed message grouping

+1.0.3.3

++ support for MathModule (requires MathModule.dll v0.3.1.5 or later)

++ support for Macromedia Flash (.swf) files in smileys and [img] BBCode

++ closing messaging window with ESC key

+* proper handling of "unevenly" aligned BBCodes

+* fixed message grouping

+1.0.3.2

++ support for external CSS files in Tlen group chats

+* rearranged option pages

+* some memory usage optimizations

+1.0.3.1

++ saving images (Save Image As... in context menu)

++ option to replace smileys in user names

+* scrollbar in smiley selection window is visible only when needed

+* fixed encoding of avatar filenames

+* bugfixes in BBCodes support

+1.0.3.0

++ support for (nested) BBCodes ! currently supported: [b][i][u][img][size][color]

++ support for Tlen group chats (requires mucc.dll v1.0.6.2 or higher)

+  support for chat.dll coming soon !

+* bugfixes & improvements

+1.0.2.2

++ internal change: support for getting selected text

++ internal change: support for code page selection

+* better links detection

+* bugfixes

+1.0.2.1

++ support for %%''%% in .asl files

+* fixed UTF8 encoding of date and time

+* other bugfixes

+1.0.2.0

+* improved Unicode support

+* bugfixes

+1.0.1.10

++ Unicode support (I would like to thank Nightwish for his support)

++ RTL support (template and CSS mode)

++ new variables: %avatarIn%, %avatarOut%, %nameIn%, %nameOut%, %proto% (please see ieview-templates.txt for details)

++ auto-scrolling to left

+* bugfixes: memory leaks, focus stealing, message grouping (Nightwish, thanks again) and a lot of other bugfixes

+1.0.1.7

++ animated smileys selection window

+  This feature is not fully available yet, because it requires also changes in TabSRMM source code and

+  you can use it in rather experimental mode at the moment. In order to do that you have to remove

+  SmileyAdd plugin and check "Replace SmileyAdd" on IEVIew->Emoticons options page.

+  Hopefully Nightwish will add support for new IEView smiley selection to TabSRMM soon.

+  Moreover, there is a new setting value available in .asl files. It is called SelectionSize and all

+  authors of .asl files are encouraged to use it in order to finetune the appearance of smileys selection

+  window. Please find more details in emots.asl file included in this package.

+* bugfixes in order to remove crashes and memory leaks in IEView (Nightwish, THX :)

+* better handling of http:// paths to CSS and background image

+* backslashes in URLs are converted to (javascript-friendly) slashes

++ 2 new variables: %avatar% and %cid%

+  %avatar% - link to an avatar file  (JPG, GIF etc.), if the file does not exist %avatar% will contain

+  value of %base%/noavatar.jpg.

+  %cid% - contact id, not available in HTMLStart template yet

+

+

+

diff --git a/plugins/IEView/docs/ieview-templates.txt b/plugins/IEView/docs/ieview-templates.txt
new file mode 100644
index 0000000000..e17303a900
--- /dev/null
+++ b/plugins/IEView/docs/ieview-templates.txt
@@ -0,0 +1,92 @@
+Each template begins with template name, which is a special kind of HTML comment, for instance:

+<!--HTMLStart-->

+or

+<!--MessageIn-->

+A template ends whenever a new template begins or EOF is reached.

+

+The following templates may be defined:

+

+<!--HTMLStart-->

+<!--MessageIn-->

+<!--hMessageIn-->

+<!--MessageOut-->

+<!--hMessageOut-->

+<!--File-->

+<!--hFile-->

+<!--URL-->

+<!--hURL-->

+<!--Status-->

+<!--hStatus-->

+<!--MessageInGroupStart-->

+<!--MessageInGroupInner-->

+<!--MessageInGroupEnd-->

+<!--hMessageInGroupStart-->

+<!--hMessageInGroupInner-->

+<!--hMessageInGroupEnd-->

+<!--MessageOutGroupStart-->

+<!--MessageOutGroupInner-->

+<!--MessageOutGroupEnd-->

+<!--hMessageOutGroupStart-->

+<!--hMessageOutGroupInner-->

+<!--hMessageOutGroupEnd-->

+

+<!--HTMLStartRTL-->

+<!--MessageInRTL-->

+<!--hMessageInRTL-->

+<!--MessageOutRTL-->

+<!--hMessageOutRTL-->

+<!--MessageInGroupStartRTL-->

+<!--MessageInGroupInnerRTL-->

+<!--MessageInGroupEndRTL-->

+<!--hMessageInGroupStartRTL-->

+<!--hMessageInGroupInnerRTL-->

+<!--hMessageInGroupEndRTL-->

+<!--MessageOutGroupStartRTL-->

+<!--MessageOutGroupInnerRTL-->

+<!--MessageOutGroupEndRTL-->

+<!--hMessageOutGroupStartRTL-->

+<!--hMessageOutGroupInnerRTL-->

+<!--hMessageOutGroupEndRTL-->

+

+

+All templates of which names begin with 'h' are used to display historical events.

+

+If a template is not present the corresponding event will not be shown in the log at all !

+

+The following variables are available in all templates EXCEPT HTMLStart:

+%base%  - base URL

+%name%  - contact's name or user's name (depends on context)

+%time%  - event's time

+%date%  - event's date

+%text%  - event's text

+%cid%  - contact's ID or user's ID (depends on context)

+%avatar% - link to contact's picture file or user's picure file (depends on context)

+%avatarIn% - link to contact's picture

+%avatarOut% - link to user's picture

+%nameIn% - contact's name

+%nameOut% - users's name

+%proto% - protocol name

+%uin% - contact's ID or user's ID

+%uinIn% - contact's ID

+%uinOut% - user's ID

+%nick% - contact's nick name or user's nick name

+%nickIn% - contact's nick name

+%nickOut% - user's nick name

+%statusMsg% - contact's status message

+%fileDesc% - file description

+

+The following variables are available in HTMLStart:

+%base%  - base URL (this variable should be used in <base> tag)

+%avatarIn% - link to contact's picture

+%avatarOut% - link to user's picture

+%nameIn% - contact's name

+%nameOut% - users's name

+%nickIn% - contact's nick name

+%nickOut% - user's nick name

+%uinIn% - contact's ID

+%uinOut% - user's ID

+%proto% - protocol name

+

+All tokens are also available in Javascript friendly (escaped) form. 

+In that case please use the follwoing token names: %\base%, %\time%, %\name% etc.

+

diff --git a/plugins/IEView/docs/ieview-translation.txt b/plugins/IEView/docs/ieview-translation.txt
new file mode 100644
index 0000000000..51f89bcde0
--- /dev/null
+++ b/plugins/IEView/docs/ieview-translation.txt
@@ -0,0 +1,38 @@
+;****************************

+;*** IEView Plugin [1.0.3.5]

+; Author: raq <braq@wp.pl>

+;****************************

+

+[IEView plugin]

+[General]

+[Options]

+[Enable BBCodes]

+[Currently the following BBCodes are supported: [b][i][u][img][size][color]]

+[Enable support for Flash files in smileys and BBCodes]

+[Enable MathModule support]

+[Message Log]

+[Mode]

+[Background image]

+[Scroll with text]

+[External CSS file]

+[Templates]

+[Events To Show]

+[Show file events]

+[Show url events]

+[Show status changes]

+[Log Options]

+[Show nicknames]

+[Show time]

+[Show seconds]

+[Show date]

+[Use long date format]

+[Use relative timestamp]

+[Use message grouping]

+[Emotikons]

+[Animated Smiley Libraries]

+[Enable smiley replacement]

+[Specify library for each protocol]

+[Only replace isolated smileys]

+[Surround smileys with spaces]

+[Replace smileys in user names]

+[Group Chats]

diff --git a/plugins/IEView/docs/scriver.css b/plugins/IEView/docs/scriver.css
new file mode 100644
index 0000000000..79ae91886d
--- /dev/null
+++ b/plugins/IEView/docs/scriver.css
@@ -0,0 +1,51 @@
+/* this changes the way main window background looks like */

+.body {margin-left: 0px; margin-right: 0px; margin-top: 0px; margin-bottom: 0px; text-align: left; background-attachment: scroll; background-color: #FFFFFF;  background-image: url(D:\mim\mim_bkg.jpg); overflow: auto;}

+/* this changes the way your links look like */

+.link {color: #0000FF; text-decoration: underline;}

+/* this changes the way smileys and log icons look like */

+.img {vertical-align: middle;}

+/* this changes the way incoming (received) events look like including timestamp, name, etc. */

+.divIn {word-wrap: break-word; background-color: #FFFFFF;}

+/* this changes the way outgoing (sent) events look like including timestamp, name, etc. */

+.divOut {word-wrap: break-word; background-color: #FFFFFF;}

+/* this changes the way incoming (received) events look like including timestamp, name, etc. */

+.divInGrid {padding-left: 2px; padding-right: 2px; word-wrap: break-word; border-top: 1px solid #000000; background-color: #FFFFFF;}

+/* this changes the way outgoing (sent) events look like including timestamp, name, etc. */

+.divOutGrid {padding-left: 2px; padding-right: 2px; word-wrap: break-word; border-top: 1px solid #000000; background-color: #FFFFFF;}

+/* this changes the way incoming (received) events look like including timestamp, name, etc. */

+.divNotice {padding-left: 2px; padding-right: 2px; word-wrap: break-word;}

+/* this changes the way outgoing (sent) events look like including timestamp, name, etc. */

+.divNoticeGrid {padding-left: 2px; padding-right: 2px; word-wrap: break-word; border-top: 1px solid #000000}

+/* this changes the way outgoing (sent by you) messages look like */

+.messageOut {font-family: Arial; font-size: 12pt; font-weight: 900; color: #6A6A6A; }

+/* this changes the way incoming (received from your contact) messages look like */

+.messageIn {font-family: Arial; font-size: 12pt; font-weight: 300; color: #000000; font-style: italic}

+/* this changes the way your name looks like in outgoing events */

+.nameOut {font-family: Arial; font-size: 12pt; font-weight: 900; color: #5369C1; }

+/* this changes the way timestamp looks like in outgoing events */

+.timeOut {font-family: Terminal; font-size: 9pt; font-weight: 900; color: #74B928; }

+/* this changes the way a colon looks like in outgoing events */

+.colonOut {font-family: Arial; font-size: 11pt; font-weight: 900; color: #56C099; }

+/* this changes the way a contact's name looks like in incoming events */

+.nameIn {font-family: Arial; font-size: 12pt; font-weight: 900; color: #D70000; }

+/* this changes the way timestamp looks like in incoming events */

+.timeIn {font-family: Terminal; font-size: 9pt; font-weight: 900; color: #000000; }

+/* this changes the way a colon looks like in incoming events */

+.colonIn {font-family: Arial; font-size: 11pt; font-weight: 900; color: #B96A8D; font-style: italic}

+/* NOT USED */

+.inputArea {font-family: Arial; font-size: 12pt; font-weight: 300; color: #000000; }

+/* this changes the way status change event look like */

+.notices {font-family: Arial; font-size: 12pt; font-weight: 300; color: #5A5AA0; }

+/* RTL-related styles */

+/* this changes the way incoming (received) events look like including timestamp, name, etc. */

+.divInRTL {text-align: right; direction:RTL; unicode-bidi:embed; word-wrap: break-word; background-color: #FFFFFF;}

+/* this changes the way outgoing (sent) events look like including timestamp, name, etc. */

+.divOutRTL {text-align: right; direction:RTL; unicode-bidi:embed; word-wrap: break-word; background-color: #FFFFFF;}

+/* this changes the way incoming (received) events look like including timestamp, name, etc. */

+.divInGridRTL {text-align: right; direction:RTL; unicode-bidi:embed; padding-left: 2px; padding-right: 2px; word-wrap: break-word; border-top: 1px solid #000000; background-color: #FFFFFF;}

+/* this changes the way outgoing (sent) events look like including timestamp, name, etc. */

+.divOutGridRTL {text-align: right; direction:RTL; unicode-bidi:embed; padding-left: 2px; padding-right: 2px; word-wrap: break-word; border-top: 1px solid #000000; background-color: #FFFFFF;}

+/* this changes the way incoming (received) events look like including timestamp, name, etc. */

+.divNoticeRTL {text-align: right; direction:RTL; unicode-bidi:embed; padding-left: 2px; padding-right: 2px; word-wrap: break-word;}

+/* this changes the way outgoing (sent) events look like including timestamp, name, etc. */

+.divNoticeGridRTL {text-align: right; direction:RTL; unicode-bidi:embed; padding-left: 2px; padding-right: 2px; word-wrap: break-word; border-top: 1px solid #000000}

diff --git a/plugins/IEView/docs/srmm.css b/plugins/IEView/docs/srmm.css
new file mode 100644
index 0000000000..ad5fadeb49
--- /dev/null
+++ b/plugins/IEView/docs/srmm.css
@@ -0,0 +1,36 @@
+/* this changes the way main window background looks like */

+.body {margin-left: 0px; margin-right: 0px; margin-top: 0px; margin-bottom: 0px; text-align: left; background-attachment: scroll; background-color: #FFFFFF;  background-image: url(D:\mim\mim_bkg.jpg); overflow: auto;}

+/* this changes the way your links look like */

+.link {color: #0000FF; text-decoration: underline;}

+/* this changes the way smileys and log icons look like */

+.img {vertical-align: middle;}

+/* this changes the way incoming (received) events look like including timestamp, name, etc. */

+.divIn {word-wrap: break-word; background-color: #FFFFFF;}

+/* this changes the way outgoing (sent) events look like including timestamp, name, etc. */

+.divOut {word-wrap: break-word; background-color: #FFFFFF;}

+/* this changes the way outgoing (sent by you) messages look like */

+.messageOut {font-family: Arial; font-size: 12pt; font-weight: 900; color: #6A6A6A; }

+/* this changes the way incoming (received from your contact) messages look like */

+.messageIn {font-family: Arial; font-size: 12pt; font-weight: 300; color: #000000; font-style: italic}

+/* this changes the way your name looks like in outgoing events */

+.nameOut {font-family: Arial; font-size: 12pt; font-weight: 900; color: #5369C1; }

+/* this changes the way timestamp looks like in outgoing events */

+.timeOut {font-family: Terminal; font-size: 9pt; font-weight: 900; color: #74B928; }

+/* this changes the way a colon looks like in outgoing events */

+.colonOut {font-family: Arial; font-size: 11pt; font-weight: 900; color: #56C099; }

+/* this changes the way a contact's name looks like in incoming events */

+.nameIn {font-family: Arial; font-size: 12pt; font-weight: 900; color: #D70000; }

+/* this changes the way timestamp looks like in incoming events */

+.timeIn {font-family: Terminal; font-size: 9pt; font-weight: 900; color: #000000; }

+/* this changes the way a colon looks like in incoming events */

+.colonIn {font-family: Arial; font-size: 11pt; font-weight: 900; color: #B96A8D; font-style: italic}

+/* NOT USED */

+.inputArea {font-family: Arial; font-size: 12pt; font-weight: 300; color: #000000; }

+/* this changes the way status change event look like */

+.notices {font-family: Arial; font-size: 12pt; font-weight: 300; color: #5A5AA0; }

+

+/* RTL-related styles */

+/* this changes the way incoming (received) events look like including timestamp, name, etc. */

+.divInRTL {text-align: right; direction:RTL; unicode-bidi:embed; word-wrap: break-word; background-color: #FFFFFF;}

+/* this changes the way outgoing (sent) events look like including timestamp, name, etc. */

+.divOutRTL {text-align: right; direction:RTL; unicode-bidi:embed; word-wrap: break-word; background-color: #FFFFFF;}

diff --git a/plugins/IEView/docs/tabsrmm.css b/plugins/IEView/docs/tabsrmm.css
new file mode 100644
index 0000000000..2e3ed0d858
--- /dev/null
+++ b/plugins/IEView/docs/tabsrmm.css
@@ -0,0 +1,61 @@
+/* this changes the way main window background looks like */

+.body {margin-left: 0px; margin-right: 0px; margin-top: 0px; margin-bottom: 0px; text-align: left; background-color: #924AB0; overflow: auto;}

+/* this changes the way your links look like */

+.link {color: #0000FF; text-decoration: underline;}

+/* this changes the way smileys and log icons look like */

+.img {vertical-align: middle;}

+/* this changes the way incoming (received) events look like including timestamp, name, etc. */

+.divIn {word-wrap: break-word; background-color: #F0E399;}

+/* this changes the way outgoing (sent) events look like including timestamp, name, etc. */

+.divOut {word-wrap: break-word; background-color: #7DC6D2;}

+/* the same as divIn, but used when Draw grid lines option is turned on */

+.divInGrid {word-wrap: break-word; border-top: 1px solid #924AB0; background-color: #F0E399;}

+/* the same as divIn, but used when Draw grid lines option is turned on */

+.divOutGrid {word-wrap: break-word; border-top: 1px solid #924AB0; background-color: #7DC6D2;}

+/* this changes the way new outgoing (sent by you) messages look like */

+.messageOut {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #000000; }

+/* this changes the way outgoing (sent) file events and url events look like - NOT USED */

+.miscOut {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #C632D1; font-style: italic}

+/* this changes the way new incoming (received from your contact) messages look like */

+.messageIn {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #A81A3E; }

+/* this changes the way new incoming file events and url events look like */

+.miscIn {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #5581D2; font-style: italic}

+/* this changes the way your name looks like in new outgoing events */

+.nameOut {font-family: Tahoma; font-size: 13pt; font-weight: 900; color: #223CB3; }

+/* this changes the way a timestamp looks like in new outgoing events */

+.timeOut {font-family: Tahoma; font-size: 8pt; font-weight: 900; color: #808080; }

+/* this changes the way a contact's name looks like in new incoming events */

+.nameIn {font-family: Tahoma; font-size: 10pt; font-weight: 300; color: #000000; }

+/* this changes the way timestamp looks like in new incoming events */

+.timeIn {font-family: Tahoma; font-size: 8pt; font-weight: 900; color: #526F70; }

+/* this changes the way historical outgoing messages look like */

+.hMessageOut {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #000000; }

+/* this changes the way historical outgoing file events and url events look like - NOT USED */

+.hMiscOut {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #000000; }

+/* this changes the way historical incoming messages look like */

+.hMessageIn {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #000000; }

+/* this changes the way historical incoming file events and url events look like */

+.hMiscIn {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #3F65BE; font-style: italic}

+/* this changes the way your name looks like in historical events */

+.hNameOut {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #000000; }

+/* this changes the way a timestamp looks like in historical outgoing events */

+.hTimeOut {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #000000; }

+/* this changes the way a contact's name looks like in incoming events */

+.hNameIn {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #000000; }

+/* this changes the way a timestamp looks like in incoming events */

+.hTimeIn {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #A81A3E; }

+/* NOT USED */

+.inputArea {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #000000; }

+/* this changes the way status change events look like */

+.statusChange {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #000000; }

+/* NOT USED */

+.dividers {font-family: Tahoma; font-size: 13pt; font-weight: 300; color: #55B9B4; }

+/* RTL-related styles */

+/* this changes the way incoming (received) events look like including timestamp, name, etc. */

+.divInRTL {text-align: right; direction:RTL; unicode-bidi:embed; word-wrap: break-word; background-color: #FFFFFF;}

+/* this changes the way outgoing (sent) events look like including timestamp, name, etc. */

+.divOutRTL {text-align: right; direction:RTL; unicode-bidi:embed; word-wrap: break-word; background-color: #FFFFFF;}

+/* this changes the way incoming (received) events look like including timestamp, name, etc. */

+.divInGridRTL {text-align: right; direction:RTL; unicode-bidi:embed; padding-left: 2px; padding-right: 2px; word-wrap: break-word; border-top: 1px solid #000000; background-color: #FFFFFF;}

+/* this changes the way outgoing (sent) events look like including timestamp, name, etc. */

+.divOutGridRTL {text-align: right; direction:RTL; unicode-bidi:embed; padding-left: 2px; padding-right: 2px; word-wrap: break-word; border-top: 1px solid #000000; background-color: #FFFFFF;}