Toggle Word Wrap 1.0 review

Toggle Word Wrap toggles word wraping in Firefox or Thunderbird (PRE elements). With Thunderbird, it comes in handy when inserti

License: MPL (Mozilla Public License) File size: 7K Developer: Kaspar Brand

0

Toggle Word Wrap toggles word wraping in Firefox or Thunderbird (PRE elements).

With Thunderbird, it comes in handy when inserting long text lines which should not get wrapped in the final message (such as log file entries). It only has an effect when using plain text mode for composition - this is a per-account setting which must be configured by disabling "Composition & Addressing" -> "Composition" -> "Compose messages in HTML format".

Unchecking "Enable Word Wrap" in the Options menu (or pressing the keyboard shortcut) will temporarily turn off word wrapping for the current message - lines will take up the whole width of the composer window, and no line breaks will get added to the outgoing message (with the exception of "hard" line breaks inserted manually). Checking "Enable Word Wrap" will enable word wrapping again and set it to the width specified in the standard settings ("Wrap plain text messages at", default is 72 characters).

For Firefox, checking "Enable Word Wrap for PRE Elements" in the View menu will temporarily enable word wrapping for PRE tags in the current document (by adding a CSS rule to the HEAD element). Unchecking the menu entry will revert the document to the previous state (no word wrapping). The following page can be used to see the effect, e.g.: http://myy.helia.fi/~karte/pre-static-no-css.html

As of release 1.0, the XPI file of this extension is signed. Its signature will successfully verify under Firefox or Thunderbird if the "Builtin Roots Module" is available in its standard configuration.

If you get an error like "could not install the file ... because: Signing could not be verified", it's either due to the fact that somebody tampered with the file (let me know where exactly you got it from, in this case) - or that you tweaked the trust settings of the built-in certification authorities. In the latter case, I assume that you're also savvy enough to figure out what trust anchor needs to be re-enabled in order to make the verification succeed again... (or how to rip the signature out of the file, otherwise) ;-)