489788 - I get "????" instead of Russian signs when typing smth in any field

Status: RESOLVED DUPLICATE of bug 401803

(Calendar :: Sunbird Only, defect)

Description

[Dmitry Romanov]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.9) Gecko/2009040820 Firefox/3.0.9
Build Identifier: Sunbird 0.9

Mac OS X leopard 10.5.6
Sunbird 0.9
All encoding works fine. Firefox works excellent 
 
P.S. have the same issue with subjects and attached files names in Thunderbird

Reproducible: Always

Steps to Reproduce:
1. start Sunbird
2. open new task/event
3. type smth in any field
Actual Results:  
see ???? instead of Russian signs 

Expected Results:  
types Russian symbols

Comment 1

[Dmitry Romanov]

Attachment: Sunbird window

that is what I see

Comment 2

[Dmitry Romanov]

my neighbor successfully uses the same (UTF-8) remote calendar on the Linux- evolution mail client, so the issue depends on Mac OS platform

Comment 3

[Stefan Sitter [:ssitter]]

Doesn't sound like a Sunbird issue at all. Could it be possible that you don't have installed or that you don't use a font that contains Cyrillic characters? Do you get correct display if you browse to a webpage that uses Cyrillic characters, e.g. <http://en.wikipedia.org/wiki/Cyrillic>?

Comment 4

[Dmitry Romanov]

Thank you Stefan for your reply, but my mac system is OK, all characters were installed and all application work fine except Thunderbird 2.0.0.21 and Sunbird 0.9.
Thunderbird 3.0b2 fixed this issue, so it seems the reason was in Gecko from Thunderbird 2.0.

Still have issue with Russian characters in Sunbird 0.9

Comment 5

[Stefan Sitter [:ssitter]]

OK, according to your last comment it is not a Sunbird issue but a Mozilla Core/Toolkit issue. I suggest that you retest with a Sunbird 1.0pre nightly test build that is based on the same Mozilla Core/Toolkit as Thunderbird 3.0. Otherwise please resolve it as a duplicate of the bug that was used to fix it in the Mozilla Core/Toolkit.

Comment 6

[Alexander L. Slovesnik]

This bug looks like duplicate of Bug 401803.