Best practice of migration strings for Firefox 3?
Channy Yun
> I created a bug to attach milestone patches again, that's
> https://bugzilla.mozilla.org/show_bug.cgi?id=397506.
>
> I expect some changes to go in after B1, yes.
Hi all,
It seems that every localization teams started the migration work from
1.8branch to trunk to complete translation for Firefox 3 Beta 1. In
case of ko
team, we didn't sync both trunk and 1.8 branch yet. In this week, our team
make a process by reviewing Firefox 2 works in the past.
There is our migration step.
[1] Find changes between en-US 2.0 and en-US 3.0 and make patch from them.
[2] Translate and review patch in case of only + strings.
[3] Patch existing ab-CD of 1.8 branch with translated diff using own
scripts.
[4] Compare patched ab-CD with en-US 3.0 with compare-locale.pl
[5] Commit patched ab-CD to trunk repository.
In detail, [1] There are some string changes such as adding space changes,
errata and smooth translations of existing translations as well new
strings. You've better review all changes. [2] You can translate + strings.
If a change don't effect your existing translation, you remove its lines in
patch. [3] We made this script to patch only changes to existing
translation.
If you have another best practice, let me know.
Channy