mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions
dotnet-installer/src/dotnet/commands/dotnet-tool/install/xlf/LocalizableStrings.it.xlf

124 lines
6.4 KiB
Text
Raw Normal View History

Refactor install command localizable strings. This commit moves the `tool` subcommand strings into its own resource file, rather than putting them into the `install` command's resource file. This better follows the patterns of other commands, such as `add`, and enables subcommands to isolate their string resources from one another. As part of this commit, the `install tool` string resources were cleaned up.
2018-01-16 12:59:34 -08:00
<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-transitional.xsd">
<file datatype="xml" source-language="en" target-language="it" original="../LocalizableStrings.resx">
<body>
<trans-unit id="InstallationSucceeded">
Better using facing string (#8809) Fix #8728 Fix #8369
2018-03-16 17:00:14 -07:00
<source>You can invoke the tool using the following command: {0}
Implement uninstall tool command. This commit implements the `uninstall tool` command. The `uninstall tool` command is responsible for uninstalling global tools that are installed with the `install tool` command. This commit heavily refactors the ToolPackage and ShellShim namespaces to better support the operations required for the uninstall command. Several string resources have been updated to be more informative or to correct oddly structured sentences. This commit also fixes `--version` on the install command not supporting ranges and wildcards. Fixes #8549. Issue #8485 is partially fixed by this commit (`--prerelease` is not yet implemented).
2018-01-28 13:35:04 -08:00
Tool '{1}' (version '{2}') was successfully installed.</source>
LOC CHECKIN | cli master | 20180315
2018-03-15 15:00:28 +01:00
<target state="translated">Se non sono presenti istruzioni aggiuntive, è possibile digitare il comando seguente per richiamare lo strumento: {0}
Lo strumento '{1}' (versione '{2}') è stato installato.</target>
Refactor install command localizable strings. This commit moves the `tool` subcommand strings into its own resource file, rather than putting them into the `install` command's resource file. This better follows the patterns of other commands, such as `add`, and enables subcommands to isolate their string resources from one another. As part of this commit, the `install tool` string resources were cleaned up.
2018-01-16 12:59:34 -08:00
<note />
</trans-unit>
<trans-unit id="PackageIdArgumentDescription">
<source>NuGet Package Id of the tool to install.</source>
LOC CHECKIN | cli master | 20180202
2018-02-02 12:31:06 +01:00
<target state="translated">ID pacchetto NuGet dello strumento da installare.</target>
Refactor install command localizable strings. This commit moves the `tool` subcommand strings into its own resource file, rather than putting them into the `install` command's resource file. This better follows the patterns of other commands, such as `add`, and enables subcommands to isolate their string resources from one another. As part of this commit, the `install tool` string resources were cleaned up.
2018-01-16 12:59:34 -08:00
<note />
</trans-unit>
<trans-unit id="CommandDescription">
<source>Installs a tool for use on the command line.</source>
LOC CHECKIN | cli master | 20180202
2018-02-02 12:31:06 +01:00
<target state="translated">Installa uno strumento da usare sulla riga di comando.</target>
Refactor install command localizable strings. This commit moves the `tool` subcommand strings into its own resource file, rather than putting them into the `install` command's resource file. This better follows the patterns of other commands, such as `add`, and enables subcommands to isolate their string resources from one another. As part of this commit, the `install tool` string resources were cleaned up.
2018-01-16 12:59:34 -08:00
<note />
</trans-unit>
<trans-unit id="ConfigFileOptionDescription">
<source>The NuGet configuration file to use.</source>
LOC CHECKIN | cli master | 20180202
2018-02-02 12:31:06 +01:00
<target state="translated">File di configurazione NuGet da usare.</target>
Refactor install command localizable strings. This commit moves the `tool` subcommand strings into its own resource file, rather than putting them into the `install` command's resource file. This better follows the patterns of other commands, such as `add`, and enables subcommands to isolate their string resources from one another. As part of this commit, the `install tool` string resources were cleaned up.
2018-01-16 12:59:34 -08:00
<note />
</trans-unit>
<trans-unit id="FrameworkOptionDescription">
<source>The target framework to install the tool for.</source>
LOC CHECKIN | cli master | 20180202
2018-02-02 12:31:06 +01:00
<target state="translated">Framework di destinazione per cui installare lo strumento.</target>
Refactor install command localizable strings. This commit moves the `tool` subcommand strings into its own resource file, rather than putting them into the `install` command's resource file. This better follows the patterns of other commands, such as `add`, and enables subcommands to isolate their string resources from one another. As part of this commit, the `install tool` string resources were cleaned up.
2018-01-16 12:59:34 -08:00
<note />
</trans-unit>
<trans-unit id="VersionOptionDescription">
<source>Version of the tool package in NuGet.</source>
LOC CHECKIN | cli master | 20180202
2018-02-02 12:31:06 +01:00
<target state="translated">Versione del pacchetto dello strumento in NuGet.</target>
Refactor install command localizable strings. This commit moves the `tool` subcommand strings into its own resource file, rather than putting them into the `install` command's resource file. This better follows the patterns of other commands, such as `add`, and enables subcommands to isolate their string resources from one another. As part of this commit, the `install tool` string resources were cleaned up.
2018-01-16 12:59:34 -08:00
<note />
</trans-unit>
<trans-unit id="PackageIdArgumentName">
<source>PACKAGE_ID</source>
LOC CHECKIN | cli master | 20180202
2018-02-02 12:31:06 +01:00
<target state="translated">PACKAGE_ID</target>
Refactor install command localizable strings. This commit moves the `tool` subcommand strings into its own resource file, rather than putting them into the `install` command's resource file. This better follows the patterns of other commands, such as `add`, and enables subcommands to isolate their string resources from one another. As part of this commit, the `install tool` string resources were cleaned up.
2018-01-16 12:59:34 -08:00
<note />
</trans-unit>
Fix missing package id error message for install tool command. This commit fixes the error message that is displayed when the `install tool` command is not given a package id to install. Previously, only `packageId` was output, which was confusing. Fixes #8381.
2018-01-16 13:57:26 -08:00
<trans-unit id="SpecifyExactlyOnePackageId">
<source>Please specify one tool Package Id to install.</source>
LOC CHECKIN | cli master | 20180202
2018-02-02 12:31:06 +01:00
<target state="translated">Specificare un ID pacchetto dello strumento da installare.</target>
Fix missing package id error message for install tool command. This commit fixes the error message that is displayed when the `install tool` command is not given a package id to install. Previously, only `packageId` was output, which was confusing. Fixes #8381.
2018-01-16 13:57:26 -08:00
<note />
</trans-unit>
[tools] Integrate NuGet (#8414) * Integrate NuGet ask * Update NuGet version. Rely on NuGet to filter TFM. And use asset.json to find entrypoint * Update XML file to per TFM * Add extra property to the fake project according to nuget * Treat nuget fallback folder as offline cache for tool * Require -g to install global tool * Copy test asset during test project build * Address code review on LockFileMatchChecker * Get NETCorePlatformsImplicitPackageVersion from PackageDefinitions * Edit and add missing loc * Change LockFileMatchChecker to local function * Adding comment * Add to content instead of copy * Download platform package instead * disable SDK side implicit NuGetFallbackFolder * merge loc * Revert extra line * use a prerelease platforms version that supports alpine
2018-01-19 17:15:34 -08:00
<trans-unit id="GlobalOptionDescription">
<source>Install user wide.</source>
LOC CHECKIN | cli master | 20180202
2018-02-02 12:31:06 +01:00
<target state="translated">Esegue l'installazione a livello di utente.</target>
[tools] Integrate NuGet (#8414) * Integrate NuGet ask * Update NuGet version. Rely on NuGet to filter TFM. And use asset.json to find entrypoint * Update XML file to per TFM * Add extra property to the fake project according to nuget * Treat nuget fallback folder as offline cache for tool * Require -g to install global tool * Copy test asset during test project build * Address code review on LockFileMatchChecker * Get NETCorePlatformsImplicitPackageVersion from PackageDefinitions * Edit and add missing loc * Change LockFileMatchChecker to local function * Adding comment * Add to content instead of copy * Download platform package instead * disable SDK side implicit NuGetFallbackFolder * merge loc * Revert extra line * use a prerelease platforms version that supports alpine
2018-01-19 17:15:34 -08:00
<note />
</trans-unit>
<trans-unit id="InstallFullCommandNameLocalized">
<source>.NET Install Command</source>
LOC CHECKIN | cli master | 20180202
2018-02-02 12:31:06 +01:00
<target state="translated">Comando di installazione .NET</target>
[tools] Integrate NuGet (#8414) * Integrate NuGet ask * Update NuGet version. Rely on NuGet to filter TFM. And use asset.json to find entrypoint * Update XML file to per TFM * Add extra property to the fake project according to nuget * Treat nuget fallback folder as offline cache for tool * Require -g to install global tool * Copy test asset during test project build * Address code review on LockFileMatchChecker * Get NETCorePlatformsImplicitPackageVersion from PackageDefinitions * Edit and add missing loc * Change LockFileMatchChecker to local function * Adding comment * Add to content instead of copy * Download platform package instead * disable SDK side implicit NuGetFallbackFolder * merge loc * Revert extra line * use a prerelease platforms version that supports alpine
2018-01-19 17:15:34 -08:00
<note />
</trans-unit>
Add verbosity option to `install tool` command. This commit adds the `--verbosity` option to the `install tool` command. MSBuild/NuGet output is now controllable by the user and defaults to being "quiet". This enables users to see warnings from NuGet that otherwise would be swallowed unless NuGet returned a non-zero exit code. As a byproduct of this change, the exception handling and error messages related to obtaining tool packages was retooled. We no longer display `install tool` command line help for installation failures, as it should only be displayed for command line syntax errors. Fixes #8465.
2018-01-17 19:26:52 -08:00
<trans-unit id="InvalidToolConfiguration">
<source>The settings file in the tool's NuGet package is invalid: {0}</source>
LOC CHECKIN | cli master | 20180222
2018-02-22 17:07:50 +01:00
<target state="translated">Il file di impostazioni nel pacchetto NuGet dello strumento non è valido: {0}</target>
Add verbosity option to `install tool` command. This commit adds the `--verbosity` option to the `install tool` command. MSBuild/NuGet output is now controllable by the user and defaults to being "quiet". This enables users to see warnings from NuGet that otherwise would be swallowed unless NuGet returned a non-zero exit code. As a byproduct of this change, the exception handling and error messages related to obtaining tool packages was retooled. We no longer display `install tool` command line help for installation failures, as it should only be displayed for command line syntax errors. Fixes #8465.
2018-01-17 19:26:52 -08:00
<note />
</trans-unit>
<trans-unit id="ToolInstallationFailed">
<source>Tool '{0}' failed to install.</source>
LOC CHECKIN | cli master | 20180222
2018-02-22 17:07:50 +01:00
<target state="translated">Non è stato possibile installare lo strumento '{0}'.</target>
Add verbosity option to `install tool` command. This commit adds the `--verbosity` option to the `install tool` command. MSBuild/NuGet output is now controllable by the user and defaults to being "quiet". This enables users to see warnings from NuGet that otherwise would be swallowed unless NuGet returned a non-zero exit code. As a byproduct of this change, the exception handling and error messages related to obtaining tool packages was retooled. We no longer display `install tool` command line help for installation failures, as it should only be displayed for command line syntax errors. Fixes #8465.
2018-01-17 19:26:52 -08:00
<note />
</trans-unit>
<trans-unit id="ToolInstallationFailedContactAuthor">
<source>Tool '{0}' failed to install. Please contact the tool author for assistance.</source>
LOC CHECKIN | cli master | 20180222
2018-02-22 17:07:50 +01:00
<target state="translated">Non è stato possibile installare lo strumento '{0}'. Per assistenza, contattare l'autore dello strumento.</target>
Add verbosity option to `install tool` command. This commit adds the `--verbosity` option to the `install tool` command. MSBuild/NuGet output is now controllable by the user and defaults to being "quiet". This enables users to see warnings from NuGet that otherwise would be swallowed unless NuGet returned a non-zero exit code. As a byproduct of this change, the exception handling and error messages related to obtaining tool packages was retooled. We no longer display `install tool` command line help for installation failures, as it should only be displayed for command line syntax errors. Fixes #8465.
2018-01-17 19:26:52 -08:00
<note />
</trans-unit>
Implement uninstall tool command. This commit implements the `uninstall tool` command. The `uninstall tool` command is responsible for uninstalling global tools that are installed with the `install tool` command. This commit heavily refactors the ToolPackage and ShellShim namespaces to better support the operations required for the uninstall command. Several string resources have been updated to be more informative or to correct oddly structured sentences. This commit also fixes `--version` on the install command not supporting ranges and wildcards. Fixes #8549. Issue #8485 is partially fixed by this commit (`--prerelease` is not yet implemented).
2018-01-28 13:35:04 -08:00
<trans-unit id="ToolAlreadyInstalled">
<source>Tool '{0}' is already installed.</source>
LOC CHECKIN | cli master | 20180315
2018-03-15 15:00:28 +01:00
<target state="translated">Lo strumento '{0}' è già installato.</target>
Implement uninstall tool command. This commit implements the `uninstall tool` command. The `uninstall tool` command is responsible for uninstalling global tools that are installed with the `install tool` command. This commit heavily refactors the ToolPackage and ShellShim namespaces to better support the operations required for the uninstall command. Several string resources have been updated to be more informative or to correct oddly structured sentences. This commit also fixes `--version` on the install command not supporting ranges and wildcards. Fixes #8549. Issue #8485 is partially fixed by this commit (`--prerelease` is not yet implemented).
2018-01-28 13:35:04 -08:00
<note />
</trans-unit>
<trans-unit id="FailedToCreateToolShim">
<source>Failed to create shell shim for tool '{0}': {1}</source>
LOC CHECKIN | cli master | 20180315
2018-03-15 15:00:28 +01:00
<target state="translated">Non è stato possibile creare lo shim della shell per lo strumento '{0}': {1}</target>
Implement uninstall tool command. This commit implements the `uninstall tool` command. The `uninstall tool` command is responsible for uninstalling global tools that are installed with the `install tool` command. This commit heavily refactors the ToolPackage and ShellShim namespaces to better support the operations required for the uninstall command. Several string resources have been updated to be more informative or to correct oddly structured sentences. This commit also fixes `--version` on the install command not supporting ranges and wildcards. Fixes #8549. Issue #8485 is partially fixed by this commit (`--prerelease` is not yet implemented).
2018-01-28 13:35:04 -08:00
<note />
</trans-unit>
<trans-unit id="NuGetConfigurationFileDoesNotExist">
<source>NuGet configuration file '{0}' does not exist.</source>
LOC CHECKIN | cli master | 20180315
2018-03-15 15:00:28 +01:00
<target state="translated">Il file di configurazione NuGet '{0}' non esiste.</target>
Implement uninstall tool command. This commit implements the `uninstall tool` command. The `uninstall tool` command is responsible for uninstalling global tools that are installed with the `install tool` command. This commit heavily refactors the ToolPackage and ShellShim namespaces to better support the operations required for the uninstall command. Several string resources have been updated to be more informative or to correct oddly structured sentences. This commit also fixes `--version` on the install command not supporting ranges and wildcards. Fixes #8549. Issue #8485 is partially fixed by this commit (`--prerelease` is not yet implemented).
2018-01-28 13:35:04 -08:00
<note />
</trans-unit>
Add verbosity option to `install tool` command. This commit adds the `--verbosity` option to the `install tool` command. MSBuild/NuGet output is now controllable by the user and defaults to being "quiet". This enables users to see warnings from NuGet that otherwise would be swallowed unless NuGet returned a non-zero exit code. As a byproduct of this change, the exception handling and error messages related to obtaining tool packages was retooled. We no longer display `install tool` command line help for installation failures, as it should only be displayed for command line syntax errors. Fixes #8465.
2018-01-17 19:26:52 -08:00
<trans-unit id="ToolInstallationRestoreFailed">
<source>The tool package could not be restored.</source>
LOC CHECKIN | cli master | 20180222
2018-02-22 17:07:50 +01:00
<target state="translated">Non è stato possibile ripristinare il pacchetto dello strumento.</target>
Add verbosity option to `install tool` command. This commit adds the `--verbosity` option to the `install tool` command. MSBuild/NuGet output is now controllable by the user and defaults to being "quiet". This enables users to see warnings from NuGet that otherwise would be swallowed unless NuGet returned a non-zero exit code. As a byproduct of this change, the exception handling and error messages related to obtaining tool packages was retooled. We no longer display `install tool` command line help for installation failures, as it should only be displayed for command line syntax errors. Fixes #8465.
2018-01-17 19:26:52 -08:00
<note />
</trans-unit>
Fix case sensitivity of tool package identifiers. This commit fixes the case sensitivity of tool package identifiers. Previously the install and uninstall commands unintentionally required the tool package ids to specified in all lowercase for the install / uninstall to work. Fixes #8682.
2018-02-22 19:13:36 -08:00
<trans-unit id="InvalidNuGetVersionRange">
<source>Specified version '{0}' is not a valid NuGet version range.</source>
LOC CHECKIN | cli master | 20180315
2018-03-15 15:00:28 +01:00
<target state="translated">La versione specificata '{0}' non è un intervallo di versioni NuGet valido.</target>
Fix case sensitivity of tool package identifiers. This commit fixes the case sensitivity of tool package identifiers. Previously the install and uninstall commands unintentionally required the tool package ids to specified in all lowercase for the install / uninstall to work. Fixes #8682.
2018-02-22 19:13:36 -08:00
<note />
</trans-unit>
tool-path option -- "Session tool" (#8716) * Change to escape string via XML * tool-path option -- "Session tool" From the beginning design, shim and packageInstaller take package location from constructor and don't have assumption anymore. From previous discussion, tool-path will simply change global location to the one user want, and everything else is the same. However, this "override" need to happen during the call, that means InstallToolCommand will create different shim and packageInstaller object according to the tool-path during the call instead of constructor DI. * global package location change * block of leading dot as command name * Localization of tool-path option
2018-03-06 15:58:05 -08:00
<trans-unit id="InstallToolCommandNeedGlobalOrToolPath">
Update translations following merge with conflicts. Updating translation status for resource strings that changed upstream.
2018-03-19 14:00:57 -07:00
<source>Please specify either the global option (--global) or the tool path option (--tool-path).</source>
<target state="needs-review-translation">È necessario specificare global o tool-path.</target>
tool-path option -- "Session tool" (#8716) * Change to escape string via XML * tool-path option -- "Session tool" From the beginning design, shim and packageInstaller take package location from constructor and don't have assumption anymore. From previous discussion, tool-path will simply change global location to the one user want, and everything else is the same. However, this "override" need to happen during the call, that means InstallToolCommand will create different shim and packageInstaller object according to the tool-path during the call instead of constructor DI. * global package location change * block of leading dot as command name * Localization of tool-path option
2018-03-06 15:58:05 -08:00
<note />
</trans-unit>
<trans-unit id="InstallToolCommandInvalidGlobalAndToolPath">
Update translations following merge with conflicts. Updating translation status for resource strings that changed upstream.
2018-03-19 14:00:57 -07:00
<source>(--global) conflicts with the tool path option (--tool-path). Please specify only one of the options.</source>
<target state="needs-review-translation">Non è possibile specificare contemporaneamente global e tool-path come opzione.</target>
tool-path option -- "Session tool" (#8716) * Change to escape string via XML * tool-path option -- "Session tool" From the beginning design, shim and packageInstaller take package location from constructor and don't have assumption anymore. From previous discussion, tool-path will simply change global location to the one user want, and everything else is the same. However, this "override" need to happen during the call, that means InstallToolCommand will create different shim and packageInstaller object according to the tool-path during the call instead of constructor DI. * global package location change * block of leading dot as command name * Localization of tool-path option
2018-03-06 15:58:05 -08:00
<note />
</trans-unit>
<trans-unit id="ToolPathDescription">
Update translations following merge with conflicts. Updating translation status for resource strings that changed upstream.
2018-03-19 14:00:57 -07:00
<source>Location where the tool will be installed.</source>
<target state="needs-review-translation">Percorso dello shim per accedere allo strumento</target>
tool-path option -- "Session tool" (#8716) * Change to escape string via XML * tool-path option -- "Session tool" From the beginning design, shim and packageInstaller take package location from constructor and don't have assumption anymore. From previous discussion, tool-path will simply change global location to the one user want, and everything else is the same. However, this "override" need to happen during the call, that means InstallToolCommand will create different shim and packageInstaller object according to the tool-path during the call instead of constructor DI. * global package location change * block of leading dot as command name * Localization of tool-path option
2018-03-06 15:58:05 -08:00
<note />
</trans-unit>
Change --source to --source-feed and make it additional (#8833) Other than change source to source-feed and make it additional instead of exclusive. I changed source to be multiple. Because restore support multiple source https://github.com/Microsoft/dotnet/issues/361 As for mock. The offline feed and source feed is considered the same, so remove the category of “source”. I renamed source to “AdditionalFeed” because that is more accurate on implementation level. Note: NuGet feed don’t have order. Whichever responses the fastest, is the first. No change on restore. scripts/cli-test-env.sh change is due to mac 10.13 is finally added to RID graph. And it is “considered” one of the CLI supported RID
2018-03-19 22:22:45 -07:00
<trans-unit id="SourceFeedOptionDescription">
<source>Adds an additional NuGet package source to use during installation.</source>
<target state="new">Adds an additional NuGet package source to use during installation.</target>
<note />
</trans-unit>
<trans-unit id="SourceFeedOptionName">
<source>SOURCE_FEED</source>
<target state="new">SOURCE_FEED</target>
<note />
</trans-unit>
Refactor install command localizable strings. This commit moves the `tool` subcommand strings into its own resource file, rather than putting them into the `install` command's resource file. This better follows the patterns of other commands, such as `add`, and enables subcommands to isolate their string resources from one another. As part of this commit, the `install tool` string resources were cleaned up.
2018-01-16 12:59:34 -08:00
</body>
</file>
</xliff>
Reference in a new issue Copy permalink