Main Views
QA Views
About Transvision
BETA
Displaying 29 results for the string encoding in et:
| Entity | et | en-US |
|---|---|---|
|
Entity
#
all locales
dom • chrome • dom • dom.properties JSONCharsetWarning |
et
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 |
et
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.
|
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 |
et
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.
|
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 |
et
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.
|
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 |
et
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.
|
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 |
et
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.
|
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 |
et
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.
|
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 |
et
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.
|
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 |
et
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.
|
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 EncDetectorReload |
et
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
en-US
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncDetectorReloadPlain |
et
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
en-US
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncError |
et
The byte stream was erroneous according to the character encoding that was declared. The character encoding declaration may be incorrect.
|
en-US
The byte stream was erroneous according to the character encoding that was declared. The character encoding declaration may be incorrect.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncErrorFrame |
et
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
en-US
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncErrorFramePlain |
et
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
en-US
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncMetaAfterHeadInKilobyte |
et
The meta tag declaring the character encoding of the document should be moved to start of the head part of the document.
|
en-US
The meta tag declaring the character encoding of the document should be moved to start of the head part of the document.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncMetaReplacement |
et
A meta tag was used to declare an encoding that is a cross-site scripting hazard. The replacement encoding was used instead.
|
en-US
A meta tag was used to declare an encoding that is a cross-site scripting hazard. The replacement encoding was used instead.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncMetaTooLate |
et
A meta tag attempting to declare the character encoding declaration was found too late, and the encoding was guessed from content instead. The meta tag needs to be moved to the start of the head part of the document.
|
en-US
A meta tag attempting to declare the character encoding declaration was found too late, and the encoding was guessed from content instead. The meta tag needs to be moved to the start of the head part of the document.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncMetaTooLateFrame |
et
A meta tag attempting to declare the character encoding declaration was found too late, and the encoding of the parent document was used instead. The meta tag needs to be moved to the start of the head part of the document.
|
en-US
A meta tag attempting to declare the character encoding declaration was found too late, and the encoding of the parent document was used instead. The meta tag needs to be moved to the start of the head part of the document.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncMetaUserDefined |
et
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 EncNoDecl |
et
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
en-US
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncNoDeclPlain |
et
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
en-US
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncProtocolReplacement |
et
An encoding that is a cross-site scripting hazard was declared on the transfer protocol level. The replacement encoding was used instead.
|
en-US
An encoding that is a cross-site scripting hazard was declared on the transfer protocol level. The replacement encoding was used instead.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncSpeculationFail2022 |
et
The start of the document was reparsed, because ISO-2022-JP is an ASCII-incompatible encoding.
|
en-US
The start of the document was reparsed, because ISO-2022-JP is an ASCII-incompatible encoding.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncSpeculationFailMeta |
et
The start of the document was reparsed, because there were non-ASCII characters before the meta tag that declared the encoding. The meta should be the first child of head without non-ASCII comments before.
|
en-US
The start of the document was reparsed, because there were non-ASCII characters before the meta tag that declared the encoding. The meta should be the first child of head without non-ASCII comments before.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncXmlDecl |
et
The character encoding of an HTML document was declared using the XML declaration syntax. This is non-conforming, and declaring the encoding using a meta tag at the start of the head part is more efficient.
|
en-US
The character encoding of an HTML document was declared using the XML declaration syntax. This is non-conforming, and declaring the encoding using a meta tag at the start of the head part is more efficient.
|
|
Entity
#
all locales
dom • chrome • layout • xmlparser.properties 18 |
et
tundmatu kodeering (unknown encoding)
|
en-US
unknown encoding
|
|
Entity
#
all locales
dom • chrome • layout • xmlparser.properties 19 |
et
XML-i deklaratsioonis määratletud kodeering on vale (encoding specified in XML declaration is incorrect)
|
en-US
encoding specified in XML declaration is incorrect
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_INVALID_INTEGER_ENCODING |
et
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
toolkit • toolkit • neterror • nsserrors.ftl mozilla-pkix-error-invalid-integer-encoding |
et
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 39 results for the string encoding in en-US:
| Entity | et | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • browser.ftl repair-text-encoding-button.label |
et
Paranda teksti kodeering
|
en-US
Repair text encoding
|
|
Entity
#
all locales
browser • browser • browser.ftl repair-text-encoding-button.tooltiptext |
et
Tuvasta lehe sisu alusel korrektne kodeering
|
en-US
Guess correct text encoding from page content
|
|
Entity
#
all locales
browser • browser • menubar.ftl menu-view-repair-text-encoding.label |
et
Paranda teksti kodeering
|
en-US
Repair Text Encoding
|
|
Entity
#
all locales
browser • browser • pageInfo.ftl general-encoding.value |
et
Teksti kodeering:
|
en-US
Text Encoding:
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties JSONCharsetWarning |
et
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 |
et
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.
|
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 |
et
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.
|
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 |
et
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.
|
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 |
et
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.
|
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 |
et
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.
|
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 |
et
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.
|
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 |
et
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.
|
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 |
et
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.
|
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 |
et
Vorm sisestati kodeeringus %S, mis pole võimeline kodeerima kõiki Unicode märke, seega võib kasutaja sisestatu rikutud saada. Probleemi vältimiseks tuleks lehte muuta nii, et vormiga sisestatud andmed oleks kodeeringus UTF-8. Selleks tuleb muuta kas leht ise kodeeringusse UTF-8 või siis lisada elemendile form järgnev atribuut: accept-charset=utf-8.
|
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 EncDetectorReload |
et
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
en-US
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncDetectorReloadPlain |
et
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
en-US
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncError |
et
The byte stream was erroneous according to the character encoding that was declared. The character encoding declaration may be incorrect.
|
en-US
The byte stream was erroneous according to the character encoding that was declared. The character encoding declaration may be incorrect.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncErrorFrame |
et
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
en-US
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncErrorFramePlain |
et
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
en-US
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncMetaAfterHeadInKilobyte |
et
The meta tag declaring the character encoding of the document should be moved to start of the head part of the document.
|
en-US
The meta tag declaring the character encoding of the document should be moved to start of the head part of the document.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncMetaReplacement |
et
A meta tag was used to declare an encoding that is a cross-site scripting hazard. The replacement encoding was used instead.
|
en-US
A meta tag was used to declare an encoding that is a cross-site scripting hazard. The replacement encoding was used instead.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncMetaTooLate |
et
A meta tag attempting to declare the character encoding declaration was found too late, and the encoding was guessed from content instead. The meta tag needs to be moved to the start of the head part of the document.
|
en-US
A meta tag attempting to declare the character encoding declaration was found too late, and the encoding was guessed from content instead. The meta tag needs to be moved to the start of the head part of the document.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncMetaTooLateFrame |
et
A meta tag attempting to declare the character encoding declaration was found too late, and the encoding of the parent document was used instead. The meta tag needs to be moved to the start of the head part of the document.
|
en-US
A meta tag attempting to declare the character encoding declaration was found too late, and the encoding of the parent document was used instead. The meta tag needs to be moved to the start of the head part of the document.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncMetaUnsupported |
et
HTML-dokumendi meta sildis määrati mittetoetatud kodeering. Määrangut ignoreeriti.
|
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 |
et
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 |
et
Kasutati meta silti, et määrata kodeeringuks UTF-16. See tõlgendati määranguna UTF-8.
|
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 EncNoDecl |
et
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
en-US
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncNoDeclPlain |
et
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
en-US
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header or using a byte order mark.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncNoDeclarationFrame |
et
Paneelil oleva dokumendi kodeering pole määratud. Selle dokumendi sisu võib näida erinev vaadates seda paneeli sisaldava dokumendita.
|
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 EncProtocolReplacement |
et
An encoding that is a cross-site scripting hazard was declared on the transfer protocol level. The replacement encoding was used instead.
|
en-US
An encoding that is a cross-site scripting hazard was declared on the transfer protocol level. The replacement encoding was used instead.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncProtocolUnsupported |
et
Ülekandeprotokolli tasemel määrati mittetoetatud kodeering. Määrangut ignoreeriti.
|
en-US
An unsupported character encoding was declared on the transfer protocol level. The declaration was ignored.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncSpeculationFail2022 |
et
The start of the document was reparsed, because ISO-2022-JP is an ASCII-incompatible encoding.
|
en-US
The start of the document was reparsed, because ISO-2022-JP is an ASCII-incompatible encoding.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncSpeculationFailMeta |
et
The start of the document was reparsed, because there were non-ASCII characters before the meta tag that declared the encoding. The meta should be the first child of head without non-ASCII comments before.
|
en-US
The start of the document was reparsed, because there were non-ASCII characters before the meta tag that declared the encoding. The meta should be the first child of head without non-ASCII comments before.
|
|
Entity
#
all locales
dom • chrome • layout • htmlparser.properties EncXmlDecl |
et
The character encoding of an HTML document was declared using the XML declaration syntax. This is non-conforming, and declaring the encoding using a meta tag at the start of the head part is more efficient.
|
en-US
The character encoding of an HTML document was declared using the XML declaration syntax. This is non-conforming, and declaring the encoding using a meta tag at the start of the head part is more efficient.
|
|
Entity
#
all locales
dom • chrome • layout • xmlparser.properties 18 |
et
tundmatu kodeering (unknown encoding)
|
en-US
unknown encoding
|
|
Entity
#
all locales
dom • chrome • layout • xmlparser.properties 19 |
et
XML-i deklaratsioonis määratletud kodeering on vale (encoding specified in XML declaration is incorrect)
|
en-US
encoding specified in XML declaration is incorrect
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_INVALID_INTEGER_ENCODING |
et
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
toolkit • toolkit • neterror • certError.ftl contentEncodingError-title |
et
Sisu kodeeringu viga
|
en-US
Content Encoding Error
|
|
Entity
#
all locales
toolkit • toolkit • neterror • nsserrors.ftl mozilla-pkix-error-invalid-integer-encoding |
et
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.
|
APIThese results are also available as an API request to search in
et or
en-US.
Learn more about the Transvision API.
Please enable JavaScript. Some features won't be available without it.