OS/2, eCS & ArcaOS - Technical > Applications

Whatever happened to...

<< < (3/3)

Ben:

--- Quote from: Pete on February 20, 2013, 08:25:10 pm ---Hi

--- End quote ---
Greetings, Pete.


--- Quote from: Pete on February 20, 2013, 08:25:10 pm ---I do agree that Wordpro was a good package and have no doubt that it can still work well - Ben seems to have the answer to making current format docs available for use in Wordpro. It would certainly be a lot more convenient if Wordpro had the necessary filters though.

--- End quote ---
Melf has a problem with the filters... though I found by trial and error, that I could eliminate those problems simply by trying different filters... of course, there is nothing to say that it will work for every format, but I have always found a solution... by using an intermediary filter, that, (in most cases), has nothing to do with the final format required... simply have OO do that when all else is done. Of course if the OO filters are lame in the final stage, then...  :(


--- Quote from: Pete on February 20, 2013, 08:25:10 pm ---As regards font antialias: I suspect the Innotek Font Engine may have a use there. You would need to add Wordpro to the applications supported by the Font Engine in the Registry - see the Font Engine readme file for details.

--- End quote ---
I did that a long time ago, Pete. It was interesting, but caused so many new problems that I had to abandon the whole thing. However, things have changed now with respect to OS/2 and fonts. Maybe it is time for me to give it another go...

Doug Bissett:

--- Quote from: Pete on February 20, 2013, 08:25:10 pm ---
As regards font antialias: I suspect the Innotek Font Engine may have a use there. You would need to add Wordpro to the applications supported by the Font Engine in the Registry - see the Font Engine readme file for details.

--- End quote ---

I don't know about antialias, but some time ago, I tried to remove the Innotek Font Engine completely. Almost everything worked okay, except OpenOffice 3.2. Apparently, OO uses the code, and the Font Engine should NOT be enabled for OO (same as for the newer Mozilla derivatives). I have every application turned off, and would never dream of using it for anything, since it is so flaky, but it seems that it is necessary for some things to run. In fact, that reminds me that I did a new eCS 2.1 install, and forgot that the old 2.4 version of the font engine is still what eCS 2.1 installs. The 2.6 version always worked better for me, but i find that it makes so little difference, that it is just not worth enabling it for other things,

Pete:
Hi Doug

OO3 does not work with IFE260 at all here - never gets onscreen. Checking the readme.1st file I found this:-

- Innotek Font Engine is required to run OpenOffice.org 3.2 for
  eComStation and OS/2. (Available by default in eComStation)
  You can download it from the following location:
  http://download.innotek.de/ft2lib/InnoTek_FT2LIB_240_Release1.exe


That seems to indicate OO3 is built to use IFE 2.40

As you say IFE2.60 is better but can cause more hangs/crashes in my experience - which may be different to yours.

I use iFE 2.40 and have added pmshell.exe to the Applications - as well as deleting all mention of Mozilla apps - and find that the Desktops on 3 systems here all look much better with regard to font display. The only real moan I have is that long folder/application names do not fit on the dropdown menus eg click eCS button (on eComCentre) and here "File and Print Client Resource Browser" has the 's' overwritten by the right arrow head and half the 'e' is missing - as is the final 'r'.

I have also added ar5os2.exe to the IFE 2.40 applications and use ar5os2.exe as the "windows runtime" for OO1.1.5 for Windows. Font display in both OO1.1.5 applications and Acrobat Reader V5.1 is much improved and so far - touch wood (touches head ;-)  - no hangs/crashes.

Using IFE 2.60 with the above applications my system did suffer the odd hang/crash from time to time. I guess that is because 2.60 is a beta version... Would have been nice if it had got past beta before development stopped  :-(


Regards

Pete






Doug Bissett:

--- Quote from: Pete on February 21, 2013, 11:03:47 pm ---Hi Doug

OO3 does not work with IFE260 at all here - never gets onscreen. Checking the readme.1st file I found this:-

- Innotek Font Engine is required to run OpenOffice.org 3.2 for
  eComStation and OS/2. (Available by default in eComStation)
  You can download it from the following location:
  http://download.innotek.de/ft2lib/InnoTek_FT2LIB_240_Release1.exe


That seems to indicate OO3 is built to use IFE 2.40

As you say IFE2.60 is better but can cause more hangs/crashes in my experience - which may be different to yours.

I use iFE 2.40 and have added pmshell.exe to the Applications - as well as deleting all mention of Mozilla apps - and find that the Desktops on 3 systems here all look much better with regard to font display. The only real moan I have is that long folder/application names do not fit on the dropdown menus eg click eCS button (on eComCentre) and here "File and Print Client Resource Browser" has the 's' overwritten by the right arrow head and half the 'e' is missing - as is the final 'r'.

I have also added ar5os2.exe to the IFE 2.40 applications and use ar5os2.exe as the "windows runtime" for OO1.1.5 for Windows. Font display in both OO1.1.5 applications and Acrobat Reader V5.1 is much improved and so far - touch wood (touches head ;-)  - no hangs/crashes.

Using IFE 2.60 with the above applications my system did suffer the odd hang/crash from time to time. I guess that is because 2.60 is a beta version... Would have been nice if it had got past beta before development stopped  :-(

Regards

Pete

--- End quote ---

IFE 2.60beta seems to work fine with OO 3.2, but all I have done, so far, is open a file to see if it rendered properly. It did. I don't use it with anything else, and would actually like to remove it completely, but I do use OO 3.2, and it seems to need it. I would like to see OO abandon IFE (any version), and start to use the same font support that the Mozilla derivatives are using. At least the source is available, so problems should be fixable (I don't know if that would actually work either).

Anyway, I will see what happens with OO 3.2, for a while. I don't plan on using it with anything else, since it seems to be unnecessary (at least on my system).

Dave Yeo:

--- Quote ---and start to use the same font support that the Mozilla derivatives are using. At least the source is available, so problems should be fixable (I don't know if that would actually work either).

--- End quote ---

Easier said then done as it would probably take a lot of rewriting. Mozilla uses Cairo http://cairographics.org. Actually following the examples link does show that work has been done on adding Cairo to OO. Nothing recent though, see https://www.google.com/search?domains=www.openoffice.org&sitesearch=www.openoffice.org&resultsPerPage=40&q=cairo&Button=search.

Doodles Screen Saver has some Cairo based modules and WPS-Wizard ftp://ftp.netlabs.org/pub/wps-wizard/ adds some classes to the WPS that adds Cairo support. Unluckily it is not the most stable and source is unavailable. Screen shots at http://svn.netlabs.org/wps-wizard

Navigation

[0] Message Index

[*] Previous page

Go to full version