Closed Bug 388031 Opened 18 years ago Closed 18 years ago

Updates to the mk transaltion in Mozilla products for 2.0.0.6

Categories

(Mozilla Localizations :: mk / Macedonian, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gdamjan, Assigned: gdamjan)

References

Details

(Keywords: fixed1.8.1.8, verified1.8.1.8)

Attachments

(4 files)

We have organizied a massive bug hount in Mozilla products this several past weeks, and also consolidated some terms used in other projects. So this is the result ... attached are patches for Firefox (browser.diff), Thunderbird (mail-editor.diff), Toolkit (toolkit.diff) and security, dom and other-licenses (other.diff)
Attached patch browser.diffSplinter Review
Attachment #272167 - Flags: approval1.8.1.6?
Attached patch mail-editor.diffSplinter Review
Attachment #272169 - Flags: approval1.8.1.6?
Attached patch toolkit.diffSplinter Review
Attachment #272170 - Flags: approval1.8.1.6?
Attached patch other.diffSplinter Review
Attachment #272171 - Flags: approval1.8.1.6?
Comment on attachment 272167 [details] [diff] [review] browser.diff Did you check that the changes to the installer properties don't leave the range of chars of the CP1251 charset?
What file exactly?? As far as I know all the files are UTF-8, and there are no files in cp1251 in Firefox 2.
Comment on attachment 272167 [details] [diff] [review] browser.diff [mk] approval1.8.1.7 granted for patch flood. I applied the patches locally and ran them through compare-locales, and checked the list of modified files.
Attachment #272167 - Flags: approval1.8.1.7? → approval1.8.1.7+
Comment on attachment 272169 [details] [diff] [review] mail-editor.diff ... Please use the fixed1.8.1.7 and verified1.8.1.7 keywords to track landing and testing.
Attachment #272169 - Flags: approval1.8.1.7? → approval1.8.1.7+
Attachment #272170 - Flags: approval1.8.1.7? → approval1.8.1.7+
Attachment #272171 - Flags: approval1.8.1.7? → approval1.8.1.7+
Blocks: 377152
Keywords: fixed1.8.1.7
> (From update of attachment 272167 [details] [diff] [review]) > Did you check that the changes to the installer properties don't leave the > range of chars of the CP1251 charset? As I spoke to Axel, at build time, the installer files are converted to cp1251 since that's what NSIS works with. For the record, I checked the following files: mk/borwser/installer/*.properties mk/mail/installer/*.properties and all convert to windows-1251 (CP1251) without problems. (the command used is "iconv -f utf-8 -t windows-1251 file.properties")
Status: NEW → RESOLVED
Closed: 18 years ago
Keywords: verified1.8.1.8
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: