Main Views
QA Views
About Transvision
BETA
Filter by folder:
Show all results browser devtools dom security toolkit editor extensions mail suiteDisplaying 75 results for the string header in tl:
| Entity | tl | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • nsserrors.ftl sec-error-cert-addr-mismatch |
tl
Ang address sa pag-sign ng certificate ay hindi tumutugma sa address sa mga message header.
|
en-US
Address in signing certificate does not match address in message headers.
|
|
Entity
#
all locales
browser • browser • preferences • siteDataSettings.ftl site-data-removing-dialog.title |
tl
{ site-data-removing-header }
|
en-US
{ site-data-removing-header }
|
|
Entity
#
all locales
devtools • client • jsonview.properties jsonViewer.requestHeaders |
tl
Mga Request Header
|
en-US
Request Headers
|
|
Entity
#
all locales
devtools • client • jsonview.properties jsonViewer.responseHeaders |
tl
Mga Response Header
|
en-US
Response Headers
|
|
Entity
#
all locales
devtools • client • jsonview.properties jsonViewer.tab.Headers |
tl
Mga header
|
en-US
Headers
|
|
Entity
#
all locales
devtools • client • netmonitor.properties headersEmptyText |
tl
Walang mga header para sa kahilingang ito
|
en-US
No headers for this request
|
|
Entity
#
all locales
devtools • client • netmonitor.properties headersFilterText |
tl
Salain ang mga header
|
en-US
Filter Headers
|
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.context.copyRequestHeaders |
tl
Kopyahin ang mga Request Header
|
en-US
Copy Request Headers
|
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.context.copyResponseHeaders |
tl
Kopyahin ang mga Response Header
|
en-US
Copy Response Headers
|
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.custom.headers |
tl
Mga Request Header
|
en-US
Request Headers
|
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.tab.headers |
tl
Mga header
|
en-US
Headers
|
|
Entity
#
all locales
devtools • client • netmonitor.properties netmonitor.toolbar.responseHeaders |
tl
Mga response header
|
en-US
Response Headers
|
|
Entity
#
all locales
devtools • client • netmonitor.properties requestHeaders |
tl
Mga Request Header
|
en-US
Request Headers
|
|
Entity
#
all locales
devtools • client • netmonitor.properties requestHeadersFromUpload |
tl
Mga request header mula sa upload stream
|
en-US
Request headers from upload stream
|
|
Entity
#
all locales
devtools • client • netmonitor.properties responseHeaders |
tl
Mga response header
|
en-US
Response Headers
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties columnheader |
tl
column header
|
en-US
column header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties columnheaderAbbr |
tl
column header
|
en-US
column header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties header |
tl
header
|
en-US
header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties headerAbbr |
tl
header
|
en-US
header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties rowheader |
tl
row header
|
en-US
row header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties rowheaderAbbr |
tl
row header
|
en-US
row header
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties ForbiddenHeaderWarning |
tl
Tinanggihan ang tangkang mag-set ng ipinagbabawal na header: %S
|
en-US
Attempt to set a forbidden header was denied: %S
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties LargeAllocationNonE10S |
tl
May hindi pinansing Large-Allocation header dahil ang document ay hindi nai-load sa labas ng process.
|
en-US
A Large-Allocation header was ignored due to the document not being loaded out of process.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties LargeAllocationNonGetRequest |
tl
May hindi pinansing Large-Allocation header dahil ang pag-load ay na-trigger ng isang non-GET request.
|
en-US
A Large-Allocation header was ignored due to the load being triggered by a non-GET request.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties LargeAllocationNonWin32 |
tl
Ang pahinang ito ay malo-load sa bagong process dahil sa Large-Allocation header, kaso ang paggawa Large-Allocation process ay naka-disable sa mga non-Win32 platform.
|
en-US
This page would be loaded in a new process due to a Large-Allocation header, however Large-Allocation process creation is disabled on non-Win32 platforms.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties LargeAllocationNotOnlyToplevelInTabGroup |
tl
May hindi pinansing Large-Allocation header dahil sa pagkakaroon ng mga window na may reference sa browsing context na ito sa pamamagitan ng frame hierarchy o window.opener.
|
en-US
A Large-Allocation header was ignored due to the presence of windows which have a reference to this browsing context through the frame hierarchy or window.opener.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties LargeAllocationSuccess |
tl
Ang pahinang ito ay na-load sa bagong process dahil sa isang Large-Allocation header.
|
en-US
This page was loaded in a new process due to a Large-Allocation header.
|
|
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 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 • dom • dom.properties ServiceWorkerScopePathMismatch |
tl
Bigong mag-register ng ServiceWorker: Ang path ng naibigay na scope na ‘%1$S’ ay hindi pasok sa max scope na pinapayagan ‘%2$S’. Baguhin ang scope, ilipat ang Service Worker script, o gamitin ang Service-Worker-Allowed HTTP header para mapayagan ang scope.
|
en-US
Failed to register a ServiceWorker: The path of the provided scope ‘%1$S’ is not under the max scope allowed ‘%2$S’. Adjust the scope, move the Service Worker script, or use the Service-Worker-Allowed HTTP header to allow the scope.
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSAllowOriginNotMatchingOrigin |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Hindi kapareho ng CORS header ‘Access-Control-Allow-Origin’ ang ‘%2$S’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Access-Control-Allow-Origin’ does not match ‘%2$S’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSInvalidAllowHeader |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Invalid token ‘%2$S’ sa CORS header ‘Access-Control-Allow-Headers’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: invalid token ‘%2$S’ in CORS header ‘Access-Control-Allow-Headers’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSInvalidAllowMethod |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Invalid token na ‘%2$S’ sa CORS header ‘Access-Control-Allow-Methods’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: invalid token ‘%2$S’ in CORS header ‘Access-Control-Allow-Methods’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMethodNotFound |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Walang natagpuang method sa CORS header ‘Access-Control-Allow-Methods’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: Did not find method in CORS header ‘Access-Control-Allow-Methods’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMissingAllowCredentials |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: inaasahang ‘true’ ang CORS header ‘Access-Control-Allow-Credentials’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: expected ‘true’ in CORS header ‘Access-Control-Allow-Credentials’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMissingAllowOrigin |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Walang CORS header na ‘Access-Control-Allow-Origin’ ).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMultipleAllowOriginNotAllowed |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Hindi pwede ang maraming ‘Access-Control-Allow-Origin’ CORS header).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: Multiple CORS header ‘Access-Control-Allow-Origin’ not allowed).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSNotSupportingCredentials |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Hindi suportado ang credential kung ang CORS header ‘Access-Control-Allow-Origin’ ay ‘*’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at ‘%1$S’. (Reason: Credential is not supported if the CORS header ‘Access-Control-Allow-Origin’ is ‘*’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSOriginHeaderNotAdded |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Hindi maidagdag ang CORS header na ‘Origin’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Origin’ cannot be added).
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReferrerLengthOverLimitation |
tl
HTTP Referrer Header: Ang haba ay lampas na sa “%1$S” bytes limit - tinapyas ang referrer header hanggang sa origin: “%2$S”
|
en-US
HTTP Referrer header: Length is over “%1$S” bytes limit - stripping referrer header down to origin: “%2$S”
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReferrerOriginLengthOverLimitation |
tl
HTTP Referrer header: Ang haba ng origin sa loob ng referrer ay lampas na sa “%1$S” bytes limit - tinanggal ang referrer na may origin na “%2$S”.
|
en-US
HTTP Referrer header: Length of origin within referrer is over “%1$S” bytes limit - removing referrer with origin “%2$S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderDuplicateGroup |
tl
Reporting Header: di pinapansin ang dobleng pangkat na may pangalang “%S”.
|
en-US
Reporting Header: ignoring duplicated group named “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidEndpoint |
tl
Reporting Header: di pinapansin ang di-wastong endpoint para sa item na may pangalang “%S”.
|
en-US
Reporting Header: ignoring invalid endpoint for item named “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidItem |
tl
Reporting Header: di pinapansin ang di-wastong item na may pangalang “%S”.
|
en-US
Reporting Header: ignoring invalid item named “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidJSON |
tl
Reporting Header: di-wastong JSON value na natanggap.
|
en-US
Reporting Header: invalid JSON value received.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidNameItem |
tl
Reporting Header: di-wastong pangalan para sa pangkat.
|
en-US
Reporting Header: invalid name for group.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidURLEndpoint |
tl
Reporting Header: di pinapansin ang di-wastong endpoint URL na “%1$S” para sa item na may pangalang “%2$S”.
|
en-US
Reporting Header: ignoring invalid endpoint URL “%1$S” for item named “%2$S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties RunningClearSiteDataValue |
tl
Ang Clear-Site-Data header ay nagpwersa ng clean up ng “%S” data.
|
en-US
Clear-Site-Data header forced the clean up of “%S” data.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSCouldNotParseHeader |
tl
Strict-Transport-Security: Nagbanggit ang site ng header na nabigo ang pagkaka-parse.
|
en-US
Strict-Transport-Security: The site specified a header that could not be parsed successfully.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSInvalidIncludeSubdomains |
tl
Strict-Transport-Security: Nagbanggit ang site ng header na nagsama ng di-wastong ‘includeSubDomains’ directive.
|
en-US
Strict-Transport-Security: The site specified a header that included an invalid ‘includeSubDomains’ directive.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSInvalidMaxAge |
tl
Strict-Transport-Security: Nagbanggit ang site ng header na nagsama ng di-wastong ‘max-age’ directive.
|
en-US
Strict-Transport-Security: The site specified a header that included an invalid ‘max-age’ directive.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleIncludeSubdomains |
tl
Strict-Transport-Security: Nagbanggit ang site ng header na nagsama ng maraming mga ‘includeSubDomains’ directive.
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘includeSubDomains’ directives.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleMaxAges |
tl
Strict-Transport-Security: Nagbanggit ang site ng header na nagsama ng maraming mga ‘max-age’ directive.
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘max-age’ directives.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSNoMaxAge |
tl
Strict-Transport-Security: Nagbanggit ang site ng header na walang kasamang ‘max-age’ directive.
|
en-US
Strict-Transport-Security: The site specified a header that did not include a ‘max-age’ directive.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSUnknownError |
tl
Strict-Transport-Security: May di-kilalang problemang naganap sa pag-process ng header na nabanggit ng site.
|
en-US
Strict-Transport-Security: An unknown error occurred processing the header specified by the site.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSUntrustworthyConnection |
tl
Strict-Transport-Security: Hindi katiwa-tiwala ang connection sa site, kaya hindi pinansin ang nabanggit na header.
|
en-US
Strict-Transport-Security: The connection to the site is untrustworthy, so the specified header was ignored.
|
|
Entity
#
all locales
dom • chrome • security • security.properties UnknownClearSiteDataValue |
tl
May natagpuang Clear-Site-Data header. Di-kilalang value na “%S”.
|
en-US
Clear-Site-Data header found. Unknown value “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties XCTOHeaderValueMissing |
tl
Babala sa X-Content-Type-Options header: ang value ay “%1$S”; ibig mo bang sabihin ay mag-send ng “nosniff”?
|
en-US
X-Content-Type-Options header warning: value was “%1$S”; did you mean to send “nosniff”?
|
|
Entity
#
all locales
security • manager • chrome • pipnss • nsserrors.properties SEC_ERROR_CERT_ADDR_MISMATCH |
tl
Ang address sa pag-sign ng certificate ay hindi tumutugma sa address sa mga message header.
|
en-US
Address in signing certificate does not match address in message headers.
|
|
Entity
#
all locales
toolkit • chrome • global • printdialog.properties customHeaderFooterPrompt |
tl
Pakilagay ang iyong custom header/footer text
|
en-US
Please enter your custom header/footer text
|
|
Entity
#
all locales
toolkit • chrome • global • printdialog.properties headerFooter |
tl
Header at Footer
|
en-US
Header and Footer
|
|
Entity
#
all locales
toolkit • chrome • global • printdialog.properties pageHeadersTitleMac |
tl
Mga Header ng Pahina:
|
en-US
Page Headers:
|
|
Entity
#
all locales
toolkit • chrome • global • printdialog.properties summaryHeaderTitle |
tl
Mga Header ng Pahina
|
en-US
Page Headers
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl advanced-tab.label |
tl
Mga Margin at Header/Footer
|
en-US
Margins & Header/Footer
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl custom-prompt-prompt |
tl
Ilagay ang iyong pasadyang teksto para sa header/footer
|
en-US
Enter your custom header/footer text
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-center-tip.tooltiptext |
tl
Gitnang header
|
en-US
Center header
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-footer-label.value |
tl
Mga Header at Footer
|
en-US
Headers & Footers
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-left-tip.tooltiptext |
tl
Kaliwang header
|
en-US
Left header
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-right-tip.tooltiptext |
tl
Kanang header
|
en-US
Right header
|
|
Entity
#
all locales
toolkit • toolkit • printing • printUI.ftl printui-headers-footers-checkbox |
tl
I-print ang mga header at footer
|
en-US
Print headers and footers
|
Displaying 82 results for the string header in en-US:
| Entity | tl | en-US |
|---|---|---|
|
Entity
#
all locales
browser • browser • preferences • siteDataSettings.ftl site-data-removing-dialog.title |
tl
{ site-data-removing-header }
|
en-US
{ site-data-removing-header }
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties columnheader |
tl
column header
|
en-US
column header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties columnheaderAbbr |
tl
column header
|
en-US
column header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties header |
tl
header
|
en-US
header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties headerAbbr |
tl
header
|
en-US
header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties rowheader |
tl
row header
|
en-US
row header
|
|
Entity
#
all locales
dom • chrome • accessibility • AccessFu.properties rowheaderAbbr |
tl
row header
|
en-US
row header
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties ForbiddenHeaderWarning |
tl
Tinanggihan ang tangkang mag-set ng ipinagbabawal na header: %S
|
en-US
Attempt to set a forbidden header was denied: %S
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties LargeAllocationNonE10S |
tl
May hindi pinansing Large-Allocation header dahil ang document ay hindi nai-load sa labas ng process.
|
en-US
A Large-Allocation header was ignored due to the document not being loaded out of process.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties LargeAllocationNonGetRequest |
tl
May hindi pinansing Large-Allocation header dahil ang pag-load ay na-trigger ng isang non-GET request.
|
en-US
A Large-Allocation header was ignored due to the load being triggered by a non-GET request.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties LargeAllocationNonWin32 |
tl
Ang pahinang ito ay malo-load sa bagong process dahil sa Large-Allocation header, kaso ang paggawa Large-Allocation process ay naka-disable sa mga non-Win32 platform.
|
en-US
This page would be loaded in a new process due to a Large-Allocation header, however Large-Allocation process creation is disabled on non-Win32 platforms.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties LargeAllocationNotOnlyToplevelInTabGroup |
tl
May hindi pinansing Large-Allocation header dahil sa pagkakaroon ng mga window na may reference sa browsing context na ito sa pamamagitan ng frame hierarchy o window.opener.
|
en-US
A Large-Allocation header was ignored due to the presence of windows which have a reference to this browsing context through the frame hierarchy or window.opener.
|
|
Entity
#
all locales
dom • chrome • dom • dom.properties LargeAllocationSuccess |
tl
Ang pahinang ito ay na-load sa bagong process dahil sa isang Large-Allocation header.
|
en-US
This page was loaded in a new process due to a Large-Allocation header.
|
|
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 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 • dom • dom.properties ServiceWorkerScopePathMismatch |
tl
Bigong mag-register ng ServiceWorker: Ang path ng naibigay na scope na ‘%1$S’ ay hindi pasok sa max scope na pinapayagan ‘%2$S’. Baguhin ang scope, ilipat ang Service Worker script, o gamitin ang Service-Worker-Allowed HTTP header para mapayagan ang scope.
|
en-US
Failed to register a ServiceWorker: The path of the provided scope ‘%1$S’ is not under the max scope allowed ‘%2$S’. Adjust the scope, move the Service Worker script, or use the Service-Worker-Allowed HTTP header to allow the scope.
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSAllowOriginNotMatchingOrigin |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Hindi kapareho ng CORS header ‘Access-Control-Allow-Origin’ ang ‘%2$S’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Access-Control-Allow-Origin’ does not match ‘%2$S’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSInvalidAllowHeader |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Invalid token ‘%2$S’ sa CORS header ‘Access-Control-Allow-Headers’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: invalid token ‘%2$S’ in CORS header ‘Access-Control-Allow-Headers’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSInvalidAllowMethod |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Invalid token na ‘%2$S’ sa CORS header ‘Access-Control-Allow-Methods’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: invalid token ‘%2$S’ in CORS header ‘Access-Control-Allow-Methods’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMethodNotFound |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Walang natagpuang method sa CORS header ‘Access-Control-Allow-Methods’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: Did not find method in CORS header ‘Access-Control-Allow-Methods’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMissingAllowCredentials |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: inaasahang ‘true’ ang CORS header ‘Access-Control-Allow-Credentials’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: expected ‘true’ in CORS header ‘Access-Control-Allow-Credentials’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMissingAllowHeaderFromPreflight2 |
tl
Warning: Source string is missing
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: header ‘%2$S’ is not allowed according to header ‘Access-Control-Allow-Headers’ from CORS preflight response).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMissingAllowOrigin |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Walang CORS header na ‘Access-Control-Allow-Origin’ ).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSMultipleAllowOriginNotAllowed |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Hindi pwede ang maraming ‘Access-Control-Allow-Origin’ CORS header).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: Multiple CORS header ‘Access-Control-Allow-Origin’ not allowed).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSNotSupportingCredentials |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Hindi suportado ang credential kung ang CORS header ‘Access-Control-Allow-Origin’ ay ‘*’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at ‘%1$S’. (Reason: Credential is not supported if the CORS header ‘Access-Control-Allow-Origin’ is ‘*’).
|
|
Entity
#
all locales
dom • chrome • security • security.properties CORSOriginHeaderNotAdded |
tl
Hinarang ang Cross-Origin Request: Hindi pinapayagan ng Same Origin Policy ang pagbasa sa remote resource sa %1$S. (Dahilan: Hindi maidagdag ang CORS header na ‘Origin’).
|
en-US
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at %1$S. (Reason: CORS header ‘Origin’ cannot be added).
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReferrerLengthOverLimitation |
tl
HTTP Referrer Header: Ang haba ay lampas na sa “%1$S” bytes limit - tinapyas ang referrer header hanggang sa origin: “%2$S”
|
en-US
HTTP Referrer header: Length is over “%1$S” bytes limit - stripping referrer header down to origin: “%2$S”
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReferrerOriginLengthOverLimitation |
tl
HTTP Referrer header: Ang haba ng origin sa loob ng referrer ay lampas na sa “%1$S” bytes limit - tinanggal ang referrer na may origin na “%2$S”.
|
en-US
HTTP Referrer header: Length of origin within referrer is over “%1$S” bytes limit - removing referrer with origin “%2$S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderDuplicateGroup |
tl
Reporting Header: di pinapansin ang dobleng pangkat na may pangalang “%S”.
|
en-US
Reporting Header: ignoring duplicated group named “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidEndpoint |
tl
Reporting Header: di pinapansin ang di-wastong endpoint para sa item na may pangalang “%S”.
|
en-US
Reporting Header: ignoring invalid endpoint for item named “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidItem |
tl
Reporting Header: di pinapansin ang di-wastong item na may pangalang “%S”.
|
en-US
Reporting Header: ignoring invalid item named “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidJSON |
tl
Reporting Header: di-wastong JSON value na natanggap.
|
en-US
Reporting Header: invalid JSON value received.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidNameItem |
tl
Reporting Header: di-wastong pangalan para sa pangkat.
|
en-US
Reporting Header: invalid name for group.
|
|
Entity
#
all locales
dom • chrome • security • security.properties ReportingHeaderInvalidURLEndpoint |
tl
Reporting Header: di pinapansin ang di-wastong endpoint URL na “%1$S” para sa item na may pangalang “%2$S”.
|
en-US
Reporting Header: ignoring invalid endpoint URL “%1$S” for item named “%2$S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties RunningClearSiteDataValue |
tl
Ang Clear-Site-Data header ay nagpwersa ng clean up ng “%S” data.
|
en-US
Clear-Site-Data header forced the clean up of “%S” data.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSCouldNotParseHeader |
tl
Strict-Transport-Security: Nagbanggit ang site ng header na nabigo ang pagkaka-parse.
|
en-US
Strict-Transport-Security: The site specified a header that could not be parsed successfully.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSInvalidIncludeSubdomains |
tl
Strict-Transport-Security: Nagbanggit ang site ng header na nagsama ng di-wastong ‘includeSubDomains’ directive.
|
en-US
Strict-Transport-Security: The site specified a header that included an invalid ‘includeSubDomains’ directive.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSInvalidMaxAge |
tl
Strict-Transport-Security: Nagbanggit ang site ng header na nagsama ng di-wastong ‘max-age’ directive.
|
en-US
Strict-Transport-Security: The site specified a header that included an invalid ‘max-age’ directive.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleIncludeSubdomains |
tl
Strict-Transport-Security: Nagbanggit ang site ng header na nagsama ng maraming mga ‘includeSubDomains’ directive.
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘includeSubDomains’ directives.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSMultipleMaxAges |
tl
Strict-Transport-Security: Nagbanggit ang site ng header na nagsama ng maraming mga ‘max-age’ directive.
|
en-US
Strict-Transport-Security: The site specified a header that included multiple ‘max-age’ directives.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSNoMaxAge |
tl
Strict-Transport-Security: Nagbanggit ang site ng header na walang kasamang ‘max-age’ directive.
|
en-US
Strict-Transport-Security: The site specified a header that did not include a ‘max-age’ directive.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSUnknownError |
tl
Strict-Transport-Security: May di-kilalang problemang naganap sa pag-process ng header na nabanggit ng site.
|
en-US
Strict-Transport-Security: An unknown error occurred processing the header specified by the site.
|
|
Entity
#
all locales
dom • chrome • security • security.properties STSUntrustworthyConnection |
tl
Strict-Transport-Security: Hindi katiwa-tiwala ang connection sa site, kaya hindi pinansin ang nabanggit na header.
|
en-US
Strict-Transport-Security: The connection to the site is untrustworthy, so the specified header was ignored.
|
|
Entity
#
all locales
dom • chrome • security • security.properties UnknownClearSiteDataValue |
tl
May natagpuang Clear-Site-Data header. Di-kilalang value na “%S”.
|
en-US
Clear-Site-Data header found. Unknown value “%S”.
|
|
Entity
#
all locales
dom • chrome • security • security.properties XCTOHeaderValueMissing |
tl
Babala sa X-Content-Type-Options header: ang value ay “%1$S”; ibig mo bang sabihin ay mag-send ng “nosniff”?
|
en-US
X-Content-Type-Options header warning: value was “%1$S”; did you mean to send “nosniff”?
|
|
Entity
#
all locales
dom • chrome • security • security.properties XFrameOptionsInvalid |
tl
Warning: Source string is missing
|
en-US
Invalid X-Frame-Options header was found when loading “%2$S”: “%1$S” is not a valid directive.
|
|
Entity
#
all locales
editor • ui • chrome • dialogs • EditorTableProperties.dtd cellHeader.label |
tl
Warning: Source string is missing
|
en-US
Header
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.header.help |
tl
Warning: Source string is missing
|
en-US
Toggles visibility of the header bar.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.header.label |
tl
Warning: Source string is missing
|
en-US
Header
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.sync-header.help |
tl
Warning: Source string is missing
|
en-US
Synchronizes all views with their current header display setting.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties cmd.toggle-ui.help |
tl
Warning: Source string is missing
|
en-US
Toggles the visibility of various pieces of the user interface. <thing> must be one of: tabstrip, userlist, header, status.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties pref.displayHeader.help |
tl
Warning: Source string is missing
|
en-US
Display the chat header on this view. This contains information like the URL of the current view, and the topic and modes for a channel view.
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties pref.displayHeader.label |
tl
Warning: Source string is missing
|
en-US
Show header
|
|
Entity
#
all locales
extensions • irc • chrome • chatzilla.properties pref.outputWindowURL.help |
tl
Warning: Source string is missing
|
en-US
You probably don't want to change this. The chat view loads this URL to display the actual messages, header, etc., and the file must correctly define certain items or you'll get JavaScript errors and a blank chat window!
|
|
Entity
#
all locales
mail • chrome • messenger • CustomHeaders.dtd newMsgHeader.label |
tl
Warning: Source string is missing
|
en-US
New message header:
|
|
Entity
#
all locales
mail • chrome • messenger • addressbook • abCard.dtd preferDisplayName.label |
tl
Warning: Source string is missing
|
en-US
Always prefer display name over message header
|
|
Entity
#
all locales
mail • chrome • messenger • custom.properties colonInHeaderName |
tl
Warning: Source string is missing
|
en-US
The header you entered contains an invalid character, such as ':', a non-printable character, a non-ascii character, or an eight bit ascii character. Please remove the invalid character and try again.
|
|
Entity
#
all locales
mail • chrome • messenger • filter.properties invalidCustomHeader |
tl
Warning: Source string is missing
|
en-US
One of your filters uses a custom header that contains an invalid character, such as ':', a non-printable character, a non-ascii character, or an eight-bit ascii character. Please edit the msgFilterRules.dat file, which contains your filters, to remove invalid characters from your custom headers.
|
|
Entity
#
all locales
mail • chrome • messenger • imapMsgs.properties imapReceivingMessageHeaders3 |
tl
Warning: Source string is missing
|
en-US
Downloading message header %1$S of %2$S in %3$S…
|
|
Entity
#
all locales
mail • chrome • messenger • messengercompose • EditorTableProperties.dtd cellHeader.label |
tl
Warning: Source string is missing
|
en-US
Header
|
|
Entity
#
all locales
mail • messenger • openpgp • msgReadStatus.ftl message-security-button.title |
tl
Warning: Source string is missing
|
en-US
{ PLATFORM() ->
[macos] Show Message Security (⌃ ⌘ { message-header-show-security-info-key })
*[other] Show Message Security (Ctrl+Alt+{ message-header-show-security-info-key })
}
|
|
Entity
#
all locales
mail • messenger • preferences • preferences.ftl chat-header-label.label |
tl
Warning: Source string is missing
|
en-US
Show Header
|
|
Entity
#
all locales
suite • chrome • editor • dialogs • EditorTableProperties.dtd cellHeader.label |
tl
Warning: Source string is missing
|
en-US
Header
|
|
Entity
#
all locales
suite • chrome • mailnews • CustomHeaders.dtd newMsgHeader.label |
tl
Warning: Source string is missing
|
en-US
New message header:
|
|
Entity
#
all locales
suite • chrome • mailnews • addressbook • abCardOverlay.dtd preferDisplayName.label |
tl
Warning: Source string is missing
|
en-US
Always prefer display name over message header
|
|
Entity
#
all locales
suite • chrome • mailnews • custom.properties colonInHeaderName |
tl
Warning: Source string is missing
|
en-US
The header you entered contains an invalid character, such as ':', a non-printable character, a non-ascii character, or an eight bit ascii character. Please remove the invalid character and try again.
|
|
Entity
#
all locales
suite • chrome • mailnews • filter.properties invalidCustomHeader |
tl
Warning: Source string is missing
|
en-US
One of your filters uses a custom header that contains an invalid character, such as ':', a non-printable character, a non-ascii character, or an eight-bit ascii character. Please edit the msgFilterRules.dat file, which contains your filters, to remove invalid characters from your custom headers.
|
|
Entity
#
all locales
suite • chrome • mailnews • imapMsgs.properties imapReceivingMessageHeaders3 |
tl
Warning: Source string is missing
|
en-US
Downloading message header %1$S of %2$S in %3$S…
|
|
Entity
#
all locales
suite • chrome • mailnews • pref • pref-composing_messages.dtd noReplyOption.label |
tl
Warning: Source string is missing
|
en-US
No Reply Header
|
|
Entity
#
all locales
suite • chrome • mailnews • pref • pref-composing_messages.dtd selectHeaderType.label |
tl
Warning: Source string is missing
|
en-US
Select reply header type:
|
|
Entity
#
all locales
toolkit • chrome • global • printdialog.properties customHeaderFooterPrompt |
tl
Pakilagay ang iyong custom header/footer text
|
en-US
Please enter your custom header/footer text
|
|
Entity
#
all locales
toolkit • chrome • global • printdialog.properties headerFooter |
tl
Header at Footer
|
en-US
Header and Footer
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl advanced-tab.label |
tl
Mga Margin at Header/Footer
|
en-US
Margins & Header/Footer
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl custom-prompt-prompt |
tl
Ilagay ang iyong pasadyang teksto para sa header/footer
|
en-US
Enter your custom header/footer text
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-center-tip.tooltiptext |
tl
Gitnang header
|
en-US
Center header
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-left-tip.tooltiptext |
tl
Kaliwang header
|
en-US
Left header
|
|
Entity
#
all locales
toolkit • toolkit • printing • printDialogs.ftl header-right-tip.tooltiptext |
tl
Kanang header
|
en-US
Right header
|
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.