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

LOC CHECKIN | cli master | 20180315

Browse source
This commit is contained in:
Zbyněk Sailer 2018-03-15 15:00:28 +01:00 • committed by Peter Huene
parent 60d71618be
commit e4e665d98a
No known key found for this signature in database
GPG key ID: E1D265D820213D6A
91 changed files with 902 additions and 837 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -721,27 +721,27 @@
</trans-unit>
<trans-unit id="ToolPackageConflictPackageId">
<source>Tool '{0}' (version '{1}') is already installed.</source>
<target state="needs-review-translation">La herramienta “{0}” ya está instalada.</target>
<target state="translated">La herramienta "{0}" (versión "{1}") 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>
<target state="translated">El comando "{0}" está en conflicto con un comando existente de otra herramienta.</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>
<target state="translated">No se pueden crear las correcciones de compatibilidad (shim) de shell para una ruta ejecutable vacía.</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>
<target state="translated">No se pueden crear las correcciones de compatibilidad (shim) de shell para un comando vacío.</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>
<target state="translated">Error al recuperar la configuración de la herramienta: {0}</target>
<note />
</trans-unit>
<trans-unit id="EnvironmentPathLinuxManualInstructions">
@ -757,15 +757,15 @@ 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:
<target state="translated">El directorio de herramientas "{0}" no está actualmente en la variable de entorno PATH.
Si usa bash, puede agregarlo a su perfil mediante la ejecución de comando siguiente:
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:
Puede agregarlo a la sesión actual mediante la ejecución del comando siguiente:
export PATH="$PATH:{0}"
</target>
@ -784,15 +784,15 @@ 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:
<target state="translated">El directorio de herramientas "{0}" no está actualmente en la variable de entorno PATH.
Si usa bash, puede agregarlo a su perfil mediante la ejecución de comando siguiente:
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:
Puede agregarlo a la sesión actual mediante la ejecución del comando siguiente:
export PATH="$PATH:{0}"
</target>
@ -805,9 +805,9 @@ 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.
<target state="translated">El directorio de herramientas "{0}" no está actualmente en la variable de entorno PATH.
You can add the directory to the PATH by running the following command:
Puede agregar el directorio a PATH mediante la ejecución del comando siguiente:
setx PATH "%PATH%;{0}"
</target>
@ -815,52 +815,52 @@ setx PATH "%PATH%;{0}"
</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>
<target state="translated">No se pudieron crear correcciones de compatibilidad (shim) de herramientas para el comando "{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>
<target state="translated">No se pudieron quitar correcciones de compatibilidad (shim) de herramientas para el comando "{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>
<target state="translated">No se pudieron establecer los permisos ejecutables del usuario para las correcciones de compatibilidad (shim) de shell: {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>
<target state="translated">No se pudo instalar el paquete de herramientas "{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>
<target state="translated">No se pudo desinstalar el paquete de herramientas "{0}": {1}</target>
<note />
</trans-unit>
<trans-unit id="ColumnMaxWidthMustBeGreaterThanZero">
<source>Column maximum width must be greater than zero.</source>
<target state="new">Column maximum width must be greater than zero.</target>
<target state="translated">El ancho máximo de la columna debe ser superior a cero.</target>
<note />
</trans-unit>
<trans-unit id="MissingToolEntryPointFile">
<source>Entry point file '{0}' for command '{1}' was not found in the package.</source>
<target state="new">Entry point file '{0}' for command '{1}' was not found in the package.</target>
<target state="translated">El archivo de punto de entrada "{0}" para el comando "{1}" no se encontró en el paquete.</target>
<note />
</trans-unit>
<trans-unit id="MissingToolSettingsFile">
<source>Settings file 'DotnetToolSettings.xml' was not found in the package.</source>
<target state="new">Settings file 'DotnetToolSettings.xml' was not found in the package.</target>
<target state="translated">El archivo de configuración "DotnetToolSettings.xml" no se encontró en el paquete.</target>
<note />
</trans-unit>
<trans-unit id="FailedToFindStagedToolPackage">
<source>Failed to find staged tool package '{0}'.</source>
<target state="new">Failed to find staged tool package '{0}'.</target>
<target state="translated">No se pudo encontrar el paquete de herramientas almacenado provisionalmente "{0}".</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingsInvalidLeadingDotCommandName">
<source>The command name '{0}' cannot begin with a leading dot (.).</source>
<target state="new">The command name '{0}' cannot begin with a leading dot (.).</target>
<source>Command '{0}' has a leading dot.</source>
<target state="translated">El comando "{0}" tiene un punto al principio.</target>
<note />
</trans-unit>
</body>