headers
Vadim Gritsenko | 1 Jun 2002 01:25
Picon

RE: Sitemap parameters failing...

Can't reproduce. Are you sure that you are using latest (2.0.3 branch
CVS) sitemap.xsl?

Vadim

--
Resistance is futile. 

> -----Original Message-----
> From: Per Kreipke [mailto:per <at> onclave.com]
> Sent: Friday, May 31, 2002 12:08 PM
> To: cocoon-dev <at> xml.apache.org
> Subject: Sitemap parameters failing...
> 
> In the following test sitemap fragment, I thought I was doing
something
> wrong because I couldn't get the sitemap to compile:
> 
> <map:match patter="client.xml">
> 	<map:parameter name="client" value="magnet" />
> 
> 	<map:generate src="config/{client}.xml" />
> 	<map:serialize type="xml" />
> </map:match>
> 
> 
> When I look at the sitemap.xsl code I think I see why: the generated
java
> fragment below is wrong, param is initialized outside the function
> definition for the matcher.
(Continue reading)

Permalink | Reply | 4 comments |
headers
Conal Tuohy | 1 Jun 2002 03:16
Picon
Favicon

RE: images problem in css during build

> >Put the image url in a commented link tag, and I think it 
> will be picked up.
> ><!-- <a href="mystylesheet">Dummy link</a> -->
> 
> Just tested it, they are not picked up.  Without the comment 
> tags it works.
> Bert

Try <a href="mystylesheet.css"></a>.
Permalink | Reply | 0 comments |
headers
Justin Fagnani-Bell | 1 Jun 2002 03:27

Re: How to make custom XSP-like language??

Thanks for the quick reply Vadim.

I'm pretty confused by the difference in the cocoon.xconf files that 
come with the Cocoon instalation and the file in the documentation and 
your example in this email.

>> I'm trying to create a new XSP-like language for my application. This
>> language needs to have a different base class than XSPGenerator, and
>> some changes are needed to the xsp.xsl logicsheet so that I can change
>> how the generate() method is created.

>> So I'd like to use my own stylesheet instead of xsp.xsl, but still keep
>> xsp.xsl and the xsp sections of cocoon.conf as distributed so that
>> normal xsp pages would still work. I can't find any documentation on
>> this.
>>
>> I'd imagine that I'd need to add something like this to cocoon.xconf:
>>
>>    <markup-languages>
>>      <xsp-language name="MyML">
>>        <parameter name="prefix" value="mml"/>
>>        <parameter name="uri" value="http://paraliansoftware.com/myml"/>
>>        <target-language name="java">
>>          <parameter name="core-logicsheet"
>> value="resource://com/paralian/myml/myml.xsl"/>
>>        </target-language>
>>      </xsp-language>
>>
>> But should this really be in an xsp-language tag, or in a myml-language
>> tag? And once I did this would I just pass "myml" to
(Continue reading)

Permalink | Reply | 4 comments |
headers
Diana Shannon | 1 Jun 2002 15:14
Picon
Favicon

Re: [report] xml-site update


On Saturday, June 1, 2002, at 08:16  AM, Robert Koberg wrote:

>>> I think we should attempt to catch internal links problems prior to 
>>> commits with the live site cvs.
>>>
>>
>> Yes. The LinkAlarm run will check them too, but that does
>> not hurt.
>>
> It seems so strange that you hard code these things...
>
> This should never be a problem. I don't understand the reluctance to 
> use basic XSLT features, but by referencing the link/menu data through 
> the document function (or whatever the right way is for cocoon - 
> strange that it has to be different...) you totally eliminate this 
> problem. If the link exists it is guaranteed to be correct. If a link 
> 'links' to something that does not exist, either do not render the <a 
> href/> (just the text) or wrap it in a span that has font-color:red or 
> something.

Part of the problem, Rob, is that we are dealing with static html files 
that are merged together. The live site is produced from static html 
files which result from release branch builds -- also html. We have to 
take partial results of a release branch build (files and directories) 
and merge with existing live site cvs files and directories. It's 
inefficient, yes, but Forrest will address this issue.

Diana
(Continue reading)

Permalink | Reply | 10 comments |
headers
Robert Koberg | 1 Jun 2002 15:29

Re: [report] xml-site update

Diana Shannon wrote:

>
> On Saturday, June 1, 2002, at 08:16  AM, Robert Koberg wrote:
>
>>>> I think we should attempt to catch internal links problems prior to 
>>>> commits with the live site cvs.
>>>>
>>>
>>> Yes. The LinkAlarm run will check them too, but that does
>>> not hurt.
>>>
>> It seems so strange that you hard code these things...
>>
>> This should never be a problem. I don't understand the reluctance to 
>> use basic XSLT features, but by referencing the link/menu data 
>> through the document function (or whatever the right way is for 
>> cocoon - strange that it has to be different...) you totally 
>> eliminate this problem. If the link exists it is guaranteed to be 
>> correct. If a link 'links' to something that does not exist, either 
>> do not render the <a href/> (just the text) or wrap it in a span that 
>> has font-color:red or something.
>
>
> Part of the problem, Rob, is that we are dealing with static html 
> files that are merged together. The live site is produced from static 
> html files which result from release branch builds -- also html. We 
> have to take partial results of a release branch build (files and 
> directories) and merge with existing live site cvs files and 
> directories. It's inefficient, yes, but Forrest will address this issue.
(Continue reading)

Permalink | Reply | 9 comments |
headers
Tom Klaasen | 1 Jun 2002 14:48
Picon

Re: DOM help!

Does this help?
http://xml.apache.org/xalan-j/apidocs/org/w3c/dom/Document.html#importNode(org.w3c.dom.Node,%20boolean)

Hope it does,
tomK

Jeremy Quinn wrote:

> Hi People,
>
> I am bashing my head against a brick wall here ;)
>
> Would some kind soul give me a clue as to how you convert an 
> org.w3c.dom.DocumentFragment into a full-blown org.w3c.dom.Document?
>
>
> Thanks for any help
>
> regards Jeremy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe <at> xml.apache.org
> For additional commands, email: cocoon-dev-help <at> xml.apache.org
>
>
>
Permalink | Reply | 1 comment |
headers
Robert Koberg | 1 Jun 2002 15:52

Re: [report] xml-site update

Robert Koberg wrote:

> Diana Shannon wrote:
>
>>
>> On Saturday, June 1, 2002, at 08:16  AM, Robert Koberg wrote:
>>
>>>>> I think we should attempt to catch internal links problems prior 
>>>>> to commits with the live site cvs.
>>>>>
>>>>
>>>> Yes. The LinkAlarm run will check them too, but that does
>>>> not hurt.
>>>>
>>> It seems so strange that you hard code these things...
>>>
>>> This should never be a problem. I don't understand the reluctance to 
>>> use basic XSLT features, but by referencing the link/menu data 
>>> through the document function (or whatever the right way is for 
>>> cocoon - strange that it has to be different...) you totally 
>>> eliminate this problem. If the link exists it is guaranteed to be 
>>> correct. If a link 'links' to something that does not exist, either 
>>> do not render the <a href/> (just the text) or wrap it in a span 
>>> that has font-color:red or something.
>>
>>
>>
>> Part of the problem, Rob, is that we are dealing with static html 
>> files that are merged together. The live site is produced from static 
>> html files which result from release branch builds -- also html. We
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mattam | 1 Jun 2002 14:04
Favicon

Re: [doc] name for new content type?

Le Sat, 1 Jun 2002 07:35:28 -0400, Diana Shannon a écrit:

>I'm about to introduce a new category of community contributions, code 
>snippets. I'm struggling with a name. Here's my own suggestions:
>
>snippet (expanded in titles to code snippets)
>recipe (expanded in titles to Cocoon code cookbook recipes)
>code (expanded in titles to code samples)
>
>Any suggestions?  I like snippet the best so far, but does that work for 
>non-native English speakers?
>

That works for non-natives, and it is is common use in mails with <snip/> (even for french language messages).
My +1 for snippet.

--

-- 
"Not only is there no God, but try finding a plumber on Sunday. " - Woody Allen

MaT|TaM (http://mattam.ath.cx)
Permalink | Reply | 0 comments |
headers
Robert Koberg | 1 Jun 2002 14:16

Re: [report] xml-site update

David Crossley wrote:

>Diana Shannon wrote:
><snip/>
>  
>
>>I think we should attempt to catch internal links problems prior to 
>>commits with the live site cvs.
>>    
>>
>
>Yes. The LinkAlarm run will check them too, but that does
>not hurt.
>
It seems so strange that you hard code these things...

This should never be a problem. I don't understand the reluctance to use 
basic XSLT features, but by referencing the link/menu data through the 
document function (or whatever the right way is for cocoon - strange 
that it has to be different...) you totally eliminate this problem. If 
the link exists it is guaranteed to be correct. If a link 'links' to 
something that does not exist, either do not render the <a href/> (just 
the text) or wrap it in a span that has font-color:red or something.

-Rob
Permalink | Reply | 11 comments |
headers
Ivelin Ivanov | 1 Jun 2002 15:51
Picon
Favicon

DocBook vs Open eBook


Does someone know the difference between these two standards initiatives:
http://www.oasis-open.org/committees/docbook/
http://www.oasis-open.org/cover/openEbook.html

They both seem to have industry backing while at the same time overlap quite
a bit.

Also, why don't we use one of these two for our documentation instead of
maintaining proprietary DTDs. There are tools on the market for WYWIWYG
editing of both of these standards, which can make doc writing easier. And
of course there are XLSTs for rendering to media from XHTML to voxml to PDF.

Regards,

Ivelin
Permalink | Reply | 7 comments |

Gmane