-apps@lists.oasis-open.org
Subject: Re: [docbook-apps] Olink logic between different trunk/branches
folders of documentation (several projects)
It seems that you want to link arbitrarily from any version of any
document into any version of any other document. Generally, I don't
think this is a good
It seems that you want to link arbitrarily from any version of any
document into any version of any other document. Generally, I don't
think this is a good idea, because it's rather confusing to link to
two different versions of one book from one version of another. I
would think the customer
, October 11, 2010 3:48 AM
Subject: RE: [docbook-apps] Olink logic between different trunk/branches folders of
documentation (several projects)
Bob, thanks for details of your idea!
Unfortunately this is not completely suitable for my needs. The problems arise
here:
olink database file for each
Subject: Re: [docbook-apps] Olink logic between different trunk/branches
folders of documentation (several projects)
Hi,
If I understand correctly, I think you can handle this situation by:
1. Generating separate target data files (target.db) in each of your trunk and
branch
directories
: Friday, October 08, 2010 5:55 AM
Subject: RE: [docbook-apps] Olink logic between different trunk/branches folders of
documentation (several projects)
Hello!
Peter, Bob, thanks for the answers. Here is some my ideas... This message is as long
as my first one, sorry. I do my best to explain all
On Wed, Oct 6, 2010 at 7:34 AM, Eduard Tibet eduard.ti...@i-free.com wrote:
I have a general question regarding olinks logic in (and between) multiple
projects with trunk/branches folders.
I wasn't able to completely understand the details of your problem.
However, I have never put the
Hi,
If I understand correctly, I think you can handle this situation by:
1. Generating separate target data files (target.db) in each of your trunk and branch
directories, for each product and guide.
2. Creating multiple olink database files, each of which identifies which versions of
