Drobe staffer PeterNaulls has been interviewed by OpenOffice.org - the online front for the popular open source office suite. Peter has recently ported OpenOffice to the ARM platform, specifically Debian ARM Linux.
As Slashdot noted, ARM processors are typically everywhere, so the addition of a recognised productivity package is a welcomed boost.
The ARM port of Openoffice is currently available from the experimental stream of Debian.
Forgive my ignorance, I've never ported anything. But I've always thought that porting one linux application to another just involved a recompile (assuming there is a compiler able to produce code for the processor of that linux variant available). Obviously that is not the case. So what is involved in porting such applications? Things like the size of an int on the destination system? little/big endian (particulary within fileformats)? Such things?
If you read the interview, it explains why porting OpenOffice is such a headache. There's a lot of assembler nastiness that needs porting/re-writing from x86 to ARM. It's not a trivial recompile.