As a compositor/developer, I run paratext on a Windows machine, in a windows->parallels session on Mac, and in a Linux->Virtualbox session on Mac. When it’s virtualized, Paratext linux and windows run at a similar speed that is noticeably slower than in a windows 7 box directly. I have installed Paratext into a true linux machine, but never one that was comparable to a windows machine for speed.
If you are going to try a linux install, I recommend Wasta Linux, because it is recommended by a related SIL site (Bloom Library.) Keeping the community as closely configured as possible minimizes the number of times an issue has to be solved.
Following these instructions will provide you with a working Wasta Linux in Virtualbox:
https://sites.google.com/site/wastalinux/home/virtualbox-installation
Following these instructions once you have Wasta on Virtualbox will get you into the supported update path for paratext.
The core features run the same regardless of platform. However, there are windows only features that aren’t available from within Linux. Among these, that are important for me are the advanced checks, and the pathway plugin. For Translators and consultants, the the Transcelerator plugin and the concordance builder are also not supported.
The advanced checks have been rumored to be supported in linux version of the upcoming Paratext 8. However, it’s now October, and there’s still no Paratext 8, with classes for it scheduled in days. If they have to release early, this support is likely to slip to the next version.
I have performed send/receive from both windows and linux without flaws, but I don’t actually contribute output into the S/R system. I only receive changes others have made.
