Closed
Bug 266642
Opened 20 years ago
Closed 20 years ago
proposed checkins for CVS for ast-ES localization
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: xspuente, Assigned: bugzilla)
References
Details
Attachments
(1 file, 7 obsolete files)
|
25.32 KB,
application/octet-stream
|
benjamin
:
approval-aviary+
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ast-ES; rv:1.7) Gecko/20040616 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; ast-ES; rv:1.7) Gecko/20040616 After smoketesting the win32 installer for Firefox 1.0RC1, a few accesskeys were found to be not localized. Here I attached the following files to replace the older ones in the CVS in order to correct those problems: browser\locales\ast-ES\chrome\browser\bookmarks\bookmarks.properties browser\locales\ast-ES\chrome\browser\pageInfo.dtd browser\locales\ast-ES\chrome\browser\history\history.dtd browser\locales\ast-ES\chrome\profile\bookmarks.html toolkit\locales\ast-ES\chrome\global\customizeToolbar.dtd toolkit\locales\ast-ES\chrome\global\editMenuOverlay.dtd toolkit\locales\ast-ES\chrome\global\viewSource.dtd Reproducible: Always Steps to Reproduce: 1. Not localized accesskeys 2. Should be localized 3. English access key appears between brackets
Attachment #163791 -
Flags: approval-aviary?
Attachment #163792 -
Flags: approval-aviary?
Attachment #163793 -
Flags: approval-aviary?
Attachment #163794 -
Flags: approval-aviary?
Attachment #163795 -
Flags: approval-aviary?
Attachment #163796 -
Flags: approval-aviary?
Attachment #163797 -
Flags: approval-aviary?
Updated•20 years ago
|
Attachment #163791 -
Flags: approval-aviary? → approval-aviary+
Comment 8•20 years ago
|
||
Next time, this should be a patch or a zip with just the changed files ;)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•20 years ago
|
Attachment #163792 -
Flags: approval-aviary? → approval-aviary+
Updated•20 years ago
|
Attachment #163793 -
Flags: approval-aviary? → approval-aviary+
Updated•20 years ago
|
Attachment #163794 -
Flags: approval-aviary? → approval-aviary+
Updated•20 years ago
|
Attachment #163795 -
Flags: approval-aviary? → approval-aviary+
Updated•20 years ago
|
Attachment #163796 -
Flags: approval-aviary? → approval-aviary+
Updated•20 years ago
|
Attachment #163797 -
Flags: approval-aviary? → approval-aviary+
I didn't see the proposed patches/files (sorry for that) landing on the ast-ES cvs. I have attached two patches (correct format now), one for the browser component, and the other for the toolkit. I hope they can be commited to cvs. It solves bug 266043 (amazondotcom.src). However, I fixed one file (bug 267500) but I cannot get a patch for it: [xa@raguel]cvs diff chrome/mozapps/plugins/plugins.dtd >patch4 cvs diff: cannot open CVS/Entries for reading: No such file or directory cvs [diff aborted]: no repository I don't know how to commit the fixed file to cvs.
Attachment #163791 -
Attachment is obsolete: true
Attachment #163792 -
Attachment is obsolete: true
Attachment #163793 -
Attachment is obsolete: true
Attachment #163794 -
Attachment is obsolete: true
Attachment #163795 -
Attachment is obsolete: true
Attachment #163796 -
Attachment is obsolete: true
Attachment #163797 -
Attachment is obsolete: true
Attachment #164741 -
Flags: approval-aviary?
Updated•20 years ago
|
Attachment #164741 -
Attachment is patch: false
Attachment #164741 -
Attachment mime type: text/plain → application/octet-stream
Updated•20 years ago
|
Attachment #164741 -
Flags: approval-aviary? → approval-aviary+
| Reporter | ||
Comment 10•20 years ago
|
||
OK, I was told how to commit the files and I think they definitly are. They were the same they were approved, plus the chrome/mozapps/plugins/plugins.dtd that covered bug 267500. I still don't see the changes in the lxr.mozilla.org, when they appear I think the bug can be closed.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•