Closed Bug 45348 Opened 26 years ago Closed 26 years ago

Default charset setting does not effect in Composer

Categories

(Core :: Internationalization, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: teruko, Assigned: ftang)

References

Details

Default charset setting does not effect in Composer. Steps of reproduce Since the dynamic Charset menu does not work, bug 39780, you need to add the Charset menu by hand. 1. Open Composer 2. Select menu View|Charset Coding->Customized... 3. Select Japanese (ISO-2022-JP), Japanese(Shift-JIS), and Japanese (EUC-JP) and add the charset coding menu 4. Open Preferences dialog 5. Select Navigator-Languages 6. Select Japanese (EUC-JP) in Default Character Coding list 7. Quit Netscape6 and restart 8. Open Composer 9. Look at menu View|Character coding Actual result Western (ISO-8859-1) menu has mark. Expected result Japanese (EUC-JP) menu should has mark. Tested 2000-07-12-09 Win32 and Mac, and 2000-07-12-11 Linux build.
This will impact the localized Japanese version for which the initial default charset will be set to a Japanese encoding, but Composer will ignore it. So when a Japanese user creates a Japanese document it will be created as an iso-8859-1 with NCRs for all of the Japanese characters!
Status: NEW → ASSIGNED
Depends on: 45360
Keywords: nsbeta3
I think this bug is already fixed by nsbeta2 while we fix other bug. mark it fixed
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Since the Default charset listing in preferences are not correct (44062), I will test this after 44062 is fixed.
After I quit Netscape and lanch again, the default character setting takes place. Verified as fixed in 2000-09-13-08 Win32, 9-13-04 Mac and 9-13-12 Linux build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.