Loading…
juansarria
Translation changed |
|
juansarria
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>Codificación porcentual</big></b><br> El tema es complicado. Es recomendable evitar caracteres reservados y espacios ( en valores para un pues la cola de impresión remota no se encuentra bajo su control). Siempre que sea posible, use s C Los caracteres no reservados son las letras minúsculas y mayúsculas, los dígitos de Incluso el gui podría puede causar problemas especiales en (e.j. só los dígitos y el gui para CUPS, mientras que el uso de mayúsculas no parece significativo en este caso). Por lo tanto, es mejor usar s y el gui Los caracteres reservados y de espacio en el valor de un componente deben ser codificados porcentualmente (también conocido como codificación URL).<br> Cuando un campo de entrada en un recuadro de diálogo se utiliza para introducir s (e.j. campos de entrada separados para el usuario y la contraseña), introducir los espacios y caracteres reservados en su forma literal, ( En estos campos de entrada la codificación porcentual caracteres reservados se efectúa automáticamente. Por ejemplo si introducirse literalmente en el campo de entrada de la contraseña Se codificara automáticamente a de la contraseña del componente se almacena realmente en el Por el contrario, cuando en un campo de entrada de un recuadro de di hay que introducir más de un valor sencillo para un único componente de (p como o un único campo de entrada para introducir tod deben introducirse los espacios y caracteres reservados codificados porcentualmente por ya que no es posible codificarlos automáticamente. Suponga que en un parámetro opcional el valor fuera el parámetro opcional sería Pero un carácter literal de distintos parámetros opcionales, por lo que un primer parámetro un segundo parámetro opcional que solo contiene Por lo tanto, un único parámetro opcional debe introducirse codificado porcentualmente como Los campos de entrada que requieren codificación porcentual de entrada se Lista espacio exclamación ! se codifica como %21<br> porcentaje % se codifica como %25<br> apostrofe paréntesis izquierdo ( paréntesis derecho asterisco * se codifica como %2A<br> signo + se codifica como %2B<br> coma , se codifica como %2C<br> barra / se codifica como %2F<br> dos puntos : se codifica como %3A<br> punto y coma ; se codifica como %3B<br> signo = se codifica como %3D<br> interrogante cerrado ? se codifica como %3F<br> corchete izquierdo [ se codifica como %5B<br> corchete derecho ] se codifica como %5D<br> Para (URI): Generic Syntax </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>Codificación porcentual</big></b><br>
El tema es complicado.
Es recomendable evitar caracteres reservados y espacios
en los valores de componentes de los URI si estos están bajo su control
(por ejemplo, no podrá evitarlos si debe especificar tales caracteres
en valores para un URI de acceso a una cola de impresión remota,
pues la cola de impresión remota no se encuentra bajo su control).
Siempre que sea posible, use solo los denominados "caracteres no reservados".
Los caracteres no reservados son las letras minúsculas y mayúsculas,
los dígitos del cero al nueve, el guion, el punto, el guion bajo y la tilde.
Incluso el guion, el punto, la tilde y el uso de mayúsculas y minúsculas
puede causar problemas especiales en algunos casos (por ejemplo, solo las letras,
los dígitos y el guion bajo funcionan en el nombre de una cola de impresión de
CUPS, mientras que el uso de mayúsculas no parece significativo en este caso).
Por lo tanto, es mejor usar solo letras minúsculas, dígitos
y el guion bajo para todos los valores en todos los URI, si es posible.
Los caracteres reservados y de espacio en el valor de un componente
deben ser codificados porcentualmente (también conocido como codificación URL).<br>
Cuando un campo de entrada en un recuadro de diálogo se utiliza para introducir
solo un único valor de un único componente de un URI (por ejemplo,
campos de entrada separados para el usuario y la contraseña), debe
introducir los espacios y caracteres reservados en su forma literal,
(es decir, sin codificación porcentual).
En estos campos de entrada la codificación porcentual de espacios y
caracteres reservados se efectúa automáticamente.
Por ejemplo si la contraseña es "Foo%20Bar" (sin codificación porcentual), debe
introducirse literalmente en el campo de entrada de la contraseña del recuadro de diálogo.
Se codificara automáticamente a "Foo%2520Bar", que es como el valor
de la contraseña del componente se almacena realmente en el URI.<br>
Por el contrario, cuando en un campo de entrada de un recuadro de diálogo
hay que introducir más de un valor sencillo para un único componente del URI
(por ejemplo, un único campo de entrada para todos los parámetros opcionales
como "opción1=valor1&opción2=valor2&opción3=valor3"
o un único campo de entrada para introducir todo el URI),
deben introducirse los espacios y caracteres reservados codificados porcentualmente,
ya que no es posible codificarlos automáticamente.
Suponga que en un parámetro opcional "opción=valor"
el valor fuera "this&that", entonces todo
el parámetro opcional sería "opción=this&that" (literal).
Pero un carácter literal "&" es la marca de separación
de distintos parámetros opcionales,
por lo que "option=this&that" en un URI significa
un primer parámetro "opción=this" y
un segundo parámetro opcional que solo contiene "that".
Por lo tanto, un único parámetro opcional "opción=this&that"
debe introducirse codificado porcentualmente como "opción=this%26that".<br>
Los campos de entrada que requieren codificación porcentual de entrada
se indican con una marca [codificación porcentual].<br>
Lista de caracteres y su codificación porcentual:<br>
espacio " " se codifica como %20<br>
exclamación ! se codifica como %21<br>
almohadilla # se codifica como %23<br>
dólar $ se codifica como %24<br>
porcentaje % se codifica como %25<br>
y comercial & se codifica como %26<br>
apostrofe o comillas simples " se codifica como %27<br>
paréntesis izquierdo (se codifica como %28<br>
paréntesis derecho) se codifica como %29<br>
asterisco * se codifica como %2A<br>
signo + se codifica como %2B<br>
coma , se codifica como %2C<br>
barra / se codifica como %2F<br>
dos puntos : se codifica como %3A<br>
punto y coma ; se codifica como %3B<br>
signo = se codifica como %3D<br>
interrogante cerrado ? se codifica como %3F<br>
arroba @ se codifica como %40<br>
corchete izquierdo [ se codifica como %5B<br>
corchete derecho ] se codifica como %5D<br>
Para obtener más detalles
mconsulte "Uniform Resource Identifier<br>(URI): Generic Syntax" en: http://tools.ietf.org/html/rfc3986
</p>