• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - davidfor

#1
Quote from: Saijin_Naib on 2007.10.30, 05:11:24
Doesnt australia observe the same changes as the US/Canada?

The parts of Australia that observe daylight saving start the last Sunday of October and end the last Sunday of March.  But, it looks like from next year we are changing to start from the first Sunday of October and end the first Sunday of April. 
#2
Quote from: lpino on 2007.10.25, 17:30:31
There are some icon convertion programs available at hobbes. I developed one of them and you could convert the icons from the Win format into the OS/2 format. The advantage of the one I did was that you convert all the icons placed in a folder and the 32x32 was converted into 40x40 without scaling just filling the border with background, that way you got an icon with 16x16, 20x20, 32x32 and 40x40. It supported 24 bits format and it didn't have the problem of PMView of painting the background black. It doesn't support PNG or any new windows format though.

The other program was very good one, and you could convert windows icon libraries into the os/2 format. The sources are also available so a programmer could include support for the new windows formats.

I have a Rexx program that converts Windows themes to OS/2.  One of the steps was to convert the icons to OS/2 format and I used one of these two programs.   From memory, I was handling icon libraries, so it must have been the second one.

And I have to agree with David Graser, its a pain doing this.  There are so many icons and other settings to setup and get right.  I have seen some very nice icon sets for Linux and considered converting those, but the amount of work involved was just to much at the time.
#3
Quote from: S.SubZero on 2007.10.16, 07:47:44

Quote from: davidfor on 2007.10.16, 03:50:19Also, it helps when asking a question like this to include the URL for the site in question.  That way we can have a look and see if we have the same problem or to examine the sites source to see if we can work out what is going on.

QuoteMany websites, especially vBulletin forum sites, display the default font too large.

If you really need a very specific example.. http://www.vbulletin.com/forum/ . That site looks wrong too.  Practically every site I visit that runs vBulletin exhibits the exact same font problem.  The image in my example is from www.abxzone.com.

A specific example is always useful.  I have never knowingly looked at a vBulletin forum site.  I have probably used them, but not paid attention to what software was being run.  So, giving a URL lets me see the site, examine the source and see if I can come up with what is happening.

Looking at http://www.abxzone.com/forums/, I see it uses a CSS file.  That appears to specify the fonts as
"10pt verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif;".  So, if "verdana" is installed, it should be used.  As verdana is part of the MS Core fonts, it should be OK.  There are a couple of spots where "tahoma" is added in front of this list, so if that is not installed, there would be a difference to the Windows machine.  But, this shouldn't be the problem as the parts that are displayed wrong do not use this.

The parts that are wrong are look like "<strong>Open Chat</strong>" and seem to be using the default page font (i.e. verdana).  That suggests that Thomas' statement that there are problems with the antialiasing is probably the answer.  If so, there is probably nothing you can do.

The last thing I can think of is if you have a vBulletin site that is OK, you could compare its CSS file with a non-working site for the differences.  This might lead to an answer as to what is wrong.  But, I suspect there won't be a fix.
#4
Quote from: warpcafe on 2007.10.16, 09:58:36
-not sure if you knew already-
some time ago I was working on a program ("feffer") that is used to easily access the Innotek fontlib settings (instead of having to use regedit2...). During that work I found that the antialiasing of Innoteks ft2lib seems to have an impact on the font sizes - meaning: They are not accurate. I'm using SeaMonkey most of the time and I can assure you that there's a difference in fontsizes between when enabling ft2lib support or not.

Not sure of this helps... to my knowledge, there is no solution so far to work around this.
You might give it a try with disabled ft2lib support (looks "ugly" of course, but check if the SIZES are OK then)

I remember playing with it sometime and seeing these sort of problems.  But, the "on" setting is so much better overall that I left it on.  Fiddling with the hinting option did help as well, but I think mainly in clarity of text and not in the size.  It's been to long since I did this to remember.
#5
The two things that occur to me are:

- Missing font.  The pages that are wrong might be specifying a font you don't have installed.  Looking at the page source should be able to Installing the "MS Core Fonts" might be the solution.

- Innotek Font Engine not setup correctly.  Firstly, are you sure it is setup to for Firefox?  This needs an entry in the registry for the Firefox executable (probably "firefox.exe").  The setting of the "Hinting" and "AntiAliasing" options change how the actual font is displayed.  Details of how to make these changes are in the readme for the font engine.  I don't have an OS/2 machine with me to check what my settings are.

Also, it helps when asking a question like this to include the URL for the site in question.  That way we can have a look and see if we have the same problem or to examine the sites source to see if we can work out what is going on.

David
#6
Utilities / Re: Master Volume widget
2007.09.10, 03:35:29
CPPOM30.DLL is a VisualAge C++ runtime DLL.  This should not be on anyone's machine unless they have a copy of VisualAge C++.  But, copies of it with different names might be on the machine.

What is happening is that when someone develops code with VisualAge, they will probably need to link to some runtime libraries for the code to run.  This can be done either at statically at build time, or dynamically runtime.  If it is linked statically, it makes the executable bigger but easier to install (in this case, only one file).  If it is dynamically linked, the executable will be a lot smaller, but will need to use a DLL with the runtime code in it.  In this case, it is dynamically linked and the runtime DLL is not included with the executable.  I fell over this problem years ago when I released my SetiView/2 program.

But, there is a problem.  The VA C++ license says you can redistribute the runtime DLLs but they must be renamed.  This is done with a program called DLLRNAME.  This renames the DLL and the references in the executable to point the the new name.  As there is probably a few versions of this DLL on most machines with different names, it is possible to bind to one that is there.  My suggestion for the developer would be to see if there is one in the XWorkplace directory and use that.  I don't have access to an OS/2 machine at the moment (I'm at work) so I can't look.  If there isn't one there, the need to decide how to link the library in and recreate the package.