Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Əgər kömək lazımdırsa lütfən yeni sual verin.

firefox 3.6.8 does not correctly display inuktitut text in an input field. Any solution?

  • 1 cavab
  • 9 have this problem
  • 2 views
  • Last reply by rjo

rjo
rjo
more options

Firefox 3.6.8 seems to have an issue with Unicode in input fields, e.g. The following code <input type="text" value="ᕿᓂᕐᓂᖅ..." style="font-family:Pigiarniq"> should look more or less the same as <input type="text" value="ei3i6..." style="font-family:AiPaiNunavik">

The first one uses a Unicode font (available at http://www.gov.nu.ca/english/font/) the second one one of the traditional non-unicode fonts.

The two squares in the first string are not really squares. When you copy and paste the string onto a system with a unicode font containing canadian syllabic characters, then the squares are displayed correctly.

Additional information: I just found that this is not related to input fields, as I thought in the beginning, but also happens within normal Ps or DIVs. Strangely enough, the following complete HTML seems to work when saving as a local file: <meta http-equiv="content-type" content="text/html; charset=utf-8"> <style>body{font-family:Arial,Pigiarniq;}</style>

ᕿᓂᕐᓂᖅ

ᕿᓂᕐᓂᖅ

a real unicode font:

<input type="text" value="ᕿᓂᕐᓂᖅ..." style="font-family:Pigiarniq">

a non-unicode font:

<input type="text" value="ei3i6..." style="font-family:AiPaiNunavik">

and opend within this same browser session in another tab. In my current browser session, I see two different renditions of the string: - on this support form submission page, the string is incorrectly displayed (with two squares) as on the webpage which is currently under development - in another tab, the above mentioned HTML file displays all instances of the string correctly.

Firefox 3.6.8 seems to have an issue with Unicode in input fields, e.g. The following code <input type="text" value="ᕿᓂᕐᓂᖅ..." style="font-family:Pigiarniq"> should look more or less the same as <input type="text" value="ei3i6..." style="font-family:AiPaiNunavik"> The first one uses a Unicode font (available at http://www.gov.nu.ca/english/font/) the second one one of the traditional non-unicode fonts. The two squares in the first string are not really squares. When you copy and paste the string onto a system with a unicode font containing canadian syllabic characters, then the squares are displayed correctly. Additional information: I just found that this is not related to input fields, as I thought in the beginning, but also happens within normal Ps or DIVs. Strangely enough, the following complete HTML seems to work when saving as a local file: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="iu-ca" lang="iu-ca"> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> <style>body{font-family:Arial,Pigiarniq;}</style> </head> <body> <p>ᕿᓂᕐᓂᖅ</p> <div>ᕿᓂᕐᓂᖅ</div> <p>a real unicode font:</p> <input type="text" value="ᕿᓂᕐᓂᖅ..." style="font-family:Pigiarniq"> <p>a non-unicode font:</p> <input type="text" value="ei3i6..." style="font-family:AiPaiNunavik"> </body> </html> and opend within this same browser session in another tab. In my current browser session, I see two different renditions of the string: - on this support form submission page, the string is incorrectly displayed (with two squares) as on the webpage which is currently under development - in another tab, the above mentioned HTML file displays all instances of the string correctly.

Modified by rjo

All Replies (1)

rjo
rjo Question owner
more options

(A) is what I see on this webpage (Firefox support form submission page)

(B) is what I see within the same browser instance in another tab, viewing the above HMTL code

(C) is what happens on the webpage under development. A and C show the same strange behaviour.

Opera, Safari on Windows and IE display it correctly.

Thanks for any hints,

Modified by rjo