Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Late changes in SeaMonkey help files for b1

1 view
Skip to first unread message

Stefan

unread,
Jul 6, 2009, 2:20:41 PM7/6/09
to dev-...@lists.mozilla.org
Hi everyone,

Despite the "light" string freeze, I like to inform that I've just
landed a quite large change (done by Ricardo) to the SeaMonkey Help
files . The relevant bug is here:
https://bugzilla.mozilla.org/show_bug.cgi?id=286975. Sorry if this
causes any trouble, but I really wanted to get this in before b1.

Regards,

/Stefan

Ricardo Palomares Martí­nez

unread,
Jul 6, 2009, 6:04:27 PM7/6/09
to


I'm really sorry too for being so verbose. :-) To all SM localizers,
if you feel better, I also have to translate it to spanish. :-)

Best regards,
Ricardo

fredchat

unread,
Jul 7, 2009, 7:18:53 AM7/7/09
to
On 7 juil, 00:04, Ricardo Palomares Martí­nez <rpm.PU...@iespana.es>
wrote:

> I'm really sorry too for being so verbose. :-) To all SM localizers,
> if you feel better, I also have to translate it to spanish. :-)
>

You'll be damned for Eternity.

Adding a new section to mail_help is simply a very very very bad idea
(I've some bad words in mind, but I too polite and too respectful).

Frédéric

Ricardo Palomares Martí­nez

unread,
Jul 7, 2009, 1:26:41 PM7/7/09
to


Why? mail_help.xhtml is /only/ 240 KBytes long, and nowadays computers
have 2 GBytes or more RAM. :-P

Seriously, the problem is not adding a new section to mail_help, the
problem existed already and that's why this bug exists:

https://bugzilla.mozilla.org/show_bug.cgi?id=246405

You're welcome to help with it. :-) I'm in favour of splitting it (see
https://bugzilla.mozilla.org/show_bug.cgi?id=286975#c29), too, but I
think doing such involves many changes in associated RDFs and links in
other help content files, and thus I believe it is better to undertake
the task after SM2 is released.

I'm traslating the changes right now into es-ES, and I think you'll
find that the patch in the bug 286975 is a good guide to find what to
change.

Ricardo

0 new messages