Closed Bug 316324 Opened 18 years ago Closed 6 years ago

Japanese Locale Files for DOM Inspector

Categories

(Mozilla Localizations :: ja / Japanese, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: bugzilla, Assigned: mozilla758+bmo)

Details

Attachments

(4 files, 2 obsolete files)

Sorry, this is quite late.
Here are our japanese locale files for DOM Inspector.

These files are included within langpack I made to QA and already well tested by
japanese testers. So if this is still in time, please include in 1.5 release.
Attachment #202937 - Flags: approval-l10n?
Attachment #202938 - Flags: approval-l10n?
Comment on attachment 202937 [details]
ja locale files for DOMI

too late for this, we may re-evaluate for 1.5.1
Attachment #202937 - Flags: approval-l10n? → approval-l10n-
Attachment #202938 - Flags: approval-l10n? → approval-l10n-
dynamis or Kozawa-san:

Why is this bug still opened? Shouldn't be already obsoleted?
(In reply to comment #4)
> Why is this bug still opened? Shouldn't be already obsoleted?

DOMi is still shipped with SeaMonkey and should be localized.
And also it could be better if DOMi at AMO contains Japanese strings.

So, the attached file is obsoleted but the bug is not obsoleted.
Oh, couldn't Seamonkey be fixed this bug, either?
(In reply to comment #6)
> Oh, couldn't Seamonkey be fixed this bug, either?

As for SeaMonkey 1.1.x and before, Japanese version is packaged by Tooyama-san manually, so this bug is not related.
But as for SeaMonkey 2, not only en-US but l10n-builds will be automatically packaged from sources, so Japanese locale files must be committed to mozilla.org repository, and this bug is needed.
Attached file ja locale files for DOMi 0.2.4 (obsolete) —
Oops, current version number is not "0.2.4".
I've just named wrong version number. (ja resources are for latest 2.0.4.)
Attachment #413588 - Attachment is obsolete: true
Attachment #413589 - Attachment is obsolete: true
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.