<?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=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <resheader name="writer">
    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <data name="IDS_btnChangeSet" xml:space="preserve">
    <value>保存</value>
  </data>
  <data name="IDS_btnChangeSiteSet_Click_Ok_Msg" xml:space="preserve">
    <value>成功修改了店鋪圖片上傳方式</value>
  </data>
  <data name="IDS_help01" xml:space="preserve">
    <value>系統提供了三種上傳方式，上傳到FTP伺服器可以大幅降低系統的網路負荷和許可權要求，如果您有FTP伺服器，則可以選擇此方式，上傳到網站虛擬目錄是最常見的一種方式，但是它要求系統對虛擬目錄有寫入的許可權，如果您沒有FTP伺服器也沒有對虛擬目錄的寫入許可權，則可以選擇上傳到資料庫，將圖片以二進位的形式保存在資料庫裡面，但是這樣會極大的加大資料庫負荷及資料檔案大小</value>
  </data>
  <data name="IDS_help02" xml:space="preserve">
    <value>設置系統可以上傳多大的圖片，超過大小的圖片則不允許上傳，圖片大小的單位為KB(1M=1024KB)</value>
  </data>
  <data name="IDS_help03" xml:space="preserve">
    <value>登錄此FTP伺服器的用戶名</value>
  </data>
  <data name="IDS_help04" xml:space="preserve">
    <value>登錄此FTP伺服器的密碼</value>
  </data>
  <data name="IDS_help042" xml:space="preserve">
    <value>請重複輸入FTP登錄密碼</value>
  </data>
  <data name="IDS_help05" xml:space="preserve">
    <value>此FTP伺服器的IP地址</value>
  </data>
  <data name="IDS_help06" xml:space="preserve">
    <value>設置FTP上保存店鋪上傳圖片的目錄，只需要輸入目錄名稱，不用在前後輸入斜杠或反斜線</value>
  </data>
  <data name="IDS_help07" xml:space="preserve">
    <value>如果選擇的上傳方式是上傳到FTP伺服器，則輸入可以訪問到FTP上傳資料夾的URL，如果是上傳到網站虛擬目錄，則輸入相對於店鋪網址的路徑</value>
  </data>
  <data name="IDS_Invalid_FtpServerPassword_NotComp" xml:space="preserve">
    <value>兩次輸入的密碼不一至</value>
  </data>
  <data name="IDS_lblFtpHomePath" xml:space="preserve">
    <value>FTP上傳資料夾：</value>
  </data>
  <data name="IDS_lblFtpServer" xml:space="preserve">
    <value>FTP伺服器：</value>
  </data>
  <data name="IDS_lblFtpServerPassword" xml:space="preserve">
    <value>FTP登錄密碼：</value>
  </data>
  <data name="IDS_lblFtpServerPassword2" xml:space="preserve">
    <value>確認登錄密碼</value>
  </data>
  <data name="IDS_lblFtpServerUserName" xml:space="preserve">
    <value>FTP用戶名：</value>
  </data>
  <data name="IDS_lblImageUrlPrefix" xml:space="preserve">
    <value>圖片路徑：</value>
  </data>
  <data name="IDS_lblMaxUploadSize" xml:space="preserve">
    <value>上傳圖片大小限制：</value>
  </data>
  <data name="IDS_lblPhotoSaveType" xml:space="preserve">
    <value>上傳方式：</value>
  </data>
  <data name="IDS_MaxUploadZize_Error" xml:space="preserve">
    <value>上傳圖片大小限制在2M以內</value>
  </data>
  <data name="IDS_PageDesc" xml:space="preserve">
    <value>管理店鋪的圖片上傳方式，您可以結合店鋪的情況選擇圖片上傳的方式</value>
  </data>
  <data name="IDS_PageTitle" xml:space="preserve">
    <value>圖片上傳管理</value>
  </data>
  <data name="String1" xml:space="preserve">
    <value>兩次輸入的密碼不一致，請重新輸入</value>
  </data>
</root>