BETA

Transvision

Filter by folder:

Show all results dom toolkit suite

Displaying 4 results for the string Unicode in tl:

Entity tl en-US
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.
<source> Translate with: Google BING
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.
<source>  
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.
<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
errNcrOutOfRange 		tl
ginagayahan na character sa labas ng permissible Unicode range.
<source> Translate with: Google BING
en-US
Character reference outside the permissible Unicode range.
<source>  
Entity # all locales toolkit • chrome • global • charsetMenu.properties
UTF-8 		tl
Unicode
<source> Translate with: Google BING
en-US
Unicode
<source>  

Displaying 14 results for the string Unicode in en-US:

Entity tl en-US
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.
<source> Translate with: Google BING
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.
<source>  
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.
<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
errNcrOutOfRange 		tl
ginagayahan na character sa labas ng permissible Unicode range.
<source> Translate with: Google BING
en-US
Character reference outside the permissible Unicode range.
<source>  
Entity # all locales mail • chrome • messenger • charsetTitles.properties
utf-16.title 		tl
Warning: Source string is missing
<source>
en-US
Unicode (UTF-16)
<source>  
Entity # all locales mail • chrome • messenger • charsetTitles.properties
utf-16be.title 		tl
Warning: Source string is missing
<source>
en-US
Unicode (UTF-16BE)
<source>  
Entity # all locales mail • chrome • messenger • charsetTitles.properties
utf-16le.title 		tl
Warning: Source string is missing
<source>
en-US
Unicode (UTF-16LE)
<source>  
Entity # all locales mail • chrome • messenger • charsetTitles.properties
utf-7.title 		tl
Warning: Source string is missing
<source>
en-US
Unicode (UTF-7)
<source>  
Entity # all locales mail • chrome • messenger • charsetTitles.properties
utf-8.title 		tl
Warning: Source string is missing
<source>
en-US
Unicode (UTF-8)
<source>  
Entity # all locales suite • chrome • mailnews • charsetTitles.properties
utf-16.title 		tl
Warning: Source string is missing
<source>
en-US
Unicode (UTF-16)
<source>  
Entity # all locales suite • chrome • mailnews • charsetTitles.properties
utf-16be.title 		tl
Warning: Source string is missing
<source>
en-US
Unicode (UTF-16BE)
<source>  
Entity # all locales suite • chrome • mailnews • charsetTitles.properties
utf-16le.title 		tl
Warning: Source string is missing
<source>
en-US
Unicode (UTF-16LE)
<source>  
Entity # all locales suite • chrome • mailnews • charsetTitles.properties
utf-7.title 		tl
Warning: Source string is missing
<source>
en-US
Unicode (UTF-7)
<source>  
Entity # all locales suite • chrome • mailnews • charsetTitles.properties
utf-8.title 		tl
Warning: Source string is missing
<source>
en-US
Unicode (UTF-8)
<source>  
Entity # all locales toolkit • chrome • global • charsetMenu.properties
UTF-8 		tl
Unicode
<source> Translate with: Google BING
en-US
Unicode
<source>  

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.