Main Views
QA Views
About Transvision
BETA
Displaying 8 results for the string Unicode in cak:
| Entity | cak | en-US |
|---|---|---|
|
Entity
#
all locales
dom • chrome • layout • HtmlForm.properties CannotEncodeAllUnicode |
cak
Xtaq jun nojwuj rik'in ri rucholajil %S, ri man nitikïr ta nub'än kicholajil konojel ri Unicode taq tz'ib', ruma ri' toq rik'in jub'a' xtz'iläx ri rokem winäq. Richin man nuya' ta re k'ayewal re', k'o ta chi ri ruxaq k'amaya'l nijal richin tikirel nitaq pa ri rucholajil UTF-8 rik'in rujalik rucholajil ri ruxaq k'amaya'l pa UTF-8 o niya' retal accept-charset=utf-8 pa ri ch'akulal form.
|
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 EncMetaUserDefined |
cak
Xokisäx jun q'i'on yaketal richin nijikib'äx ri kicholajil taq tz'ib' achi'el x-user-defined. Xa xe chi xq'ijüx achi'el jun windows-1252 jikib'anïk ruma rujunamil kik'in ojer taq ruwäch tz'ib', ri kan echolajin pa man ütz ta rub'anikil. Re ruxaq k'amaya'l re' k'o ta chi nib'e pa Unicode.\u0020
|
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 errNcrOutOfRange |
cak
Retal jun tz'ib' elenäq pa ri okel Unicode rajilab'al.
|
en-US
Character reference outside the permissible Unicode range.
|
|
Entity
#
all locales
mail • chrome • messenger • charsetTitles.properties utf-16.title |
cak
Unicode (UTF-16)
|
en-US
Unicode (UTF-16)
|
|
Entity
#
all locales
mail • chrome • messenger • charsetTitles.properties utf-16be.title |
cak
Unicode (UTF-16BE)
|
en-US
Unicode (UTF-16BE)
|
|
Entity
#
all locales
mail • chrome • messenger • charsetTitles.properties utf-16le.title |
cak
Unicode (UTF-16LE)
|
en-US
Unicode (UTF-16LE)
|
|
Entity
#
all locales
mail • chrome • messenger • charsetTitles.properties utf-7.title |
cak
Unicode (UTF-7)
|
en-US
Unicode (UTF-7)
|
|
Entity
#
all locales
mail • chrome • messenger • charsetTitles.properties utf-8.title |
cak
Unicode (UTF-8)
|
en-US
Unicode (UTF-8)
|
Displaying 14 results for the string Unicode in en-US:
| Entity | cak | en-US |
|---|---|---|
|
Entity
#
all locales
dom • chrome • layout • HtmlForm.properties CannotEncodeAllUnicode |
cak
Xtaq jun nojwuj rik'in ri rucholajil %S, ri man nitikïr ta nub'än kicholajil konojel ri Unicode taq tz'ib', ruma ri' toq rik'in jub'a' xtz'iläx ri rokem winäq. Richin man nuya' ta re k'ayewal re', k'o ta chi ri ruxaq k'amaya'l nijal richin tikirel nitaq pa ri rucholajil UTF-8 rik'in rujalik rucholajil ri ruxaq k'amaya'l pa UTF-8 o niya' retal accept-charset=utf-8 pa ri ch'akulal form.
|
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 EncMetaUserDefined |
cak
Xokisäx jun q'i'on yaketal richin nijikib'äx ri kicholajil taq tz'ib' achi'el x-user-defined. Xa xe chi xq'ijüx achi'el jun windows-1252 jikib'anïk ruma rujunamil kik'in ojer taq ruwäch tz'ib', ri kan echolajin pa man ütz ta rub'anikil. Re ruxaq k'amaya'l re' k'o ta chi nib'e pa Unicode.\u0020
|
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 errNcrOutOfRange |
cak
Retal jun tz'ib' elenäq pa ri okel Unicode rajilab'al.
|
en-US
Character reference outside the permissible Unicode range.
|
|
Entity
#
all locales
mail • chrome • messenger • charsetTitles.properties utf-16.title |
cak
Unicode (UTF-16)
|
en-US
Unicode (UTF-16)
|
|
Entity
#
all locales
mail • chrome • messenger • charsetTitles.properties utf-16be.title |
cak
Unicode (UTF-16BE)
|
en-US
Unicode (UTF-16BE)
|
|
Entity
#
all locales
mail • chrome • messenger • charsetTitles.properties utf-16le.title |
cak
Unicode (UTF-16LE)
|
en-US
Unicode (UTF-16LE)
|
|
Entity
#
all locales
mail • chrome • messenger • charsetTitles.properties utf-7.title |
cak
Unicode (UTF-7)
|
en-US
Unicode (UTF-7)
|
|
Entity
#
all locales
mail • chrome • messenger • charsetTitles.properties utf-8.title |
cak
Unicode (UTF-8)
|
en-US
Unicode (UTF-8)
|
|
Entity
#
all locales
suite • chrome • mailnews • charsetTitles.properties utf-16.title |
cak
Warning: Source string is missing
|
en-US
Unicode (UTF-16)
|
|
Entity
#
all locales
suite • chrome • mailnews • charsetTitles.properties utf-16be.title |
cak
Warning: Source string is missing
|
en-US
Unicode (UTF-16BE)
|
|
Entity
#
all locales
suite • chrome • mailnews • charsetTitles.properties utf-16le.title |
cak
Warning: Source string is missing
|
en-US
Unicode (UTF-16LE)
|
|
Entity
#
all locales
suite • chrome • mailnews • charsetTitles.properties utf-7.title |
cak
Warning: Source string is missing
|
en-US
Unicode (UTF-7)
|
|
Entity
#
all locales
suite • chrome • mailnews • charsetTitles.properties utf-8.title |
cak
Warning: Source string is missing
|
en-US
Unicode (UTF-8)
|
|
Entity
#
all locales
toolkit • chrome • global • charsetMenu.properties UTF-8 |
cak
UNIKOTE
|
en-US
Unicode
|
APIThese results are also available as an API request to search in
cak or
en-US.
Learn more about the Transvision API.
Please enable JavaScript. Some features won't be available without it.