/
githubmirror
/
PowerShell
Обзор
Документация
Войти
/
githubmirror
/
PowerShell
Код
Запросы
0
Пакеты
0
Релизы
0
Аналитика
Безопасность
master
src/System.Management.Automation/resources/it/PathUtilsStrings.it.resx
166 строк
9 KB
olprod
Localized file check-in by OneLocBuild Task: Build definition ID 13420: Build ID 2660148 (#27752)
05 авг 2026, 00:40
Не верифицирован
05 авг 2026, 00:40
ead4ce4
Код
Авторство
О чём код?
<?xml version="1.0" encoding="utf-8"?> <root> <!-- Microsoft ResX Schema Version 2.0 The primary goals of this format is to allow a simple XML format that is mostly human readable. The generation and parsing of the various data types are done through the TypeConverter classes associated with the data types. Example: ... ado.net/XML headers & schema ... <resheader name="resmimetype">text/microsoft-resx</resheader> <resheader name="version">2.0</resheader> <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader> <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader> <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data> <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data> <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64"> <value>[base64 mime encoded serialized .NET Framework object]</value> </data> <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64"> <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value> <comment>This is a comment</comment> </data> There are any number of "resheader" rows that contain simple name/value pairs. Each data row contains a name, and value. The row also contains a type or mimetype. Type corresponds to a .NET class that support text/value conversion through the TypeConverter architecture. Classes that don't support this are serialized and stored with the mimetype set. The mimetype is used for serialized objects, and tells the ResXResourceReader how to depersist the object. This is currently not extensible. For a given mimetype the value must be set accordingly: Note - application/x-microsoft.net.object.binary.base64 is the format that the ResXResourceWriter will generate, however the reader can read any of the formats listed below. mimetype: application/x-microsoft.net.object.binary.base64 value : The object must be serialized with : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter : and then encoded with base64 encoding. mimetype: application/x-microsoft.net.object.soap.base64 value : The object must be serialized with : System.Runtime.Serialization.Formatters.Soap.SoapFormatter : and then encoded with base64 encoding. mimetype: application/x-microsoft.net.object.bytearray.base64 value : The object must be serialized into a byte array : using a System.ComponentModel.TypeConverter : and then encoded with base64 encoding. --> <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"> <xsd:import namespace="http://www.w3.org/XML/1998/namespace" /> <xsd:element name="root" msdata:IsDataSet="true"> <xsd:complexType> <xsd:choice maxOccurs="unbounded"> <xsd:element name="metadata"> <xsd:complexType> <xsd:sequence> <xsd:element name="value" type="xsd:string" minOccurs="0" /> </xsd:sequence> <xsd:attribute name="name" use="required" type="xsd:string" /> <xsd:attribute name="type" type="xsd:string" /> <xsd:attribute name="mimetype" type="xsd:string" /> <xsd:attribute ref="xml:space" /> </xsd:complexType> </xsd:element> <xsd:element name="assembly"> <xsd:complexType> <xsd:attribute name="alias" type="xsd:string" /> <xsd:attribute name="name" type="xsd:string" /> </xsd:complexType> </xsd:element> <xsd:element name="data"> <xsd:complexType> <xsd:sequence> <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" /> <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" /> </xsd:sequence> <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" /> <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" /> <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" /> <xsd:attribute ref="xml:space" /> </xsd:complexType> </xsd:element> <xsd:element name="resheader"> <xsd:complexType> <xsd:sequence> <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" /> </xsd:sequence> <xsd:attribute name="name" type="xsd:string" use="required" /> </xsd:complexType> </xsd:element> </xsd:choice> </xsd:complexType> </xsd:element> </xsd:schema> <resheader name="resmimetype"> <value>text/microsoft-resx</value> </resheader> <resheader name="version"> <value>2.0</value> </resheader> <resheader name="reader"> <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value> </resheader> <resheader name="writer"> <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value> </resheader> <data name="Utf7EncodingObsolete" xml:space="preserve"> <value>La codifica 'UTF-7' è obsoleta; usare UTF-8.</value> </data> <data name="UtilityFileExistsNoClobber" xml:space="preserve"> <value>Il file {0} esiste già e {1} è stato specificato.</value> </data> <data name="OutFile_ReadWriteFileNotFileSystemProvider" xml:space="preserve"> <value>Non è possibile aprire il file perché il provider corrente ({0}) non riesce ad aprire un file.</value> </data> <data name="OutFile_MultipleFilesNotSupported" xml:space="preserve"> <value>Non è possibile eseguire l'operazione perché il percorso è stato risolto in più file. Il comando non può eseguire operazioni su più file.</value> </data> <data name="OutFile_DidNotResolveFile" xml:space="preserve"> <value>Non è possibile eseguire l'operazione perché il percorso con caratteri jolly {0} non si è risolto in un file.</value> </data> <data name="OutFile_WriteToFileEncodingUnknown" xml:space="preserve"> <value>Codifica sconosciuta {0}; i valori validi sono {1}.</value> </data> <data name="ExportPSSession_ErrorDirectoryExists" xml:space="preserve"> <value>La directory '{0}' esiste già. Utilizzare il parametro -Force se si vuole sovrascrivere la directory e i file al suo interno.</value> </data> <data name="ExportPSSession_ErrorModuleNameOrPath" xml:space="preserve"> <value>Il percorso dei moduli utente non esiste. Pertanto non è possibile creare una cartella di moduli per il nome del modulo '{0}'.</value> </data> <data name="ExportPSSession_CannotCreateOutputDirectory" xml:space="preserve"> <value>Non è possibile creare il modulo {0} a causa di quanto segue:{1}. Utilizzare un argomento diverso per il parametro -OutputModule e riprovare.</value> <comment>{StrContains="OutputModule"} {0} is a placeholder for the name of a directory {1} is a placeholder for an error message from the inner exception Reviewed by TArcher on 2010-07-21 Example usage: PS C:\> $s = New-PSSession PS C:\> Export-PSSession -Session $s -OutputModule gibberish:here Export-PSSession : Cannot create the module 'gibberish:here' due to the following: Cannot find drive. A drive with the name 'gibberish' does not exist. Use a different argument for the -OutputModule parameter and try again. At line:1 char:1 + Export-PSSession -Session $s -OutputModule gibberish:here + ^ + CategoryInfo : ResourceExists: (gibberish:here:String) [Export-PSSession], ArgumentException + FullyQualifiedErrorId : ExportProxyCommand_CannotCreateOutputDirectory,Microsoft.PowerShell.Commands.ExportPSSessionCommand </comment> </data> <data name="ExportPSSession_ScriptGeneratorVersionMismatch" xml:space="preserve"> <value>Non è possibile caricare il modulo perché è stato generato con una versione non compatibile del cmdlet {0}. Generare il modulo con il cmdlet {0} della sessione corrente e riprovare a caricare il modulo.</value> </data> </root>