Closed
Bug 260806
Opened 22 years ago
Closed 22 years ago
Allow localization of README.txt
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
FIXED
Firefox1.0
People
(Reporter: p.franc, Assigned: chase)
References
Details
(Keywords: fixed-aviary1.0, l12y, late-l10n)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10
To allow localization of README.txt move it into l10n tree
http://lxr.mozilla.org/aviarybranch/source/browser/app/README.txt
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Updated•22 years ago
|
Assignee: firefox → bsmedberg
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-aviary1.0?
Keywords: l12y
Target Milestone: --- → Firefox1.0
Updated•22 years ago
|
Flags: blocking-aviary1.0? → blocking-aviary1.0+
Comment 1•22 years ago
|
||
chase/granrose can you help on this one?
| Assignee | ||
Comment 2•22 years ago
|
||
choffman: Sure thing.
Pawell: Where do you recommend this file go in the mozilla source tree? Also,
what builds is this file a part of? We're not certain how/where it's being
packaged right now.
| Reporter | ||
Comment 3•22 years ago
|
||
This file is part of firefox browser.xpi (bin/README.txt) package which should
be locale independent. The idea is to move the file from
/mozilla/browser/app/ into
/mozilla/browser/locales/en-US/ and every /l10n/browser/locales/@AB-CD@/
and then packed it into @AB-CD@.jar (bin\README.txt)
Thus you have to remove corresponding lines form
/mozilla/browser/app/Makefile.in and add them into
/mozilla/browser/locales/Makefile.in
This is just my idea as a l10n guy, it must be approved/corrected/dumped by
Benjamin.
| Reporter | ||
Comment 4•22 years ago
|
||
Related bug 263446
Updated•22 years ago
|
Assignee: bsmedberg → cmp
Comment 5•22 years ago
|
||
wonder if we could put a copy of the file in mozilla/browser/locales/en-US/ as
step one to allow translation work to get going, and then follow up with mods to
the build and installer packaging systems to start to pick up the file from the
new location...
Comment 7•22 years ago
|
||
Which character encoding to use for README.txt?
| Assignee | ||
Comment 8•22 years ago
|
||
Dean: The fix was discussed and reviewed by bsmedberg last week. I just got
around to implementing it today.
I meant to post my write-up of the fix sooner. Here it is:
Moved README.txt from browser/app/ to browser/locales/en-US/. Updated
browser/app/Makefile.in to remove install of README.txt during libs target.
Updated browser/locales/Makefile.in to handle installing README.txt for every
locale instance.
Updated•22 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•