Closed Bug 57061 Opened 25 years ago Closed 25 years ago

Need installer to patch Java font.properties.* files

Categories

(SeaMonkey :: Installer, defect, P3)

x86
Windows 95
defect

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: bobj, Assigned: ssu0262)

Details

(Whiteboard: [rtm-])

Need to restore Windows JRE patching mechanism in installer to workaround JRE bug, bug 54578 "JRE 1.3.0_01 does not display Japanese characters in applet". Patcher needs to replace 9 font.properties.* files as described in bug 54578. These files should be the same versions installed by the PR3 JRE self-extracting archive. We're still working with Sun to restore the bug fix that was backed out. But if Sun does not do this in time for RTM, we need to fix by patching via the installer.
Adding RTM keyword. Nominating for [RTM need info]. Adding Dan and Todd to cc: list.
Keywords: rtm
This bug needs to be set to [rtm+] by a manager level person to get into PDT's radar.
Status: NEW → ASSIGNED
Is this for Netscape or Mozilla?
Sean: what's the fix for this? I'm confused by this bug -- it's not clear this is "pull it off the wire", sounds like possibly Sun is going to fix it, and other uncertainties. Henrik: this is Netscape-only, should have been filed in Bugscape.
QA Contact: gemal → gbush
Do we have a patch and the appropriate reviews? We can't get a rtm+ without those steps.
Dan - Sun might fix it, but given their past performance we can't count on them with 100% certainty. Hence, we need this patch to ensure we have a way to address this issue from our end.
I have the a set of .properties files that were used to test PR3 (but not shipped with PR3). If that's not good enough, we need another set.
Ftang - Can you work with ssu and Dan on this one? I think we are kewl with the font.propoerties file he currently has for PR3, but you and Bob are the best authority on this one.
I would also like some kind of hint from PDT that they will take this fix if Sun does not come through. I rather not waste time if PDT won't even take this, so I'm not going to start working until I hear from PDT.
ssu - I plan on updating the PDT this afternoon on this issue. On Mondya, they asked me to look into this option, and return to them with an update by this afternoon. Can you give me your opinion on the level of effort needed to implement this patch and the amount of code it would take (i.e. 5 lines or greater than 20)?
It would take me about 1 day to get the code merged from a private branch into the RTM branch and tested. I'd guess it's about between 20-30 lines of code change. (Adding Tao to the Cc: list because this fix will affect his change to config.it)
This is extremely late. Any reason it should not be rtm- ? Any hope that the PDT would approve a 20-30 line non-crash-fix change?
Whiteboard: [rtm need info]
I had checked in my patch for config.it. Please go ahead to apply your patch.
Comments in i18n status said they got a fix from Sun. RTM-
Whiteboard: [rtm need info] → [rtm-]
Actually I guess this is WONTFIX.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
vfy
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.