Main Views
QA Views
About Transvision
BETA
Filter by folder:
Show all results browser dom security toolkit calendar editor extensions mail mobile suiteDisplaying 30 results for the string encoding in tl:
| Entity | tl | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-invalid-integer-encoding |
tl
Ang server ay nagprisinta ng certificate na naglalaman ng di-wastong encoding ng isang integer. Ang mga karaniwang sanhi ay kagaya ng mga negative serial number, negative RSA moduli, at mga encoding na mas mahaba kaysa sa kinakailangan.
|
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 |
tl
Text Encoding:
|
en-US
Text Encoding:
|
|
Entity
#
all locales
browser • browser • preferences • fonts.ftl fonts-languages-fallback-header |
tl
Encoding ng Teksto para sa Lumang Nilalaman
|
en-US
Text Encoding for Legacy Content
|
|
Entity
#
all locales
browser • browser • preferences • fonts.ftl fonts-languages-fallback-label |
tl
Fallback na Encoding ng Teksto
|
en-US
Fallback Text Encoding
|
|
Entity
#
all locales
browser • chrome • browser • customizableui • customizableWidgets.properties characterencoding-button2.label |
tl
\u00adText Encoding
|
en-US
\u00adText Encoding
|
|
Entity
#
all locales
browser • chrome • browser • customizableui • customizableWidgets.properties characterencoding-button2.tooltiptext |
tl
Ipakita ang mga pagpipilian sa text encoding
|
en-US
Show text encoding options
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties JSONCharsetWarning |
tl
May pagtatangkang mag-declare ng non-UTF-8 encoding sa JSON na nakuha gamit ang XMLHttpRequest. Tanging UTF-8 lamang ang suportado sa pag-decode ng 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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Ang ‘Crypto-Key‘ header ay dapat magsama ng ‘dh‘ parameter na naglalakip ng public key ng app server. Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Dapat ang ‘Content-Encoding‘ header ay ‘aesgcm‘. Pinapayagan ang ‘aesgcm128‘, pero deprecated na ito at malapit nang tanggalin. Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Ang ‘Encryption’ header ay dapat magsama ng bukod-tanging ‘salt‘ parameter para sa bawat message. Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Ang ‘Encryption-Key’ header ay dapat magsama ng ‘dh‘ parameter. Ang header na ito ay deprecated na at malapit nang tanggalin. Sa halip ay pakigamit ang ‘Crypto-Key‘ na may ‘Content-Encoding: aesgcm‘. Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. May record sa encrypted message na hindi padded nang maayos. Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Dapat ang ‘rs‘ parameter ng ‘Encryption‘ header ay nasa pagitan ng %2$S at 2^36-31, o tinanggal nang buo. Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Dapat ang ‘salt‘ parameter sa ‘Encryption‘ header ay base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C), at dapat ay 16 bytes man lamang bago i-encode. Tingan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Dapat ang ‘dh‘ parameter sa ‘Crypto-Key‘ header ay ang Diffie-Hellman public key ng app server, base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C), at nasa “uncompressed” o “raw” form (65 bytes bago i-encode). Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 para sa karagdagang impormasyon.
|
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 |
tl
May form na na-submit gamit ang %S encoding na hindi kayang mag-encode ng lahat ng Unicode character, kung kaya't maaaring masira ang user input. Para maiwasan ito, dapat baguhin ang pahina para ang form ay ma-submit gamit ang UTF-8 encoding sa pamamagitan ng pagbago ng encoding ng pahina mismo sa UTF-8 o magbanggit ng accept-charset=utf-8 sa form element.
|
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 |
tl
May natuklasang UTF-16-encoded Basic Latin-only text na walang byte order mark at walang transfer protocol-level declaration. Ang pag-encode nitong content sa UTF-16 ay hindi epektibo at ang character encoding ay dapat na-declare anuman ang nangyari.
|
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 |
tl
Ang character encoding declaration ng HTML document ay hindi natagpuan habang pini-prescan ang unang 1024 bytes ng file. Kapag tiningnan sa browser na ibang configuration, ang pahinang ito magre-reload nang kusa. Ang encoding declaration ay kailangang mailipat sa loob ng unang 1024 bytes ng 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 |
tl
Ang dineklarang character encoding ng naka-frame na HTML document ay hindi natagpuan habang pini-prescan ang unang 1024 bytes ng file. Kapag tiningnan na hindi na-frame ng document, ang pahina ay magre-reload nang kusa. Ang encoding declaration ay kailangang mailipat sa loob ng unang 1024 bytes ng 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 |
tl
Nireload ang pahina, dahil ang character encoding declaration ng HTML document ay hindi natagpuan habang pini-prescan ang unang 1024 bytes ng file. Ang encoding declaration ay kailangang mailipat sa loob ng unang 1024 bytes ng 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 |
tl
Ang character encoding declaration ng document ay huli nang natagpuan para maging epektibo. Ang encoding declaration ay kailangang mailipat sa loob ng unang 1024 bytes ng 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 |
tl
May di-suportadong character encoding na dineklara para sa HTML document gamit ang meta tag. Hindi pinansin ang declaration.
|
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 |
tl
May meta tag na ginamit para magdeklara ng character encoding bilang x-user-defined. Sa halip, ito ay kinilala bilang isang windows-1252 declaration para sa compatibility sa mga sinadyang mis-encoded legacy font. Ang site na ito ay dapat mag-migrate sa 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 |
tl
May meta tag na ginamit para magdeklara ng character encoding bilang UTF-16. Sa halip, ito ay kinilala bilang isang UTF-8 declaration.
|
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 |
tl
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 |
tl
Hindi naka-declare ang character encoding ng dokumentong naka-frame. Maaaring magbago ang itsura nito kung titingnan nang direcho.
|
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 |
tl
Ang character encoding ng plain text document ay hindi nadeklara. Ang document ay magre-render na may garbled text sa ilang mga browser configuration kung ang document ay naglalaman ng mga character sa labas ng US-ASCII range. Ang character encoding ng file ay kinakailangang madeklara sa transfer protocol o kailangan ng file na gumamit ng byte order mark bilang 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 |
tl
May di-suportadong character encoding na dineklara sa transfer protocol level. Hindi pinansin ang declaration.
|
en-US
An unsupported character encoding was declared on the transfer protocol level. The declaration was ignored.
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_INVALID_INTEGER_ENCODING |
tl
Ang server ay nagprisinta ng certificate na naglalaman ng di-wastong encoding ng isang integer. Ang mga karaniwang sanhi ay kagaya ng mga negative serial number, negative RSA moduli, at mga encoding na mas mahaba kaysa sa kinakailangan.
|
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 • chrome • global • charsetMenu.properties charsetMenuCharsets |
tl
Character Encoding
|
en-US
Character Encoding
|
Displaying 84 results for the string encoding in en-US:
| Entity | tl | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • aboutCertError.ftl contentEncodingError-title |
tl
May mali sa pag-encode na content
|
en-US
Content Encoding Error
|
|
Entity
#
all locales
browser • browser • menubar.ftl menu-view-charset.label |
tl
Pag-encode ng Teksto
|
en-US
Text Encoding
|
|
Entity
#
all locales
browser • browser • nsserrors.ftl mozilla-pkix-error-invalid-integer-encoding |
tl
Ang server ay nagprisinta ng certificate na naglalaman ng di-wastong encoding ng isang integer. Ang mga karaniwang sanhi ay kagaya ng mga negative serial number, negative RSA moduli, at mga encoding na mas mahaba kaysa sa kinakailangan.
|
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 |
tl
Text Encoding:
|
en-US
Text Encoding:
|
|
Entity
#
all locales
browser • browser • preferences • fonts.ftl fonts-languages-fallback-desc |
tl
Ang pag-encode ng teksto na ito ay ginagamit para sa lumang nilalaman na nabigong ipahayag ang pag-encode nito.
|
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 |
tl
Encoding ng Teksto para sa Lumang Nilalaman
|
en-US
Text Encoding for Legacy Content
|
|
Entity
#
all locales
browser • browser • preferences • fonts.ftl fonts-languages-fallback-label |
tl
Fallback na Encoding ng Teksto
|
en-US
Fallback Text Encoding
|
|
Entity
#
all locales
browser • chrome • browser • customizableui • customizableWidgets.properties characterencoding-button2.label |
tl
\u00adText Encoding
|
en-US
\u00adText Encoding
|
|
Entity
#
all locales
browser • chrome • browser • customizableui • customizableWidgets.properties characterencoding-button2.tooltiptext |
tl
Ipakita ang mga pagpipilian sa text encoding
|
en-US
Show text encoding options
|
|
Entity
#
all locales
calendar • chrome • calendar • calendar.properties utf8DecodeError |
tl
Warning: Source string is missing
|
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 |
tl
May pagtatangkang mag-declare ng non-UTF-8 encoding sa JSON na nakuha gamit ang XMLHttpRequest. Tanging UTF-8 lamang ang suportado sa pag-decode ng 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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Ang ‘Crypto-Key‘ header ay dapat magsama ng ‘dh‘ parameter na naglalakip ng public key ng app server. Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Dapat ang ‘Content-Encoding‘ header ay ‘aesgcm‘. Pinapayagan ang ‘aesgcm128‘, pero deprecated na ito at malapit nang tanggalin. Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Ang ‘Encryption’ header ay dapat magsama ng bukod-tanging ‘salt‘ parameter para sa bawat message. Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Ang ‘Encryption-Key’ header ay dapat magsama ng ‘dh‘ parameter. Ang header na ito ay deprecated na at malapit nang tanggalin. Sa halip ay pakigamit ang ‘Crypto-Key‘ na may ‘Content-Encoding: aesgcm‘. Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. May record sa encrypted message na hindi padded nang maayos. Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-2 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Dapat ang ‘rs‘ parameter ng ‘Encryption‘ header ay nasa pagitan ng %2$S at 2^36-31, o tinanggal nang buo. Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Dapat ang ‘salt‘ parameter sa ‘Encryption‘ header ay base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C), at dapat ay 16 bytes man lamang bago i-encode. Tingan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-3.1 para sa karagdagang impormasyon.
|
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 |
tl
Ang ServiceWorker para sa scope ‘%1$S’ ay bigong makapag-decrypt ng push message. Dapat ang ‘dh‘ parameter sa ‘Crypto-Key‘ header ay ang Diffie-Hellman public key ng app server, base64url-encoded (https://tools.ietf.org/html/rfc7515#appendix-C), at nasa “uncompressed” o “raw” form (65 bytes bago i-encode). Tingnan ang https://tools.ietf.org/html/draft-ietf-httpbis-encryption-encoding-02#section-4 para sa karagdagang impormasyon.
|
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 |
tl
May form na na-submit gamit ang %S encoding na hindi kayang mag-encode ng lahat ng Unicode character, kung kaya't maaaring masira ang user input. Para maiwasan ito, dapat baguhin ang pahina para ang form ay ma-submit gamit ang UTF-8 encoding sa pamamagitan ng pagbago ng encoding ng pahina mismo sa UTF-8 o magbanggit ng accept-charset=utf-8 sa form element.
|
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 |
tl
May natuklasang UTF-16-encoded Basic Latin-only text na walang byte order mark at walang transfer protocol-level declaration. Ang pag-encode nitong content sa UTF-16 ay hindi epektibo at ang character encoding ay dapat na-declare anuman ang nangyari.
|
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 |
tl
Ang character encoding declaration ng HTML document ay hindi natagpuan habang pini-prescan ang unang 1024 bytes ng file. Kapag tiningnan sa browser na ibang configuration, ang pahinang ito magre-reload nang kusa. Ang encoding declaration ay kailangang mailipat sa loob ng unang 1024 bytes ng 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 |
tl
Ang dineklarang character encoding ng naka-frame na HTML document ay hindi natagpuan habang pini-prescan ang unang 1024 bytes ng file. Kapag tiningnan na hindi na-frame ng document, ang pahina ay magre-reload nang kusa. Ang encoding declaration ay kailangang mailipat sa loob ng unang 1024 bytes ng 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 |
tl
Nireload ang pahina, dahil ang character encoding declaration ng HTML document ay hindi natagpuan habang pini-prescan ang unang 1024 bytes ng file. Ang encoding declaration ay kailangang mailipat sa loob ng unang 1024 bytes ng 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 |
tl
Ang character encoding declaration ng document ay huli nang natagpuan para maging epektibo. Ang encoding declaration ay kailangang mailipat sa loob ng unang 1024 bytes ng 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 |
tl
May di-suportadong character encoding na dineklara para sa HTML document gamit ang meta tag. Hindi pinansin ang declaration.
|
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 |
tl
May meta tag na ginamit para magdeklara ng character encoding bilang x-user-defined. Sa halip, ito ay kinilala bilang isang windows-1252 declaration para sa compatibility sa mga sinadyang mis-encoded legacy font. Ang site na ito ay dapat mag-migrate sa 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 |
tl
May meta tag na ginamit para magdeklara ng character encoding bilang UTF-16. Sa halip, ito ay kinilala bilang isang UTF-8 declaration.
|
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 |
tl
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 |
tl
Hindi naka-declare ang character encoding ng dokumentong naka-frame. Maaaring magbago ang itsura nito kung titingnan nang direcho.
|
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 |
tl
Ang character encoding ng plain text document ay hindi nadeklara. Ang document ay magre-render na may garbled text sa ilang mga browser configuration kung ang document ay naglalaman ng mga character sa labas ng US-ASCII range. Ang character encoding ng file ay kinakailangang madeklara sa transfer protocol o kailangan ng file na gumamit ng byte order mark bilang 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 |
tl
May di-suportadong character encoding na dineklara sa transfer protocol level. Hindi pinansin ang declaration.
|
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 |
tl
hindi alam na pag-encode
|
en-US
unknown encoding
|
|
Entity
#
all locales
dom • chrome • layout • xmlparser.properties 19 |
tl
Hindi tama ang pag-encode na tinukoy sa deklarasyon ng XML
|
en-US
encoding specified in XML declaration is incorrect
|
|
Entity
#
all locales
dom • chrome • netError.dtd contentEncodingError.title |
tl
Error sa Pag-encode ng Nilalaman
|
en-US
Content Encoding Error
|
|
Entity
#
all locales
editor • ui • chrome • composer • editingOverlay.dtd saveAsChangeEncodingCmd2.label |
tl
Warning: Source string is missing
|
en-US
Save And Change Text Encoding
|
|
Entity
#
all locales
editor • ui • chrome • dialogs • EditorFormProperties.dtd FormEncType.label |
tl
Warning: Source string is missing
|
en-US
Encoding:
|
|
Entity
#
all locales
editor • ui • chrome • dialogs • EditorSaveAsCharset.dtd documentCharsetDesc2.label |
tl
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 |
tl
Warning: Source string is missing
|
en-US
Text Encoding
|
|
Entity
#
all locales
editor • ui • chrome • dialogs • EditorSaveAsCharset.dtd windowTitle2.label |
tl
Warning: Source string is missing
|
en-US
Save And Change Text Encoding
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.charset.help |
tl
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 |
tl
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 |
tl
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 |
tl
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 |
tl
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 |
tl
Warning: Source string is missing
|
en-US
Invalid character encoding mode ``%S''.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties pref.charset.help |
tl
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 |
tl
Warning: Source string is missing
|
en-US
Character encoding
|
|
Entity
#
all locales
mail • chrome • messenger • am-server-top.dtd serverDefaultCharset2.label |
tl
Warning: Source string is missing
|
en-US
Default Text Encoding:
|
|
Entity
#
all locales
mail • chrome • messenger • folderProps.dtd folderCharsetEnforce2.label |
tl
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
mail • chrome • messenger • folderProps.dtd folderCharsetFallback2.label |
tl
Warning: Source string is missing
|
en-US
Fallback Text Encoding:
|
|
Entity
#
all locales
mail • chrome • messenger • messengercompose • messengercompose.dtd encodingStatusPanel.tooltip |
tl
Warning: Source string is missing
|
en-US
Text encoding
|
|
Entity
#
all locales
mail • chrome • mozldap • ldap.properties 83 |
tl
Warning: Source string is missing
|
en-US
Encoding error
|
|
Entity
#
all locales
mail • chrome • overrides • netError.dtd contentEncodingError.title |
tl
Warning: Source string is missing
|
en-US
Content encoding error
|
|
Entity
#
all locales
mail • messenger • menubar.ftl menu-view-charset.label |
tl
Warning: Source string is missing
|
en-US
Text Encoding
|
|
Entity
#
all locales
mail • messenger • openpgp • openpgp.ftl quoted-printable-warn |
tl
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 |
tl
Warning: Source string is missing
|
en-US
When possible, use the default text encoding in replies
|
|
Entity
#
all locales
mail • messenger • preferences • fonts.ftl text-encoding-description |
tl
Warning: Source string is missing
|
en-US
Set the default text encoding for sending and receiving mail
|
|
Entity
#
all locales
mail • messenger • preferences • fonts.ftl text-encoding-legend |
tl
Warning: Source string is missing
|
en-US
Text Encoding
|
|
Entity
#
all locales
mobile • overrides • netError.dtd contentEncodingError.title |
tl
Error sa Pag-encode ng Nilalaman
|
en-US
Content Encoding Error
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties MOZILLA_PKIX_ERROR_INVALID_INTEGER_ENCODING |
tl
Ang server ay nagprisinta ng certificate na naglalaman ng di-wastong encoding ng isang integer. Ang mga karaniwang sanhi ay kagaya ng mga negative serial number, negative RSA moduli, at mga encoding na mas mahaba kaysa sa kinakailangan.
|
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 |
tl
Warning: Source string is missing
|
en-US
Encoding:
|
|
Entity
#
all locales
suite • chrome • browser • pageInfo.dtd generalEncoding2 |
tl
Warning: Source string is missing
|
en-US
Text Encoding:
|
|
Entity
#
all locales
suite • chrome • common • pref • pref-languages.dtd languages.customize.Fallback2.desc |
tl
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 |
tl
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 |
tl
Warning: Source string is missing
|
en-US
Fallback Text Encoding:
|
|
Entity
#
all locales
suite • chrome • editor • dialogs • EditorFormProperties.dtd FormEncType.label |
tl
Warning: Source string is missing
|
en-US
Encoding:
|
|
Entity
#
all locales
suite • chrome • editor • dialogs • EditorSaveAsCharset.dtd documentCharsetDesc2.label |
tl
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 |
tl
Warning: Source string is missing
|
en-US
Text Encoding
|
|
Entity
#
all locales
suite • chrome • editor • dialogs • EditorSaveAsCharset.dtd windowTitle2.label |
tl
Warning: Source string is missing
|
en-US
Save And Change Text Encoding
|
|
Entity
#
all locales
suite • chrome • editor • editingOverlay.dtd saveAsChangeEncodingCmd2.label |
tl
Warning: Source string is missing
|
en-US
Save And Change Text Encoding
|
|
Entity
#
all locales
suite • chrome • mailnews • folderProps.dtd folderCharsetEnforce2.label |
tl
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 |
tl
Warning: Source string is missing
|
en-US
Fallback Text Encoding:
|
|
Entity
#
all locales
suite • chrome • mailnews • pref • am-server-top.dtd serverDefaultCharset2.label |
tl
Warning: Source string is missing
|
en-US
Default Text Encoding:
|
|
Entity
#
all locales
suite • chrome • mailnews • pref • mailPrefsOverlay.dtd characterEncoding2.label |
tl
Warning: Source string is missing
|
en-US
Text Encoding
|
|
Entity
#
all locales
suite • chrome • mailnews • pref • pref-character_encoding.dtd pref.character.encoding2.title |
tl
Warning: Source string is missing
|
en-US
Text Encoding
|
|
Entity
#
all locales
suite • chrome • mailnews • pref • pref-character_encoding.dtd replyInDefaultCharset3.label |
tl
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 |
tl
Warning: Source string is missing
|
en-US
Default Text Encoding:
|
|
Entity
#
all locales
suite • chrome • mailnews • pref • pref-character_encoding.dtd useMIME.label |
tl
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 |
tl
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 |
tl
Warning: Source string is missing
|
en-US
Fallback Text Encoding:
|
|
Entity
#
all locales
suite • chrome • mozldap • ldap.properties 83 |
tl
Warning: Source string is missing
|
en-US
Encoding error
|
|
Entity
#
all locales
toolkit • chrome • global • charsetMenu.dtd charsetMenu2.label |
tl
Pag-encode ng Teksto
|
en-US
Text Encoding
|
|
Entity
#
all locales
toolkit • chrome • global • charsetMenu.properties charsetMenuCharsets |
tl
Character Encoding
|
en-US
Character Encoding
|
APIThese results are also available as an API request to search in
tl or
en-US.
Learn more about the Transvision API.
Please enable JavaScript. Some features won't be available without it.