Loading…
graceyu
Translation approved |
|
graceyu
Translation changed |
<p>
<b><big>Percent Encoding</big></b><br> The issue is complicated. It is recommended to avoid reserved characters and spaces for component values in URIs if the values are under your control (e.g. you cannot avoid it when you must specify such characters in values for an URI to access a remote print queue but the remote print queue is not under your control). Whenever possible use only so called 'unreserved characters'. Unreserved characters are uppercase and lowercase letters, decimal digits, hyphen, period, underscore, and tilde. Even hyphen, period, tilde, and case sensitivity could cause special issues in special cases (e.g. only letters, digits, and underscore are known to work for a CUPS print queue name and case is not significant there). Therefore it is best to use only lowercase letters, digits, and underscore for all values in all URIs if possible.<br> Reserved characters and space characters in the value of a component must be percent-encoded (also known as URL encoding).<br> When an input field in the dialog is intended to enter only a single value for a single component of the URI (e.g. separated input fields for username and password), you must enter spaces and reserved characters literally (i.e. non-percent-encoded). For such input fields all spaces and reserved characters will be automatically percent-encoded. For example if a password is actually 'Foo%20Bar' (non-percent-encoded), it must be entered literally in the password input field in the dialog. The automated percent-encoding results 'Foo%2520Bar' which is how the value of the password component is actually stored in the URI.<br> In contrast when an input field in the dialog is intended to enter more that a single value for a single component of the URI (e.g. a single input field for all optional parameters like 'option1=value1&option2=value2&option3=value3' or a single input field to enter the whole URI), you must enter spaces and reserved characters percent-encoded because an automated percent-encoding is no longer possible. Assume in an optional parameter 'option=value' the value would be 'this&that' so that the whole optional parameter would be 'option=this&that' (literally). But a literal '&' character denotes the separation of different optional parameters so that 'option=this&that' in an URI means a first optional parameter 'option=this' and a second optional parameter which is only 'that'. Therefore a single optional parameter 'option=this&that' must be entered percent-encoded as 'option=this%26that'<br> Input fields which require percent-encoded input are denoted by a '[percent-encoded]' hint.<br> Listing of characters and their percent encoding:<br> space ' ' is percent encoded as %20<br> exclamation mark ! is percent encoded as %21<br> number sign # is percent encoded as %23<br> Dollar sign $ is percent encoded as %24<br> percentage % is percent encoded as %25<br> ampersand & is percent encoded as %26<br> apostrophe / single quotation mark ' is percent encoded as %27<br> left parenthesis ( is percent encoded as %28<br> right parenthesis ) is percent encoded as %29<br> asterisk * is percent encoded as %2A<br> plus sign + is percent encoded as %2B<br> comma , is percent encoded as %2C<br> slash / is percent encoded as %2F<br> colon : is percent encoded as %3A<br> semicolon ; is percent encoded as %3B<br> equals sign = is percent encoded as %3D<br> question mark ? is percent encoded as %3F<br> at sign @ is percent encoded as %40<br> left bracket [ is percent encoded as %5B<br> right bracket ] is percent encoded as %5D<br> For details see 'Uniform Resource Identifier (URI): Generic Syntax' at<br> http://tools.ietf.org/html/rfc3986 </p>
<p>
<b><big>百分号编码</big></b><br> 该问题很复杂。 建议您避免在 URI 中使用保留字符和空格 作为组件值,前提是您能控制这些值 (例如当您必须在 URI 中指定这样的字符 作为值以访问远程打印队列,但远程打印队列又 不在您控制下时,您就无法避免使用它们)。 可能的情况下,请只使用“非保留字符”。 非保留字符包括大小写字母、 十进位数字、连字符、句号、下划线和波浪号。 甚至在特殊情况下,连字符、句号、波浪号和大小写 都会导致特殊问题 (例如,只有字符、数字和下划线已知可以用在 CUPS 打印 队列名称中,一般不会有什么显著问题)。 因此,如果可能,所有 URI 中的所有值最好 只使用小写字母、数字和下划线。<br> 组件值中的保留字符和空格字符 必须进行百分号编码(也叫做 URL 编码)。<br> 当对话框中输入字段是用来输入 URI 的一个组件的一个值时 (例如,用户名和口令的输入字段是分开的), 您必须按字面输入空格和保留字符 (非百分号编码)。 这样的输入字段会自动对所有空格 和保留字符进行百分号编码。 例如,口令实际上是“Foo%20Bar”(非百分号编码), 您必须在对话框中的口令输入字段中按字面输入该口令。 URI 中实际上储存的口令组件值是 自动进行了百分号编码的结果“Foo%2520Bar”。<br> 相反,当对话框中的输入字段是用来 输入 URI 的一个组件的多个值时 (例如,一个用于输入类似于 “option1=value1&option2=value2&option3=value3” 的所有可选参数的输入字段或一个用于输入整个 URI 的输入字段), 您必须输入经过百分号编码的空格和保留字符, 因为系统不会再进行自动百分号编码。 假设要输入可选参数“ 值是“this&that”,那么整个可选 参数应该是“ 但是字面上的“&”字符代表 不同可选参数的分隔符, 因此 URI 中的“ 第一个可选参数是“ 第二个可选参数只是“that”。 因此,单个可选参数“ 百分号编码格式“ 要求以百分号编码格式输入的输入字段 通过“[百分号编码]”提示标出。<br> 下面是字符和它们的百分号编码的列表:<br> 空格“ ”的百分号编码是 %20<br> 感叹号 ! 的百分号编码是 %21<br> 数字符号 # 的百分号编码是 %23<br> 美元符号 $ 的百分号编码是 %24<br> 百分号 % 的百分号编码是 %25<br> 符号 & 的百分号编码是 %26<br> 单引号 ‘ 的百分号编码是 %27<br> 左括号 ( 的百分号编码是 %28<br> 右括号 ) 的百分号编码是 %29<br> 星号 * 的百分号编码是 %2A<br> 加号 + 的百分号编码是 %2B<br> 逗号 , 的百分号编码是 %2C<br> 斜线 / 的百分号编码是 %2F<br> 冒号 : 的百分号编码是 %3A<br> 分号 ; 的百分号编码是 %3B<br> 等号 = 的百分号编码是 %3D<br> 问号 ? 的百分号编码是 %3F<br> at 号 @ 的百分号编码是 %40<br> 左方括号 [ 的百分号编码是 %5B<br> 右方括号 ] 的百分号编码是 %5D<br> 详情见“统一资源标识符 (URI):通用语法”,网址为:<br> http://tools.ietf.org/html/rfc3986 </p> |
graceyu
Translation changed |
<p>
<b><big>Percent Encoding</big></b><br> The issue is complicated. It is recommended to avoid reserved characters and spaces for component values in URIs if the values are under your control (e.g. you cannot avoid it when you must specify such characters in values for an URI to access a remote print queue but the remote print queue is not under your control). Whenever possible use only so called 'unreserved characters'. Unreserved characters are uppercase and lowercase letters, decimal digits, hyphen, period, underscore, and tilde. Even hyphen, period, tilde, and case sensitivity could cause special issues in special cases (e.g. only letters, digits, and underscore are known to work for a CUPS print queue name and case is not significant there). Therefore it is best to use only lowercase letters, digits, and underscore for all values in all URIs if possible.<br> Reserved characters and space characters in the value of a component must be percent-encoded (also known as URL encoding).<br> When an input field in the dialog is intended to enter only a single value for a single component of the URI (e.g. separated input fields for username and password), you must enter spaces and reserved characters literally (i.e. non-percent-encoded). For such input fields all spaces and reserved characters will be automatically percent-encoded. For example if a password is actually 'Foo%20Bar' (non-percent-encoded), it must be entered literally in the password input field in the dialog. The automated percent-encoding results 'Foo%2520Bar' which is how the value of the password component is actually stored in the URI.<br> In contrast when an input field in the dialog is intended to enter more that a single value for a single component of the URI (e.g. a single input field for all optional parameters like 'option1=value1&option2=value2&option3=value3' or a single input field to enter the whole URI), you must enter spaces and reserved characters percent-encoded because an automated percent-encoding is no longer possible. Assume in an optional parameter 'option=value' the value would be 'this&that' so that the whole optional parameter would be 'option=this&that' (literally). But a literal '&' character denotes the separation of different optional parameters so that 'option=this&that' in an URI means a first optional parameter 'option=this' and a second optional parameter which is only 'that'. Therefore a single optional parameter 'option=this&that' must be entered percent-encoded as 'option=this%26that'<br> Input fields which require percent-encoded input are denoted by a '[percent-encoded]' hint.<br> Listing of characters and their percent encoding:<br> space ' ' is percent encoded as %20<br> exclamation mark ! is percent encoded as %21<br> number sign # is percent encoded as %23<br> Dollar sign $ is percent encoded as %24<br> percentage % is percent encoded as %25<br> ampersand & is percent encoded as %26<br> apostrophe / single quotation mark ' is percent encoded as %27<br> left parenthesis ( is percent encoded as %28<br> right parenthesis ) is percent encoded as %29<br> asterisk * is percent encoded as %2A<br> plus sign + is percent encoded as %2B<br> comma , is percent encoded as %2C<br> slash / is percent encoded as %2F<br> colon : is percent encoded as %3A<br> semicolon ; is percent encoded as %3B<br> equals sign = is percent encoded as %3D<br> question mark ? is percent encoded as %3F<br> at sign @ is percent encoded as %40<br> left bracket [ is percent encoded as %5B<br> right bracket ] is percent encoded as %5D<br> For details see 'Uniform Resource Identifier (URI): Generic Syntax' at<br> http://tools.ietf.org/html/rfc3986 </p>
<p>
<b><big>百分号编码</big></b><br> 该问题很复杂。 建议您避免在 URI 中使用保留字符和空格 作为组件值,前提是您能控制这些值 (例如当您必须在 URI 中指定这样的字符 作为值以访问远程打印队列, 不在您控制下时,您就无法避免使用它们)。 可能的情况下,请只使用“非保留字符”。 非保留字符包括大小写字母、 十进位数字、连字符、句号、下划线和波浪号。 甚至在特殊情况下,连字符、句号、波浪号和大小写 都会导致特殊问题 (例如,只有字符、数字和下划线已知可以用在 CUPS 打印 队列名称中,一般不会有什么显著问题)。 因此,如果可能,所有 URI 中的所有值最好 只使用小写字母、数字 组件值中的保留字符和空格字符 必须进行百分号编码(也叫做 URL 编码)。<br> 当对话框中输入字段是用来输入 URI 的一个组件的一个值时 (例如,用户名和口令的输入字段是分开的), 您必须按字面输入空格和保留字符 (非百分号编码)。 这样的输入字段会自动对所有空格 和保留字符进行百分号编码。 例如,口令实际上是“Foo%20Bar”(非百分号编码), 您必须在对话框中的口令输入字段中按字面输入该口令。 URI 中 自动进行了百分号编码的结果“Foo%2520Bar”。<br> 相反,当对话框中的输入字段是用来 输入 URI 的一个组件的多个值时 (例如,一个用于输入类似于 “option1=value1&option2=value2&option3=value3” 的所有可选参数的输入字段 或者 您必须输入经过百分号编码 因为系统不会再 假设要输入可选参数“选项=值”, 值是“this&that”,那么整个可选 参数应该是“选项=this&that”(字面上)。 但是字面上的“&”字符代表 不同可选参数的分隔符, 因此 URI 中的“选项=this&that”意思是 第一个可选参数是“选项=this”, 第二个可选参数只是“that”。 因此,单个可选参数“选项=this&that”必须以 百分号编码格式“选项=this%26that”输入。<br> 要求以百分号编码格式输入的输入字段 通过“[ 下面是字符和它们的百分号编码的列表:<br> 空格“ ”的百分号编码 感叹号 ! 的百分号编码是 %21<br> 数字符号 # 的百分号编码是 %23<br> 美元符号 $ 的百分号编码是 %24<br> 百分号 % 的百分号编码是 %25<br> 符号 & 的百分号编码是 %26<br> 单引号 ‘ 的百分号编码是 %27<br> 左括号 ( 的百分号编码是 %28<br> 右括号 ) 的百分号编码是 %29<br> 星号 * 的百分号编码是 %2A<br> 加号 + 的百分号编码是 %2B<br> 逗号 , 的百分号编码是 %2C<br> 斜线 / 的百分号编码是 %2F<br> 冒号 : 的百分号编码是 %3A<br> 分号 ; 的百分号编码是 %3B<br> 等号 = 的百分号编码是 %3D<br> 问号 ? 的百分号编码是 %3F<br> at 号 @ 的百分号编码是 %40<br> 左方括号 [ 的百分号编码是 %5B<br> 右方括号 ] 的百分号编码是 %5D<br> 详情见“统一资源标识符 (URI):通用语法”,网址为:<br> http://tools.ietf.org/html/rfc3986 </p> |
graceyu
Suggestion accepted |
<p>
<b><big>Percent Encoding</big></b><br> The issue is complicated. It is recommended to avoid reserved characters and spaces for component values in URIs if the values are under your control (e.g. you cannot avoid it when you must specify such characters in values for an URI to access a remote print queue but the remote print queue is not under your control). Whenever possible use only so called 'unreserved characters'. Unreserved characters are uppercase and lowercase letters, decimal digits, hyphen, period, underscore, and tilde. Even hyphen, period, tilde, and case sensitivity could cause special issues in special cases (e.g. only letters, digits, and underscore are known to work for a CUPS print queue name and case is not significant there). Therefore it is best to use only lowercase letters, digits, and underscore for all values in all URIs if possible.<br> Reserved characters and space characters in the value of a component must be percent-encoded (also known as URL encoding).<br> When an input field in the dialog is intended to enter only a single value for a single component of the URI (e.g. separated input fields for username and password), you must enter spaces and reserved characters literally (i.e. non-percent-encoded). For such input fields all spaces and reserved characters will be automatically percent-encoded. For example if a password is actually 'Foo%20Bar' (non-percent-encoded), it must be entered literally in the password input field in the dialog. The automated percent-encoding results 'Foo%2520Bar' which is how the value of the password component is actually stored in the URI.<br> In contrast when an input field in the dialog is intended to enter more that a single value for a single component of the URI (e.g. a single input field for all optional parameters like 'option1=value1&option2=value2&option3=value3' or a single input field to enter the whole URI), you must enter spaces and reserved characters percent-encoded because an automated percent-encoding is no longer possible. Assume in an optional parameter 'option=value' the value would be 'this&that' so that the whole optional parameter would be 'option=this&that' (literally). But a literal '&' character denotes the separation of different optional parameters so that 'option=this&that' in an URI means a first optional parameter 'option=this' and a second optional parameter which is only 'that'. Therefore a single optional parameter 'option=this&that' must be entered percent-encoded as 'option=this%26that'<br> Input fields which require percent-encoded input are denoted by a '[percent-encoded]' hint.<br> Listing of characters and their percent encoding:<br> space ' ' is percent encoded as %20<br> exclamation mark ! is percent encoded as %21<br> number sign # is percent encoded as %23<br> Dollar sign $ is percent encoded as %24<br> percentage % is percent encoded as %25<br> ampersand & is percent encoded as %26<br> apostrophe / single quotation mark ' is percent encoded as %27<br> left parenthesis ( is percent encoded as %28<br> right parenthesis ) is percent encoded as %29<br> asterisk * is percent encoded as %2A<br> plus sign + is percent encoded as %2B<br> comma , is percent encoded as %2C<br> slash / is percent encoded as %2F<br> colon : is percent encoded as %3A<br> semicolon ; is percent encoded as %3B<br> equals sign = is percent encoded as %3D<br> question mark ? is percent encoded as %3F<br> at sign @ is percent encoded as %40<br> left bracket [ is percent encoded as %5B<br> right bracket ] is percent encoded as %5D<br> For details see 'Uniform Resource Identifier (URI): Generic Syntax' at<br> http://tools.ietf.org/html/rfc3986 </p>
<p>
<b><big>百分号编码</big></b><br> 该问题很复杂。 建议您避免在 URI 中使用保留字符和空格 作为组件值, (例如当您必须在 URI 中指定这样的字符 作为值以访问远程打印队列, 但远程打印队列又不在您控制下时,您就无法避免使用它们 可能的情况下,请只使用 非保留 十进位数字、连字符、句号、下划线和波浪号。 甚至在特殊情况下,连字符 都会导致特殊问题 (例如,只有字符 队列名 因此 只使用小写字母 组件值中的保留字符和空格字符 必须 当对话框中输入 URI 的一个组件的一个值时 (例如,用户名和 您必须按字面输入空格和保留字符 (非百分号编码)。 这样的输入 和保留字符进行百分号编码。 例如 您必须在对话框中的 URI 中的 自动进行了百分 相反,当对话框中的输入 输入 URI 的一个组件的多 (例如,一个 的所有可选参数的输入字段 或者一个用于输入整个 URI 的输入字段), 您必须输入编码过的空格和保留字符, 因为 假设 值是“this&that 参数应该是 但是字面上的 不同可选参数的分隔符, 因此 URI 中的 第一个可选参数是 第二个可选参数只是 因此 要求以百分 通过“[percent-encoded] 下面是字符和它们的百分 空格 感叹号 ! 的百分 数字符号 # 的百分 美元符号 $ 的百分 百分号 % 的百分 符号 & 的百分 单引号 ‘ 的百分 左括号 ( 的百分 右括号 ) 的百分 星号 * 的百分 加号 + 的百分 逗号 斜 冒号 : 的百分 分号 ; 的百分 等号 = 的百分 问号 ? 的百分 at 号 @ 的百分 左 右 详情见 http://tools.ietf.org/html/rfc3986 </p> |
sle-merge-robot
Suggestion added |
<p>
<b><big>Percent Encoding</big></b><br> The issue is complicated. It is recommended to avoid reserved characters and spaces for component values in URIs if the values are under your control (e.g. you cannot avoid it when you must specify such characters in values for an URI to access a remote print queue but the remote print queue is not under your control). Whenever possible use only so called 'unreserved characters'. Unreserved characters are uppercase and lowercase letters, decimal digits, hyphen, period, underscore, and tilde. Even hyphen, period, tilde, and case sensitivity could cause special issues in special cases (e.g. only letters, digits, and underscore are known to work for a CUPS print queue name and case is not significant there). Therefore it is best to use only lowercase letters, digits, and underscore for all values in all URIs if possible.<br> Reserved characters and space characters in the value of a component must be percent-encoded (also known as URL encoding).<br> When an input field in the dialog is intended to enter only a single value for a single component of the URI (e.g. separated input fields for username and password), you must enter spaces and reserved characters literally (i.e. non-percent-encoded). For such input fields all spaces and reserved characters will be automatically percent-encoded. For example if a password is actually 'Foo%20Bar' (non-percent-encoded), it must be entered literally in the password input field in the dialog. The automated percent-encoding results 'Foo%2520Bar' which is how the value of the password component is actually stored in the URI.<br> In contrast when an input field in the dialog is intended to enter more that a single value for a single component of the URI (e.g. a single input field for all optional parameters like 'option1=value1&option2=value2&option3=value3' or a single input field to enter the whole URI), you must enter spaces and reserved characters percent-encoded because an automated percent-encoding is no longer possible. Assume in an optional parameter 'option=value' the value would be 'this&that' so that the whole optional parameter would be 'option=this&that' (literally). But a literal '&' character denotes the separation of different optional parameters so that 'option=this&that' in an URI means a first optional parameter 'option=this' and a second optional parameter which is only 'that'. Therefore a single optional parameter 'option=this&that' must be entered percent-encoded as 'option=this%26that'<br> Input fields which require percent-encoded input are denoted by a '[percent-encoded]' hint.<br> Listing of characters and their percent encoding:<br> space ' ' is percent encoded as %20<br> exclamation mark ! is percent encoded as %21<br> number sign # is percent encoded as %23<br> Dollar sign $ is percent encoded as %24<br> percentage % is percent encoded as %25<br> ampersand & is percent encoded as %26<br> apostrophe / single quotation mark ' is percent encoded as %27<br> left parenthesis ( is percent encoded as %28<br> right parenthesis ) is percent encoded as %29<br> asterisk * is percent encoded as %2A<br> plus sign + is percent encoded as %2B<br> comma , is percent encoded as %2C<br> slash / is percent encoded as %2F<br> colon : is percent encoded as %3A<br> semicolon ; is percent encoded as %3B<br> equals sign = is percent encoded as %3D<br> question mark ? is percent encoded as %3F<br> at sign @ is percent encoded as %40<br> left bracket [ is percent encoded as %5B<br> right bracket ] is percent encoded as %5D<br> For details see 'Uniform Resource Identifier (URI): Generic Syntax' at<br> http://tools.ietf.org/html/rfc3986 </p> |
Things to check
Source string description
ConnectionWizardDialog help 3/7:Flags
c-format
<b><big>Percent Encoding</big></b><br>
The issue is complicated.
It is recommended to avoid reserved characters and spaces
for component values in URIs if the values are under your control
(e.g. you cannot avoid it when you must specify such characters
in values for an URI to access a remote print queue
but the remote print queue is not under your control).
Whenever possible use only so called 'unreserved characters'.
Unreserved characters are uppercase and lowercase letters,
decimal digits, hyphen, period, underscore, and tilde.
Even hyphen, period, tilde, and case sensitivity
could cause special issues in special cases
(e.g. only letters, digits, and underscore are known to work
for a CUPS print queue name and case is not significant there).
Therefore it is best to use only lowercase letters, digits,
and underscore for all values in all URIs if possible.<br>
Reserved characters and space characters in the value of a component
must be percent-encoded (also known as URL encoding).<br>
When an input field in the dialog is intended to enter
only a single value for a single component of the URI
(e.g. separated input fields for username and password),
you must enter spaces and reserved characters literally
(i.e. non-percent-encoded).
For such input fields all spaces and reserved characters
will be automatically percent-encoded.
For example if a password is actually 'Foo%20Bar' (non-percent-encoded),
it must be entered literally in the password input field in the dialog.
The automated percent-encoding results 'Foo%2520Bar' which is how
the value of the password component is actually stored in the URI.<br>
In contrast when an input field in the dialog is intended to enter
more that a single value for a single component of the URI
(e.g. a single input field for all optional parameters
like 'option1=value1&option2=value2&option3=value3'
or a single input field to enter the whole URI),
you must enter spaces and reserved characters percent-encoded
because an automated percent-encoding is no longer possible.
Assume in an optional parameter 'option=value'
the value would be 'this&that' so that the whole
optional parameter would be 'option=this&that' (literally).
But a literal '&' character denotes
the separation of different optional parameters
so that 'option=this&that' in an URI means
a first optional parameter 'option=this' and
a second optional parameter which is only 'that'.
Therefore a single optional parameter 'option=this&that'
must be entered percent-encoded as 'option=this%26that'<br>
Input fields which require percent-encoded input
are denoted by a '[percent-encoded]' hint.<br>
Listing of characters and their percent encoding:<br>
space ' ' is percent encoded as %20<br>
exclamation mark ! is percent encoded as %21<br>
number sign # is percent encoded as %23<br>
Dollar sign $ is percent encoded as %24<br>
percentage % is percent encoded as %25<br>
ampersand & is percent encoded as %26<br>
apostrophe / single quotation mark ' is percent encoded as %27<br>
left parenthesis ( is percent encoded as %28<br>
right parenthesis ) is percent encoded as %29<br>
asterisk * is percent encoded as %2A<br>
plus sign + is percent encoded as %2B<br>
comma , is percent encoded as %2C<br>
slash / is percent encoded as %2F<br>
colon : is percent encoded as %3A<br>
semicolon ; is percent encoded as %3B<br>
equals sign = is percent encoded as %3D<br>
question mark ? is percent encoded as %3F<br>
at sign @ is percent encoded as %40<br>
left bracket [ is percent encoded as %5B<br>
right bracket ] is percent encoded as %5D<br>
For details see 'Uniform Resource Identifier (URI): Generic Syntax' at<br>
http://tools.ietf.org/html/rfc3986
</p>
<b><big>百分号编码</big></b><br>
该问题很复杂。
建议您避免在 URI 中使用保留字符和空格
作为组件值,前提是您能控制这些值
(例如当您必须在 URI 中指定这样的字符
作为值以访问远程打印队列,但远程打印队列又
不在您控制下时,您就无法避免使用它们)。
可能的情况下,请只使用
“"非保留字符”。非保留字符包括大小写字母、
十进位数字、连字符、句号、下划线和波浪号。
甚至在特殊情况下,连字符、句号、波浪号和大小写
都会导致特殊问题
(例如,只有字符、数字和下划线已知可以用在 CUPS 打印
队列名称中,一般不会有什么显著问题)。
因此,如果可能,所有 URI 中的所有值最好
只使用小写字母、数字和下划线。<br>
组件值中的保留字符和空格字符
必须进行百分号编码(也叫做 URL 编码)。<br>
当对话框中输入字段是用来输入
URI 的一个组件的一个值时
(例如,用户名和口令的输入字段是分开的),
您必须按字面输入空格和保留字符
(非百分号编码)。
这样的输入字段会自动对所有空格
和保留字符进行百分号编码。
例如,口令实际上是
“"Foo%20Bar”(非百分号编码),您必须在对话框中的口令输入字段中按字面输入该口令。
URI 中实际上储存的口令组件值是
自动进行了百分号编码的结果
“"Foo%2520Bar”"。<br>相反,当对话框中的输入字段是用来
输入 URI 的一个组件的多个值时
(例如,一个用于输入类似于
“"option1=value1&option2=value2&option3=value3”"的所有可选参数的输入字段或一个用于输入整个 URI 的输入字段),
您必须输入经过百分号编码的空格和保留字符,
因为系统不会再进行自动百分号编码。
假设要输入可选参数
“"option=value”",值是
“"this&that”",那么整个可选参数应该是
“"option=this&that”"(字面上)。但是字面上的
“"&”" 字符代表不同可选参数的分隔符,
因此 URI 中的
“"option=this&that”" 意思是第一个可选参数是
“"option=this”",第二个可选参数只是
“"that”"。因此,单个可选参数
“"option=this&that”" 必须以百分号编码格式
“"option=this%26that”" 输入。<br>要求以百分号编码格式输入的输入字段
通过
“"[百分号编码]”" 提示标出。<br>下面是字符和它们的百分号编码的列表:<br>
空格
“ ”" " 的百分号编码是 %20<br>感叹号 ! 的百分号编码是 %21<br>
数字符号 # 的百分号编码是 %23<br>
美元符号 $ 的百分号编码是 %24<br>
百分号 % 的百分号编码是 %25<br>
符号 & 的百分号编码是 %26<br>
单引号 ‘ 的百分号编码是 %27<br>
左括号 ( 的百分号编码是 %28<br>
右括号 ) 的百分号编码是 %29<br>
星号 * 的百分号编码是 %2A<br>
加号 + 的百分号编码是 %2B<br>
逗号 , 的百分号编码是 %2C<br>
斜线 / 的百分号编码是 %2F<br>
冒号 : 的百分号编码是 %3A<br>
分号 ; 的百分号编码是 %3B<br>
等号 = 的百分号编码是 %3D<br>
问号 ? 的百分号编码是 %3F<br>
at 号 @ 的百分号编码是 %40<br>
左方括号 [ 的百分号编码是 %5B<br>
右方括号 ] 的百分号编码是 %5D<br>
详情见
“"统一资源标识符 (URI):通用语法”",网址为:<br>http://tools.ietf.org/html/rfc3986
</p>