Closed Bug 326003 Opened 19 years ago Closed 18 years ago

Move brand.dtd and brand.properties to locales

Categories

(Calendar :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mostafah, Assigned: mostafah)

References

Details

Attachments

(3 files)

We originally added brand.dtd.in and brand.properties in sunbird/app since Firefox did the same. Firefox has long moved their branding files to the locales directory. We should be following the same path.
complete path will be calendar/locales/en-US/chrome/branding

brand.dtd should use new version as in bug #325985 but without lang.version entity.
one more thing. The old stuff should be removed with checkin for bug 325985.
This is the patch to create those files in the right place to begin with. Changes to Makefiles will follow in separate patches.
Attachment #210788 - Flags: first-review?(mvl)
Comment on attachment 210788 [details] [diff] [review]
Creation of brand.dtd and brand.properties in locales

r=mvl
Attachment #210788 - Flags: first-review?(mvl) → first-review+
Comment on attachment 210788 [details] [diff] [review]
Creation of brand.dtd and brand.properties in locales

Patch checked in. (Files added).
Wolfgang, can you please prepare a new patch that will only take care of adding a simple Makefile.in and a jar.mn (in locales) for the new files? They don't need to be part of the build yet (but should work if they were). I can review it once you do.
AFAIK the branding stuff don't need a jar.mn and/or Makefile in this place.
Both are referenced only from sunbird/apps and the patch to activate them is already in bug 325985. So if this gets reviewed and checked in, the new files will be used. At least this is what happens for en-US builds. What's missing is a direct build of "language-packs".
You're right, the patch for bug 325985 does add the branding files to the chrome but:
1) The main intention is to start populating the 'locales' directory so we can switch over to it easily, hence I suggested to have a Makefile.in and a jar.mn first.
2) To mimic what Firefox does, we should move that to the make procedure inside 'locales' itself which makes more sense too.

But as you have mentioned branding files are Sunbird specific and shouldn't be in the chrome when the 'locales' directory is being built for an extension. One way to avoid that is to keep the addition of the branding files inside the app directory. That's true, but when we get to the part where we should deal with langpacks, the ideal solution is to just copy the related parts from browser/locales/Makefile.in without worrying about the fact that the branding stuff is packed elsewhere.
So my suggestion is to proceed with the move but use an ifdef MOZ_SUNBIRD in the jar.mn instead.
What do you think?
Attached patch build infrastructure — — Splinter Review
(Is this patch-format OK?)

This adds some needed files to populate calendar-AB_CD.jar with branding files.
The patch to actually activate it is not included. So nothing should change in the current calendar build.
Comment on attachment 210907 [details] [diff] [review]
build infrastructure


>diff -uprN mozilla/calendar/locales/jar.mn mozilla-l10n/calendar/locales/jar.mn
>--- mozilla/calendar/locales/jar.mn	1970-01-01 01:00:00.000000000 +0100
>+++ mozilla-l10n/calendar/locales/jar.mn	2006-02-06 20:55:15.000000000 +0100
>@@ -0,0 +1,9 @@
>+#filter substitution
>+
>+calendar-@AB_CD@.jar:

that's wrong. The branding stuff should go to @AB_CD@.jar IIRC.
Attachment #210907 - Flags: first-review?(mostafah)
review-request given the above mentioned change for sure
Comment on attachment 210907 [details] [diff] [review]
build infrastructure

r=mostafah.

Patch checked in with following change:
(Note that the ifdef is moved to top of @AB_CD@.jar)

diff -uprN mozilla/calendar/locales/jar.mn mozilla-l10n/calendar/locales/jar.mn
-- mozilla/calendar/locales/jar.mn	1970-01-01 01:00:00.000000000 +0100
+++ mozilla-l10n/calendar/locales/jar.mn	2006-02-06 20:55:15.000000000 +0100
@@ -0,0 +1,9 @@
+#filter substitution
+
+#ifdef MOZ_SUNBIRD
+@AB_CD@.jar:

Next proposed step: Minimal and unified patch to disable using brand.dtd from sunbird/app and enabling build process in the 'locales' directory.
Attachment #210907 - Flags: first-review?(mostafah) → first-review+
Depends on: 326794
Attached patch build modification — — Splinter Review
contents.rdf is obsolete for sunbird AFAIK.

After this gets applied localized builds don't work anymore without having
branding stuff in l10n cvs.

And we need the patch for bug 326794 prior to this one.
Attachment #211486 - Flags: first-review?(mostafah)
Comment on attachment 211486 [details] [diff] [review]
build modification

Patch checked in and obsolete files removed. Is this bug fixed?
Attachment #211486 - Flags: first-review?(mostafah) → first-review+
The bug itself is almost fixed.
What we need now are localizations in the l10n CVS for branding as for example
http://lxr.mozilla.org/l10n/source/de/calendar/chrome/branding/
The locales which are added there should be added to a new file
calendar/locales/all-locales

Notifying Pike in CC
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: