Closed Bug 46449 Opened 24 years ago Closed 24 years ago

Legacy font name support in Java font.properties files for Japanese & other Asian languages

Categories

(Core Graveyard :: Java: OJI, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: momoi, Assigned: stanley.ho)

References

()

Details

(Whiteboard: [nsbeta2-] STANLEY_WORKAROUND)

** Observed with 7/25/2000 Win32 build **

We finally do the correct enocding conversion for Java plugins -- see Bug 17169.
So this means that all the backend work is done for internaitonal character
display for Java. But there is one big issue left and that is we cannot find the right
font for Japanese and other Asian characters unless the font.properties files are
updated. This is a simple matter of modifying 3 lines in the font.properties files
for non-English languages. This is already done for the main font.properties file.

So for Japanese, we need to modify font.properties.ja file, for Traditional Chinese,
we need to modify font.properties.zh.TW, etc. 

   # alias.timesroman=serif       
   # alias.helvetica=sansserif
   # alias.courier=monospaced

All we need to do is to uncomment the 3 lines above in each of the font.properties. file.
The reason is that there are many applets out there which use these older font names and
without this aliasing working, fonts for Japanese characters, for example, cannot be found
and instead Java displays blank squares.

I suggest a very low cost solution. That is to have Sun uncomment these 3 lines for the
appropriate font.properties files and give to the Netscape installer team. That will solve the
problem and since Java already does this for teh main font.properties file, this is not
anything with any risk attached to it.
I would like this JRE files to be in PR2.
Keywords: nsbeta2
In Netscape PR2, we will uncomment these three lines in the font.properties* 
files to get the applets working. We will continue our internal discussion and 
make a discussion in the final FCS release.
Status: NEW → ASSIGNED
per stanley's xomment, set the TM to M17.
Target Milestone: --- → M17
but must be fixed quickly and low risk manner. 
Whiteboard: [nsbeta2+]
Stanley, the time is very short.
Can you deliver the revised files to the
installer team ASAP?
Workaround being provided in the Win32 Java Plug-In by Stanley Ho today.
Whiteboard: [nsbeta2+] → [nsbeta2+] STANLEY_WORKAROUND
drapeau@eng.sun.com, what do you mean in your last comment?
QA Contact: shrir → teruko
Per drapeau, the workaround is in the branch.  But need to complete fix.  Thus 
putting on [nsbeta2-], and nominating for nsbeta3
Keywords: nsbeta3
Whiteboard: [nsbeta2+] STANLEY_WORKAROUND → [nsbeta2-] STANLEY_WORKAROUND
This fix has been provided in the latest JDK/JRE 1.3.0_01 beta on 
Win32/Linux/Solaris.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Verified as fixed in 2000-09-29 and 2000-09-30 Win32 branch build.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.