======================================================================== * runtime/spell/README.txt ======================================================================== The spell files included here are in Vim's special format. You can't edit them. See ":help spell" for more information. COPYRIGHT The files used as input for the spell files come from the OpenOffice.org spell files. Most of them go under the LGPL or a similar license. Copyright notices for specific languages are in README_??.txt. Note that the files for different regions are merged, both to save space and to make it possible to highlight words for another region different from bad words. Most of the soundslike mappings come from Aspell ??_phonet.dat files: ftp://ftp.gnu.org/gnu/aspell/dict/. Most go under the GPL or LGPL copyright. GENERATING .SPL FILES This involves downloading the files from the OpenOffice.org server, applying a patch and running Vim to generate the .spl file. To do this all in one go use the Aap program (www.a-a-p.org). It's simple to install, it only requires Python. Before generating spell files, verify your system has the required locale support. Source the check_locales.vim script to find out. If something is missing, see LOCALE below. You can also do it manually: 1. Fetch the right spell file from: http://ftp.services.openoffice.org/pub/OpenOffice.org/contrib/dictionaries 2. Unzip the archive: unzip LL_RR.zip 3. Apply the patch: patch < LL_RR.diff 4. If the language has multiple regions do the above for each region. E.g., for English there are five regions: US, CA, AU, NZ and GB. 5. Run Vim and execute ":mkspell". Make sure you do this with the correct locale, that influences the upper/lower case letters and word characters. On Unix it's something like: env LANG=en_US.UTF-8 vim mkspell! en en_US en_AU en_CA en_GB en_NZ 6. Repeat step 5 for other locales. For English you could generate a spell file for latin1, utf-8 and ASCII. ASCII only makes sense for languages that have very few words with non-ASCII letters. Now you understand why I prefer using the Aap recipe :-). MAINTAINING A LANGUAGE Every language should have a maintainer. His tasks are to track the changes in the OpenOffice.org spell files and make updated patches. Words that haven't been added/removed from the OpenOffice lists can also be handled by the patches. It is important to keep the version of the .dic and .aff files that you started with. When OpenOffice brings out new versions of these files you can find out what changed and take over these changes in your patch. When there are very many changes you can do it the other way around: re-apply the changes for Vim to the new versions of the .dic and .aff files. This procedure should work well: 1. Obtain the zip archive with the .aff and .dic files. Unpack it as explained above and copy (don't rename!) the .aff and .dic files to .orig.aff and .orig.dic. Using the Aap recipe should work, it will make the copies for you. 2. Tweak the .aff and .dic files to generate the perfect .spl file. Don't change too much, the OpenOffice people are not stupid. However, you may want to remove obvious mistakes. And remove single-letter words that aren't really words, they mess up the suggestions (English has this problem). You can use the "fixdup.vim" Vim script to find duplicate words. 3. Make the diff file. "aap diff" will do this for you. If a diff would be too big you might consider writing a Vim script to do systematic changes. Do check that someone else can reproduce building the spell file. Send the result to Bram for inclusion in the distribution. Bram will generate the .spl file and upload it to the ftp server (if he can't generate it you will have to send him the .spl file too). 4. When OpenOffice makes a new zip file available you need to update the patch. "aap check" should do most of the work for you: if there are changes the .new.dic and .new.aff files will appear. You can now figure out the differences with .orig.dic and .orig.aff, adjust the .dic and .aff files and finally move the .new.dic to .orig.dic and .new.aff to .orig.aff. 5. Repeat step 4. regularly. LOCALE For proper spell file generation the required locale must be installed. Otherwise Vim doesn't know what are letters and upper-lower case differences. Modern systems use UTF-8, but we also generate spell files for 8-bit locales for users with older systems. On Ubuntu the default is to only support locales for your own language. To add others you need to do this: sudo vim /var/lib/locales/supported.d/local Add needed lines from /usr/share/i18n/SUPPORTED sudo dpkg-reconfigure locales When using the check_locales.vim script, you need to exit Vim and restart it to pickup the newly installed locales. ======================================================================== * runtime/spell/README_en.txt ======================================================================== en_US 20040623 release. -- This dictionary is based on a subset of the original English wordlist created by Kevin Atkinson for Pspell and Aspell and thus is covered by his original LGPL license. The affix file is a heavily modified version of the original english.aff file which was released as part of Geoff Kuenning's Ispell and as such is covered by his BSD license. Thanks to both authors for there wonderful work. =================================================== en_AU: This dictionary was based on the en_GB Myspell dictionary which in turn was initially based on a subset of the original English wordlist created by Kevin Atkinson for Pspell and Aspell and thus is covered by his original LGPL licence. The credit for this en_AU dictionary goes to: Kelvin Eldridge (maintainer) Jean Hollis Weber David Wilson - Words incorrect in Australian English removed - a list from the previously removed words with corrected spelling was added - a list of major rivers was added - a list of place names was added - a list of Australian mammals was added - a list of Aboriginal/Koori words commonly used was added A total of 119,267 words are now recognized by the dictionary. Of course, special thanks go to the editors of the en_GB dictionary (David Bartlett, Brian Kelk and Andrew Brown) which provided the starting point for this dictionary. The affix file is currently a duplicate of the en_AU.aff created completely from scratch by David Bartlett and Andrew Brown, based on the published rules for MySpell and is also provided under the LGPL. If you find omissions or bugs or have new words to add to the dictionary, please contact the en_AU maintainer at: "Kelvin" =================================================== en_CA: The dictionary file was created using the "final" English and Canadian SCOWL (Spell Checker Oriented Word Lists) wordlists available at Kevin's Word Lists Page (http://wordlist.sourceforge.net). Lists with the suffixes 10, 20, 35, 50, 65 and 65 were used. Lists with the suffixes 70, 80 and 95 were excluded. Copyright information for SCOWL and the wordlists used in creating it is reproduced below. The affix file is identical to the MySpell English (United States) affix file. It is a heavily modified version of the original english.aff file which was released as part of Geoff Kuenning's Ispell and as such is covered by his BSD license. --- COPYRIGHT, SOURCES, and CREDITS from SCOWL readme file: The collective work is Copyright 2000 by Kevin Atkinson as well as any of the copyrights mentioned below: Copyright 2000 by Kevin Atkinson Permission to use, copy, modify, distribute and sell these word lists, the associated scripts, the output created from the scripts, and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Kevin Atkinson makes no representations about the suitability of this array for any purpose. It is provided "as is" without express or implied warranty. Alan Beale also deserves special credit as he has, in addition to providing the 12Dicts package and being a major contributor to the ENABLE word list, given me an incredible amount of feedback and created a number of special lists (those found in the Supplement) in order to help improve the overall quality of SCOWL. The 10 level includes the 1000 most common English words (according to the Moby (TM) Words II [MWords] package), a subset of the 1000 most common words on the Internet (again, according to Moby Words II), and frequently class 16 from Brian Kelk's "UK English Wordlist with Frequency Classification". The MWords package was explicitly placed in the public domain: The Moby lexicon project is complete and has been place into the public domain. Use, sell, rework, excerpt and use in any way on any platform. Placing this material on internal or public servers is also encouraged. The compiler is not aware of any export restrictions so freely distribute world-wide. You can verify the public domain status by contacting Grady Ward 3449 Martha Ct. Arcata, CA 95521-4884 grady@netcom.com grady@northcoast.com The "UK English Wordlist With Frequency Classification" is also in the Public Domain: Date: Sat, 08 Jul 2000 20:27:21 +0100 From: Brian Kelk > I was wondering what the copyright status of your "UK English > Wordlist With Frequency Classification" word list as it seems to > be lacking any copyright notice. There were many many sources in total, but any text marked "copyright" was avoided. Locally-written documentation was one source. An earlier version of the list resided in a filespace called PUBLIC on the University mainframe, because it was considered public domain. Date: Tue, 11 Jul 2000 19:31:34 +0100 > So are you saying your word list is also in the public domain? That is the intention. The 20 level includes frequency classes 7-15 from Brian's word list. The 35 level includes frequency classes 2-6 and words appearing in at least 11 of 12 dictionaries as indicated in the 12Dicts package. All words from the 12Dicts package have had likely inflections added via my inflection database. The 12Dicts package and Supplement is in the Public Domain. The WordNet database, which was used in the creation of the Inflections database, is under the following copyright: This software and database is being provided to you, the LICENSEE, by Princeton University under the following license. By obtaining, using and/or copying this software and database, you agree that you have read, understood, and will comply with these terms and conditions.: Permission to use, copy, modify and distribute this software and database and its documentation for any purpose and without fee or royalty is hereby granted, provided that you agree to comply with the following copyright notice and statements, including the disclaimer, and that the same appear on ALL copies of the software, database and documentation, including modifications that you make for internal use or for distribution. WordNet 1.6 Copyright 1997 by Princeton University. All rights reserved. THIS SOFTWARE AND DATABASE IS PROVIDED "AS IS" AND PRINCETON UNIVERSITY MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PRINCETON UNIVERSITY MAKES NO REPRESENTATIONS OR WARRANTIES OF MERCHANT- ABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE LICENSED SOFTWARE, DATABASE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. The name of Princeton University or Princeton may not be used in advertising or publicity pertaining to distribution of the software and/or database. Title to copyright in this software, database and any associated documentation shall at all times remain with Princeton University and LICENSEE agrees to preserve same. The 50 level includes Brian's frequency class 1, words appearing in at least 5 of 12 of the dictionaries as indicated in the 12Dicts package, and uppercase words in at least 4 of the previous 12 dictionaries. A decent number of proper names is also included: The top 1000 male, female, and Last names from the 1990 Census report; a list of names sent to me by Alan Beale; and a few names that I added myself. Finally a small list of abbreviations not commonly found in other word lists is included. The name files form the Census report is a government document which I don't think can be copyrighted. The name list from Alan Beale is also derived from the linux words list, which is derived from the DEC list. He also added a bunch of miscellaneous names to the list, which he released to the Public Domain. The DEC Word list doesn't have a formal name. It is labeled as "FILE: english.words; VERSION: DEC-SRC-92-04-05" and was put together by Jorge Stolfi DEC Systems Research Center. The DEC Word list has the following copyright statement: (NON-)COPYRIGHT STATUS To the best of my knowledge, all the files I used to build these wordlists were available for public distribution and use, at least for non-commercial purposes. I have confirmed this assumption with the authors of the lists, whenever they were known. Therefore, it is safe to assume that the wordlists in this package can also be freely copied, distributed, modified, and used for personal, educational, and research purposes. (Use of these files in commercial products may require written permission from DEC and/or the authors of the original lists.) Whenever you distribute any of these wordlists, please distribute also the accompanying README file. If you distribute a modified copy of one of these wordlists, please include the original README file with a note explaining your modifications. Your users will surely appreciate that. (NO-)WARRANTY DISCLAIMER These files, like the original wordlists on which they are based, are still very incomplete, uneven, and inconsistent, and probably contain many errors. They are offered "as is" without any warranty of correctness or fitness for any particular purpose. Neither I nor my employer can be held responsible for any losses or damages that may result from their use. However since this Word List is used in the linux.words package which the author claims is free of any copyright I assume it is OK to use for most purposes. If you want to use this in a commercial project and this concerns you the information from the DEC word list can easily be removed without much sacrifice in quality as only the name lists were used. The file special-jargon.50 uses common.lst and word.lst from the "Unofficial Jargon File Word Lists" which is derived from "The Jargon File". All of which is in the Public Domain. This file also contain a few extra UNIX terms which are found in the file "unix-terms" in the special/ directory. The 60 level includes Brian's frequency class 0 and all words appearing in at least 2 of the 12 dictionaries as indicated by the 12Dicts package. A large number of names are also included: The 4,946 female names and 3,897 male names from the MWords package and the files "computer.names", "misc.names", and "org.names" from the DEC package. The 65 level includes words found in the Ispell "medium" word list. The Ispell word lists are under the same copyright of Ispell itself which is: Copyright 1993, Geoff Kuenning, Granada Hills, CA All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All modifications to the source code must be clearly marked as such. Binary redistributions based on modified source code must be clearly marked as modified versions in the documentation and/or other materials provided with the distribution. 4. All advertising materials mentioning features or use of this software must display the following acknowledgment: This product includes software developed by Geoff Kuenning and other unpaid contributors. 5. The name of Geoff Kuenning may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY GEOFF KUENNING AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL GEOFF KUENNING OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The 70 level includes the 74,550 common dictionary words and the 21,986 names list from the MWords package. The common dictionary words, like those from the 12Dicts package, have had all likely inflections added. The 80 level includes the ENABLE word list, all the lists in the ENABLE supplement package (except for ABLE), the "UK Advanced Cryptics Dictionary" (UKACD), the list of signature words in from YAWL package, and the 10,196 places list from the MWords package. The ENABLE package, mainted by M\Cooper , is in the Public Domain: The ENABLE master word list, WORD.LST, is herewith formally released into the Public Domain. Anyone is free to use it or distribute it in any manner they see fit. No fee or registration is required for its use nor are "contributions" solicited (if you feel you absolutely must contribute something for your own peace of mind, the authors of the ENABLE list ask that you make a donation on their behalf to your favorite charity). This word list is our gift to the Scrabble community, as an alternate to "official" word lists. Game designers may feel free to incorporate the WORD.LST into their games. Please mention the source and credit us as originators of the list. Note that if you, as a game designer, use the WORD.LST in your product, you may still copyright and protect your product, but you may *not* legally copyright or in any way restrict redistribution of the WORD.LST portion of your product. This *may* under law restrict your rights to restrict your users' rights, but that is only fair. UKACD, by J Ross Beresford , is under the following copyright: Copyright (c) J Ross Beresford 1993-1999. All Rights Reserved. The following restriction is placed on the use of this publication: if The UK Advanced Cryptics Dictionary is used in a software package or redistributed in any form, the copyright notice must be prominently displayed and the text of this document must be included verbatim. There are no other restrictions: I would like to see the list distributed as widely as possible. The 95 level includes the 354,984 single words and 256,772 compound words from the MWords package, ABLE.LST from the ENABLE Supplement, and some additional words found in my part-of-speech database that were not found anywhere else. Accent information was taken from UKACD. My VARCON package was used to create the American, British, and Canadian word list. Since the original word lists used in the VARCON package came from the Ispell distribution they are under the Ispell copyright. The variant word lists were created from a list of variants found in the 12dicts supplement package as well as a list of variants I created myself. =================================================== en_GB: This dictionary was initially based on a subset of the original English wordlist created by Kevin Atkinson for Pspell and Aspell and thus is covered by his original LGPL licence. It has been extensively updated by David Bartlett, Brian Kelk and Andrew Brown: - numerous Americanism have been removed - numerous American spellings have been corrected - missing words have been added - many errors have been corrected - compound hyphenated words have been added where appropriate Valuable inputs to this process were received from many other people - far too numerous to name. Serious thanks to you all for your greatly appreciated help. This word list is intended to be a good representation of current modern British English and thus it should be a good basis for Commonwealth English in most countries of the world outside North America. The affix file has been created completely from scratch by David Bartlett and Andrew Brown, based on the published rules for MySpell and is also provided under the LGPL. In creating the affix rules an attempt has been made to reproduce the most general rules for English word formation, rather than merely use it as a means to compress the size of the dictionary. It is hoped that this will facilitate future localisation to other variants of English. Please let David Bartlett know of any errors that you find. The current release is R 1.18, 11/04/05 =================================================== en_NZ: I. Copyright II. Copying (Licence) ---------------------------- I. Copyright NZ English Dictionary v0.9 beta - Build 06SEP03 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NB This is an initial version, please check: http://lingucomponent.openoffice.org/download_dictionary.html or http://www.girlza.com/dictionary/download.html for a final version, after a little while (no hurry). This dictionary is based on the en_GB Myspell dictionary which in turn was initially based on a subset of the original English wordlist created by Kevin Atkinson for Pspell and Aspell and thus is covered by his original LGPL licence. Introduction ~~~~~~~~~~~~ en_NZ.dic has been altered to include New Zealand places, including major cities and towns, and major suburbs. It also contains NZ words, organisations and expressions. en_NZ.aff has had a few REPlace strings added, but is basically unchanged. Acknowledgements ~~~~~~~~~~~~~~~~ Thanks must go to the original creators of the British dictionary, David Bartlett, Brian Kelk and Andrew Brown. I wouldn't have started this without seeing the Australian dictionary, thanks Kelvin Eldridge, Jean Hollis Weber and David Wilson. And thank you to all who've contributed to OpenOffice.org. License ~~~~~~~ This dictionary is covered by the GNU Lesser General Public License, viewable at http://www.gnu.org/copyleft/lesser.html Issues ~~~~~~ Many of the proper nouns already in the dictionary do not have an affix for 's. All my new words start after the z's of the original dictionary. Contact ~~~~~~~ Contact Tristan Burtenshaw (hooty@slingshot.co.nz) with any words, places or other suggestions for the dictionary. II. Copying GNU LESSER GENERAL PUBLIC LICENSE Version 2.1, February 1999 Copyright (C) 1991, 1999 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. [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.] Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below. When we speak of free software, we are referring to freedom of use, 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 and use pieces of it in new free programs; and that you are informed that you can do these things. To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it. For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights. We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library. To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others. Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license. Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs. When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library. We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances. For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License. In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system. Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library. The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run. GNU LESSER GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you". A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".) "Source code" for a work means the preferred form of the work for making modifications to it. For a library, 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 library. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does. 1. You may copy and distribute verbatim copies of the Library's complete 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 distribute a copy of this License along with the Library. 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 Library or any portion of it, thus forming a work based on the Library, 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) The modified work must itself be a software library. b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change. c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License. d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, 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 Library, 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 Library. In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy. This option is useful when you wish to copy part of the code of the Library into a program that is not a library. 4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you 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. If distribution of 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 satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code. 5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.) Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself. 6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things: a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.) b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with. c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution. d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place. e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy. For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be 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. It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute. 7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above. b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library 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. 9. 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 Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it. 10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library 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 with this License. 11. 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 Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library 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 Library. 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. 12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library 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. 13. The Free Software Foundation may publish revised and/or new versions of the Lesser 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 Library 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 Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation. 14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, 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 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "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 LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. 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 LIBRARY 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 LIBRARY (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 LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS ======================================================================== * runtime/spell/yi/README.txt ======================================================================== README file for the Yiddish spell file. The word list was provided by Raphael Finkel. It is the same one that is used by uspell. There also is a romanized (transliterated) word list. This is used for latin1. To use this list when 'encoding' is utf-8 use ":set spelllang=yi-tr". Copyright Raphael Finkel. Included with permission in Vim. ======================================================================== * src/VisVim/README_VisVim.txt ======================================================================== =============================== Visual Studio - Vim Integration =============================== Copyright (C) 1997 Heiko Erhardt VisVim is a Visual Studio Add-In that allows Vim to be integrated as the default text editor. It will be used instead of the Visual Studio built-in editor when you double-click on a file or press F4 after compiling (it will go to the proper line in the Vim buffer). The file can be loaded exclusively by Vim or additionally to the builtin Visual Studio editor (this option can be set in the VisVim configuration dialog inside Visual Studio). Vim does not replace the Visual Studio editor, it still runs in its own window. VisVim is based upon VisEmacs by Christopher Payne (Copyright (C) Christopher Payne 1997). Author: Heiko Erhardt Based upon: VisEmacs by Christopher Payne Version: 1.0 Created: 23 Oct 1997 Date: 23 Oct 1997 VisVim was originally GNU GPL licensed, as stated below. On March 21 2012 Heiko Erhardt declared this work to be relicensed under the Vim license, as stated in ../../runtime/doc/uganda.txt (or ":help uganda" in Vim). VisVim 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, or (at your option) any later version. VisVim 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. Requirements ------------ VisVim works with the *OLE-enabled* version of Vim version 5.0 and higher only!!! You must download the extra archive containing the OLE-enabled executable from your Vim download site. When building your own Vim executable, use the if_ole_vc.mak makefile (Vim 5.1 and higher). VisVim needs DevStudio 5.0 or higher. It does not work with DevStudio 4.2. Installation ------------ 1) Close running instances of DevStudio. 2) Copy VisVim.dll into a convenient directory like \vim, \vim\lib, or \vim\addin 3) Register the DLL using regsvr32.exe ... (Skip this on Windows 95/98) Example: > cd \vim\addin > regsvr32 VisVim.dll On NT, you should do this from an administrator account. Before installing a new version of VisVim you should unregister the old one using > regsvr32 -unregister VisVim.dll The batch files register.bat and unregister.bat can do that for you. 3a) If you didn't do this yet: Register the OLE gvim: > gvim -register 4) Start Visual Studio and go to: Tools Customize... Add-Ins and Macro Files 5) Click on Browse, and point Visual Studio to your VisVim.dll file. 6) Click the checkbox to indicate that you want to use the Add-In, and Close the Customize dialog box. 7) You should notice the VisVim Toolbar with the Vim Icon. Click the first item of the toolbar to get to the options dialog. Compiling VisVim ---------------- Two Options: 1) Load the VisVim.mak file as a Workspace in Visual Studio and compile 2) Use the MSVC command line compiler: vcvars32 nmake -f VisVim.mak Using VisVim ------------ The VisVim DLL exposes several functions to the user. These functions are accessible using the toolbar or by assigning hotkeys to them (see below). The following functions are visible on the toolbar (from left to right): 1. VisVim settings dialog The settings you adjust here will be saved in the registry and will be reloaded on program startup. 2. Enable Vim Enables Vim as Visual Studio editor. Control will be switched to Vim when: - Clicking a file in the file view - Clicking a compiler error message line - Using the 'File-Open' Dialog - Showing the current source line when encountering a debugger breakpoint. - Using File-New 3. Disable Vim The internal Visual Studio editor will be used to edit files. 4. Toggle enable state Toggles the enable state of VisVim. Use this function if you want to have one button only to activate/deactivate Vim. 5. Load current file in Vim Loads the file shown in the internal editor into Vim. Use this function if you want the internal editor to stay active and just edit one file in Vim. This command works always whether Vim is enabled as default editor or not. You cannot use DevStudio's debugger commands from inside Vim, so you should disable Vim before running the debugger. You can customize the Vim toolbar itself or add the Vim buttons to other toolbars. To have fast access to the VisVim options dialog I suggest to create keyboard shortcuts: 1) Choose Tools Customize... Keyboard 2) Choose Category:AddIns and Commands:VisVim. 3) Choose 'Main' as editor, enter each hotkey and press the Assign button. I suggest: VisVimDialogCmd Alt+Shift+V VisVimEnableCmd Alt+Shift+E VisVimDisableCmd Alt+Shift+D VisVimToggleCmd Alt+Shift+T VisVimLoadCmd Alt+Shift+G 4) Close the dialog Now a typical debugging example: Using "Alt+Shift+d" you turn off Vim before starting the debugger. After hitting the breakpoint you single step through your application using the internal source code editor and examine variables. When you stumble across the line with the null pointer assignment, just press "Alt+Shift+g", and correct the error in Vim. Save the file, press Alt+Tab to return to DevStudio and press F7 to compile. That's it. Troubleshooting --------------- 1. When opening a file in DevStudio the file is opened in the DevStudio editor and immediately vanishes. No Vim shows up. Cause: Probably you don't have the OLE-enabled Vim or you didn't register it. Explanation: VisVim is notified by DevStudio if an 'open document' event occurs. It then closes the document in the internal editor and tries to start Vim. If Vim isn't properly OLE-registered, this won't work. Workaround: Download and install the OLE-enable version of Vim and execute "gvim -register". 2. Sometimes when clicking on a file, the file won't be opened by Vim but instead the Visual Studio editor comes up. Cause: The file was already loaded by the DevStudio editor. Explanation: VisVim works by hooks exposed by Visual Studio. Most of the functionality works from the OpenDocument hook. If a document is already loaded in the Visual Studio editor, no 'open document' event will be generated when clicking the file in the file list. Workaround: Close the document in Visual Studio first. 3. I can't get VisVim to work. Either the Vim toolbar does not appear at all or weird crashes happen. Cause: The Visual Studio installation is messed up. Explanation: I can't give you one. Ask M$. Workaround: Reinstall DevStudio (I know this is brute, but in some cases it helped). There was one case where the service pack 1 had to be installed, too. 4. If an instance of Vim is already running, VisVim will use that instance and not start a new one. Cause: This is proper OLE behaviour Explanation: Some call it a bug, some a feature. That's just the way OLE works. 5. When being in insert mode in Vim and selecting a file in Visual Studio, the Vim command :e ... is inserted as text instead of being executed. Cause: You probably know... Explanation: The Vim OLE automation interface interprets the VisVim commands as if they were typed in by the user. So if you're in insert mode Vim considers it to be text. I decided against sending an ESC before the command because it may cause a beep or at least a screen flash when noeb is set. Workaround: Get used to press ESC before switching to DevStudio. 6. I'm tired of VisVim but I can't get rid of it. I can't delete it in Tools-Customize-Add-Ins. Cause: You can't delete an item you once added to the add-ins list box. Explanation: M$ just didn't put a 'delete' button in the dialog box. Unfortunately there is no DEL key accellerator as well... Workaround: You can't kill it, but you can knock it out: 1. Uncheck the check box in front of 'Vim Developer Studio Add-in'. 2. Close Visual Studio. 3. Delete VisVim.dll or move it somewhere it can't be found. 4. Run Visual Studio. 5. Tools -> Customize ->Add-ins and Macro-Files. 6. A message appears: ".../VisVim.dll" "This add-in no longer exists. It will no longer be displayed." That's it! Change history -------------- 1.0a to 1.0 ----------- - All settings in the VisVim dialog are remembered between DevStudio sessions by keeping them in the registry (HKEY_CURRENT_USER\Software\Vim\VisVim). - Added an option to do a :cd before opening the file (having a file opened by clicking it but finding out to be still in C:\Windows\system when trying to open another file by ":e" can be annoying). Change directory can be done to the source file's directory or it's parent directory. - Added some explanations to the error message for the CO_E_CLASSSTRING error ("Use OLE Vim and make sure to register..."). 1.0 to 1.1a ----------- - The VisVim toolbar button now shows the new Vim icon instead of the old one. - Made some changes to the documentation, added the troubleshooting chapter and ToDo list. - File-New-* now invokes Vim instead of the builtin editor if enabled. 1.1 to 1.1b ----------- - Extended the VisVim toolbar to have multiple buttons instead of one. - Moved the enable/disable commands from the settings dialog to the toolbar. - Added the toggle enable/disable command - Added the 'load current file' command. 1.1b to 1.2 ----------- No new features, just some fine tuning: - Changed the GUID of the VisVim OLE interface to avoid conflicts with a version of VisEmacs or VisVile on the same computer (Guy Gascoigne) - Fixed a bug caused by a bug in the Developer Studio add-in code generator (Clark Morgan) - Fixed a memory leak (Clark Morgan) - Added an option in the VisVim dialog to prepend ESC before the first command that is sent to Vim. This will avoid inserting the command as text when Vim is still in insert mode. - An :update command is sent to Vim before any other command to update the current file if it is modified, or else the following :cd or :e command will fail. 1.2 to 1.3a ----------- - Fixed a bug caused by a missing EnableModeless() function call in VimLoad(). This seems to reduce VisVim crashing DevStudio on some systems (it occasionally still seems to happen, but it's more stable now). (Vince Negri) - Added support for the new CTRL-\ CTRL-N command of Vim 5.4a. This prevents Vim from beeping when a VisVim command is executed and Vim is not in insert mode. ToDo List --------- P1 is highest priority, P10 lowest P9 Switching to DevStudio using ALT-TAB may get annoying. Would be nice to have the option to map ActivateApplication("Visual Studio") in Vim. Vim DLLs would solve that problem. P8 Execute :tag command in Vim for word under cursor in DevStudio P7 Controlling the Visual Studio Debugger from inside Vim See message above. Also a 'Debug' highlight group and a command to highlight a certain line would be necessary. P6 Provide an option to open the current file in VisVim in Visual Studio editor Same as above message. A kind of two way OLE automation would have to be established between VisVim and Vim. Also a 'Debug' highlight group and a command to highlight a certain line would be necessary. Known Problems -------------- - Occasional memory corruptions in DevStudio may appear on some systems. Reinstalling DevStudio helped in some cases. The cause of these crashes is unclear; there is no way to debug this. Recompiling VisVim with DevStudio SP3 didn't help. I assume it's a problem deep inside the DevStudio add-in OLE interfaces. This will hopefully be fixed with DevStudio 6. Have fun! Heiko Erhardt heiko.erhardt@gmx.net ======================================================================== * src/xpm/README.txt ======================================================================== This is XPM library compiled for Windows which is intended for use with Vim 'signs' feature. Libraries in x86 directory were compiled with MSVC6 and MinGW. Proposed commands to compile Vim are: Any version of MSVC starting from version 6.0: nmake -f Make_mvc.mak GUI=yes CSCOPE=yes NETBEANS=yes XPM=e:\hg\xpm\x86 MinGW: mingw32-make -f Make_ming.mak GUI=yes CSCOPE=yes XPM=e:/hg/xpm/x86 MinGW 64 for x64: mingw32-make -f Make_ming.mak GUI=yes ARCH=x86-64 XPM=E:\HG\xpm\x64 Microsoft Visual C++ on x64 (tested with versions 2008 and 2010): nmake -f Make_mvc.mak GUI=yes CSCOPE=yes XPM=E:\HG\xpm\x64 To test, open some file in Vim and execute commands below: :exe 'sign define vimxpm icon='.$VIMRUNTIME.'\\vim32x32.xpm' :exe 'sign place 1 line=1 name=vimxpm file='.expand('%:p') See COPYRIGHT for XPM licence. If you have questions please email sergey.khorev@gmail.com. ======================================================================== * src/xpm/COPYRIGHT ======================================================================== /* * Copyright (C) 1989-95 GROUPE BULL * * Permission is hereby granted, free of charge, to any person obtaining a copy * of this software and associated documentation files (the "Software"), to * deal in the Software without restriction, including without limitation the * rights to use, copy, modify, merge, publish, distribute, sublicense, and/or * sell copies of the Software, and to permit persons to whom the Software is * furnished to do so, subject to the following conditions: * * The above copyright notice and this permission notice shall be included in * all copies or substantial portions of the Software. * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL * GROUPE BULL BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN * AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. * * Except as contained in this notice, the name of GROUPE BULL shall not be * used in advertising or otherwise to promote the sale, use or other dealings * in this Software without prior written authorization from GROUPE BULL. */ Arnaud LE HORS BULL Research FRANCE -- Koala Project (XPM - X PixMap format version 2 & 3) Internet: lehors@sophia.inria.fr Surface Mail: Arnaud LE HORS, INRIA - Sophia Antipolis, 2004, route des Lucioles, 06565 Valbonne Cedex -- FRANCE Voice phone: (33) 93.65.77.71, Fax: (33) 93 65 77 66, Telex: 97 00 50 F