Bug 81338 - Mozilla must have translated lang packs.
Summary: Mozilla must have translated lang packs.
Alias: None
Product: Red Hat Linux Beta
Classification: Retired
Component: mozilla
Version: beta2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Christopher Blizzard
QA Contact: Ben Levenson
Whiteboard: qa-i18n
Depends On:
Blocks: 79578
TreeView+ depends on / blocked
Reported: 2003-01-08 07:25 UTC by Nakai
Modified: 2007-04-18 16:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-01-30 06:18:17 UTC

Attachments (Terms of Use)

Description Nakai 2003-01-08 07:25:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.0.1) Gecko/20020830

Description of problem:
Mozilla must have translated lang packs
for all Red Hat Linux supporting languages.



Without them, other localized distros provide better
web environment, which is one of most important features
in nowdays OS/Desktop.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Using Mozilla on Red Hat Linux
2. Why they don't prepare language packs in the CDs?

Additional info:

Comment 1 Leon Ho 2003-01-23 05:04:40 UTC
Users are having problem of sending mail with selecting correct charset. Is lang 
pack localizate the default charset as well? 

Comment 2 Christopher Blizzard 2003-01-23 18:20:30 UTC
I'm not sure where it gets the default charset for sending mail, but I'm pretty
sure it doesn't have anything to do with the lang packs.  I would have to poke
around at the source to figure it out.

There is, however, a preference for the character coding for composing messages.

Preferences -> Mail & Newsgroups -> Composition -> Character Coding

Comment 3 Leon Ho 2003-01-30 06:18:17 UTC
I noticed language packs have included into the main package.  
And I have also tested the default charset by selecting the specific lang pack (ie. 
zh_CN), and it has default charset after a restart. 
I am closing this bug. Thank you. 

Note You need to log in before you can comment on or make changes to this bug.