mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Merge branch 'master' into loc_20180220_master

Browse source
This commit is contained in:
Nick Guerrera 2018-02-22 16:02:54 -08:00
commit 8a1ff2eac0
137 changed files with 6388 additions and 3168 deletions
Download patch file Download diff file Expand all files Collapse all files

182
src/dotnet/xlf/CommonLocalizableStrings.es.xlf
View file

@ -679,85 +679,21 @@
<target state="translated">XML no válido: {0}</target>
<note />
</trans-unit>
<trans-unit id="NuGetConfigurationFileDoesNotExist">
<source>NuGet configuration file {0} does not exist.</source>
<target state="translated">El archivo de configuración de NuGet {0} no existe.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxNeedLogout">
<source>Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</source>
<target state="translated">Dado que acaba de instalar el SDK de .Net Core, tendrá que cerrar sesión o reiniciarla antes de ejecutar la herramienta instalada.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash. You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="translated">No se encuentra la ruta de acceso del ejecutable de las herramientas. Compruebe que se ha agregado {0} a su valor PATH.
Si usa bash, puede hacerlo con la ejecución del comando siguiente:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</source>
<target state="translated">Dado que acaba de instalar el SDK de .Net Core, tendrá que volver a abrir la terminal antes de ejecutar la herramienta instalada.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
If you are using bash, You can do this by running the following command:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="translated">No se encuentra la ruta de acceso del ejecutable de las herramientas. Compruebe que se ha agregado {0} a su valor PATH.
Si usa bash, puede hacerlo con la ejecución del comando siguiente:
cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="translated">No se pudo instalar la herramienta {0}. Ya existe un comando con el mismo nombre.</target>
<note />
</trans-unit>
<trans-unit id="FailInstallToolPermission">
<source>Failed to change permission:
Error: {0}
Output: {1}</source>
<target state="translated">No se pudo cambiar el permiso:
Error: {0}
Salida: {1}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsNeedReopen">
<source>Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</source>
<target state="translated">Dado que acaba de instalar el SDK de .Net Core, tendrá que volver a abrir la ventana del símbolo del sistema antes de ejecutar la herramienta instalada.</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstruction">
<source>Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="translated">No se encuentra la ruta de acceso del ejecutable de las herramientas. Compruebe que se ha agregado {0} a su valor PATH.
Para ello, puede ejecutar el comando siguiente:
setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
<trans-unit id="ToolPackageMissingEntryPointFile">
<source>Package '{0}' is missing entry point file {1}.</source>
<target state="translated">Al paquete "{0}" le falta el archivo de punto de entrada {1}.</target>
@ -794,8 +730,122 @@ setx PATH "%PATH%;{1}"</target>
<note />
</trans-unit>
<trans-unit id="ToolPackageConflictPackageId">
<source>Tool '{0}' is already installed.</source>
<target state="translated">La herramienta “{0}” ya está instalada.</target>
<source>Tool '{0}' (version '{1}') is already installed.</source>
<target state="needs-review-translation">La herramienta “{0}” ya está instalada.</target>
<note />
</trans-unit>
<trans-unit id="ShellShimConflict">
<source>Command '{0}' conflicts with an existing command from another tool.</source>
<target state="new">Command '{0}' conflicts with an existing command from another tool.</target>
<note />
</trans-unit>
<trans-unit id="CannotCreateShimForEmptyExecutablePath">
<source>Cannot create shell shim for an empty executable path.</source>
<target state="new">Cannot create shell shim for an empty executable path.</target>
<note />
</trans-unit>
<trans-unit id="CannotCreateShimForEmptyCommand">
<source>Cannot create shell shim for an empty command.</source>
<target state="new">Cannot create shell shim for an empty command.</target>
<note />
</trans-unit>
<trans-unit id="FailedToRetrieveToolConfiguration">
<source>Failed to retrieve tool configuration: {0}</source>
<target state="new">Failed to retrieve tool configuration: {0}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstructions">
<source>Tools directory '{0}' is not currently on the PATH environment variable.
If you are using bash, you can add it to your profile by running the following command:
cat &lt;&lt; \EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{0}"
EOF
You can add it to the current session by running the following command:
export PATH="$PATH:{0}"
</source>
<target state="new">Tools directory '{0}' is not currently on the PATH environment variable.
If you are using bash, you can add it to your profile by running the following command:
cat &lt;&lt; \EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{0}"
EOF
You can add it to the current session by running the following command:
export PATH="$PATH:{0}"
</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathOSXManualInstructions">
<source>Tools directory '{0}' is not currently on the PATH environment variable.
If you are using bash, you can add it to your profile by running the following command:
cat &lt;&lt; \EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{0}"
EOF
You can add it to the current session by running the following command:
export PATH="$PATH:{0}"
</source>
<target state="new">Tools directory '{0}' is not currently on the PATH environment variable.
If you are using bash, you can add it to your profile by running the following command:
cat &lt;&lt; \EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{0}"
EOF
You can add it to the current session by running the following command:
export PATH="$PATH:{0}"
</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathWindowsManualInstructions">
<source>Tools directory '{0}' is not currently on the PATH environment variable.
You can add the directory to the PATH by running the following command:
setx PATH "%PATH%;{0}"
</source>
<target state="new">Tools directory '{0}' is not currently on the PATH environment variable.
You can add the directory to the PATH by running the following command:
setx PATH "%PATH%;{0}"
</target>
<note />
</trans-unit>
<trans-unit id="FailedToCreateShellShim">
<source>Failed to create tool shim for command '{0}': {1}</source>
<target state="new">Failed to create tool shim for command '{0}': {1}</target>
<note />
</trans-unit>
<trans-unit id="FailedToRemoveShellShim">
<source>Failed to remove tool shim for command '{0}': {1}</source>
<target state="new">Failed to remove tool shim for command '{0}': {1}</target>
<note />
</trans-unit>
<trans-unit id="FailedSettingShimPermissions">
<source>Failed to set user executable permissions for shell shim: {0}</source>
<target state="new">Failed to set user executable permissions for shell shim: {0}</target>
<note />
</trans-unit>
<trans-unit id="FailedToInstallToolPackage">
<source>Failed to install tool package '{0}': {1}</source>
<target state="new">Failed to install tool package '{0}': {1}</target>
<note />
</trans-unit>
<trans-unit id="FailedToUninstallToolPackage">
<source>Failed to uninstall tool package '{0}': {1}</source>
<target state="new">Failed to uninstall tool package '{0}': {1}</target>
<note />
</trans-unit>
</body>