Fixes optional instructions regarding PR ##801 (missing 'set')

shell=/bin/bash needs to start with `set` in order to actually make vim+fish work correctly.

Removes example script lines which breaks install

Add note about adding shell=/bin/bash to .vimrc for fish shell users

See #690

According to this discussion https://github.com/VundleVim/Vundle.vim/issues/713 this plugin is simply an example, but the example seems to consistently break the installation process.

If this is the case better to remove it.

Another example of it causing problems: https://github.com/VundleVim/Vundle.vim/issues/784

refine Chinese (Traditional) translations

Fixes a typo corresponding to f4cea90

* Updates readme to use github markdown checkmarks

A traditional Chinese version of the updated `README_ZH_CN.md`.

Update README_ZH_CN.md

Fix typo

Updates traditional Chinese readme translation per English readme update (corresponding to 52f3443)

A traditional Chinese version of the updated `README_ZH_CN.md`.

Removes BOM and CR

Updates example in readme to better explain the 'name' option

They are added by Notepad on M$ Windows.

Adds traditional Chinese version of README_ZH_TW.md

This is done based on the simplified Chinese version at commit 232cb92.
Traditional Chinese is used by people in Taiwan, Hong Kong and Macao.

Setting Vundle key mappings to be silent

Add 'vundlelog' filetype + settings/highlighting

i have added an readme_zh_cn.md in to this repo!

Repository references to VundleVim instead of gmarik

incorrect URL and updated references to ':Bundle' commands to ':Plugin'
commands

Fixing 'modifiable', 'bufhidden', and other small buffer properties for Vundle buffers

buffers will not persist after they're closed.

Update repository references in README

Saves a 301 redirect and removes a tad bit of confusion when `git
clone`-ing Vundle when installing.

Prevent insecure plugin names.

Plugins' names which contain '../', '$HOME', '%h', '..\', etc.
can be dangerous.
Use a sensible whitelist for plugin names and prevent its expansion.

Refactor global variables to autoload variables

The setting of the default values for the autoload variables is moved out of
any function.  One reason being that these settings do not depend on the
argument of the function.  The second being that Vim will source the autoload
script if an undefined autoload variable is referenced and the file is
expected to define the variable (see :help autoload).

All global variables that are not part of the public API (mentioned in the
documentation) are turned into autoload variables.  This is intended to give
all global variables defined by Vundle.vim a common prefix.  The variable
g:default_git_proto is part of the public API and is therefor not changed.
This is the only exception.

Changed:
   g:bundle_dir            -> vundle#bundle_dir
   g:bundles               -> vundle#bundles
   g:updated_bundles       -> vundle#updated_bundles
   g:vundle_lazy_load      -> vundle#lazy_load
   g:vundle_log            -> vundle#log
Unchanged:
   g:default_git_proto

If it was loaded, unload the log buffer before editing it.  Otherwise the
editing command can "hang" if the user has `set hidden`.

This problem was originally discovered with the VundleChangelog command and
the analogous fix was applied in 7d9b10.  See github issue #468 for more.

These variables only occur in one file each.  By making them script local
variables this is "documented" in the code.  At the same time the global
namespace is polluted less.

Changed:
    g:bundle_names          -> s:bundle_names
    g:vundle_last_status    -> s:last_status
    g:vundle_log_file       -> s:log_file
    g:vundle_view           -> s:view

The variable is script local to autoload/vundle/scripts.vim since #468.

The command `silent pedit ...` was causing trouble if the user had `set
hidden`.  Now we `bdelete` the changelog buffer before editing it anew.

Use svg instead of png to get better image quality