I have done some work to convert table information from the taw converter format into the pfm format. As a result, I have made new DBFileTypes files for pfm which (a) fix 9 tables for which pfm had wrong data, (b) improve 15 tables where pfm field types were unknown, and (c) add support for 128 tables which were missing from pfm.
To use these new files, please follow these steps.
1. In your PFM installation directory, rename the directory DBFileTypes to orig-db-files or similar, to make a backup of the original files.
2. Unzip the attached zipfile into your PFM installation directory. Check to make sure that you have a new DBFileTypes directory containing files like DBFileTypes_0.txt.
3. Run PFM and load one or two of the files in the detail lists below to make sure you see the new capability. For example, the dilemmas file was not previously supported by pfm; now it is.
4. (Optional) Come back to this post and add to my reputation by clicking the little green "+" button under my name at the left. This will help my standing in the forum.
The data here is entirely produced by taw and his converter. I have just correlated against pfm and converted into pfm format. For more detail on this correlation project see this thread.
(UPDATE 6 Oct 2012: sorry for leaving the following paragraph; it is no longer true. As of PFM 1.6.7 and patch9, unit_stats_land is working correctly.
Please note that the key file unit_stats_land is not currently working in either taw's converter or pfm. For a temporary workaround in pfm, see this thread. For the current status of this problem, see this post; if there is any new news, I will update here.
END UPDATE)
If you compare my directory DBFileTypes against the previous directory, you will notice several things.
1. The files DBFileTypes.txt and DBFileTypes_1-2.txt are missing from my directory on purpose. They were never read by PFM anyway, and they just make things confusing.
2. I have added DBFileTypes_16.txt. PFM does not read this yet. But, if we are successful in recompiling PFM from its outdated source files, then this file is needed to support the new unit_stats_land file.
3. In the case of (a,b) where I have replaced existing PFM data, I have deleted the section of data from its previous location. For all the 9 + 15 + 128 tables, I have put them in alphabetical order at the bottom of the file. These two decisions are intended to reduce the amount of "diffs" which may occur if we add these files into the current PFM source control "svn" area. I would prefer to completely regenerate the data, including the old unchanged data. This would make the files look cleaner and more organized, but it would make the number of "diffs" so huge that nobody would be able to compare versions. Presently we cannot access the svn anyway; but if we can, we will discuss which of these two approaches is best for updating svn.
Here is the list of the 9 fixed tables (a) and the 15 improved tables (b).
Here is a list of the 128 files (c) which are added to pfm.