BETA

Transvision

Displaying 29 results for the string encoding in eo:

Entity eo en-US
Entity # all locales browser • browser • nsserrors.ftl
mozilla-pkix-error-invalid-integer-encoding
eo
The server presented a certificate that contains an invalid encoding of an integer. Common causes include negative serial numbers, negative RSA moduli, and encodings that are longer than necessary.
en-US
The server presented a certificate that contains an invalid encoding of an integer. Common causes include negative serial numbers, negative RSA moduli, and encodings that are longer than necessary.
Entity # all locales calendar • chrome • calendar • calendar.properties
utf8DecodeError
eo
An error occured while decoding an iCalendar (ics) file as UTF-8. Check that the file, including symbols and accented letters, is encoded using the UTF-8 character encoding.
en-US
An error occurred while decoding an iCalendar (ics) file as UTF-8. Check that the file, including symbols and accented letters, is encoded using the UTF-8 character encoding.
Entity # all locales dom • chrome • dom • dom.properties
JSONCharsetWarning
eo
An attempt was made to declare a non-UTF-8 encoding for JSON retrieved using XMLHttpRequest. Only UTF-8 is supported for decoding JSON.
en-US
An attempt was made to declare a non-UTF-8 encoding for JSON retrieved using XMLHttpRequest. Only UTF-8 is supported for decoding JSON.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadCryptoKeyHeader
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La mesaĝkapo ‘Crypto-Key‘ devas inkluzivi parametron ‘dh‘ , kiu enhavas la publikan ŝlosilon de la servilo de programoj. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Crypto-Key‘ header must include a ‘dh‘ parameter containing the app server’s public key. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadEncodingHeader
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La mesaĝkapo ‘Content-Encoding‘ devas esti ‘aesgcm‘. ‘aesgcm128‘ estas permesata, sed kaduka kaj baldaŭ forigota. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Content-Encoding‘ header must be ‘aesgcm‘. ‘aesgcm128‘ is allowed, but deprecated and will soon be removed. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadEncryptionHeader
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La mesaĝkapo ‘Encryption’ devas inkluzivi unikan ‘salt‘ paramentron por ĉiu mesaĝo. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Encryption’ header must include a unique ‘salt‘ parameter for each message. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadEncryptionKeyHeader
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La mesaĝkapo ‘Encryption-Key’devas inkluzivi parametron ‘dh‘. Tiu ĉi mesaĝkapo estas kaduka kaj baldaŭ forigota. Bonvolu anstataŭe uzi ‘Crypto-Key‘ kun ‘Content-Encoding: aesgcm‘. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Encryption-Key’ header must include a ‘dh‘ parameter. This header is deprecated and will soon be removed. Please use ‘Crypto-Key‘ with ‘Content-Encoding: aesgcm‘ instead. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadPaddingError
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. Registro en la ĉifrita mesaĝo ne estis ĝuste ŝtopita. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. A record in the encrypted message was not padded correctly. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadRecordSize
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La parametro ‘rs‘ parameter de la mesaĝkapo ‘Encryption‘ devas esti ĉu inter %2$S kaj 2^36-31 ĉu preterlasita. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 por pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘rs‘ parameter of the ‘Encryption‘ header must be between %2$S and 2^36-31, or omitted entirely. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadSalt
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La parametro ‘salt‘ en la mesaĝkapo ‘Encryption‘ devas esti kodita de base64url (https://tools.ietf.org/html/rfc7515#appendix-C), kaj esti minimume 16 oktetoj longa antaŭ kodigo. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘salt‘ parameter in the ‘Encryption‘ header must be base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C), and be at least 16 bytes before encoding. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadSenderKey
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La parametro ‘dh‘ en la mesaĝkapo ‘Crypto-Key‘ devas esti la publika ŝlosilo Diffie-Hellman de la servilo de programoj, base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C) kaj en “uncompressed” or “raw” formo (65 oktetoj antaŭ kodigo). Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘dh‘ parameter in the ‘Crypto-Key‘ header must be the app server’s Diffie-Hellman public key, base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C) and in “uncompressed” or “raw” form (65 bytes before encoding). See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncBomlessUtf16
eo
Detected UTF-16-encoded Basic Latin-only text without a byte order mark and without a transfer protocol-level declaration. Encoding this content in UTF-16 is inefficient and the character encoding should have been declared in any case.
en-US
Detected UTF-16-encoded Basic Latin-only text without a byte order mark and without a transfer protocol-level declaration. Encoding this content in UTF-16 is inefficient and the character encoding should have been declared in any case.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncLateMeta
eo
The character encoding declaration of the HTML document was not found when prescanning the first 1024 bytes of the file. When viewed in a differently-configured browser, this page will reload automatically. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
en-US
The character encoding declaration of the HTML document was not found when prescanning the first 1024 bytes of the file. When viewed in a differently-configured browser, this page will reload automatically. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncLateMetaFrame
eo
The character encoding declaration of the framed HTML document was not found when prescanning the first 1024 bytes of the file. When viewed without the document framing it, the page will reload automatically. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
en-US
The character encoding declaration of the framed HTML document was not found when prescanning the first 1024 bytes of the file. When viewed without the document framing it, the page will reload automatically. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncLateMetaReload
eo
The page was reloaded, because the character encoding declaration of the HTML document was not found when prescanning the first 1024 bytes of the file. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
en-US
The page was reloaded, because the character encoding declaration of the HTML document was not found when prescanning the first 1024 bytes of the file. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncLateMetaTooLate
eo
The character encoding declaration of document was found too late for it to take effect. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
en-US
The character encoding declaration of document was found too late for it to take effect. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaUnsupported
eo
An unsupported character encoding was declared for the HTML document using a meta tag. The declaration was ignored.
en-US
An unsupported character encoding was declared for the HTML document using a meta tag. The declaration was ignored.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaUserDefined
eo
A meta tag was used to declare the character encoding as x-user-defined. This was interpreted as a windows-1252 declaration instead for compatibility with intentionally mis-encoded legacy fonts. This site should migrate to Unicode.
en-US
A meta tag was used to declare the character encoding as x-user-defined. This was interpreted as a windows-1252 declaration instead for compatibility with intentionally mis-encoded legacy fonts. This site should migrate to Unicode.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaUtf16
eo
A meta tag was used to declare the character encoding as UTF-16. This was interpreted as an UTF-8 declaration instead.
en-US
A meta tag was used to declare the character encoding as UTF-16. This was interpreted as an UTF-8 declaration instead.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncNoDeclaration
eo
The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must to be declared in the document or in the transfer protocol.
en-US
The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncNoDeclarationFrame
eo
The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it.
en-US
The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncNoDeclarationPlain
eo
The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature.
en-US
The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncProtocolUnsupported
eo
An unsupported character encoding was declared on the transfer protocol level. The declaration was ignored.
en-US
An unsupported character encoding was declared on the transfer protocol level. The declaration was ignored.
Entity # all locales mail • chrome • mozldap • ldap.properties
83
eo
Encoding error
en-US
Encoding error
Entity # all locales mail • chrome • overrides • netError.dtd
contentEncodingError.title
eo
Content encoding error
en-US
Content encoding error
Entity # all locales mail • messenger • preferences • fonts.ftl
default-font-reply-checkbox.label
eo
When possible, use the default text encoding in replies
en-US
When possible, use the default text encoding in replies
Entity # all locales mail • messenger • preferences • fonts.ftl
text-encoding-description
eo
Set the default text encoding for sending and receiving mail
en-US
Set the default text encoding for sending and receiving mail
Entity # all locales mail • messenger • preferences • fonts.ftl
text-encoding-legend
eo
Text Encoding
en-US
Text Encoding
Entity # all locales security • manager • chrome • pipnss • nsserrors.properties
MOZILLA_PKIX_ERROR_INVALID_INTEGER_ENCODING
eo
The server presented a certificate that contains an invalid encoding of an integer. Common causes include negative serial numbers, negative RSA moduli, and encodings that are longer than necessary.
en-US
The server presented a certificate that contains an invalid encoding of an integer. Common causes include negative serial numbers, negative RSA moduli, and encodings that are longer than necessary.

Displaying 84 results for the string encoding in en-US:

Entity eo en-US
Entity # all locales browser • browser • aboutCertError.ftl
contentEncodingError-title
eo
Eraro de enkodigo de enhavo
en-US
Content Encoding Error
Entity # all locales browser • browser • menubar.ftl
menu-view-charset.label
eo
Teksta enkodigo
en-US
Text Encoding
Entity # all locales browser • browser • nsserrors.ftl
mozilla-pkix-error-invalid-integer-encoding
eo
The server presented a certificate that contains an invalid encoding of an integer. Common causes include negative serial numbers, negative RSA moduli, and encodings that are longer than necessary.
en-US
The server presented a certificate that contains an invalid encoding of an integer. Common causes include negative serial numbers, negative RSA moduli, and encodings that are longer than necessary.
Entity # all locales browser • browser • pageInfo.ftl
general-encoding.value
eo
Teksta enkodigo:
en-US
Text Encoding:
Entity # all locales browser • browser • preferences • fonts.ftl
fonts-languages-fallback-desc
eo
Tiu ĉi teksta enkodigo estas uzita por kaduka enhavo kiu ne deklaris sian enkodigon.
en-US
This text encoding is used for legacy content that fails to declare its encoding.
Entity # all locales browser • browser • preferences • fonts.ftl
fonts-languages-fallback-header
eo
Teksta enkodigo por kaduka enhavo
en-US
Text Encoding for Legacy Content
Entity # all locales browser • browser • preferences • fonts.ftl
fonts-languages-fallback-label
eo
Alternativa teksta ekondigo
en-US
Fallback Text Encoding
Entity # all locales browser • chrome • browser • customizableui • customizableWidgets.properties
characterencoding-button2.label
eo
\u00Teksta enkodigo
en-US
\u00adText Encoding
Entity # all locales browser • chrome • browser • customizableui • customizableWidgets.properties
characterencoding-button2.tooltiptext
eo
Montri preferojn de teksta enkodigo
en-US
Show text encoding options
Entity # all locales calendar • chrome • calendar • calendar.properties
utf8DecodeError
eo
An error occured while decoding an iCalendar (ics) file as UTF-8. Check that the file, including symbols and accented letters, is encoded using the UTF-8 character encoding.
en-US
An error occurred while decoding an iCalendar (ics) file as UTF-8. Check that the file, including symbols and accented letters, is encoded using the UTF-8 character encoding.
Entity # all locales dom • chrome • dom • dom.properties
JSONCharsetWarning
eo
An attempt was made to declare a non-UTF-8 encoding for JSON retrieved using XMLHttpRequest. Only UTF-8 is supported for decoding JSON.
en-US
An attempt was made to declare a non-UTF-8 encoding for JSON retrieved using XMLHttpRequest. Only UTF-8 is supported for decoding JSON.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadCryptoKeyHeader
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La mesaĝkapo ‘Crypto-Key‘ devas inkluzivi parametron ‘dh‘ , kiu enhavas la publikan ŝlosilon de la servilo de programoj. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Crypto-Key‘ header must include a ‘dh‘ parameter containing the app server’s public key. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadEncodingHeader
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La mesaĝkapo ‘Content-Encoding‘ devas esti ‘aesgcm‘. ‘aesgcm128‘ estas permesata, sed kaduka kaj baldaŭ forigota. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Content-Encoding‘ header must be ‘aesgcm‘. ‘aesgcm128‘ is allowed, but deprecated and will soon be removed. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadEncryptionHeader
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La mesaĝkapo ‘Encryption’ devas inkluzivi unikan ‘salt‘ paramentron por ĉiu mesaĝo. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Encryption’ header must include a unique ‘salt‘ parameter for each message. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadEncryptionKeyHeader
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La mesaĝkapo ‘Encryption-Key’devas inkluzivi parametron ‘dh‘. Tiu ĉi mesaĝkapo estas kaduka kaj baldaŭ forigota. Bonvolu anstataŭe uzi ‘Crypto-Key‘ kun ‘Content-Encoding: aesgcm‘. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘Encryption-Key’ header must include a ‘dh‘ parameter. This header is deprecated and will soon be removed. Please use ‘Crypto-Key‘ with ‘Content-Encoding: aesgcm‘ instead. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadPaddingError
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. Registro en la ĉifrita mesaĝo ne estis ĝuste ŝtopita. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. A record in the encrypted message was not padded correctly. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadRecordSize
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La parametro ‘rs‘ parameter de la mesaĝkapo ‘Encryption‘ devas esti ĉu inter %2$S kaj 2^36-31 ĉu preterlasita. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 por pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘rs‘ parameter of the ‘Encryption‘ header must be between %2$S and 2^36-31, or omitted entirely. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadSalt
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La parametro ‘salt‘ en la mesaĝkapo ‘Encryption‘ devas esti kodita de base64url (https://tools.ietf.org/html/rfc7515#appendix-C), kaj esti minimume 16 oktetoj longa antaŭ kodigo. Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘salt‘ parameter in the ‘Encryption‘ header must be base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C), and be at least 16 bytes before encoding. See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 for more information.
Entity # all locales dom • chrome • dom • dom.properties
PushMessageBadSenderKey
eo
La ServiceWorker por amplekso ‘%1$S’ ne sukcesis malĉifri mesaĝon push. La parametro ‘dh‘ en la mesaĝkapo ‘Crypto-Key‘ devas esti la publika ŝlosilo Diffie-Hellman de la servilo de programoj, base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C) kaj en “uncompressed” or “raw” formo (65 oktetoj antaŭ kodigo). Vidu https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 por havi pli da informo.
en-US
The ServiceWorker for scope ‘%1$S’ failed to decrypt a push message. The ‘dh‘ parameter in the ‘Crypto-Key‘ header must be the app server’s Diffie-Hellman public key, base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C) and in “uncompressed” or “raw” form (65 bytes before encoding). See https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 for more information.
Entity # all locales dom • chrome • layout • HtmlForm.properties
CannotEncodeAllUnicode
eo
Formularo estis sendita per la enkodigo %S, kiu ne povas kodigi ĉiujn signojn de Unikodo, do la informo enigita de la uzanto povus difektiĝi. Por eviti tiun ĉi problemon, la paĝon oni devus ŝanĝi tiel ke la formularo estos sendita en la enkodigo UTF-8, ĉu per ŝanĝado de la enkodigo de la paĝo al UTF-8, ĉu per specifado de accept-charset=utf-8 en la formulara elemento.
en-US
A form was submitted in the %S encoding which cannot encode all Unicode characters, so user input may get corrupted. To avoid this problem, the page should be changed so that the form is submitted in the UTF-8 encoding either by changing the encoding of the page itself to UTF-8 or by specifying accept-charset=utf-8 on the form element.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncBomlessUtf16
eo
Detected UTF-16-encoded Basic Latin-only text without a byte order mark and without a transfer protocol-level declaration. Encoding this content in UTF-16 is inefficient and the character encoding should have been declared in any case.
en-US
Detected UTF-16-encoded Basic Latin-only text without a byte order mark and without a transfer protocol-level declaration. Encoding this content in UTF-16 is inefficient and the character encoding should have been declared in any case.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncLateMeta
eo
The character encoding declaration of the HTML document was not found when prescanning the first 1024 bytes of the file. When viewed in a differently-configured browser, this page will reload automatically. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
en-US
The character encoding declaration of the HTML document was not found when prescanning the first 1024 bytes of the file. When viewed in a differently-configured browser, this page will reload automatically. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncLateMetaFrame
eo
The character encoding declaration of the framed HTML document was not found when prescanning the first 1024 bytes of the file. When viewed without the document framing it, the page will reload automatically. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
en-US
The character encoding declaration of the framed HTML document was not found when prescanning the first 1024 bytes of the file. When viewed without the document framing it, the page will reload automatically. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncLateMetaReload
eo
The page was reloaded, because the character encoding declaration of the HTML document was not found when prescanning the first 1024 bytes of the file. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
en-US
The page was reloaded, because the character encoding declaration of the HTML document was not found when prescanning the first 1024 bytes of the file. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncLateMetaTooLate
eo
The character encoding declaration of document was found too late for it to take effect. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
en-US
The character encoding declaration of document was found too late for it to take effect. The encoding declaration needs to be moved to be within the first 1024 bytes of the file.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaUnsupported
eo
An unsupported character encoding was declared for the HTML document using a meta tag. The declaration was ignored.
en-US
An unsupported character encoding was declared for the HTML document using a meta tag. The declaration was ignored.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaUserDefined
eo
A meta tag was used to declare the character encoding as x-user-defined. This was interpreted as a windows-1252 declaration instead for compatibility with intentionally mis-encoded legacy fonts. This site should migrate to Unicode.
en-US
A meta tag was used to declare the character encoding as x-user-defined. This was interpreted as a windows-1252 declaration instead for compatibility with intentionally mis-encoded legacy fonts. This site should migrate to Unicode.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaUtf16
eo
A meta tag was used to declare the character encoding as UTF-16. This was interpreted as an UTF-8 declaration instead.
en-US
A meta tag was used to declare the character encoding as UTF-16. This was interpreted as an UTF-8 declaration instead.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncNoDeclaration
eo
The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must to be declared in the document or in the transfer protocol.
en-US
The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncNoDeclarationFrame
eo
The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it.
en-US
The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncNoDeclarationPlain
eo
The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature.
en-US
The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature.
Entity # all locales dom • chrome • layout • htmlparser.properties
EncProtocolUnsupported
eo
An unsupported character encoding was declared on the transfer protocol level. The declaration was ignored.
en-US
An unsupported character encoding was declared on the transfer protocol level. The declaration was ignored.
Entity # all locales dom • chrome • layout • xmlparser.properties
18
eo
nekonata signokodo
en-US
unknown encoding
Entity # all locales dom • chrome • layout • xmlparser.properties
19
eo
malĝustas la signokodo difinita en la XMLa deklaro
en-US
encoding specified in XML declaration is incorrect
Entity # all locales dom • chrome • netError.dtd
contentEncodingError.title
eo
Eraro de enkodigo de enhavo
en-US
Content Encoding Error
Entity # all locales editor • ui • chrome • composer • editingOverlay.dtd
saveAsChangeEncodingCmd2.label
eo
Konservi kaj ŝanĝi tekstan enkodigon
en-US
Save And Change Text Encoding
Entity # all locales editor • ui • chrome • dialogs • EditorFormProperties.dtd
FormEncType.label
eo
Warning: Source string is missing
en-US
Encoding:
Entity # all locales editor • ui • chrome • dialogs • EditorSaveAsCharset.dtd
documentCharsetDesc2.label
eo
Warning: Source string is missing
en-US
Select the text encoding you want to save a document in:
Entity # all locales editor • ui • chrome • dialogs • EditorSaveAsCharset.dtd
documentCharsetTitle2.label
eo
Warning: Source string is missing
en-US
Text Encoding
Entity # all locales editor • ui • chrome • dialogs • EditorSaveAsCharset.dtd
windowTitle2.label
eo
Warning: Source string is missing
en-US
Save And Change Text Encoding
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.charset.help
eo
Warning: Source string is missing
en-US
Sets the character encoding mode for the current view to <new-charset>, or displays the current character encoding mode if <new-charset> is not provided.
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.default-charset.help
eo
Warning: Source string is missing
en-US
Sets the global default character encoding mode to <new-charset>, or displays the current global default character encoding mode if <new-charset> is not provided.
Entity # all locales extensions • irc • chrome • chatzilla.properties
cmd.join-charset.help
eo
Warning: Source string is missing
en-US
Joins the global (name starts with #), local (name starts with &), or modeless (name starts with a +) channel named <channel-name>. Messages will be encoded and decoded according to the character encoding specified by <charset>. The <charset> parameter is independent of the default character encoding, which can be selected with the /charset command. If no prefix is given, # is assumed. Provides the key <key> if specified.
Entity # all locales extensions • irc • chrome • chatzilla.properties
msg.current.charset
eo
Warning: Source string is missing
en-US
Using ``%S'' as default character encoding.
Entity # all locales extensions • irc • chrome • chatzilla.properties
msg.current.charset.view
eo
Warning: Source string is missing
en-US
Using ``%S'' as character encoding for this view.
Entity # all locales extensions • irc • chrome • chatzilla.properties
msg.err.invalid.charset
eo
Warning: Source string is missing
en-US
Invalid character encoding mode ``%S''.
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.charset.help
eo
Warning: Source string is missing
en-US
For multiple clients to correctly read messages with non-ASCII characters on IRC, they need to use the same character encoding.
Entity # all locales extensions • irc • chrome • chatzilla.properties
pref.charset.label
eo
Warning: Source string is missing
en-US
Character encoding
Entity # all locales mail • chrome • messenger • am-server-top.dtd
serverDefaultCharset2.label
eo
Implicita teksta kodprezento:
en-US
Default Text Encoding:
Entity # all locales mail • chrome • messenger • folderProps.dtd
folderCharsetEnforce2.label
eo
Apliki elektitan kodprezenton por ĉiuj mesaĝoj en la mesaĝujo (ignori individuan kodprezenton difinitan en mesaĝkapo kaj aŭtomatan eltrovon de kodprezento)
en-US
Apply encoding to all messages in the folder (individual message text encoding settings and auto-detection will be ignored)
Entity # all locales mail • chrome • messenger • folderProps.dtd
folderCharsetFallback2.label
eo
Alternativa teksta kodprezento:
en-US
Fallback Text Encoding:
Entity # all locales mail • chrome • messenger • messengercompose • messengercompose.dtd
encodingStatusPanel.tooltip
eo
Teksta kodprezento
en-US
Text encoding
Entity # all locales mail • chrome • mozldap • ldap.properties
83
eo
Encoding error
en-US
Encoding error
Entity # all locales mail • chrome • overrides • netError.dtd
contentEncodingError.title
eo
Content encoding error
en-US
Content encoding error
Entity # all locales mail • messenger • menubar.ftl
menu-view-charset.label
eo
Warning: Source string is missing
en-US
Text Encoding
Entity # all locales mail • messenger • openpgp • openpgp.ftl
quoted-printable-warn
eo
Warning: Source string is missing
en-US
You have enabled 'quoted-printable' encoding for sending messages. This may result in incorrect decryption and/or verification of your message. Do you wish to turn off sending 'quoted-printable' messages now?
Entity # all locales mail • messenger • preferences • fonts.ftl
default-font-reply-checkbox.label
eo
When possible, use the default text encoding in replies
en-US
When possible, use the default text encoding in replies
Entity # all locales mail • messenger • preferences • fonts.ftl
text-encoding-description
eo
Set the default text encoding for sending and receiving mail
en-US
Set the default text encoding for sending and receiving mail
Entity # all locales mail • messenger • preferences • fonts.ftl
text-encoding-legend
eo
Text Encoding
en-US
Text Encoding
Entity # all locales mobile • overrides • netError.dtd
contentEncodingError.title
eo
Eraro de enkodigo de enhavo
en-US
Content Encoding Error
Entity # all locales security • manager • chrome • pipnss • nsserrors.properties
MOZILLA_PKIX_ERROR_INVALID_INTEGER_ENCODING
eo
The server presented a certificate that contains an invalid encoding of an integer. Common causes include negative serial numbers, negative RSA moduli, and encodings that are longer than necessary.
en-US
The server presented a certificate that contains an invalid encoding of an integer. Common causes include negative serial numbers, negative RSA moduli, and encodings that are longer than necessary.
Entity # all locales suite • chrome • browser • pageInfo.dtd
formEncoding
eo
Warning: Source string is missing
en-US
Encoding:
Entity # all locales suite • chrome • browser • pageInfo.dtd
generalEncoding2
eo
Warning: Source string is missing
en-US
Text Encoding:
Entity # all locales suite • chrome • common • pref • pref-languages.dtd
languages.customize.Fallback2.desc
eo
Warning: Source string is missing
en-US
Used for legacy content that fails to declare its encoding.
Entity # all locales suite • chrome • common • pref • pref-languages.dtd
languages.customize.Fallback2.grouplabel
eo
Warning: Source string is missing
en-US
Text Encoding for Legacy Content
Entity # all locales suite • chrome • common • pref • pref-languages.dtd
languages.customize.Fallback2.label
eo
Warning: Source string is missing
en-US
Fallback Text Encoding:
Entity # all locales suite • chrome • editor • dialogs • EditorFormProperties.dtd
FormEncType.label
eo
Warning: Source string is missing
en-US
Encoding:
Entity # all locales suite • chrome • editor • dialogs • EditorSaveAsCharset.dtd
documentCharsetDesc2.label
eo
Warning: Source string is missing
en-US
Select the text encoding you want to save a document in:
Entity # all locales suite • chrome • editor • dialogs • EditorSaveAsCharset.dtd
documentCharsetTitle2.label
eo
Warning: Source string is missing
en-US
Text Encoding
Entity # all locales suite • chrome • editor • dialogs • EditorSaveAsCharset.dtd
windowTitle2.label
eo
Warning: Source string is missing
en-US
Save And Change Text Encoding
Entity # all locales suite • chrome • editor • editingOverlay.dtd
saveAsChangeEncodingCmd2.label
eo
Warning: Source string is missing
en-US
Save And Change Text Encoding
Entity # all locales suite • chrome • mailnews • folderProps.dtd
folderCharsetEnforce2.label
eo
Warning: Source string is missing
en-US
Apply encoding to all messages in the folder (individual message text encoding settings and auto-detection will be ignored)
Entity # all locales suite • chrome • mailnews • folderProps.dtd
folderCharsetFallback2.label
eo
Warning: Source string is missing
en-US
Fallback Text Encoding:
Entity # all locales suite • chrome • mailnews • pref • am-server-top.dtd
serverDefaultCharset2.label
eo
Warning: Source string is missing
en-US
Default Text Encoding:
Entity # all locales suite • chrome • mailnews • pref • mailPrefsOverlay.dtd
characterEncoding2.label
eo
Warning: Source string is missing
en-US
Text Encoding
Entity # all locales suite • chrome • mailnews • pref • pref-character_encoding.dtd
pref.character.encoding2.title
eo
Warning: Source string is missing
en-US
Text Encoding
Entity # all locales suite • chrome • mailnews • pref • pref-character_encoding.dtd
replyInDefaultCharset3.label
eo
Warning: Source string is missing
en-US
When possible, use this default text encoding in replies. (When unchecked, only new messages use this default.)
Entity # all locales suite • chrome • mailnews • pref • pref-character_encoding.dtd
sendDefaultCharset2.label
eo
Warning: Source string is missing
en-US
Default Text Encoding:
Entity # all locales suite • chrome • mailnews • pref • pref-character_encoding.dtd
useMIME.label
eo
Warning: Source string is missing
en-US
For messages that contain 8-bit characters, use 'quoted printable' MIME encoding. Leave unchecked to send the messages as is.
Entity # all locales suite • chrome • mailnews • pref • pref-character_encoding.dtd
viewFallbackCharset.desc
eo
Warning: Source string is missing
en-US
(Used for legacy content that does not declare its encoding.)
Entity # all locales suite • chrome • mailnews • pref • pref-character_encoding.dtd
viewFallbackCharset2.label
eo
Warning: Source string is missing
en-US
Fallback Text Encoding:
Entity # all locales suite • chrome • mozldap • ldap.properties
83
eo
Warning: Source string is missing
en-US
Encoding error
Entity # all locales toolkit • chrome • global • charsetMenu.dtd
charsetMenu2.label
eo
Teksta enkodigo
en-US
Text Encoding
Entity # all locales toolkit • chrome • global • charsetMenu.properties
charsetMenuCharsets
eo
Signa enkodigo
en-US
Character Encoding
Please enable JavaScript. Some features won't be available without it.