Re: link rel=

[Joerg Heinicke]

Really strange, but this is definitely a Mozilla problem. I use Mozilla 
1.1 and have no problems. Maybe you should post a bug at 
http://bugzilla.mozilla.org.

Joerg

Alessio Sangalli wrote:

Joerg Heinicke wrote:


Hmm, what exactly do you mean? You request an XML page, but you don't
see anything? Mozilla has no built-in stylesheet by default like IE. But
you can see the source of the document (Ctrl + u).



no, I mean when I reply an email like yours, containing a piece of xml 
code. All your message is quoted, but the lines with code are blank.

bye
as


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: link rel=

[Jeremy Quinn]

On Tuesday, Nov 12, 2002, at 13:55 Europe/London, Alessio Sangalli 
wrote:


Jeremy Quinn wrote:


what I do to deal with this kind of thing is to have a menu.xml
structure, that is imported into all my pages via CInclude, then xslt


mh, I've never understood the difference between Xinclude and 
Cinclude...


Unfortunately (in 2.1) there are three (?) versions, 
CachingCIncludeTransformer, CIncludeTransformer and 
XIncludeTransformer. They all basically do the same job, but have 
different options.

The XInclude on uses the W3c XInclude standard tags and includes the 
XPointer syntax, the CInclude 'family' use Cocoon-specific tags.

(having been provided with the 'id' of the page via the sitemap) makes
two structures from the menu.xml, 1) my html navigation 2) the meta
links you mention.


yes, cool; I would like to prepare accurate documentation about the 
way my website was built. This could also be a useful how-to for 
cocoon newbies. If you want to contribute, I'd accept some pieces of 
code from your xsl-transformations...!

Well that is tricky, mine works with my data, I cannot guarantee this 
even works as it stands  my data is more complex than this, I 
hope the xslt below works properly with the simplified case, it is not 
tested!

My menus look something like this:


	
		A Menu
		this is a sample
	
	Home Page
	index
	
		Page One
		one/index
	
	
		Page Two
		two/index
		
			Page Two/One
			two/one
		
		
			Page Two/Two
			two/two
		
	
	etc ..


This is my xslt for making s (in it's present design, it works 
on the  being the only content). This does not deal with the 
internal links within documents.


	xmlns:xsl="http://www.w3.org/1999/XSL/Transform";

	 

	
	
	
	
	

	
		
			
		
		
			
		
		
			
		
		
			
		
		
			
		
		
			
		
		
			
		
		
			
		
		
			
		
	



Hope this helps

regards Jeremy


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: link rel=

[Diana Shannon]

On Tuesday, November 12, 2002, at 08:55  AM, Alessio Sangalli wrote:


mh, I've never understood the difference between Xinclude and 
Cinclude...

Have you checked:
  http://xml.apache.org/cocoon/faq/faq-transformers.html#faq-2


Diana


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: link rel=

[Alessio Sangalli]

Jeremy Quinn wrote:

yours code is quite different than mine because I use a different 
approach: this is the xml data I Xinclude in all files:


 Indexindex.html
 Toolstools.html
 Partsparts.html
 Circuitcircuit.html
 0101.html
 0202.html
 0303.html
 0404.html
 0505.html
 Linkslinks.html


and this is the xsl code wich generates the link rel things:














bye! and thank you you example gave me inspiration (is it the correct 
english word? boh)

bye
as





-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: link rel=

[Joerg Heinicke]

Alessio Sangalli wrote:

Hi I've a little problem because I want to automatically generate the 
"link" header (if you use Mozilla, it's very useful, if you want to show 
it: menu -> view - show-hide - site navigation toolbar - show [as needed]).




How can I implement it? Perhaps on the sitemap a parameter to the xsl 
transformer wich tells the actual file name; the xsl-t should then check 
it against an xml file where I wrote the exact order of the pages, and 
write the link headers accordingly.

What do you think?
Thank you
as

Exactly the way I would do it. But beware: XSLTs are chached with their 
parameters. So it's interesting to know, how many pages you have or how 
big the XSLTs are. Maybe it's an alternative to aggregate the XML source 
with the navigation XML.

Regards,

Joerg


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: link rel=

[Jeremy Quinn]

On Monday, Nov 11, 2002, at 18:21 Europe/London, Alessio Sangalli wrote:


Hi I've a little problem because I want to automatically generate the 
"link" header (if you use Mozilla, it's very useful, if you want to 
show it: menu -> view - show-hide - site navigation toolbar - show [as 
needed]).

Here is an example:








what I do to deal with this kind of thing is to have a menu.xml 
structure, that is imported into all my pages via CInclude, then xslt 
(having been provided with the 'id' of the page via the sitemap) makes 
two structures from the menu.xml, 1) my html navigation 2) the meta 
links you mention. I also output rel="Chapter" (of sub-pages) links so 
all nav can be done from the site nav toolbar. Mozilla also handles 
rel="Section" and rel="SubSection".


Hope this helps

regards Jeremy


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: link rel=

[Alessio Sangalli]

Joerg Heinicke wrote:


Exactly the way I would do it. But beware: XSLTs are chached with their
parameters. So it's interesting to know, how many pages you have or how
big the XSLTs are.



$ ls *.xml | wc -l
 12
(to be honest two xml pages are only tests)

$ wc -ml html.xsl
 862055 html.xsl
$ grep -c "  Maybe it's an alternative to aggregate the XML source
> with the navigation XML.

I don't understand this, could you explain?


bye
as




-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: link rel=

[Alessio Sangalli]

Jeremy Quinn wrote:


what I do to deal with this kind of thing is to have a menu.xml
structure, that is imported into all my pages via CInclude, then xslt


mh, I've never understood the difference between Xinclude and Cinclude...


(having been provided with the 'id' of the page via the sitemap) makes
two structures from the menu.xml, 1) my html navigation 2) the meta
links you mention.


yes, cool; I would like to prepare accurate documentation about the way 
my website was built. This could also be a useful how-to for cocoon 
newbies. If you want to contribute, I'd accept some pieces of code from 
your xsl-transformations...!


 I also output rel="Chapter" (of sub-pages) links so
all nav can be done from the site nav toolbar. Mozilla also handles
rel="Section" and rel="SubSection".



my data is rather simple so I don't need chapters and subchapters. Maybe 
I will use those features in the future, thank you!

bye
as





-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: link rel=

[Joerg Heinicke]

Hello Alessio,

Alessio Sangalli wrote:


Joerg Heinicke wrote:


Exactly the way I would do it. But beware: XSLTs are chached with their
parameters. So it's interesting to know, how many pages you have or how
big the XSLTs are.


$ ls *.xml | wc -l
 12
(to be honest two xml pages are only tests)

$ wc -ml html.xsl
 862055 html.xsl
$ grep -c "

that's ok ;-) It was more a general statement than a need for the numbers.


 >  Maybe it's an alternative to aggregate the XML source
 > with the navigation XML.

I don't understand this, could you explain?


example of sitemap aggregation:


  


  
  
  


> Jeremy Quinn wrote:
>>
>> what I do to deal with this kind of thing is to have a menu.xml
>> structure, that is imported into all my pages via CInclude, then xslt
>
> mh, I've never understood the difference between Xinclude and
> Cinclude...

CInclude was an earlier implementation. Later the standard conform 
XInclude was implemented and the CInclude refactored. Now they have in 
general the same functionality AFAIK and somebody wanted to bring them 
to the same code and functionality (so that only the namespaces are 
different and both are usable and do the same).

Regards,

Joerg


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: link rel=

[Alessio Sangalli]

Joerg Heinicke wrote:


that's ok ;-) It was more a general statement than a need for the numbers.


:) ok I wanted to be precise!



>  >  Maybe it's an alternative to aggregate the XML source
>  > with the navigation XML.
>
> I don't understand this, could you explain?


example of sitemap aggregation:


I use Mozilla 1.2b. When I quote xml code it doesn't appear. Is this a 
know bug?

Back to aggragation: I see I can use it like a 'multiple generator' now 
I should read the docs/references. There is not so much difference than 
a Xinclude I think, and I'm going to (hopefully) use Cocoon by command 
line to generate static html, pdf, so performance isn't a key feature.

Many thanks, this discussion clarified my ideas!


bye
as




-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: link rel=

[Joerg Heinicke]

I use Mozilla 1.2b. When I quote xml code it doesn't appear. Is this a 
know bug?

Hmm, what exactly do you mean? You request an XML page, but you don't 
see anything? Mozilla has no built-in stylesheet by default like IE. But 
you can see the source of the document (Ctrl + u).

Joerg


-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Re: link rel=

[Alessio Sangalli]

Joerg Heinicke wrote:


Hmm, what exactly do you mean? You request an XML page, but you don't
see anything? Mozilla has no built-in stylesheet by default like IE. But
you can see the source of the document (Ctrl + u).


no, I mean when I reply an email like yours, containing a piece of xml 
code. All your message is quoted, but the lines with code are blank.

bye
as





-
Please check that your question  has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>