Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 26469 invoked by uid 500); 1 Jun 2002 08:45:35 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 26458 invoked from network); 1 Jun 2002 08:45:35 -0000 Date: Sat, 1 Jun 2002 11:51:47 +0300 (EEST) From: Cocoon User To: "'cocoon-users@xml.apache.org'" Subject: RE: .htc how to In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N .htc files are nothing more than .js files plus they are working just like VS's class modules so .htc are not well-formed xml they are not xml i dontd understand why cocoon dont handle .htc file just like .js On Tue, 28 May 2002, Kelly Cole wrote: > Did you get this to work? I don't know much about htc's except that I have > used the MS sample calendar.htc. I can't figure out how to set the rule for > it with Cocoon. > > How did you do it? I tried: > > > > > > Note: My htc file is not well-formed xml. Is this the problem for me? > > Thanks, > Kelly > > -----Original Message----- > From: Stephen Ng [mailto:stephen.ng@verizon.net] > Sent: Tuesday, May 14, 2002 6:39 PM > To: cocoon-users@xml.apache.org > Subject: RE: .htc how to > > > You must serve the .htc from Cocoon--do you have a rule for it in your > sitemap? > > > -----Original Message----- > > From: Cocoon User [mailto:cocoon@eng.gr] > > Sent: Monday, May 13, 2002 8:07 PM > > To: cocoon-users@xml.apache.org > > Subject: .htc how to > > > > > > > > i have a behavor (microsoft .htc) > > attached in a stylesheet > > i aply this style into a
element in a .xml page > > when i transofrm this .xml using xsl in IE6 i recieve re corect result > > > > but through cocoon i see everything except the result i'm waiting from > > .htc > > > > > > any idea ? > > > > thanks > > > > > > > > > > --------------------------------------------------------------------- > > Please check that your question has not already been answered in the > > FAQ before posting. > > > > To unsubscribe, e-mail: > > For additional commands, e-mail: > > > > > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. > > To unsubscribe, e-mail: > For additional commands, e-mail: > > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. > > To unsubscribe, e-mail: > For additional commands, e-mail: > > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: