perltidy Files

## Changes from version 2020 01 10  to version 2020 06 19

    - Added support for Switch::Plain syntax, issue git #31.

    - Fixed minor problem where trailing 'unless' clauses were not 
      getting vertically aligned.

    - Added a parameter --logical-padding or -lop to allow logical padding
      to be turned off.  Requested by git #29. This flag is on by default.
      The man pages have examples.

    - Added a parameter -kpit=n to control spaces inside of parens following
      certain keywords, requested in git#26. This flag is off by default.

    - Added fix for git#25, improve vertical alignment for long lists with
      varying numbers of items per line.

    - calls to the module Perl::Tidy can now capture any output produced
      by a debug flag or one of the 'tee' flags through the new 'debugfile' and
      'teefile' call parameters.  These output streams are rarely used but
      they are now treated the same as any 'logfile' stream.

    - add option --break-at-old-semicolon-breakpoints', -bos, requested 
      in RT#131644.  This flag will keep lines beginning with a semicolon.

    - Added --use-unicode-gcstring to control use of Unicode::GCString for
      evaluating character widths of encoded data.  The default is 
      not to use this (--nouse-unicode-gcstring). If this flag is set,
      perltidy will look for Unicode::GCString and, if found, will use it 
      to evaluate character display widths.  This can improve displayed
      vertical alignment for files with wide characters.  It is a nice
      feature but it is off by default to avoid conflicting formatting
      when there are multiple developers.  Perltidy installation does not 
      require Unicode::GCString, so users wanting to use this feature need 
      set this flag and also to install Unicode::GCString separately.

    - Added --character-encoding=guess or -guess to have perltidy guess
      if a file (or other input stream) is encoded as -utf8 or some 
      other single-byte encoding. This is useful when processing a mixture 
      of file types, such as utf8 and latin-1.

      Please Note: The default encoding has been set to be 'guess'
      instead of 'none'. This seems like the best default, since 
      it allows perltidy work properly with both
      utf8 files and older latin-1 files.  The guess mode uses Encode::Guess,
      which is included in standard perl distributions, and only tries to 
      guess if a file is utf8 or not, never any other encoding.  If the guess is 
      utf8, and if the file successfully decodes as utf8, then it the encoding 
      is assumed to be utf8.  Otherwise, no encoding is assumed. 
      If you do not want to use this new default guess mode, or have a 
      problem with it, you can set --character-encoding=none (the previous 
      default) or --character-encoding=utf8 (if you deal with utf8 files).

    - Specific encodings of input files other than utf8 may now be given, for
      example --character-encoding=euc-jp.

    - Fix for git#22, Preserve function signature on a single line. An
      unwanted line break was being introduced when a closing signature paren
      followed a closing do brace.

    - Fix RT#132059, the -dac parameter was not working and caused an error exit

    - When -utf8 is used, any error output is encoded as utf8

    - Fix for git#19, adjust line break around an 'xor'

    - Fix for git#18, added warning for missing comma before unknown bare word.