154746 - fonts displaying problem (russian ttf?)

Status: RESOLVED FIXED

(Core :: Internationalization, defect)

Description

[Artem S. Tashkinov]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1a+) Gecko/20020626
BuildID:    

I have TrueType fonts installed and when aa (antialiasing) is turned on many
russian KOI-8 pages are displayed abnormally: there're no spaces between words.

Reproducible: Always
Steps to Reproduce:
1. Have TTF fonts installed
2. Tell Mozilla documents can use their own fonts(i.e. turn on aa)
3. Go to http://securitylab.ru/ or http://www.rusc.ru


Actual Results:  There are no spaces between words! The text is very hard to read

Expected Results:  Words to have spaces

Comment 1

[Artem S. Tashkinov]

Attachment: image 1 for truetype fonts

that's how my Mozilla shows http://securitylab.ru/

Comment 2

[Artem S. Tashkinov]

Attachment: image 2

http://rusc.ru

Comment 3

[Artem S. Tashkinov]

When there's a mixture of English and Russian words spaces appear just OK

Comment 4

[Andrew Schultz]

==> Intl

Comment 5

[Roy Yokoyama]

->shanjian

Comment 6

[Yuying Long]

cc Brian.

So, this problem only happens when aa with ttf installed, right? cause I don't
see it on my linux RH7.2 machine ( I don't have russian ttf fonts).

Comment 7

[Artem S. Tashkinov]

Yuying Long wrote:
> So, this problem only happens when aa with ttf installed, right? cause I don't
> see it on my linux RH7.2 machine ( I don't have russian ttf fonts).

Right you are, yet russian web pages look ugly and unreadable

Comment 8

[Yuying Long]

I'm confirm this according to comment above.

Comment 9

[Jason Bassford]

What was this resolved as FIXED?  I don't see anything indicating either that
the problem's gone away or that, if it has, it was due to something in Mozilla
being broken and then fixed by a check of code.

Either it's not resolved, or it should be resolved as WORKSFORME.

Comment 10

[Artem S. Tashkinov]

This happened only in some Mozilla SeaMonkey nightlies (and then someone
accidently identified and solved this bug) and this problem went away a long
time ago. Generally it's better to have a gtk1 based binary with xft support on
the website 'cause in this case Mozilla gtk1 port out-of-the-box would support
antialiasing (without any extra tricks with its configuration).