These day's more and more component venders are moving into multiplatform and are adopting fpc/laz (or even IMHO buggy and less capable Firemonkey). We are getting more and more interest in moving completely to FPC since Firemonkey would be a complete rewrite. In our case imageen is just one of the few components holding us back. So i want to try and convince you to rethink (if possible)..
We would fully understand parts of imageen unavailable for fpc (because of assembler and/or other OS dependent stuff) and we would accept a less capable package if there is a valid reason (for example a missing Twain/WIA interface etc.). Much of our needs would already be covered if we can use the TImageEnView, TImageEnMView and TImageEnVect (and much of the internal TImageEnIO methods).
Unfortunately, because of the huge effort it would be to write even a minor implementation of ImageEn for FPC/Lazarus it is highly unlikely it is something we can do in the foreseeable future.
When we do make the move to cross-platform support it would most likely be via Firemonkey, but we are not ready to make that jump yet either.