Closed Bug 669082 Opened 9 years ago Closed 9 years ago

Create l10n.ini's for aurora and beta

Categories

(Calendar :: Build Config, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Pike, Assigned: Fallen)

References

Details

To set up the l10n dashboard on aurora and beta, we'll need l10n.ini's for aurora and beta, much like for tb in http://hg.mozilla.org/releases/comm-aurora/file/default/mail/locales.
Axel, do you specifically need them to be named "l10n-<branchname>.ini" ? I have updated the l10n.ini's on beta and aurora now:

http://hg.mozilla.org/releases/comm-beta/file/tip/calendar/locales/l10n.ini
http://hg.mozilla.org/releases/comm-aurora/file/tip/calendar/locales/l10n.ini

We should also consider the fact that now that we only care about lightning, we don't really need to include toolkit. Maybe we can copy the l10n.inis to calendar/lightning/locales?
If you want to stop including toolkit, you can totally do that.

If you continue to include toolkit, you'll probably want a different file per branch, as otherwise your per-branch version will get overwritten on each migration. Without toolkit, you don't need different content across branches, though.

I wouldn't want to support both sunbird and lightning independently, though. The l10n.ini should describe the project's scope, and I'd rather keep it where it is right now.
(In reply to Axel Hecht [:Pike] from comment #2)
> If you want to stop including toolkit, you can totally do that.

> I wouldn't want to support both sunbird and lightning independently, though.
> The l10n.ini should describe the project's scope, and I'd rather keep it
> where it is right now.

Yes, I totally understand this. The current scope is Lightning only, so I think its feasible to drop toolkit including. I'll put a comment in the file to make sure its clear why.
Assignee: nobody → philipp
Pushed to comm-central <http://hg.mozilla.org/comm-central/rev/8b34b659a284>
-> FIXED
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Trunk
Backported to comm-aurora <http://hg.mozilla.org/releases/comm-aurora/rev/253dc0829ebd>
Target Milestone: Trunk → 1.0b6
Pike, anything needed on the dashboard side here? We have a quite special situation that may require us to do string changes on beta and aurora until the next release. I'm trying to keep the amount low, so I'll handle these as late-l10n changes. Any thoughts or objections there?
You need to log in before you can comment on or make changes to this bug.