<?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>
</root>