udtools 0.1.9__tar.gz

udtools-0.1.9/LICENSE.txt

@@ -0,0 +1,339 @@
+GNU GENERAL PUBLIC LICENSE
+                       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc., <http://fsf.org/>
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 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 Lesser 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.
+
+    {description}
+    Copyright (C) {year}  {fullname}
+
+    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.,
+    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 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) year 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 Lesser General
+Public License instead of this License.

udtools-0.1.9/PKG-INFO

@@ -0,0 +1,258 @@
+Metadata-Version: 2.4
+Name: udtools
+Version: 0.1.9
+Summary: Python tools for Universal Dependencies
+Author-email: Daniel Zeman <zeman@ufal.mff.cuni.cz>
+License-Expression: GPL-2.0-or-later
+Project-URL: Homepage, https://universaldependencies.org/
+Project-URL: Issues, https://github.com/UniversalDependencies/tools/issues
+Classifier: Development Status :: 1 - Planning
+Classifier: Intended Audience :: Science/Research
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE.txt
+Requires-Dist: udapi>=0.5.0
+Requires-Dist: regex>=2020.09.27
+Dynamic: license-file
+
+# UD Tools
+
+[![alt text](https://avatars0.githubusercontent.com/u/7457237?s=200&v=4 "Universal Dependencies")](http://universaldependencies.org/)
+
+This repository contains various scripts in Perl and Python that can be used as tools for Universal Dependencies.
+
+
+
+## [validate.py](https://github.com/UniversalDependencies/tools/blob/master/validate.py)
+
+Reads a CoNLL-U file and verifies that it complies with the UD specification. It must be run with
+the language code and there must exist corresponding lists of treebank-specific features and
+dependency relations in order to check that they are valid, too.
+
+The script runs under Python 3 and needs the third-party module **regex** and **udapi**
+(at least version 0.5.0; and udapi has its own dependencies, **colorama** and **termcolor**).
+If you do not have the required modules, install them like this:
+`pip install -r requirements.txt`.
+
+NOTE: Depending on the configuration of your system, it is possible that both Python 2 and 3 are
+installed; then you may have to run `python3` instead of `python`, and `pip3` instead of `pip`.
+
+```
+cat la_proiel-ud-train.conllu | python validate.py --lang la --max-err=0
+```
+
+You can run `python validate.py --help` for a list of available options.
+
+
+
+## [eval.py](https://github.com/UniversalDependencies/tools/blob/master/eval.py)
+
+Evaluates the accuracy of a UD tokenizer / lemmatizer / tagger / parser against gold-standard data.
+The script was originally developed for the [CoNLL 2017](http://universaldependencies.org/conll17/)
+and [2018 shared tasks](http://universaldependencies.org/conll18/) in UD parsing, and later extended
+to handle the enhanced dependency representation in the [IWPT 2020](https://universaldependencies.org/iwpt20/)
+and [2021 shared tasks](https://universaldependencies.org/iwpt21/).
+
+```
+python eval.py -v goldstandard.conllu systemoutput.conllu
+```
+
+For more details on usage, see the comments in the script. For more details on the metrics reported,
+see the overview papers of the shared tasks linked above.
+
+
+
+## [check_sentence_ids.pl](https://github.com/UniversalDependencies/tools/blob/master/check_sentence_ids.pl)
+
+Reads CoNLL-U files from STDIN and verifies that every sentence has a unique id in the sent_id
+comment. All files of one treebank (repository) must be supplied at once in order to test
+treebank-wide id uniqueness.
+
+```
+cat *.conllu | perl check_sentence_ids.pl
+```
+
+
+
+## [normalize_unicode.pl](https://github.com/UniversalDependencies/tools/blob/master/normalize_unicode.pl)
+
+Converts Unicode to the NFC normalized form. Can be applied to any UTF-8-encoded text file, including
+CoNLL-U. As a result, if there are character combinations that by definition must look the same,
+the same sequence of bytes will be used to represent the glyph, thus improving accuracy of models
+(as long as they are applied to normalized data too).
+
+**Beware**: The output may slightly differ depending on your version of Perl because the Unicode
+standard evolves and newer Perl versions incorporate newer versions of Unicode data.
+
+```
+perl normalize_unicode.pl < input.conllu > normalized_output.conllu
+```
+
+
+
+## [conllu-stats.pl](https://github.com/UniversalDependencies/tools/blob/master/conllu-stats.pl)
+
+Reads a CoNLL-U file, collects various statistics and prints them.
+This Perl script (conllu-stats.pl) is used to generate the stats.xml files in each data repository.
+
+The script depends on Perl libraries `YAML` and `JSON::Parse` that may not be installed
+automatically with Perl. If they are not installed on your system, you should be able
+to install them with the `cpan` command: `cpan YAML` and `cpan JSON::Parse`.
+
+```
+perl conllu-stats.pl *.conllu > stats.xml
+```
+
+
+
+## [mwtoken-stats.pl](https://github.com/UniversalDependencies/tools/blob/master/mwtoken-stats.pl)
+
+Reads a CoNLL-U file, collects statistics of multi-word tokens and prints them.
+
+```
+cat *.conllu | perl mwtoken-stats.pl > mwtoken-stats.txt
+```
+
+
+
+## [enhanced_graph_properties.pl](https://github.com/UniversalDependencies/tools/blob/master/enhanced_graph_properties.pl)
+
+Reads a CoNLL-U file, collects statistics about the enhanced graphs in the DEPS column and prints
+them. This script uses the modules Graph.pm and Node.pm that lie in the same folder. On UNIX-like
+systems it should be able to tell Perl where to find the modules even if the script is invoked from
+a remote folder. If that does not work, use `perl -I libfolder script` to invoke it. Also note that
+other third-party modules are needed that are not automatically included in the installation of
+Perl: Moose, MooseX::SemiAffordanceAccessor, List::MoreUtils. You may need to install these modules
+using the `cpan` tool (simply go to commandline and type `sudo cpan Moose`).
+```
+cat *.conllu | perl enhanced_graph_properties.pl > eud-stats.txt
+```
+
+
+
+## [enhanced_collapse_empty_nodes.pl](https://github.com/UniversalDependencies/tools/blob/master/enhanced_collapse_empty_nodes.pl)
+
+Reads a CoNLL-U file, removes empty nodes and adjusts the enhanced graphs so that a path traversing
+one or more empty nodes is contracted into a single edge: if there was a "conj" edge from node 27
+to node 33.1, and a **nsubj** edge from node 33.1 to node 33, the resulting graph will have an edge
+from 27 to 33, labeled **conj>nsubj**
+
+This script uses the modules Graph.pm and Node.pm that lie in the same folder. On UNIX-like systems
+it should be able to tell Perl where to find the modules even if the script is invoked from a
+remote folder. If that does not work, use `perl -I libfolder script` to invoke it. Also note that
+other third-party modules are needed that are not automatically included in the installation of
+Perl: Moose, MooseX::SemiAffordanceAccessor, List::MoreUtils. You may need to install these modules
+using the `cpan` tool (simply go to commandline and type `sudo cpan Moose`).
+```
+perl enhanced_collapse_empty_nodes.pl enhanced.conllu > collapsed.conllu
+```
+
+
+
+## [overlap.py](https://github.com/UniversalDependencies/tools/blob/master/overlap.py)
+
+Compares two CoNLL-U files and searches for sentences that occur in both (verbose duplicates of
+token sequences). Some treebanks, especially those where the original text had been acquired from
+the web, contained duplicate documents that were found at different addresses and downloaded twice.
+This tool helps to find out whether one of the duplicates fell in the training data and the other
+in development or test. The output has to be verified manually, as some “duplicates” are
+repetitions that occur naturally in the language (in particular short sentences such as “Thank you.”)
+
+The script can also help to figure out whether training-dev-test data split has been changed
+between two releases so that a previously training sentence is now in test or vice versa. That is
+something we want to avoid.
+
+
+
+## [find_duplicate_sentences.pl](https://github.com/UniversalDependencies/tools/blob/master/find_duplicate_sentences.pl) & [remove_duplicate_sentences.pl](https://github.com/UniversalDependencies/tools/blob/master/remove_duplicate_sentences.pl)
+
+Similar to overlap.py but it works with the sentence-level attribute **text**. It remembers all
+sentences from STDIN or from input files whose names are given as arguments. The find script prints
+the duplicate sentences (ordered by length and number of occurrences) to STDOUT. The remove script
+works as a filter: it prints the CoNLL-U data from the input, except for the second and any
+subsequent occurrence of the duplicate sentences.
+
+
+
+## [conllu_to_conllx.pl](https://github.com/UniversalDependencies/tools/blob/master/conllu_to_conllx.pl)
+
+Converts a file in the CoNLL-U format to the old CoNLL-X format. Useful with old tools (e.g.
+parsers) that require CoNLL-X as their input. Usage:
+```
+perl conllu_to_conllx.pl < file.conllu > file.conll
+```
+
+
+
+## [restore_conllu_lines.pl](https://github.com/UniversalDependencies/tools/blob/master/restore_conllu_lines.pl)
+
+Merges a CoNLL-X and a CoNLL-U file, taking only the CoNLL-U-specific lines from CoNLL-U. Can be
+used to merge the output of an old parser that only works with CoNLL-X with the original annotation
+that the parser could not read.
+```
+restore_conllu_lines.pl file-parsed.conll file.conllu
+```
+
+
+
+## [conllu_to_text.pl](https://github.com/UniversalDependencies/tools/blob/master/conllu_to_text.pl)
+
+Converts a file in the CoNLL-U format to plain text, word-wrapped to lines of 80 characters (but
+the output line will be longer if there is a word that is longer than the limit). The script can
+use either the sentence-level text attribute, or the word forms plus the SpaceAfter=No MISC
+attribute to output detokenized text. It also observes the sentence-level newdoc and newpar
+attributes, and the NewPar=Yes MISC attribute, if they are present, and prints an empty line
+between paragraphs or documents.
+
+Optionally, the script takes the language code as a parameter. Codes 'zh' and 'ja' will trigger
+a different word-wrapping algorithm that is more suitable for Chinese and Japanese.
+
+**Usage**:
+```
+perl conllu_to_text.pl --lang zh < file.conllu > file.txt
+```
+
+
+
+## [conll_convert_tags_to_uposf.pl](https://github.com/UniversalDependencies/tools/blob/master/conll_convert_tags_to_uposf.pl)
+This script takes the CoNLL columns CPOS, POS and FEAT and converts their combined values to the universal POS tag and features.
+
+You need Perl. On Linux, you probably already have it; on Windows, you may have to download and install Strawberry Perl. You also need the Interset libraries. Once you have Perl, it is easy to get them via the following (call `cpan` instead of `cpanm` if you do not have cpanm).
+```
+cpanm Lingua::Interset
+```
+Then use the script like this:
+```
+perl conll_convert_tags_to_uposf.pl -f source_tagset < input.conll > output.conll
+```
+The source tagset is the identifier of the tagset used in your data and known to Interset. Typically it is the language code followed by two colons and **conll**, e.g. **sl::conll** for the Slovenian data of CoNLL 2006. See the [tagset conversion tables](http://universaldependencies.github.io/docs/tagset-conversion/index.html) for more tagset codes.
+
+**IMPORTANT**:
+
+The script assumes the CoNLL-X (2006 and 2007) file format. If your data is in another format (most notably CoNLL-U, but also e.g. CoNLL 2008/2009, which is not identical to 2006/2007), you have to modify the data or the script. Furthermore,
+you have to know something about the tagset driver (-f source_tagset above) you are going to use. Some drivers do not expect to receive three values joined by TAB characters. Some expect two values and many expect just a single tag, perhaps the one you have in your POS column. These factors may also require you to adapt the script to your needs. You may want to consult the [documentation](https://metacpan.org/pod/Lingua::Interset). Go to Browse / Interset / Tagset, look up your language code and tagset name, then locate the list() function in the source code. That will give you an idea of what the input tags should look like (usually the driver is able to decode even some tags that are not on the list but have the same structure and feature values).
+
+
+
+## [check_files.pl](https://github.com/UniversalDependencies/tools/blob/master/check_files.pl)
+This script checks the contents of one data repositories for missing/extra files,
+invalid metadata in README etc. Together with validate.py, which checks the contents
+of individual CoNLL-U files, this script assesses whether a treebank is valid and
+ready to be released.
+
+
+
+## [check_release.pl](https://github.com/UniversalDependencies/tools/blob/master/check_release.pl)
+This script must be run in a folder where all the data repositories (UD_*) are
+stored as subfolders. It checks the contents of the data repositories for various
+issues that we want to solve before a new release of UD is published.
+
+
+
+## [conllu_align_tokens.pl](https://github.com/UniversalDependencies/tools/blob/master/conllu_align_tokens.pl)
+Compares tokenization and word segmentation of two CoNLL-U files. Assumes that no normalization was performed, that is, the sequence of non-whitespace characters is identical on both sides. Use case: We want to merge a gold-standard file, which has no lemmas, with lemmatization predicted by an external tool. But the tool also performed tokenization and we have no guarantee that it matches the gold-standard tokenization. Despite its name, the script now does exactly that, i.e., copies the system lemma to the gold-standard annotation if the tokens match, and prints the merged file to STDOUT. If something else than lemma shall be copied, the source code must be adjusted.
+```
+perl conllu_align_tokens.pl UD_Turkish-PUD/tr_pud-ud-test.conllu media/conll17-ud-test-2017-05-09/UFAL-UDPipe-1-2/2017-05-15-02-00-38/output/tr_pud.conllu
+```