bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Bug-gnubg] New gnubg-no-gui.exe unable to read MET


From: macherius
Subject: RE: [Bug-gnubg] New gnubg-no-gui.exe unable to read MET
Date: Thu, 17 Feb 2005 15:52:02 +0100

Moving the DTD wont help as log as you don't move or change the catalog file
along with it. I did not check the code, but I think that one is used as an
indirection to find the DTD by the parser. 

PUBLIC "-//GNU Backgammon//DTD Match Equity Tables//EN" "met.dtd"

So all XML documents of public ID Gnu are instructed to use "met.dtd", with
a relative path to the catalog.

There are 2 ways to solve this:

1. Make the installer change the path to the DTD during installation using
macro expansion, e.g.
@MET@ -> c:\program files\gnubg\met\gnubg.dtd

2. Not using a catalog at all, it may add just one extra indirection for no
effect as all it says is "the DTD is in the same directory I am and it is
named met.dtd".

Ingo


> -----Original Message-----
> From: address@hidden 
> [mailto:address@hidden On Behalf 
> Of Jon Kinsey
> Sent: Thursday, February 17, 2005 11:01 AM
> To: Øystein Johansen
> Cc: address@hidden
> Subject: Re: [Bug-gnubg] New gnubg-no-gui.exe unable to read MET
> 
> 
> Øystein Johansen wrote:
> > 
> > I checked the getInstallDir() returns in the new function 
> compared to 
> > the previous implementation.
> > 
> > The new implementation returns the string of the install directory, 
> > however the earlier (before 7 Feb) implementation returned NULL 
> > pointer? If the function returns NULL, everything else works?
> 
> Try moving (or copying) met.dtd to the parent directory.  
> There seems to 
> be a bug in the latest xml lib where the searching doesn't 
> work very well.
> 
> Jon
> 
> Ps. The function used to read the install dir from the registry - so 
> would return null if the key wasn't there.
> 
> 
> _______________________________________________
> Bug-gnubg mailing list
> address@hidden http://lists.gnu.org/mailman/listinfo/bug-gnubg
> 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]