Next in thread → Next in month →

RE: [docbook-apps] Universal Olinks in DB5

From
Eric Johnson <>
Date
2009-08-27T20:23:47+00:00
ID
Thread
RE: [docbook-apps] Universal Olinks in DB5
nope just hit reply instead reply all

From: Bob Stayton [mailto:] 

Sent: Thursday, August 27, 2009 3:13 PM
To: Eric 
Johnson
Subject: Re: [docbook-apps] Universal Olinks in 
DB5

Hi Eric,

Is there some reason your response didn't also go 
to docbook-apps?  I like to get exchanges like this recorded there for 
future reference.

 

Bob Stayton
Sagehill Enterprises


 

 

  
----- Original Message ----- 

  
From: 
  Eric 
  Johnson 

  
To: Bob Stayton 

  
Sent: Thursday, August 27, 2009 9:56 
  AM

  
Subject: RE: [docbook-apps] Universal 
  Olinks in DB5

  

  
Bob,

  
It is XHTML and I am using a sitemap. I did do a little 
  customizing of the olink template to make the links open in a new window. 
  Could that be the issue?

  
Thanks,

  
Eric J.

  

 

  

  
  From: Bob Stayton [mailto:] 
  
Sent: Thursday, August 27, 2009 12:39 PM
To: Eric 
  Johnson; DocBook Apps ML
Subject: Re: [docbook-apps] Universal 
  Olinks in DB5

  

  
It should work.  Is this PDF or HTML 
  output?  Are you using a sitemap in your olink database 
file?

  
 

  
Bob Stayton
Sagehill Enterprises


  
 

  
 

  
    
----- Original Message ----- 

    
From: 
    Eric 
    Johnson 

    
To: DocBook Apps ML 

    
Sent: Thursday, August 27, 2009 8:38 
    AM

    
Subject: [docbook-apps] Universal 
    Olinks in DB5

    

    
I was trying to 
    use the universal olinking in a DB5 book (the latest DB tools release) and 
    it seems to fail.

    
 

    
I used the 
    following markup:

    

    
<firstterm 
    xl:href="#RootResourceClass" xl:role="http://docbook.org/xlink/role/olink">root resource class</firstterm>

    
 

    
When building the source I got an error saying invalid 
    olink cannot find match for " / ".

    
When I used a regular olink element everything worked as 
    expected.

    
Is this a known issue or a bug that could be caused by my 
    customization 
layer?
Next in thread → Next in month →