Karan,
WOFF is not any kind of font, legacy or otherwise.
A far as I can tell, it is simply a new(ish) data file compression format, specifically designed to compress web pages.
I quote from the official WOFF docs: (search for WOFF)
"This document specifies a simple compressed file format for fonts, designed primarily for use on the Web and known as WOFF (Web Open Font Format).
Despite this name, WOFF should be regarded as a container format or "wrapper" for font data in already-existing formats rather than an actual font format in its own right."
If the data so wrapped, is already Unicode savvy, I would assume its ready to go.
But material, in legacy fonts (XDVNG, Times_CSX + etc. etc.) requires the recipient to have the exact same font manually installed on his machine. It would still be ready to go, but with quite a high probability of on-page garbage characters!
Legacy font conversion utilities.
To this end, many free software packages are available to use, on and off line, to make the conversion from old to new.
However, each legacy font has to be individually remapped to the UTF standard (UCS Transformation Format)
where USC = Universal Character Set
It's the Universal Character Set, that makes all things garbage free, readable to all men, anywhere.
Now, another however: Legacy font conversion utilities are a mixed bag.
A while ago I wrote two-way conversions for my own use (using .NET C#), for the aforementioned, including one to automatically distinguish the one from the other and thus do such jobs in one go.
Now, these things are tricky, they can have their quirks (i.e. they can be buggy).
The so called professional packages, likewise, have their limitations, re. accents, ligatures, etc. (and bugs . . .).
I would therefore suggest that you gather a few recommendations from other publishers and evaluate them against your particular requirements
(the packages, not the publishers (:-)
As for how to WOOF the universalised product . . ..
Taff Rivers