Translation of "Vagrant is a tool for building and distributing virtualized development environments."

Vagrant is a tool for building and distributing virtualized development environments.

"Creating home directory since it doesn't exist: %{directory}"

#-------------------------------------------------------------------------------
# Translations for exception classes
#-------------------------------------------------------------------------------

The base VM with the name '%{name}' was not found.

Box '%{name}' could not be found.

The chef (either `chef-solo` or `chef-client`) binary was not found on
the VM and is required for chef provisioning. Please verify that chef
is installed and that the binary is available on the PATH.

This command requires that a Vagrant environment be properly passed in as the last parameter.

There was a problem with the configuration of Vagrant. The error message(s)
are printed below:
%{messages}

The local file Vagrant uses to store data ".vagrant" already exists
and is a directory! If you are in your home directory, then please run
this command in another directory. If you aren't in a home directory,
then please rename ".vagrant" to something else, or configure Vagrant
to use another filename by modifying `config.vagrant.dotfile_name`.

Vagrant exited after cleanup due to external interrupt.

A multi-vm environment is required for name specification to this command.

`vagrant %{command}` requires a specific VM name to target in a multi-VM environment.

No Vagrant environment detected. Run `vagrant init` to set one up.

SSH authentication failed! This is typically caused by the public/private
keypair for the SSH user not being properly set on the guest VM. Please
verify that the guest VM is setup with the proper public key, and that
the private key path for Vagrant is setup properly as well.

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
%{command}

SSH connection was refused! This usually happens if the VM failed to
boot properly. Some steps to try to fix this: First, try reloading your
VM with `vagrant reload`, since a simple restart sometimes fixes things.
If that doesn't work, destroy your VM and recreate it with a `vagrant destroy`
followed by a `vagrant up`. If that doesn't work, contact a Vagrant
maintainer (support channels listed on the website) for more assistance.