AUTHORS

+Benedikt Meurer <benny@xfce.org>
+Jannis Pohlmann <jannis@xfce.org>
+Jeffs Franks <jcfranks@xfce.org>
+Nick Schermer <nick@xfce.org>
+Harald Judt <hjudt@xfce.org>
+Andre Miranda <andreldm@xfce.org>
+
+The stock_folder-copy and stock_folder-move icons where taken from
+gnome-icon-theme 2.18.0 whose authors are Lapo Calamandrei <calamandrei@gmail.com>,
+Rodney Dawes <dobey@novell.com>, Luca Ferretti <elle.uca@libero.it>,
+Tuomas Kuosmanen <tigert@gimp.org>, Andreas Nilsson <nisses.mail@home.se>
+and Jakub Steiner <jimmac@novell.com>. The icons are licensed under GPL.

COPYING

+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+     59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+			    NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+		     END OF TERMS AND CONDITIONS
+
+	    How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) 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 Library General
+Public License instead of this License.

FAQ

+This file contains a list of frequently asked questions about Thunar and the
+appropriate answers to these questions.
+
+
+1. What is Thunar?
+==================
+
+  Thunar is a fast and easy-to-use file manager for the X Window System, with a
+  special focus on the Xfce Desktop Environment.
+
+
+2. Why doesn't Thunar execute files marked as executable?
+=========================================================
+
+  For security reasons Thunar only executes files of type application/x-desktop,
+  application/x-executable and application/x-shellscript. For desktop files
+  the execution feature will only be enabled if the desktop file is of type
+  Application and a valid Exec line is given. For the other types the feature
+  is available if the file is marked executable for the current user.
+
+  Also note that for application/x-executable and application/x-shellscript, the
+  types of the file don't really need to match these types exactly, but it is
+  suffice if the detected type has a parent that matches one of the two types
+  listed above, or if the MIME-type is an alias for one of the above.
+
+
+3. Where does Thunar store the metadata associated with files?
+==============================================================
+
+  Thunar uses the metadata daemon provided by GVFS.
+
+
+4. Where does Thunar store its preferences?
+===========================================
+
+  Thunar stores the user configurable preferences (and hidden settings) in
+  an .ini file, which is located at
+
+    $XDG_CONFIG_HOME/Thunar/thunarrc
+
+  and can be examined using a text editor. See docs/README.thunarrc for an
+  overview of the various preferences.
+
+
+5. How to use mouse gestures in Thunar?
+=======================================
+
+  Thunar currently features basic support for so called "mouse gestures" in its
+  icon view. You can use these "mouse gestures" by holding down the middle
+  mouse button (usually the mouse wheel) while the mouse pointer is on the
+  background area of the icon view component (any area that is not covered by
+  an icon or a text). Now you can move the cursor into four directions to
+  perform certain actions, which are described below.
+
+   * Left  - opens the previous visited folder
+   * Up    - opens the parent folder
+   * Right - opens the next visited folder
+   * Down  - reload the current folder
+
+
+6. How do I assign different keyboard shortcuts?
+================================================
+
+  If you want to rebind a shortcut, Thunar supports the standard GTK+ way
+  of changing shortcuts: simply hover over the menu option with the mouse
+  pointer and press the keyboard shortcut you want to rebind it to.
+
+  To delete a keyboard assignment, press the Backspace key while you are
+  on the menu entry.
+
+  If the shortcut doesn't change, then you need to enable the feature in
+  GTK+. This can be achieved in 3 ways:
+
+   1. If you are running Xfce 4.3 or above then you can enable "Editable
+      menu accelerators" in the "User Interface Preferences" dialog.
+   2. If you are running GNOME then you can enable "Editable menu
+      accelerators" in the "Menu and Toolbars" control center dialog.
+   3. Otherwise put the following in your ~/.gtkrc-2.0 file (create the
+      file if it doesn't exist):
+
+       gtk-can-change-accels=1
+
+
+7. Where does Thunar store the keyboard shortcuts?
+==================================================
+
+  The custom keyboard shortcuts are stored in the standard Gtk accel map
+  format in a file located at
+
+    $XDG_CONFIG_HOME/Thunar/accels.scm
+
+  Lines starting with ; are comments. See the GTK+ documentation for details
+  about the file format. If you are a packager or a system administrator and
+  want to provide a system-wide default for the keyboard shortcuts, that is
+  different from the default shortcuts in Thunar, you can create a file
+  Thunar/accels.scm in one of the $XDG_CONFIG_DIRS. For example, if /etc/xdg
+  is part of $XDG_CONFIG_DIRS (most likely for most Linux distributions), you
+  can install system-wide defaults to
+
+    /etc/xdg/Thunar/accels.scm
+
+  Thunar will then load shortcuts from this file on first startup.
+

HACKING

+Bug tracking system
+===================
+
+Thunar uses the Xfce bug tracking system at http://bugzilla.xfce.org/,
+hosted and maintained by the Xfce project.
+
+
+Patches
+=======
+
+Please submit patches to the Xfce bug tracking system or to the thunar-dev
+mailinglist. Your patch should be in unified diff format (the -u option
+to GNU diff) and it must comply with the coding style described below.
+
+Please send a patch against a recent version of this package. Patches
+against the Git master branch are most preferable. You can always
+clone the Thunar repository from
+
+  https://git.xfce.org/xfce/thunar
+
+
+Feature requests
+================
+
+Please file feature requests to the Xfce bug tracking system
+(http://buzilla.xfce.org, product Thunar) with a Severity of
+enhancement. Make sure that your feature request wasn't reported
+already before; requesting a feature several times won't increase
+the changed that it gets added!
+
+
+Coding Style
+============
+
+ - GNU coding conventions, with GLib-like extensions, mostly the same
+   as GTK+.
+ - Always expand tabs. This differs from the GNU suggestion, but it is
+   necessary to be independent from a given tab setting.
+ - Do NOT ever misuse debugging macros like g_return_val_if_fail() or
+   g_return_if_fail() to control program flow. They are solely useful
+   to discover bugs, the final binary won't include code for these
+   statements, and so any use of these macros to control program
+   flow presents a bug!
+ - Do NOT follow the philosophy "If it works, it's right" that most
+   other open source projects follow, instead Thunar's philosophy is
+   "It doesn't work unless it's right". Think carefully of what you want
+   to do, don't just fire up your favourite editor and start hacking
+   in the hope that it will evolve into something useful one day.
+ - Maintainability goes over performance. If you have to choose between
+   a maintainable and a fast solution, always prefer the former, as it's
+   quite easy to optimize well-designed modules, but very hard and costly
+   to make spaghetti-code readable.
+ - Write ChangeLog entries. Whenever you commit a change or send a patch,
+   write a good entry per change to the ChangeLog file, see the libexo
+   ChangeLog for the exact format; it's very important to be descriptive
+   and correct here, else you'll loose your commit bits or your patches
+   won't be considered for inclusion.
+ - Use GObject whenever possible. Object-oriented design and programming
+   makes it easier to separate functionality and also aids in verification
+   and testing, and GObject provides a very solid base.
+
+
+Release process
+===============
+
+Yet to be defined!

INSTALL

+Installation Instructions
+*************************
+
+   Copyright (C) 1994-1996, 1999-2002, 2004-2016 Free Software
+Foundation, Inc.
+
+   Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved.  This file is offered as-is,
+without warranty of any kind.
+
+Basic Installation
+==================
+
+   Briefly, the shell command './configure && make && make install'
+should configure, build, and install this package.  The following
+more-detailed instructions are generic; see the 'README' file for
+instructions specific to this package.  Some packages provide this
+'INSTALL' file but do not implement all of the features documented
+below.  The lack of an optional feature in a given package is not
+necessarily a bug.  More recommendations for GNU packages can be found
+in *note Makefile Conventions: (standards)Makefile Conventions.
+
+   The 'configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation.  It uses
+those values to create a 'Makefile' in each directory of the package.
+It may also create one or more '.h' files containing system-dependent
+definitions.  Finally, it creates a shell script 'config.status' that
+you can run in the future to recreate the current configuration, and a
+file 'config.log' containing compiler output (useful mainly for
+debugging 'configure').
+
+   It can also use an optional file (typically called 'config.cache' and
+enabled with '--cache-file=config.cache' or simply '-C') that saves the
+results of its tests to speed up reconfiguring.  Caching is disabled by
+default to prevent problems with accidental use of stale cache files.
+
+   If you need to do unusual things to compile the package, please try
+to figure out how 'configure' could check whether to do them, and mail
+diffs or instructions to the address given in the 'README' so they can
+be considered for the next release.  If you are using the cache, and at
+some point 'config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+   The file 'configure.ac' (or 'configure.in') is used to create
+'configure' by a program called 'autoconf'.  You need 'configure.ac' if
+you want to change it or regenerate 'configure' using a newer version of
+'autoconf'.
+
+   The simplest way to compile this package is:
+
+  1. 'cd' to the directory containing the package's source code and type
+     './configure' to configure the package for your system.
+
+     Running 'configure' might take a while.  While running, it prints
+     some messages telling which features it is checking for.
+
+  2. Type 'make' to compile the package.
+
+  3. Optionally, type 'make check' to run any self-tests that come with
+     the package, generally using the just-built uninstalled binaries.
+
+  4. Type 'make install' to install the programs and any data files and
+     documentation.  When installing into a prefix owned by root, it is
+     recommended that the package be configured and built as a regular
+     user, and only the 'make install' phase executed with root
+     privileges.
+
+  5. Optionally, type 'make installcheck' to repeat any self-tests, but
+     this time using the binaries in their final installed location.
+     This target does not install anything.  Running this target as a
+     regular user, particularly if the prior 'make install' required
+     root privileges, verifies that the installation completed
+     correctly.
+
+  6. You can remove the program binaries and object files from the
+     source code directory by typing 'make clean'.  To also remove the
+     files that 'configure' created (so you can compile the package for
+     a different kind of computer), type 'make distclean'.  There is
+     also a 'make maintainer-clean' target, but that is intended mainly
+     for the package's developers.  If you use it, you may have to get
+     all sorts of other programs in order to regenerate files that came
+     with the distribution.
+
+  7. Often, you can also type 'make uninstall' to remove the installed
+     files again.  In practice, not all packages have tested that
+     uninstallation works correctly, even though it is required by the
+     GNU Coding Standards.
+
+  8. Some packages, particularly those that use Automake, provide 'make
+     distcheck', which can by used by developers to test that all other
+     targets like 'make install' and 'make uninstall' work correctly.
+     This target is generally not run by end users.
+
+Compilers and Options
+=====================
+
+   Some systems require unusual options for compilation or linking that
+the 'configure' script does not know about.  Run './configure --help'
+for details on some of the pertinent environment variables.
+
+   You can give 'configure' initial values for configuration parameters
+by setting variables in the command line or in the environment.  Here is
+an example:
+
+     ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+
+   *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+   You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory.  To do this, you can use GNU 'make'.  'cd' to the
+directory where you want the object files and executables to go and run
+the 'configure' script.  'configure' automatically checks for the source
+code in the directory that 'configure' is in and in '..'.  This is known
+as a "VPATH" build.
+
+   With a non-GNU 'make', it is safer to compile the package for one
+architecture at a time in the source code directory.  After you have
+installed the package for one architecture, use 'make distclean' before
+reconfiguring for another architecture.
+
+   On MacOS X 10.5 and later systems, you can create libraries and
+executables that work on multiple system types--known as "fat" or
+"universal" binaries--by specifying multiple '-arch' options to the
+compiler but only a single '-arch' option to the preprocessor.  Like
+this:
+
+     ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+                 CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+                 CPP="gcc -E" CXXCPP="g++ -E"
+
+   This is not guaranteed to produce working output in all cases, you
+may have to build one architecture at a time and combine the results
+using the 'lipo' tool if you have problems.
+
+Installation Names
+==================
+
+   By default, 'make install' installs the package's commands under
+'/usr/local/bin', include files under '/usr/local/include', etc.  You
+can specify an installation prefix other than '/usr/local' by giving
+'configure' the option '--prefix=PREFIX', where PREFIX must be an
+absolute file name.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+pass the option '--exec-prefix=PREFIX' to 'configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
+
+   In addition, if you use an unusual directory layout you can give
+options like '--bindir=DIR' to specify different values for particular
+kinds of files.  Run 'configure --help' for a list of the directories
+you can set and what kinds of files go in them.  In general, the default
+for these options is expressed in terms of '${prefix}', so that
+specifying just '--prefix' will affect all of the other directory
+specifications that were not explicitly provided.
+
+   The most portable way to affect installation locations is to pass the
+correct locations to 'configure'; however, many packages provide one or
+both of the following shortcuts of passing variable assignments to the
+'make install' command line to change installation locations without
+having to reconfigure or recompile.
+
+   The first method involves providing an override variable for each
+affected directory.  For example, 'make install
+prefix=/alternate/directory' will choose an alternate location for all
+directory configuration variables that were expressed in terms of
+'${prefix}'.  Any directories that were specified during 'configure',
+but not in terms of '${prefix}', must each be overridden at install time
+for the entire installation to be relocated.  The approach of makefile
+variable overrides for each directory variable is required by the GNU
+Coding Standards, and ideally causes no recompilation.  However, some
+platforms have known limitations with the semantics of shared libraries
+that end up requiring recompilation when using this method, particularly
+noticeable in packages that use GNU Libtool.
+
+   The second method involves providing the 'DESTDIR' variable.  For
+example, 'make install DESTDIR=/alternate/directory' will prepend
+'/alternate/directory' before all installation names.  The approach of
+'DESTDIR' overrides is not required by the GNU Coding Standards, and
+does not work on platforms that have drive letters.  On the other hand,
+it does better at avoiding recompilation issues, and works well even
+when some directory options were not specified in terms of '${prefix}'
+at 'configure' time.
+
+Optional Features
+=================
+
+   If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving 'configure' the
+option '--program-prefix=PREFIX' or '--program-suffix=SUFFIX'.
+
+   Some packages pay attention to '--enable-FEATURE' options to
+'configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to '--with-PACKAGE' options, where PACKAGE
+is something like 'gnu-as' or 'x' (for the X Window System).  The
+'README' should mention any '--enable-' and '--with-' options that the
+package recognizes.
+
+   For packages that use the X Window System, 'configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the 'configure' options '--x-includes=DIR' and
+'--x-libraries=DIR' to specify their locations.
+
+   Some packages offer the ability to configure how verbose the
+execution of 'make' will be.  For these packages, running './configure
+--enable-silent-rules' sets the default to minimal output, which can be
+overridden with 'make V=1'; while running './configure
+--disable-silent-rules' sets the default to verbose, which can be
+overridden with 'make V=0'.
+
+Particular systems
+==================
+
+   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU CC
+is not installed, it is recommended to use the following options in
+order to use an ANSI C compiler:
+
+     ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
+
+and if that doesn't work, install pre-built binaries of GCC for HP-UX.
+
+   HP-UX 'make' updates targets which have the same time stamps as their
+prerequisites, which makes it generally unusable when shipped generated
+files such as 'configure' are involved.  Use GNU 'make' instead.
+
+   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
+parse its '<wchar.h>' header file.  The option '-nodtk' can be used as a
+workaround.  If GNU CC is not installed, it is therefore recommended to
+try
+
+     ./configure CC="cc"
+
+and if that doesn't work, try
+
+     ./configure CC="cc -nodtk"
+
+   On Solaris, don't put '/usr/ucb' early in your 'PATH'.  This
+directory contains several dysfunctional programs; working variants of
+these programs are available in '/usr/bin'.  So, if you need '/usr/ucb'
+in your 'PATH', put it _after_ '/usr/bin'.
+
+   On Haiku, software installed for all users goes in '/boot/common',
+not '/usr/local'.  It is recommended to use the following options:
+
+     ./configure --prefix=/boot/common
+
+Specifying the System Type
+==========================
+
+   There may be some features 'configure' cannot figure out
+automatically, but needs to determine by the type of machine the package
+will run on.  Usually, assuming the package is built to be run on the
+_same_ architectures, 'configure' can figure that out, but if it prints
+a message saying it cannot guess the machine type, give it the
+'--build=TYPE' option.  TYPE can either be a short name for the system
+type, such as 'sun4', or a canonical name which has the form:
+
+     CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+     OS
+     KERNEL-OS
+
+   See the file 'config.sub' for the possible values of each field.  If
+'config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+   If you are _building_ compiler tools for cross-compiling, you should
+use the option '--target=TYPE' to select the type of system they will
+produce code for.
+
+   If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with '--host=TYPE'.
+
+Sharing Defaults
+================
+
+   If you want to set default values for 'configure' scripts to share,
+you can create a site shell script called 'config.site' that gives
+default values for variables like 'CC', 'cache_file', and 'prefix'.
+'configure' looks for 'PREFIX/share/config.site' if it exists, then
+'PREFIX/etc/config.site' if it exists.  Or, you can set the
+'CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all 'configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+   Variables not defined in a site shell script can be set in the
+environment passed to 'configure'.  However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost.  In order to avoid this problem, you should set
+them in the 'configure' command line, using 'VAR=value'.  For example:
+
+     ./configure CC=/usr/local2/bin/gcc
+
+causes the specified 'gcc' to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+Unfortunately, this technique does not work for 'CONFIG_SHELL' due to an
+Autoconf limitation.  Until the limitation is lifted, you can use this
+workaround:
+
+     CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+'configure' Invocation
+======================
+
+   'configure' recognizes the following options to control how it
+operates.
+
+'--help'
+'-h'
+     Print a summary of all of the options to 'configure', and exit.
+
+'--help=short'
+'--help=recursive'
+     Print a summary of the options unique to this package's
+     'configure', and exit.  The 'short' variant lists options used only
+     in the top level, while the 'recursive' variant lists options also
+     present in any nested packages.
+
+'--version'
+'-V'
+     Print the version of Autoconf used to generate the 'configure'
+     script, and exit.
+
+'--cache-file=FILE'
+     Enable the cache: use and save the results of the tests in FILE,
+     traditionally 'config.cache'.  FILE defaults to '/dev/null' to
+     disable caching.
+
+'--config-cache'
+'-C'
+     Alias for '--cache-file=config.cache'.
+
+'--quiet'
+'--silent'
+'-q'
+     Do not print messages saying which checks are being made.  To
+     suppress all normal output, redirect it to '/dev/null' (any error
+     messages will still be shown).
+
+'--srcdir=DIR'
+     Look for the package's source code in directory DIR.  Usually
+     'configure' can determine that directory automatically.
+
+'--prefix=DIR'
+     Use DIR as the installation prefix.  *note Installation Names:: for
+     more details, including other options available for fine-tuning the
+     installation locations.
+
+'--no-create'
+'-n'
+     Run the configure checks, but stop before creating any output
+     files.
+
+'configure' also accepts some other, not widely useful, options.  Run
+'configure --help' for more details.

Makefile.am

+# vi:set ts=8 sw=8 noet ai nocindent syntax=automake:
+# -
+# Copyright (c) 2010 Jannis Pohlmann <jannis@xfce.org>
+# 
+# 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.
+
+ACLOCAL_AMFLAGS = -I m4 ${ACLOCAL_FLAGS}
+
+SUBDIRS =								\
+	icons								\
+	pixmaps								\
+	po								\
+	thunarx								\
+	thunar								\
+	docs								\
+	examples							\
+	plugins
+
+distclean-local:
+	rm -rf *.cache *~
+	find . -type f -name Makefile -delete
+	find . -type f -name Makefile.in -delete
+
+distuninstallcheck_listfiles = 						\
+	find . -type f -print | grep -v ./share/icons/hicolor/icon-theme.cache
+
+.PHONY: ChangeLog
+
+ChangeLog: Makefile
+	(GIT_DIR=$(top_srcdir)/.git git log > .changelog.tmp \
+	&& mv .changelog.tmp ChangeLog; rm -f .changelog.tmp) \
+	|| (touch ChangeLog; echo 'Git directory not found: installing possibly empty changelog.' >&2)
+
+dist-hook: ChangeLog
+
+thunar_scriptsdir = $(HELPER_PATH_PREFIX)/Thunar
+thunar_scripts_SCRIPTS =						\
+	ThunarBulkRename
+
+ThunarBulkRename: ThunarBulkRename.in Makefile
+	$(AM_V_GEN) (							\
+		rm -f ThunarBulkRename.gen ThunarBulkRename		\
+		&& $(SED) -e "s,\@bindir\@,$(bindir),g" 			\
+			< $(srcdir)/ThunarBulkRename.in			\
+			> ThunarBulkRename.gen				\
+		&& mv ThunarBulkRename.gen ThunarBulkRename 		\
+	)
+
+desktopdir = $(datadir)/applications
+desktop_in_in_files = 							\
+	Thunar.desktop.in.in						\
+	Thunar-bulk-rename.desktop.in.in				\
+	Thunar-folder-handler.desktop.in.in
+desktop_in_files = $(desktop_in_in_files:.desktop.in.in=.desktop.in)
+%.desktop.in: %.desktop.in.in Makefile
+	$(AM_V_GEN) $(SED) -e "s,\@HELPERDIR\@,$(HELPER_PATH_PREFIX),g" < $< > $@
+desktop_DATA = $(desktop_in_files:.desktop.in=.desktop)
+@INTLTOOL_DESKTOP_RULE@
+
+#
+# .appdata
+#
+@INTLTOOL_XML_RULE@
+appdatadir = $(datadir)/metainfo
+appdata_DATA = $(appdata_in_files:.xml.in=.xml)
+appdata_in_files = org.xfce.thunar.appdata.xml.in
+
+servicedir = $(datadir)/dbus-1/services
+service_in_files = org.xfce.FileManager.service.in	\
+	org.xfce.Thunar.service.in						\
+	org.xfce.Thunar.FileManager1.service.in
+service_DATA = $(service_in_files:.service.in=.service)
+
+systemd_userdir = $(prefix)/lib/systemd/user
+systemd_user_in_files = thunar.service.in
+systemd_user_DATA = $(systemd_user_in_files:.service.in=.service)
+
+%.service: %.service.in Makefile
+	$(AM_V_GEN) $(SED) -e "s,\@bindir\@,$(bindir),g" < $< > $@
+
+polkit_policydir = $(datadir)/polkit-1/actions
+polkit_in_in_files =			\
+	org.xfce.thunar.policy.in.in
+polkit_in_files = $(polkit_in_in_files:.policy.in.in=.policy.in)
+%.policy.in: %.policy.in.in Makefile
+	sed -e "s,\@bindir\@,$(bindir),g" < $< > $@
+polkit_policy_DATA = $(polkit_in_files:.policy.in=.policy)
+@INTLTOOL_POLICY_RULE@
+
+EXTRA_DIST =								\
+	FAQ								\
+	HACKING								\
+	ThunarBulkRename.in						\
+	intltool-extract.in						\
+	intltool-merge.in						\
+	intltool-update.in						\
+	$(desktop_in_in_files)						\
+	$(service_in_files)						\
+	$(systemd_user_in_files)					\
+	$(appdata_in_files)						\
+	$(polkit_in_in_files)					\
+	m4/introspection.m4
+
+CLEANFILES		= $(appdata_DATA)
+
+DISTCLEANFILES =							\
+	ThunarBulkRename						\
+	intltool-extract						\
+	intltool-merge							\
+	intltool-update							\
+	$(desktop_in_files)						\
+	$(desktop_DATA)							\
+	$(service_DATA)							\
+	$(systemd_user_DATA)						\
+	$(polkit_in_files)						\
+	$(polkit_policy_DATA)
+
+DISTCHECK_CONFIGURE_FLAGS =						\
+	--enable-gtk-doc							\
+	--enable-gen-doc							\
+	--enable-introspection

README

+What is it?
+===========
+
+Thunar is a modern file manager for the Unix/Linux desktop, aiming to be
+easy-to-use and fast.
+
+
+Required packages
+=================
+
+Thunar depends on the following packages:
+
+ - perl 5.6 or above
+ - GTK+ 3.20.0 or above
+ - GLib 2.30.0 or above
+ - exo 0.10.0 or above
+ - intltool 0.30 or above
+
+Thunar can optionally use the following packages:
+
+ - D-Bus 0.34 or above (strongly suggested)
+ - libstartup-notification 0.4 or above
+ - xfce4-panel 4.10.0 or above (for the trash applet)
+ - xfconf-query
+
+
+Installation
+============
+
+The file 'INSTALL' contains generic installation instructions. For more
+detailed information, visit https://docs.xfce.org/xfce/thunar/start.
+
+
+Debugging Support
+=================
+
+Thunar currently supports four different levels of debugging support, which
+can be setup using the configure flag `--enable-debug' (check the output of
+`configure --help'):
+
+  `full'	Use this if you want to debug Thunar to locate a bug. The
+  		build will most probably be noticably slower. This is also
+		recommended for people that want to develop Thunar stuff.
+
+  `yes'		This is the default for SVN snapshot builds. It adds all
+  		kinds of checks to the code, and is therefore likely to run
+		slower. Use this if you want to develop for Thunar (e.g.
+		writing Thunar extensions and such).
+
+  `minimum'	This is the default for release builds, and presents the
+  		recommended behaviour.
+
+  `no'		Disables all sanity checks. Don't use this unless you know
+  		exactly what you do.
+
+
+Standards compliance
+====================
+
+Thunar supports the following standards/specifications:
+
+  * XDG Base Directory Specification
+    http://freedesktop.org/wiki/Standards_2fbasedir_2dspec
+
+  * Shared MIME Database Specification
+    http://freedesktop.org/wiki/Standards_2fshared_2dmime_2dinfo_2dspec
+
+  * X Direct Save (XDS) Protocol for the X Window System
+    http://freedesktop.org/wiki/Standards_2fdirect_2dsave
+
+  * Icon Theme Specification
+    http://freedesktop.org/wiki/Standards_2ficon_2dtheme_2dspec
+
+  * Thumbnail Managing Standard
+    http://jens.triq.net/thumbnail-spec/index.html
+
+  * File URI Specification
+    http://freedesktop.org/wiki/Standards_2ffile_2duri_2dspec
+
+  * Desktop Trash Can Specification
+    http://freedesktop.org/wiki/Standards_2ftrash_2dspec
+
+
+How to report bugs?
+===================
+
+Bugs should be reported to the Xfce bug tracking system
+(http://bugzilla.xfce.org, product Thunar). You will need to
+create an account for yourself.
+
+Please read the HACKING file for information on where to send
+changes or bugfixes for this package.

THANKS

+What's this file about?
+-----------------------
+This file lists all external people that have contributed to this project and
+thereby helped to make Thunar such a successful project.
+
+
+
+Testers (sorted by name):
+--------------------------
+These people have contributed to Thunar by testing the software,
+reporting problems and making useful suggestions.
+
+
+
+Translators (sorted by language):
+----------------------------------
+These people have translated Thunar to foreign languages.
+
+ Mohamed Magdy <mohamed.m.k@gmail.com>
+  * ar translations
+
+ Alexander Nyakhaychyk <nyakhaychyk@gmail.com>
+  * be translations
+
+ Carles Muñoz Gorriz <carlesmu@internautas.org>
+  * ca translations
+
+ Pau Rul·lan Ferragut <paurullan@bulma.net>
+  * ca translations
+
+ Michal Várady <miko.vaji@gmail.com>
+  * cs translations
+
+ Benedikt Meurer <benny@xfce.org>
+  * de translations
+ 
+ Fabian Nowak <timystery@arcor.de>
+  * de translations
+
+ Jannis Pohlmann <jannis@xfce.org>
+  * de translations
+
+ Sonam Pelden <sonaa_peldn@yahoo.com>
+  * dz translations
+
+ Stathis Kamperis <ekamperi@auth.gr>
+  * el translations
+
+ Stavros Giannouris <stavrosg2002@freemail.gr>
+  * el translations
+
+ Jeff Bailes <thepizzaking@gmail.com>
+  * en_GB translations
+
+ Antono Vasiljev <antono.vasiljev@gmail.com>
+  * eo translations
+
+ Sylvain Vedrenne <gnu_sylvain@xfce.org>
+  * eo translations
+
+ Daniel Fuertes Pérez <danifp25@yahoo.es>
+  * es translations
+
+ Miguel Angel Ruiz Manzano <debianized@gmail.com>
+  * es translations
+
+ Pablo Hernández-M. Saiz <homeless3d@gmail.com>
+  * es translations
+
+ Peeter Vois <Peeter.Vois@proekspert.ee>
+  * et translations
+
+ Piarres Beobide <pi@beobide.net>
+  * eu translations
+
+ Jari Rahkonen <jari.rahkonen@pp1.inet.fi>
+  * fi translations
+
+ Gérald Barré <g.barre@free.fr>
+  * fr translations
+
+ Maximilian Schleiss <maxschleiss@bluewin.ch>
+  * fr translations
+
+ Rafaël Carré <wavael@yahoo.fr>
+  * fr translations
+
+ Stephane Roy <sroy@j2n.net>
+  * fr translations
+
+ Iván Seoane Pardo <talivan.ivan@gmail.com>
+  * gl translations
+
+ Yo'av Moshe <bjesus@gmail.com>
+  * he translations
+
+ Yuval Tanny <tanai@int.gov.il>
+  * he translations
+
+ Szervác Attila <sas@321.hu>
+  * hu translations
+
+ Roberto Pariset <r.pariset@gmail.com>
+  * it translations
+
+ Daichi Kawahata <daichi@xfce.org>
+  * ja translations
+
+ Dimitri Gogelia <delphi.knight@gmail.com>
+  * ka translations
+
+ ByungHyun Choi <byunghyun.choi@debianusers.org>
+  * ko translations
+
+ Mantas Zapolskas <mantaz@users.sourceforge.net>
+  * lt translations
+
+ Rihards Prieditis <rprieditis@inbox.lv>
+  * lv translations
+
+ Vincent Tunru <imnotb@gmail.com>
+  * nl translations
+
+ Jovan Naumovski <jovan@lugola.net>
+  * mk translations
+
+ Viktor Stojanovski <viktor@lugola.net>
+  * mk translations
+
+ Terje Uriansrud <ter@operamail.com>
+  * nb_NO translations
+
+ Stephan Arts <psybsd@gmail.com>
+  * nl translations
+
+ Vincent Tunru <imnotb@gmail.com>
+  * nl translations
+
+ Amanpreet Singh Alam <aalam@users.sf.net>
+  * pa translations
+
+ Piotr Maliński <admin@rk.edu.pl>
+  * pl translations
+
+ Szymon Kałasz <szymon_maestro@gazeta.pl>
+  * pl translations
+
+ Tomasz Michał Łukaszewski <T.Lukaszewski@aster.pl>
+  * pl translations
+
+ Adriano Winter Bess <awbess@gmail.com>
+  * pt_BR translations
+
+ William Koch <wkromani@gmail.com>
+  * pt_BR translations
+
+ Fábio Nogueira <deb-user-ba@ubuntu.com>
+  * pt_BR translations
+
+ Joao Pedrosa <joaopedrosa@gmail.com>
+  * pt_BR translations
+
+ Rodrigo Coacci <rcoacci@gmail.com>
+  * pt_BR translations
+
+ Nuno Miguel <nunis@netcabo.pt>
+  * pt_PT translations
+
+ Misu Moldovan <dumol@gnome.ro>
+  * ro translations
+
+ Andrey Fedoseev <andrey.fedoseev@gmail.com>
+  * ru translations
+
+ Sergey Fedoseev <fedoseev.sergey@gmail.com>
+  * ru translations
+
+ Ivan Masár <helix84@centrum.sk>
+  * sk translations
+
+ Besnik Bleta <besnik@programeshqip.org>
+  * sq translations
+
+ Alexander Toresson <alexander.toresson@gmail.com>
+  * sv translations
+
+ Daniel Nylander <po@danielnylander.se>
+  * sv translations
+
+ Türker Sezer <turkersezer@tsdesign.info>
+  * tr translations
+
+ Eren Türkay <turkay.eren@gmail.com>
+  * tr translations
+
+ Cem Ünal <admincemunal@gmail.com>
+  * tr translations
+
+ Maxim V. Dziumanenko <mvd@mylinux.ua>
+  * uk translations
+
+ Dmitry Nikitin <luckas_fb@mail.ru>
+  * uk translations
+
+ Muhammad Ali Makki <makki.ma@gmail.com>
+  * ur translations
+
+ kangkang <kanger@gmail.com>
+  * zh_CN translations
+
+ Li Linxiao <linxiao.li@gmail.com>
+  * zh_CN translations
+
+ Hydonsingore Cia <hydonsingore@mail.educities.edu.tw>
+  * zh_TW translations
+
+ Cosmo Chene <cosmolax@gmail.com>
+  * zh_TW translations
+
+
+
+Other contributors (sorted by name):
+------------------------------------
+
+ Young Hahn <youngjin.hahn@gmail.com>
+  * icon designer
+
+ Daichi Kawahata <daichi@xfce.org>
+  * i18n coordinator
+
+ Laurent Meunier <meunier.laurent@laposte.net>
+  * patches
+
+ Danny Milosavljevic <danny.milo@gmx.net>
+  * patches
+
+ Matt McClinch <mattmcclinch@gmail.com>
+  * patches
+
+ Nick Schermer <nick@xfce.org>
+  * patches
+
+ Peter de Ridder <peter@xfce.org>
+  * patches

TODO

+Important for Thunar 1.2
+========================
+
+ - The layouting code for ThunarLocationButtons is still buggy. Problem shows
+   with paths that include a very long directory; you cannot scroll to the
+   last path component then.
+
+ - A design for the ThunarDesktopView module must be developed and later
+   be implemented.
+
+ - We need a suite of unit tests and probably high-level tests, that enable
+   us to test parts of the file manager automatically and isolate bugs
+   early.
+
+ - Setup gtk-doc to present developers with the internal API of Thunar
+   to ease development of core modules (and later plugins).
+
+ - Write good user documentation. Must be both precise and complete.
+
+ - We need some easy way to manage diagrams and related developer
+   information, which also includes results from discussions on
+   thunar-dev.
+
+ - The HACKING file must be updated with strict rules about how
+   development of Thunar core modules is to be done, and what
+   material each developer in addition to the source code.
+

Thunar-bulk-rename.desktop.in.in

+[Desktop Entry]
+_Name=Bulk Rename
+_Comment=Rename Multiple Files
+_GenericName=Bulk Rename
+Exec=@HELPERDIR@/Thunar/ThunarBulkRename %F
+Icon=Thunar
+Terminal=false
+StartupNotify=true
+Type=Application
+Categories=System;Utility;Core;GTK;Filesystem;
+
+# vi:set encoding=UTF-8:

Thunar-folder-handler.desktop.in.in

+[Desktop Entry]
+_Name=Open Folder with Thunar
+_Comment=Open the specified folders in Thunar
+_GenericName=Open Folder
+TryExec=Thunar
+Exec=thunar %F
+Icon=Thunar
+NoDisplay=true
+Terminal=false
+StartupNotify=true
+Type=Application
+Categories=System;Utility;Core;GTK;FileTools;FileManager;
+MimeType=inode/directory;
+
+# vi:set encoding=UTF-8:

Thunar.desktop.in.in

+[Desktop Entry]
+_Name=Thunar File Manager
+_Comment=Browse the filesystem with the file manager
+_GenericName=File Manager
+Exec=thunar %F
+Icon=Thunar
+Terminal=false
+StartupNotify=true
+Type=Application
+Categories=System;Utility;Core;GTK;FileTools;FileManager;
+
+# vi:set encoding=UTF-8:

ThunarBulkRename.in

+#!/bin/sh
+#
+# Copyright (c) 2006 Benedikt Meurer <benny@xfce.org>
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+#
+
+# This is an ugly hack, required because xfdesktop simply
+# strips off all parameters from the Exec field, and so
+# we cannot just invoke Thunar --bulk-rename %F there
+exec @bindir@/Thunar --bulk-rename "$@"
+
+# vim:set ts=2 sw=2 et ai:

acinclude.m4

+dnl Copyright (c) 2004-2006
+dnl         The Thunar development team. All rights reserved.
+dnl
+dnl Written for Thunar by Benedikt Meurer <benny@xfce.org>.
+dnl
+
+
+
+dnl # BM_THUNAR_PLUGIN_APR()
+dnl #
+dnl # Check whether the "Advanced Properties" plugin
+dnl # should be built and installed.
+dnl #
+AC_DEFUN([BM_THUNAR_PLUGIN_APR],
+[
+AC_ARG_ENABLE([apr-plugin], [AC_HELP_STRING([--disable-apr-plugin], [Don't build the thunar-apr plugin, see plugins/thunar-apr/README])],
+  [ac_bm_thunar_plugin_apr=$enableval], [ac_bm_thunar_plugin_apr=yes])
+AC_MSG_CHECKING([whether to build the thunar-apr plugin])
+AM_CONDITIONAL([THUNAR_PLUGIN_APR], [test x"$ac_bm_thunar_plugin_apr" = x"yes"])
+AC_MSG_RESULT([$ac_bm_thunar_plugin_apr])
+
+dnl Check for libexif (for the "Image" properties page)
+XDT_CHECK_OPTIONAL_PACKAGE([EXIF], [libexif], [0.6.0], [exif], [Exif support])
+])
+
+
+
+dnl # BM_THUNAR_PLUGIN_SBR()
+dnl #
+dnl # Check whether the "Simple Builtin Renamers" plugin
+dnl # should be built and installed.
+dnl #
+AC_DEFUN([BM_THUNAR_PLUGIN_SBR],
+[
+AC_ARG_ENABLE([sbr-plugin], AC_HELP_STRING([--disable-sbr-plugin], [Don't build the thunar-sbr plugin, see plugins/thunar-sbr/README]),
+  [ac_bm_thunar_plugin_sbr=$enableval], [ac_bm_thunar_plugin_sbr=yes])
+AC_MSG_CHECKING([whether to build the thunar-sbr plugin])
+AM_CONDITIONAL([THUNAR_PLUGIN_SBR], [test x"$ac_bm_thunar_plugin_sbr" = x"yes"])
+AC_MSG_RESULT([$ac_bm_thunar_plugin_sbr])
+
+dnl Check for PCRE (for the "Search & Replace" renamer)
+XDT_CHECK_OPTIONAL_PACKAGE([PCRE], [libpcre], [6.0], [pcre], [Regular expression support])
+])
+
+
+
+dnl # BM_THUNAR_PLUGIN_TPA()
+dnl #
+dnl # Check whether the "Trash Panel Applet" plugin should
+dnl # be built and installed (this is actually a plugin
+dnl # for the Xfce panel, not for Thunar).
+dnl #
+AC_DEFUN([BM_THUNAR_PLUGIN_TPA],
+[
+AC_ARG_ENABLE([tpa-plugin], AC_HELP_STRING([--disable-tpa-plugin], [Don't build the thunar-tpa plugin, see plugins/thunar-tpa/README]),
+  [ac_bm_thunar_plugin_tpa=$enableval], [ac_bm_thunar_plugin_tpa=yes])
+if test x"$ac_bm_thunar_plugin_tpa" = x"yes"; then
+  XDT_CHECK_PACKAGE([LIBXFCE4PANEL], [libxfce4panel-2.0], [4.12.0],
+  [
+    ac_bm_thunar_plugin_tpa=yes
+  ],
+  [
+    dnl # Cannot build thunar-tpa if xfce4-panel is not installed
+    ac_bm_thunar_plugin_tpa=no
+  ])
+else
+  ac_bm_thunar_plugin_tpa=no
+fi
+AC_MSG_CHECKING([whether to build the thunar-tpa plugin])
+AM_CONDITIONAL([THUNAR_PLUGIN_TPA], [test x"$ac_bm_thunar_plugin_tpa" = x"yes"])
+AC_MSG_RESULT([$ac_bm_thunar_plugin_tpa])
+])
+
+
+
+dnl # BM_THUNAR_PLUGIN_UCA()
+dnl #
+dnl # Check whether the "User Customizable Actions" plugin
+dnl # should be built and installed.
+dnl #
+AC_DEFUN([BM_THUNAR_PLUGIN_UCA],
+[
+AC_ARG_ENABLE([uca-plugin], AC_HELP_STRING([--disable-uca-plugin], [Don't build the thunar-uca plugin, see plugins/thunar-uca/README]),
+  [ac_bm_thunar_plugin_uca=$enableval], [ac_bm_thunar_plugin_uca=yes])
+AC_MSG_CHECKING([whether to build the thunar-uca plugin])
+AM_CONDITIONAL([THUNAR_PLUGIN_UCA], [test x"$ac_bm_thunar_plugin_uca" = x"yes"])
+AC_MSG_RESULT([$ac_bm_thunar_plugin_uca])
+])
+
+dnl # BM_THUNAR_PLUGIN_WALLPAPER()
+dnl #
+dnl # Check whether the "Wallpaper" plugin
+dnl # should be built and installed.
+dnl #
+AC_DEFUN([BM_THUNAR_PLUGIN_WALLPAPER],
+[
+AC_ARG_ENABLE([wallpaper-plugin], AC_HELP_STRING([--disable-wallpaper-plugin], [Don't build the thunar-wallpaper plugin, see plugins/thunar-wallpaper/README]),
+  [ac_bm_thunar_plugin_wallpaper=$enableval], [ac_bm_thunar_plugin_wallpaper=yes])
+AC_MSG_CHECKING([whether to build the thunar-wallpaper plugin])
+AM_CONDITIONAL([THUNAR_PLUGIN_WALLPAPER], [test x"$ac_bm_thunar_plugin_wallpaper" = x"yes"])
+AC_MSG_RESULT([$ac_bm_thunar_plugin_wallpaper])
+if test x"$ac_bm_thunar_plugin_wallpaper" = x"yes"; then
+	AC_CHECK_PROG([xfconf_query_found], [xfconf-query], [yes], [no])
+	if test x"$xfconf_query_found" = x"no"; then
+		echo "***"
+		echo "*** xfconf-query was not found on your system."
+		echo "*** The wallpaper won't work without it installed."
+		echo "***"
+	fi
+fi
+])

compile

+#! /bin/sh
+# Wrapper for compilers which do not understand '-c -o'.
+
+scriptversion=2018-03-07.03; # UTC
+
+# Copyright (C) 1999-2018 Free Software Foundation, Inc.
+# Written by Tom Tromey <tromey@cygnus.com>.
+#
+# 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, 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, see <https://www.gnu.org/licenses/>.
+
+# As a special exception to the GNU General Public License, if you
+# distribute this file as part of a program that contains a
+# configuration script generated by Autoconf, you may include it under
+# the same distribution terms that you use for the rest of that program.
+
+# This file is maintained in Automake, please report
+# bugs to <bug-automake@gnu.org> or send patches to
+# <automake-patches@gnu.org>.
+
+nl='
+'
+
+# We need space, tab and new line, in precisely that order.  Quoting is
+# there to prevent tools from complaining about whitespace usage.
+IFS=" ""	$nl"
+
+file_conv=
+
+# func_file_conv build_file lazy
+# Convert a $build file to $host form and store it in $file
+# Currently only supports Windows hosts. If the determined conversion
+# type is listed in (the comma separated) LAZY, no conversion will
+# take place.
+func_file_conv ()
+{
+  file=$1
+  case $file in
+    / | /[!/]*) # absolute file, and not a UNC file
+      if test -z "$file_conv"; then
+	# lazily determine how to convert abs files
+	case `uname -s` in
+	  MINGW*)
+	    file_conv=mingw
+	    ;;
+	  CYGWIN*)
+	    file_conv=cygwin
+	    ;;
+	  *)
+	    file_conv=wine
+	    ;;
+	esac
+      fi
+      case $file_conv/,$2, in
+	*,$file_conv,*)
+	  ;;
+	mingw/*)
+	  file=`cmd //C echo "$file " | sed -e 's/"\(.*\) " *$/\1/'`
+	  ;;
+	cygwin/*)
+	  file=`cygpath -m "$file" || echo "$file"`
+	  ;;
+	wine/*)
+	  file=`winepath -w "$file" || echo "$file"`
+	  ;;
+      esac
+      ;;
+  esac
+}
+
+# func_cl_dashL linkdir
+# Make cl look for libraries in LINKDIR
+func_cl_dashL ()
+{
+  func_file_conv "$1"
+  if test -z "$lib_path"; then
+    lib_path=$file
+  else
+    lib_path="$lib_path;$file"
+  fi
+  linker_opts="$linker_opts -LIBPATH:$file"
+}
+
+# func_cl_dashl library
+# Do a library search-path lookup for cl
+func_cl_dashl ()
+{
+  lib=$1
+  found=no
+  save_IFS=$IFS
+  IFS=';'
+  for dir in $lib_path $LIB
+  do
+    IFS=$save_IFS
+    if $shared && test -f "$dir/$lib.dll.lib"; then
+      found=yes
+      lib=$dir/$lib.dll.lib
+      break
+    fi
+    if test -f "$dir/$lib.lib"; then
+      found=yes
+      lib=$dir/$lib.lib
+      break
+    fi
+    if test -f "$dir/lib$lib.a"; then
+      found=yes
+      lib=$dir/lib$lib.a
+      break
+    fi
+  done
+  IFS=$save_IFS
+
+  if test "$found" != yes; then
+    lib=$lib.lib
+  fi
+}
+
+# func_cl_wrapper cl arg...
+# Adjust compile command to suit cl
+func_cl_wrapper ()
+{
+  # Assume a capable shell
+  lib_path=
+  shared=:
+  linker_opts=
+  for arg
+  do
+    if test -n "$eat"; then
+      eat=
+    else
+      case $1 in
+	-o)
+	  # configure might choose to run compile as 'compile cc -o foo foo.c'.
+	  eat=1
+	  case $2 in
+	    *.o | *.[oO][bB][jJ])
+	      func_file_conv "$2"
+	      set x "$@" -Fo"$file"
+	      shift
+	      ;;
+	    *)
+	      func_file_conv "$2"
+	      set x "$@" -Fe"$file"
+	      shift
+	      ;;
+	  esac
+	  ;;
+	-I)
+	  eat=1
+	  func_file_conv "$2" mingw
+	  set x "$@" -I"$file"
+	  shift
+	  ;;
+	-I*)
+	  func_file_conv "${1#-I}" mingw
+	  set x "$@" -I"$file"
+	  shift
+	  ;;
+	-l)
+	  eat=1
+	  func_cl_dashl "$2"
+	  set x "$@" "$lib"
+	  shift
+	  ;;
+	-l*)
+	  func_cl_dashl "${1#-l}"
+	  set x "$@" "$lib"
+	  shift
+	  ;;
+	-L)
+	  eat=1
+	  func_cl_dashL "$2"
+	  ;;
+	-L*)
+	  func_cl_dashL "${1#-L}"
+	  ;;
+	-static)
+	  shared=false
+	  ;;
+	-Wl,*)
+	  arg=${1#-Wl,}
+	  save_ifs="$IFS"; IFS=','
+	  for flag in $arg; do
+	    IFS="$save_ifs"
+	    linker_opts="$linker_opts $flag"
+	  done
+	  IFS="$save_ifs"
+	  ;;
+	-Xlinker)
+	  eat=1
+	  linker_opts="$linker_opts $2"
+	  ;;
+	-*)
+	  set x "$@" "$1"
+	  shift
+	  ;;
+	*.cc | *.CC | *.cxx | *.CXX | *.[cC]++)
+	  func_file_conv "$1"
+	  set x "$@" -Tp"$file"
+	  shift
+	  ;;
+	*.c | *.cpp | *.CPP | *.lib | *.LIB | *.Lib | *.OBJ | *.obj | *.[oO])
+	  func_file_conv "$1" mingw
+	  set x "$@" "$file"
+	  shift
+	  ;;
+	*)
+	  set x "$@" "$1"
+	  shift
+	  ;;
+      esac
+    fi
+    shift
+  done
+  if test -n "$linker_opts"; then
+    linker_opts="-link$linker_opts"
+  fi
+  exec "$@" $linker_opts
+  exit 1
+}
+
+eat=
+
+case $1 in
+  '')
+     echo "$0: No command.  Try '$0 --help' for more information." 1>&2
+     exit 1;
+     ;;
+  -h | --h*)
+    cat <<\EOF
+Usage: compile [--help] [--version] PROGRAM [ARGS]
+
+Wrapper for compilers which do not understand '-c -o'.
+Remove '-o dest.o' from ARGS, run PROGRAM with the remaining
+arguments, and rename the output as expected.
+
+If you are trying to build a whole package this is not the
+right script to run: please start by reading the file 'INSTALL'.
+
+Report bugs to <bug-automake@gnu.org>.
+EOF
+    exit $?
+    ;;
+  -v | --v*)
+    echo "compile $scriptversion"
+    exit $?
+    ;;
+  cl | *[/\\]cl | cl.exe | *[/\\]cl.exe | \
+  icl | *[/\\]icl | icl.exe | *[/\\]icl.exe )
+    func_cl_wrapper "$@"      # Doesn't return...
+    ;;
+esac
+
+ofile=
+cfile=
+
+for arg
+do
+  if test -n "$eat"; then
+    eat=
+  else
+    case $1 in
+      -o)
+	# configure might choose to run compile as 'compile cc -o foo foo.c'.
+	# So we strip '-o arg' only if arg is an object.
+	eat=1
+	case $2 in
+	  *.o | *.obj)
+	    ofile=$2
+	    ;;
+	  *)
+	    set x "$@" -o "$2"
+	    shift
+	    ;;
+	esac
+	;;
+      *.c)
+	cfile=$1
+	set x "$@" "$1"
+	shift
+	;;
+      *)
+	set x "$@" "$1"
+	shift
+	;;
+    esac
+  fi
+  shift
+done
+
+if test -z "$ofile" || test -z "$cfile"; then
+  # If no '-o' option was seen then we might have been invoked from a
+  # pattern rule where we don't need one.  That is ok -- this is a
+  # normal compilation that the losing compiler can handle.  If no
+  # '.c' file was seen then we are probably linking.  That is also
+  # ok.
+  exec "$@"
+fi
+
+# Name of file we expect compiler to create.
+cofile=`echo "$cfile" | sed 's|^.*[\\/]||; s|^[a-zA-Z]:||; s/\.c$/.o/'`
+
+# Create the lock directory.
+# Note: use '[/\\:.-]' here to ensure that we don't use the same name
+# that we are using for the .o file.  Also, base the name on the expected
+# object file name, since that is what matters with a parallel build.
+lockdir=`echo "$cofile" | sed -e 's|[/\\:.-]|_|g'`.d
+while true; do
+  if mkdir "$lockdir" >/dev/null 2>&1; then
+    break
+  fi
+  sleep 1
+done
+# FIXME: race condition here if user kills between mkdir and trap.
+trap "rmdir '$lockdir'; exit 1" 1 2 15
+
+# Run the compile.
+"$@"
+ret=$?
+
+if test -f "$cofile"; then
+  test "$cofile" = "$ofile" || mv "$cofile" "$ofile"
+elif test -f "${cofile}bj"; then
+  test "${cofile}bj" = "$ofile" || mv "${cofile}bj" "$ofile"
+fi
+
+rmdir "$lockdir"
+exit $ret
+
+# Local Variables:
+# mode: shell-script
+# sh-indentation: 2
+# eval: (add-hook 'before-save-hook 'time-stamp)
+# time-stamp-start: "scriptversion="
+# time-stamp-format: "%:y-%02m-%02d.%02H"
+# time-stamp-time-zone: "UTC0"
+# time-stamp-end: "; # UTC"
+# End: