Re: [Hypercontent-users] Project Definition xml

[Alex V. <av...@co...>]

Hi Liying,
	You'll find a directory =
"/config/project-definition.xml/editions/" in=20
your project repository (whose base path you configured in=20
filesystem.xml).  Under this directory will be a sub-directory for each=20=

edition you have saved; go into the most recent directory (the highest=20=

number) and edit "data_file".

-Alex

On Jul 8, 2005, at 5:11 PM, Liying Miao wrote:

> Hi Alex,
> =A0
> Could I physically edit the project-definition .xml instead of edit=20
> from web? I was trying to add an xml-doctype and didn=92t do it=20
> correctly, and now I can=92t get to it online, instead, I get java=20
> errors.
> =A0
> If yes, where is the file please? I only see project-definition.xml in=20=

> this folder:=20
> C:\hc2.0\hypercontent2.0b2\hypercontent2\repositories\bootstrap\config
> =A0
> Thanks,
> Liying
> =A0
> =A0
>
> From: hyp...@li...=20
> [mailto:hyp...@li...] On Behalf Of=20=

> Alex Vigdor
> Sent: Friday, July 08, 2005 11:39 AM
> To: 'Hypercontent-users' users
> Subject: Re: [Hypercontent-users] Ant Configuration Problem
> =A0
>> Hi Liying,
>>  This is not a serious error; the XML isn't really intended for=20
>> display, but rather for use as a data storage format, and=20
>> HyperContent uses an Oasis XML catalog=20
>> (/classes/properties/catalog.xml) to map these URLs to local copies=20=

>> of the core DTDs (this is why the DTD is found fine when you go to=20
>> edit the file, even though it isn't up on the web site yet). No=20
>> matter what you do, don't try to change the URL of those core system=20=

>> DTDs! Some, for example the custom-dictionary DTD, must have the=20
>> exact URL in order to function properly.
>>
>>  I will try to load those DTDs on the web site later today, after I=20=

>> finish packaging the beta3 release, to remove the annoyance of those=20=

>> browser errors. Just as a note, I believe Firefox and Mozilla will go=20=

>> ahead and display the XML whether or not they find the DTD; that=20
>> error is really IE specific.
>>
>>  Alex
>>