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

LOC CHECKIN | cli master | 20180202

Browse source
This commit is contained in:
Zbyněk Sailer 2018-02-02 12:31:06 +01:00
parent 78904831f9
commit f0be5cc1ef
52 changed files with 645 additions and 645 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -676,46 +676,46 @@
</trans-unit>
<trans-unit id="CannotBeNullOrWhitespace">
<source>Cannot be null or whitespace.</source>
<target state="new">Cannot be null or whitespace.</target>
<target state="translated">No puede ser nulo ni un espacio en blanco.</target>
<note />
</trans-unit>
<trans-unit id="ContainInvalidCharacters">
<source>Contains one or more invalid characters: {0}</source>
<target state="new">Contains one or more invalid characters: {0}</target>
<target state="translated">Contiene uno o varios caracteres no válidos: {0}</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingsInvalidXml">
<source>The tool's settings file is invalid xml.
{0}</source>
<target state="new">The tool's settings file is invalid xml.
<target state="translated">El archivo de configuración de la herramienta es un xml no válido.
{0}</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingInvalidRunner">
<source>The tool's settings file has non "dotnet" as runner.</source>
<target state="new">The tool's settings file has non "dotnet" as runner.</target>
<target state="translated">El archivo de configuración de la herramienta tiene un ejecutor diferente de "dotnet".</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingMoreThanOneCommand">
<source>The tool's settings file has more than one command defined.</source>
<target state="new">The tool's settings file has more than one command defined.</target>
<target state="translated">El archivo de configuración de la herramienta tiene más de un comando definido.</target>
<note />
</trans-unit>
<trans-unit id="ToolSettingsContainError">
<source>The tool's settings file contains error.
{0}</source>
<target state="new">The tool's settings file contains error.
<target state="translated">El archivo de configuración de la herramienta contiene un error.
{0}</target>
<note />
</trans-unit>
<trans-unit id="NuGetConfigurationFileDoesNotExist">
<source>NuGet configuration file {0} does not exist.</source>
<target state="new">NuGet configuration file {0} does not exist.</target>
<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="new">Since you just installed the .NET Core SDK, you will need to logout or restart your session before running the tool you installed.</target>
<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">
@ -726,8 +726,8 @@ cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">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:
<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
@ -737,7 +737,7 @@ EOF</target>
</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="new">Since you just installed the .NET Core SDK, you will need to reopen terminal before running the tool you installed.</target>
<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">
@ -748,8 +748,8 @@ cat &lt;&lt; EOF &gt;&gt; ~/.bash_profile
# Add .NET Core SDK tools
export PATH="$PATH:{1}"
EOF</source>
<target state="new">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:
<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
@ -759,21 +759,21 @@ EOF</target>
</trans-unit>
<trans-unit id="FailInstallToolSameName">
<source>Failed to install tool {0}. A command with the same name already exists.</source>
<target state="new">Failed to install tool {0}. A command with the same name already exists.</target>
<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="new">Failed to change permission:
<target state="translated">No se pudo cambiar el permiso:
Error: {0}
Output: {1}</target>
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="new">Since you just installed the .NET Core SDK, you will need to reopen the Command Prompt window before running the tool you installed.</target>
<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">
@ -781,20 +781,20 @@ Output: {1}</target>
You can do this by running the following command:
setx PATH "%PATH%;{1}"</source>
<target state="new">Cannot find the tools executable path. Please ensure {0} is added to your PATH.
You can do this by running the following command:
<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="new">Package '{0}' is missing entry point file {1}.</target>
<target state="translated">Al paquete "{0}" le falta el archivo de punto de entrada {1}.</target>
<note />
</trans-unit>
<trans-unit id="ToolPackageMissingSettingsFile">
<source>Package '{0}' is missing tool settings file DotnetToolSettings.xml.</source>
<target state="new">Package '{0}' is missing tool settings file DotnetToolSettings.xml.</target>
<target state="translated">Al paquete "{0}" le falta el archivo de configuración de herramientas DotnetToolSettings.xml.</target>
<note />
</trans-unit>
</body>