Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site. If this applications suite ever comes out in usable form, it is unlikely to have a look/feel as it does now, and the idea of using it to take advantage of interesting plug-ins is frustrated by the lack of interesting plug-ins. There is also no further reason to explore the program further. However, unless one is truly desperate about making a plug-in with a function you really need (unlikely given the limited set) and you really can't get it anywhere else, I see no reason to try. Application permissions have to be fixed so installation files can be written, though even opening Symphony as root didn't help from within Debian. My guess is that I saw files being installed in SLED10 that I didn't see getting installed in Debian. I'm sure that the problems of making plug-ins work properly in Debian/Ubuntu can be solved. Note that both the "Translate Buddy" and Google translators are server-powered i.e., Translate Buddy is a web client, suggesting that the problem is at the server/software translation end. In support of the Forum is a great place to share your experiences and help others like you.
#Lotus symphony forums install#
While it's probably possible to install this successfully in OpenSUSE11, to pursue this further is pointless because my purpose is to see whether the fonts are equally ugly in a "supported" Linux distro.
It failed with the same error (the chown and chmod had already been done). So I checked it in OpenSUSE, figuring it was close enough to make the claimed support for Symphony in RHEL work.įrom the Fedora Forum: # sed -i s/" \/tmp\/symphony.tmp\$RANDOM"/""/ IBM_Lotus_Symphony_linux.bin. When asked about this issue, tech support said that the problem was with an unsupported Linux distro (Fedora in the case of the person who asked). Figure 6 Symphony opening existing document