the story so far…
bug 665142 seems quite unlikely as :bienvenu said it might not be a suitable bug for me to work on
as for bug 614407 :mconley gave me some clues on where to work on the bug. I shall paste the conversation here:
jyeo: hey – do you have a development build up?
jyeo: it’s awesome that you want to work on that bug, by the way.
TheOne left the room (quit: Ping timeout).
jyeo: cool – so I believe the XUL you’ll want to edit is in mailnews/base/prefs/content/am-identity-edit.xul
jyeo: it looks like this might impact Seamonkey too – so you might want to talk to someone on that team
jyeo: but anyhow, the translation strings for TB should go in mail/locales/en-US/chrome/messenger/am-identity-edit.dtd. For Seamonkey, it’s suite/locales/en-US/chrome/mailnews/pref/am-identity-edit.dtd
jyeo: you’ll want some UI review once you’re done – you can assign that to bwinton I suppose
jyeo: that should be enough to get you started. Good luck! Let us know if you need more help.
mconley: it seems simple but why is it that no one has taken it up yet?
jyeo: well, I suppose it was waiting for you to come along and snag it. Well, it’s a simple bug, but not a critical one. Often times, the TB team is working on more critical projects / problems.
jyeo: it’s an awesome starter bug though – maybe you can hunt down a few more like it after you’re done!
mconley: sure thing. i will definitely do that. bug squashing is fun.
jyeo: much appreciated! Thanks!
======================================end of conversation==================================
whee at least some progress is being made!