BETA

Transvision

Displaying 6 results for the string Meta in hi-IN:

Entity hi-IN en-US
Entity # all locales browser • browser • screenshots.ftl
screenshots-notification-image-copied-details 		hi-IN
आपके शॉट के लिंक क्लिपबोर्ड पर कॉपी किए गए हैं. पेस्ट करने के लिए { screenshots-meta-key }-V दबाएँ.
<source> Translate with: Google BING
en-US
Your shot has been copied to the clipboard. Press { screenshots-meta-key }-V to paste.
<source>  
Entity # all locales browser • browser • screenshots.ftl
screenshots-notification-link-copied-details 		hi-IN
आपके शॉट के लिंक क्लिपबोर्ड पर कॉपी किए गए हैं. पेस्ट करने के लिए { screenshots-meta-key }-V दबाएँ.
<source> Translate with: Google BING
en-US
The link to your shot has been copied to the clipboard. Press { screenshots-meta-key }-V to paste.
<source>  
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaUnsupported 		hi-IN
An unsupported character encoding was declared for the HTML document using a meta tag. The declaration was ignored.
<source> Translate with: Google BING
en-US
An unsupported character encoding was declared for the HTML document using a meta tag. The declaration was ignored.
<source>  
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaUtf16 		hi-IN
A meta tag was used to declare the character encoding as UTF-16. This was interpreted as an UTF-8 declaration instead.
<source> Translate with: Google BING
en-US
A meta tag was used to declare the character encoding as UTF-16. This was interpreted as an UTF-8 declaration instead.
<source>  
Entity # all locales toolkit • chrome • global-platform • unix • platformKeys.properties
VK_META 		hi-IN
Meta
<source> Translate with: Google BING
en-US
Meta
<source>  
Entity # all locales toolkit • chrome • global-platform • win • platformKeys.properties
VK_META 		hi-IN
Meta
<source> Translate with: Google BING
en-US
Meta
<source>  

Displaying 26 results for the string Meta in en-US:

Entity hi-IN en-US
Entity # all locales browser • browser • aboutLogins.ftl
about-logins-import-dialog-items-error 		hi-IN
Warning: Source string is missing
<source>
en-US
{ NUMBER($count) -> *[other] <span>Errors:</span> <span data-l10n-name="count">{ $count }</span> <span data-l10n-name="meta">(not imported)</span> }
<source>   Large string?
Entity # all locales browser • browser • aboutLogins.ftl
about-logins-import-dialog-items-no-change 		hi-IN
Warning: Source string is missing
<source>
en-US
{ NUMBER($count) -> *[other] <span>Duplicate logins found:</span> <span data-l10n-name="count">{ $count }</span> <span data-l10n-name="meta">(not imported)</span> }
<source>   Large string?
Entity # all locales browser • browser • aboutLogins.ftl
about-logins-import-dialog-items-no-change2 		hi-IN
Warning: Source string is missing
<source>
en-US
{ NUMBER($count) -> *[other] <span>Duplicate entries found:</span> <span data-l10n-name="count">{ $count }</span> <span data-l10n-name="meta">(not imported)</span> }
<source>   Large string?
Entity # all locales browser • browser • aboutRobots.ftl
error-long-desc4 		hi-IN
रोबोट के पीछे चमकीला धातु है जिसे काटा नहीं जाना चाहिए.
<source> Translate with: Google BING
en-US
Robots have shiny metal posteriors which should not be bitten.
<source>  
Entity # all locales browser • browser • pageInfo.ftl
general-meta-tags.value 		hi-IN
{ $tags -> [one] मेटा (1 टैग) *[other] मेटा ({ $tags } टैग्स) }
<source> Translate with: Google BING
en-US
{ NUMBER($tags) -> [one] Meta (1 tag) *[other] Meta ({ $tags } tags) }
<source>  
Entity # all locales browser • browser • screenshots.ftl
screenshots-notification-image-copied-details 		hi-IN
आपके शॉट के लिंक क्लिपबोर्ड पर कॉपी किए गए हैं. पेस्ट करने के लिए { screenshots-meta-key }-V दबाएँ.
<source> Translate with: Google BING
en-US
Your shot has been copied to the clipboard. Press { screenshots-meta-key }-V to paste.
<source>  
Entity # all locales browser • browser • screenshots.ftl
screenshots-notification-link-copied-details 		hi-IN
आपके शॉट के लिंक क्लिपबोर्ड पर कॉपी किए गए हैं. पेस्ट करने के लिए { screenshots-meta-key }-V दबाएँ.
<source> Translate with: Google BING
en-US
The link to your shot has been copied to the clipboard. Press { screenshots-meta-key }-V to paste.
<source>  
Entity # all locales devtools • client • webconsole.properties
webconsole.message.componentDidCatch.copyButton.label 		hi-IN
Warning: Source string is missing
<source>
en-US
Copy message metadata to clipboard
<source>  
Entity # all locales devtools • client • webconsole.properties
webconsole.message.componentDidCatch.label 		hi-IN
Warning: Source string is missing
<source>
en-US
[DEVTOOLS ERROR] We’re sorry, we couldn’t render the message. This shouldn’t have happened - please file a bug at %S with the message metadata in the description.
<source>   Large string?
Entity # all locales dom • chrome • layout • htmlparser.properties
EncDetectorReload 		hi-IN
Warning: Source string is missing
<source>
en-US
The character encoding of the document was not declared, and the encoding was guessable from content only late. This caused the document to be reloaded. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
<source>   Large string?
Entity # all locales dom • chrome • layout • htmlparser.properties
EncErrorFrame 		hi-IN
Warning: Source string is missing
<source>
en-US
The byte stream was erroneous according to the character encoding that was inherited from the parent document. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
<source>   Large string?
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaAfterHeadInKilobyte 		hi-IN
Warning: Source string is missing
<source>
en-US
The meta tag declaring the character encoding of the document should be moved to start of the head part of the document.
<source>   Large string?
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaReplacement 		hi-IN
Warning: Source string is missing
<source>
en-US
A meta tag was used to declare an encoding that is a cross-site scripting hazard. The replacement encoding was used instead.
<source>   Large string?
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaTooLate 		hi-IN
Warning: Source string is missing
<source>
en-US
A meta tag attempting to declare the character encoding declaration was found too late, and the encoding was guessed from content instead. The meta tag needs to be moved to the start of the head part of the document.
<source>   Large string?
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaTooLateFrame 		hi-IN
Warning: Source string is missing
<source>
en-US
A meta tag attempting to declare the character encoding declaration was found too late, and the encoding of the parent document was used instead. The meta tag needs to be moved to the start of the head part of the document.
<source>   Large string?
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaUnsupported 		hi-IN
An unsupported character encoding was declared for the HTML document using a meta tag. The declaration was ignored.
<source> Translate with: Google BING
en-US
An unsupported character encoding was declared for the HTML document using a meta tag. The declaration was ignored.
<source>  
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaUserDefined 		hi-IN
वर्ण एन्कोडिंग घोषित करने के लिए मेटा टैग प्रयोग किया गया था बतौर x-उपयोक्ता परिभाषित. इसे windows-1252 घोषणा के रूप में निर्वचित किया गया गलत रूप से एन्कोड किए पुरातन फॉन्ट के साथ वांछित रूप से संगतता के लिए. इस साइट को यूनीकोड में जाना चाहिए.
<source> Translate with: Google BING
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.
<source>  
Entity # all locales dom • chrome • layout • htmlparser.properties
EncMetaUtf16 		hi-IN
A meta tag was used to declare the character encoding as UTF-16. This was interpreted as an UTF-8 declaration instead.
<source> Translate with: Google BING
en-US
A meta tag was used to declare the character encoding as UTF-16. This was interpreted as an UTF-8 declaration instead.
<source>  
Entity # all locales dom • chrome • layout • htmlparser.properties
EncNoDecl 		hi-IN
Warning: Source string is missing
<source>
en-US
The character encoding of the document was not declared, so the encoding was guessed from content. The character encoding needs to be declared in the Content-Type HTTP header, using a meta tag, or using a byte order mark.
<source>   Large string?
Entity # all locales dom • chrome • layout • htmlparser.properties
EncSpeculationFailMeta 		hi-IN
Warning: Source string is missing
<source>
en-US
The start of the document was reparsed, because there were non-ASCII characters before the meta tag that declared the encoding. The meta should be the first child of head without non-ASCII comments before.
<source>   Large string?
Entity # all locales dom • chrome • layout • htmlparser.properties
EncSpeculationFailXml 		hi-IN
Warning: Source string is missing
<source>
en-US
The start of the document was reparsed, because there were non-ASCII characters in the part of the document that was unsuccessfully searched for a meta tag before falling back to the XML declaration syntax. A meta tag at the start of the head part should be used instead of the XML declaration syntax.
<source>   Large string?
Entity # all locales dom • chrome • layout • htmlparser.properties
EncXmlDecl 		hi-IN
Warning: Source string is missing
<source>
en-US
The character encoding of an HTML document was declared using the XML declaration syntax. This is non-conforming, and declaring the encoding using a meta tag at the start of the head part is more efficient.
<source>   Large string?
Entity # all locales dom • chrome • security • csp.properties
ignoringSrcFromMetaCSP 		hi-IN
स्रोत '%1$S' (जब मेटा एलिमेंट के द्वारा पहुँचाया जाता है तो समर्थन नहीं मिलता) की अनदेखी.
<source> Translate with: Google BING
en-US
Ignoring source ‘%1$S’ (Not supported when delivered via meta element).
<source>  
Entity # all locales dom • chrome • security • security.properties
NoValidMetadata 		hi-IN
अखंडता खासियत कोई वैध मेटाडाटा नहीं रखता हैं.
<source> Translate with: Google BING
en-US
The integrity attribute does not contain any valid metadata.
<source>  
Entity # all locales toolkit • chrome • global-platform • unix • platformKeys.properties
VK_META 		hi-IN
Meta
<source> Translate with: Google BING
en-US
Meta
<source>  
Entity # all locales toolkit • chrome • global-platform • win • platformKeys.properties
VK_META 		hi-IN
Meta
<source> Translate with: Google BING
en-US
Meta
<source>  

APIThese results are also available as an API request to search in hi-IN or en-US.
Learn more about the Transvision API.

Please enable JavaScript. Some features won't be available without it.