BETA

Transvision

Filter by folder:

Show all results dom toolkit suite

Displaying 4 results for the string Unicode in ff:

Entity ff en-US
Entity # all locales dom • chrome • layout • HtmlForm.properties
CannotEncodeAllUnicode 		ff
Formere nde waawaa dokkitaade alkule Unicode kala naatnaama e dokkitannde %S, wadde naatnal kuutoro ena waawi waɗde caɗeele. Ngam ruuɗaade ɗeen caɗeele, hello ngoo ena foti wayleede tawa formere ndee naatnaa ko e dokkitannde UTF-8 so waylude dokkitannde hello ngoo fayde e UTF-8 walla teeŋtinde jeɓgol charset=utf-8 e formere ndee.
<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 		ff
Tagere meta huutoraama ngam sifaade kodgol alkule x-user-defined. Ɗuum faamiraa ko no cifagol lomtotoongl ngol Windows-1252 nii ngam jahdugol e muulte donaaɗe ɗe kodiraaka no feewi. Ndee lowre ina foti eggude feewde 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 		ff
Tuugorɗe alkule boowal nokku Unicode jamiraaɗo.
<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 		ff
Unicode
<source> Translate with: Google BING
en-US
Unicode
<source>  

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

Entity ff en-US
Entity # all locales dom • chrome • layout • HtmlForm.properties
CannotEncodeAllUnicode 		ff
Formere nde waawaa dokkitaade alkule Unicode kala naatnaama e dokkitannde %S, wadde naatnal kuutoro ena waawi waɗde caɗeele. Ngam ruuɗaade ɗeen caɗeele, hello ngoo ena foti wayleede tawa formere ndee naatnaa ko e dokkitannde UTF-8 so waylude dokkitannde hello ngoo fayde e UTF-8 walla teeŋtinde jeɓgol charset=utf-8 e formere ndee.
<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 		ff
Tagere meta huutoraama ngam sifaade kodgol alkule x-user-defined. Ɗuum faamiraa ko no cifagol lomtotoongl ngol Windows-1252 nii ngam jahdugol e muulte donaaɗe ɗe kodiraaka no feewi. Ndee lowre ina foti eggude feewde 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 		ff
Tuugorɗe alkule boowal nokku Unicode jamiraaɗo.
<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 		ff
Warning: Source string is missing
<source>
en-US
Unicode (UTF-16)
<source>  
Entity # all locales mail • chrome • messenger • charsetTitles.properties
utf-16be.title 		ff
Warning: Source string is missing
<source>
en-US
Unicode (UTF-16BE)
<source>  
Entity # all locales mail • chrome • messenger • charsetTitles.properties
utf-16le.title 		ff
Warning: Source string is missing
<source>
en-US
Unicode (UTF-16LE)
<source>  
Entity # all locales mail • chrome • messenger • charsetTitles.properties
utf-7.title 		ff
Warning: Source string is missing
<source>
en-US
Unicode (UTF-7)
<source>  
Entity # all locales mail • chrome • messenger • charsetTitles.properties
utf-8.title 		ff
Warning: Source string is missing
<source>
en-US
Unicode (UTF-8)
<source>  
Entity # all locales suite • chrome • mailnews • charsetTitles.properties
utf-16.title 		ff
Warning: Source string is missing
<source>
en-US
Unicode (UTF-16)
<source>  
Entity # all locales suite • chrome • mailnews • charsetTitles.properties
utf-16be.title 		ff
Warning: Source string is missing
<source>
en-US
Unicode (UTF-16BE)
<source>  
Entity # all locales suite • chrome • mailnews • charsetTitles.properties
utf-16le.title 		ff
Warning: Source string is missing
<source>
en-US
Unicode (UTF-16LE)
<source>  
Entity # all locales suite • chrome • mailnews • charsetTitles.properties
utf-7.title 		ff
Warning: Source string is missing
<source>
en-US
Unicode (UTF-7)
<source>  
Entity # all locales suite • chrome • mailnews • charsetTitles.properties
utf-8.title 		ff
Warning: Source string is missing
<source>
en-US
Unicode (UTF-8)
<source>  
Entity # all locales toolkit • chrome • global • charsetMenu.properties
UTF-8 		ff
Unicode
<source> Translate with: Google BING
en-US
Unicode
<source>  

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

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