From noreply+feedproxy at google.com  Sat Jul  1 00:08:40 2017
From: noreply+feedproxy at google.com (oXygen XML Editor Blog)
Date: Sat, 01 Jul 2017 05:08:40 +0000
Subject: [oXygen-user] [oXygen XML Editor Blog] - DITA Linking Strategies
Message-ID: <001a1141b9e8ee5e5e05533a867a@google.com>

oXygen XML Editor Blog

///////////////////////////////////////////
DITA Linking Strategies

Posted: 30 Jun 2017 06:11 AM PDT
http://feedproxy.google.com/~r/AboutOxygenXmlEditor/~3/NkzlLkUcD9Q/dita-linking-strategies.html?utm_source=feedburner&utm_medium=email

         This small tutorial is based on the "DITA Linking Strategies"  
presentations I made for       the DITA Europe 2016 and DITA North America  
2017 conferences. It's a general overview about       DITA linking  
possibilities and best practices. Also, it's meant as a continuation of the  
DITA Reuse Strategies blog post.         According to Wikipedia: "A link,  
is a reference to data that the                 reader can directly follow  
either by clicking, tapping, or hovering."         Basically, we should  
regard linking as yet another form of content reuse, except that        
instead of presenting the content in place, it re-directs the end user to  
some other       resource.     I'll start with describing linking at DITA  
Map level.         Map-Level Linking                         A DITA Map  
uses topic references to assemble the content of a         publication.  
<topicref href="installation.dita">
   <topicref href="server_installation.dita"/>
   <topicref href="client_side_installation.dita"/>
  </topicref>             Depending on the output format, the topic  
reference may be a link in the table of         contents for the  
XHTML-based outputs or it may be interpreted as a content reference for  
the         PDF-based output that generates a single monolith document. So  
the role of the           topicref is dual, it may sometimes be regarded as  
a link to a topic and         sometimes as a content  
reference.                  Chunking                         DITA topic  
modules should be kept as small as possible, but sometimes the end  
user         may need to read more than one topic to achieve a single task.  
So, when publishing to         HTML-based outputs, you will end up asking  
yourself this question:Should I prefer larger           HTML files or more  
links in the TOC?             And you should always consider these two  
ideas:                                            Links are disruptive.  
Ideally, users would not need to jump around in               content to  
read the entire story they are searching  
for.                                           Small topics that are  
usually read consecutively by the end user can             probably get  
merged together.                              For example, if the  
installation of your product requires installing both a         server-side  
and a client-side component, by using DITA chunking you can choose to  
have         separate DITA topic modules for each of the installation  
procedures but merge the topics         together in the web-based          
outputs:<map>
  <title>User Guide</title>
  <topicref href="installation.dita" chunk="to-content">
   <topicref href="server_installation.dita" toc="no"/>
   <topicref href="client_side_installation.dita" toc="no"/>
  </topicref>
</map>             You can read more about chunking in the DITA 1.3  
specification. The DITA Style Guide also has a good overview about  
why         it is preferable to write small topics and then merge them  
together using the chunking         mechanism.                  Topic-Level  
Linking                         Links that appear inside topics can be  
divided into various categories and I'll         discuss each of these  
categories separately.                  In-Content  
Links                         In-content links are links added manually in  
the topic                 content:<li>See: <xref href="http://www.../"  
format="html" scope="external"/></li>             You should keep in mind  
that this kind of link is disruptive to the reading         experience  
because when end users encounter them, they need to decide weather to  
read         further on or to follow the link. On the other hand, this may  
sometimes be a good thing. For         example, one of the installation  
steps may require the end user to download a certain         library from  
an external website before continuing.             You can read more about  
links in general in the DITA 1.3 specification. The DITA Style Guide,  
written by Tony Self, also         discourages the use of in-content  
links.                  Related Links                         Related links  
are placed at the end of the DITA topic and they allow the end user  
to                 explore additional resources after the current topic has  
been                 read.<related-links>
     <link href="http://tomcat.apache.org/" format="html" scope="external"/>
</related-links>             To minimize disruption when reading the  
content in general, the preferred place where         to place links is at  
the end of the generated HTML page.             You can read more about  
related links in the DITA 1.3 specification.                  Defining  
Related Links using Relationship Tables                         Related  
links do not need to be manually added at the end of each topic. You  
can                 define relationship tables in the DITA                  
Map:<reltable>
   <relrow>
    <relcell>
     <topicref href="client_side_installation.dita"/>
    </relcell>
    <relcell>
     <topicref href="server_installation.dita"/>
    </relcell>
   </relrow>
   ……..
  </reltable>             These tables can define associations between two  
or more topics, associations that         automatically contribute to the  
related links creation in the generated HTML output.             Here are  
some benefits of using relationship tables:                      A topic  
should have as few links as possible defined directly within. This makes  
it               easier to reuse the topic in various contexts and keeps it  
as separate as possible for               other parts of the DITA project,  
decreasing the possibility of broken  
links.                                   By default, links defined in  
relationship tables are bi-directional, allowing users               to  
land on any of the topics when searching for solutions and find their way  
to the               related ones.                                   Using  
a relationship table separates the task of writing topics from the task  
of               finding relationships between  
topics.                                 You can read more about  
relationship tables in the DITA 1.3 specification. The DITA Style Guide  
also recommends using relationship         tables.                   
Indirect Links (Key References)                         All the link  
samples we've look at so far have been direct links, links that point  
to         the target using the @href attribute. Indirect links require two  
steps:          Define a key in the DITA Map for the              
target.<keydef keys="client_installation"  
href="client_side_installation.dita"/>           Use the defined key to  
reference the target             resources.<xref  
keyref="client_installation"/>                      Here are some of the  
benefits of indirect linking:                                             
Offers the ability to reuse link target text and meta data. If you  
want               to have custom text for a certain link, you can define  
it directly in the DITA               Map:<keydef keys="dita_ot_website"  
href="http://www.dita-ot.org/" format="html"
   scope="external">
   <topicmeta>
    <linktext>DITA Open Toolkit Web Site</linktext>
   </topicmeta>
  </keydef>and               then add key references in all  
other               places:<xref  
keyref="dita_ot_website"/>                                                                   
Easier conditional linking (including links to topics that sometimes  
may               be missing). If you want your topic to link either to one  
target or to another               depending on the filtering/profiling  
conditions, instead of adding profiling directly               on the link,  
you can add the profiling conditions directly in the DITA                
Map: <topicref keys="slicing" href="slicing_vegetables_for_experts.dita"  
audience="expert"/>
  <topicref keys="slicing" href="slicing_vegetables_for_novices.dita"  
audience="novice"/>
  <keydef keys="slicing" audience="noLink"><topicmeta><keywords>
     <keyword>Slicing</keyword></keywords></topicmeta>
  </keydef>and               then link to the key from each  
topic:               <xref  
keyref="slicing"/>                                                                   
Easier link management. A good overview about all the outbound links  
in               your project helps you maintain and control lists of  
allowed external web sites. With               indirect references, you can  
define all references to external resources in a separate                
DITA Map. An example of a DITA project using indirect links to achieve  
separation of               links by purpose can be found here:  
https://github.com/oxygenxml/dita-project-best-practices.                                           
Makes it easier to move/rename topics. When you move or rename a  
topic             referenced via indirect links, only the link defined in  
the DITA Map will break, making             it easier to fix broken  
links.                              There is an overview about indirect  
addressing on the DITA XML Org website. The DITA 1.3 specification also has  
a chapter                 about indirect links.                   
Auto-Generated Links                         Until now, I've talked about  
manually added links, either in the topic or in         relationship  
tables. Using the DITA @collection-type attribute, you can         define  
relationships between parent and child topic references in the DITA  
Map,         relationships that result in automatic links added  
between         them: <topicref href="installation.dita"  
collection-type="sequence">
   <topicref href="server_installation.dita"/>
   <topicref href="client_side_installation.dita"/>
  </topicref>         There are 3 useful types of @collection-type  
values:                      Unordered - Links are generated from parent to  
children, and from children to                
parent.                                   Family - Links are generated from  
parent to children, from children to parent,               and from sibling  
to sibling.                                   Sequence - Links are  
generated from parent to children, from children to               parent,  
and from child to previous sibling (if applicable) and next sibling  
(if               applicable).                                  You can  
read more about auto-generated links in the DITA Style  
Guide.                  Conditional Links in Distinct  
Publications                         You may publish documentation for  
multiple products from the same DITA        content. Also, you may want to  
have links point to various targets depending on the product         for  
which you want to publish the documentation. Or, you may want to suppress  
links         completely in certain publications.             When using  
direct linking, you will need to profile each link depending on the          
publication:Find our more about slicing vegetables: <xref  
href="slicing_vegetables_for_experts.dita" audience="expert"/>
<xref href="slicing_vegetables_for_novices.dita"  
audience="novice"/>.With         indirect links, you can define the  
profiling attributes as DITA Map         level: <topicref keys="slicing"  
href="slicing_vegetables_for_experts.dita" audience="expert"/>
  <topicref keys="slicing" href="slicing_vegetables_for_novices.dita"  
audience="novice"/>and         thus, simplify the reference made in the  
topic         content:Find our more about slicing vegetables: <xref  
keyref="slicing/>.                  Conditional Links in the Same  
PublicationUsing DITA 1.3 key scopes, you can reuse a topic multiple times  
in a         DITA Map and have each referenced topic contain links to  
various target topics. For example,         if my preparing_vegetables.dita  
topic has a         link:<link keyref="slicing"/>you       can define  
various key scopes in the DITA Map that bind the "slicing" key to  
various         targets: <topichead navtitle="Cooking for Experts"  
keyscope="expert">
   <topicref href="preparing_vegetables.dita" keys="preparing"/>
   <topicref href="slicing_vegetables_for_experts.dita" keys="slicing"/>
  </topichead>
  <topichead navtitle="Cooking for Novices" keyscope="novice">
   <topicref href="preparing_vegetables.dita" keys="preparing"/>
   <topicref href="slicing_vegetables_for_novices.dita" keys="slicing"/>
  </topichead>This         previous blog post contains more details about  
key         scopes.         Link Text                         When linking  
to an external resource or to a DITA topic or element, the  
publishing         engine will attempt to deduce the link text from the  
target context. For example, the link         to a DITA topic or element  
that contains a <title> will use that         title as the link text. The  
link to an external resource (for example to            
http://www.oxygenxml.com) will, by default, use the HTTP location as  
the         link text. You can also customize each link text individually.  
So, ask yourself this         question:                             Should  
I leave the link text to be automatically computed or should I set a  
more                     friendly text?                          For  
internal links to elements that have a title, in general it is more  
flexible to         not set a custom text and let the publishing engine  
decide one for you. For external links,         you should usually specify  
your custom link text.                   Should I Link or Should I  
Reuse?                         Suppose you want to bring a certain  
paragraph, note, or section to the end user's         attention. If that  
particular target element is not very large, you should always reuse  
it         (using a content reference) instead of linking to  
it.                  Conclusions                         As with all large  
projects, managing links in a growing DITA project can be          
problematic, so you need to become organized. As an overview of what we've  
discussed so far,         I suggest the following best  
practices:                      Linking is a form of reuse  
so:                           Reuse small pieces of content instead of  
linking to them               Avoid too much linking (linking is  
disruptive)                                               Use indirect  
links. It will allow you to reuse link text and make  
profiling/filtering               easier while giving you a better overview  
of the outbound links for your  
project.                                      If you want to experiment  
with the various linking strategies I discussed above, you can       find  
some samples here:  
https://www.oxygenxml.com/forum/files/linking-strategies-samples.zip.

--
You are subscribed to email updates from "oXygen XML Editor Blog."
To stop receiving these emails, you may unsubscribe now:  
https://feedburner.google.com/fb/a/mailunsubscribe?k=y_tRXtumvTurKTedh51JnlYsGXw

Email delivery powered by Google.
Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, United  
States

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20170701/2847eb8c/attachment.html>

From lionel.moizeau at l-acoustics.com  Wed Jul  5 07:11:26 2017
From: lionel.moizeau at l-acoustics.com (Lionel MOIZEAU)
Date: Wed, 5 Jul 2017 12:11:26 +0000
Subject: [oXygen-user] Current ditamap editor variable
Message-ID: <AM5PR0101MB24202A2DB52A981D471092C7D1D40@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>

Hi !

Is there a way to get the current ditamap as an editor variable ? By current map I mean the one open in the DITA Maps manager or selected in the Root map dropdown menu
[cid:image001.png at 01D2F598.961ECA00]

It would be very helpful !

Best regards,

Lionel MOIZEAU
Head of Technical Information Department

L-Acoustics
Tel : +33 1 69 63 23 99

www.l-acoustics.com<http://www.l-acoustics.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20170705/302e42c4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 10231 bytes
Desc: image001.png
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20170705/302e42c4/attachment.png>

From support at oxygenxml.com  Wed Jul  5 07:43:25 2017
From: support at oxygenxml.com (Oxygen XML Editor Support (Radu Coravu) )
Date: Wed, 5 Jul 2017 15:43:25 +0300
Subject: [oXygen-user] Current ditamap editor variable
In-Reply-To: <AM5PR0101MB24202A2DB52A981D471092C7D1D40@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>
References: <AM5PR0101MB24202A2DB52A981D471092C7D1D40@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>
Message-ID: <cee7c3a1-9d0d-4879-b321-e85d465a9fec@oxygenxml.com>

Hi Lionel,

We will have an editor variable available for that in Oxygen 19.1 
(Autumn this year).

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 7/5/2017 3:11 PM, Lionel MOIZEAU wrote:
> Hi !
>
>
>
> Is there a way to get the current ditamap as an editor variable ? By
> current map I mean the one open in the DITA Maps manager or selected in
> the Root map dropdown menu
>
>
>
> It would be very helpful !
>
>
>
> Best regards,
>
>
>
> Lionel MOIZEAU
> Head of Technical Information Department
>
> *L-Acoustics*
> Tel : +33 1 69 63 23 99
>
> www.l-acoustics.com <http://www.l-acoustics.com/>
>
>
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
>

From lionel.moizeau at l-acoustics.com  Wed Jul  5 08:12:41 2017
From: lionel.moizeau at l-acoustics.com (Lionel MOIZEAU)
Date: Wed, 5 Jul 2017 13:12:41 +0000
Subject: [oXygen-user] Current ditamap editor variable
In-Reply-To: <cee7c3a1-9d0d-4879-b321-e85d465a9fec@oxygenxml.com>
References: <AM5PR0101MB24202A2DB52A981D471092C7D1D40@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>
 <cee7c3a1-9d0d-4879-b321-e85d465a9fec@oxygenxml.com>
Message-ID: <AM5PR0101MB24201F31AB69945F01948B65D1D40@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>

Perfect !

Lionel MOIZEAU
Head of Technical Information Department

L-Acoustics
Tel : +33 1 69 63 23 99

www.l-acoustics.com
-----Message d'origine-----
De : oXygen-user [mailto:oxygen-user-bounces at oxygenxml.com] De la part de Oxygen XML Editor Support (Radu Coravu) 
Envoyé : mercredi 5 juillet 2017 14:43
À : oxygen-user at oxygenxml.com
Objet : Re: [oXygen-user] Current ditamap editor variable

Hi Lionel,

We will have an editor variable available for that in Oxygen 19.1 (Autumn this year).

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.oxygenxml.com&data=02%7C01%7Clionel.moizeau%40l-acoustics.com%7C85afcbd9747a4124349908d4c3a37f92%7C68e431e8d632483eae79f28a7b4c69e6%7C1%7C0%7C636348554383421745&sdata=38wMbdh7ZLu2%2FlOyBdPST4Oq59JquYpPnRkA6BMCVG0%3D&reserved=0

On 7/5/2017 3:11 PM, Lionel MOIZEAU wrote:
> Hi !
>
>
>
> Is there a way to get the current ditamap as an editor variable ? By 
> current map I mean the one open in the DITA Maps manager or selected 
> in the Root map dropdown menu
>
>
>
> It would be very helpful !
>
>
>
> Best regards,
>
>
>
> Lionel MOIZEAU
> Head of Technical Information Department
>
> *L-Acoustics*
> Tel : +33 1 69 63 23 99
>
> www.l-acoustics.com <http://www.l-acoustics.com/>
>
>
>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
> .oxygenxml.com%2Fmailman%2Flistinfo%2Foxygen-user&data=02%7C01%7Clione
> l.moizeau%40l-acoustics.com%7C85afcbd9747a4124349908d4c3a37f92%7C68e43
> 1e8d632483eae79f28a7b4c69e6%7C1%7C0%7C636348554383421745&sdata=Y31dPZd
> 9njXuQt8uF5HRZsB3O6L83K3wGzHvxRgiN9s%3D&reserved=0
>
_______________________________________________
oXygen-user mailing list
oXygen-user at oxygenxml.com
https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.oxygenxml.com%2Fmailman%2Flistinfo%2Foxygen-user&data=02%7C01%7Clionel.moizeau%40l-acoustics.com%7C85afcbd9747a4124349908d4c3a37f92%7C68e431e8d632483eae79f28a7b4c69e6%7C1%7C0%7C636348554383421745&sdata=Y31dPZd9njXuQt8uF5HRZsB3O6L83K3wGzHvxRgiN9s%3D&reserved=0

From adrian at sync.ro  Wed Jul  5 09:20:04 2017
From: adrian at sync.ro (Adrian Buza)
Date: Wed, 5 Jul 2017 17:20:04 +0300
Subject: [oXygen-user] [Ann] New maintenance build available for oXygen 19.0
	(2017062918)
Message-ID: <e80a4891-06f0-2f73-f44f-c44d48c7a0ab@sync.ro>

Dear oXygen users,

We announce the release of a new maintenance build (2017062918) for 
oXygen 19.0 (XML Editor, XML Developer, XML Author, XML WebHelp).
The build number can be verified in the Help -> About dialog box from 
the application (next to the version number).

You can download the new installation kits from our web site:
http://www.oxygenxml.com/download.html

Here you can find the complete list of bug-fixes:
http://www.oxygenxml.com/build_history.html#2017062918

You can follow our oXygen release/build RSS feed here:
http://www.oxygenxml.com/rssBuildID.xml

Please let us know if you encounter any problems with this new build.

Regards,
Adrian

-- 
Adrian Buza
oXygen XML Editor and Author Support

Tel: +1-650-352-1250 ext.202
Fax: +40-251-461482
support at oxygenxml.com
http://www.oxygenxml.com

From lionel.moizeau at l-acoustics.com  Tue Jul 11 04:46:23 2017
From: lionel.moizeau at l-acoustics.com (Lionel MOIZEAU)
Date: Tue, 11 Jul 2017 09:46:23 +0000
Subject: [oXygen-user] Fatal error when using refactoring action
Message-ID: <AM5PR0101MB24202F654F3AA192A9E5CC79D1AE0@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>

Hi,

When I use a refactoring action such as Insert element, I get the following error !

Description

java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace

Severity

Fatal

System ID

C:\Program Files\Oxygen XML Editor 19\refactoring\insert-element.xq<file:///C:\Program%20Files\Oxygen%20XML%20Editor%2019\refactoring\insert-element.xq>


With the following trace.

java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace
         at net.sf.saxon.query.StaticQueryContext.declareNamespace(StaticQueryContext.java:750)
         at net.sf.saxon.s9api.XQueryCompiler.declareNamespace(XQueryCompiler.java:365)
         at ro.sync.exml.xmlrefactory.c.c.d.p(Unknown Source)
         at ro.sync.exml.xmlrefactory.c.c.d.g(Unknown Source)
         at ro.sync.exml.xmlrefactory.c.d.k(Unknown Source)
         at ro.sync.exml.xmlrefactory.c.c.c(Unknown Source)
         at ro.sync.exml.xmlrefactory.c.c.b(Unknown Source)
         at ro.sync.exml.xmlrefactory.ui.i.j(Unknown Source)
         at ro.sync.exml.xmlrefactory.ui.i.k(Unknown Source)
         at ro.sync.exml.xmlrefactory.ui.i.i(Unknown Source)
         at ro.sync.exml.xmlrefactory.ui.i$_b.rhe(Unknown Source)
         at ro.sync.ui.application.nb.run(Unknown Source)


I tried to add a <test> element under the <foo> element in a file like this:
<?xml version="1.0" encoding="UTF-8"?>
<root>
    <foo/>
</root>

Can you help me?

Best regards,

Lionel MOIZEAU
Head of Technical Information Department

L-Acoustics
Tel : +33 1 69 63 23 99

www.l-acoustics.com<http://www.l-acoustics.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20170711/2200ff56/attachment.html>

From cmarchand at oxiane.com  Tue Jul 11 04:50:58 2017
From: cmarchand at oxiane.com (cmarchand at oxiane.com)
Date: Tue, 11 Jul 2017 11:50:58 +0200
Subject: [oXygen-user] Fatal error when using refactoring action
In-Reply-To: <AM5PR0101MB24202F654F3AA192A9E5CC79D1AE0@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>
References: <AM5PR0101MB24202F654F3AA192A9E5CC79D1AE0@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>
Message-ID: <886900c7150da6cc0fbbf3c74fe695c8@oxiane.com>

Could you post your insert-element.xq ?

Best,
Christophe

Le 2017-07-11 11:46, Lionel MOIZEAU a écrit :
> Hi,
> 
> When I use a refactoring action such as Insert element, I get the
> following error !
> 
> DESCRIPTION
> 
> java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace
> 
> SEVERITY
> 
> Fatal
> 
> SYSTEM ID
> 
> C:\Program Files\Oxygen XML Editor 19\refactoring\insert-element.xq
> [1]
> 
> With the following trace.
> 
> java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace
> 
>          at
> net.sf.saxon.query.StaticQueryContext.declareNamespace(StaticQueryContext.java:750)
> 
> 
>          at
> net.sf.saxon.s9api.XQueryCompiler.declareNamespace(XQueryCompiler.java:365)
> 
> 
>          at ro.sync.exml.xmlrefactory.c.c.d.p(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.c.c.d.g(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.c.d.k(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.c.c.c(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.c.c.b(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.ui.i.j(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.ui.i.k(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.ui.i.i(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.ui.i$_b.rhe(Unknown Source)
> 
>          at ro.sync.ui.application.nb.run(Unknown Source)
> 
> I tried to add a <test> element under the <foo> element in a file like
> this:
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <root>
>     <foo/>
> </root>
> 
> Can you help me?
> 
> Best regards,
> 
> Lionel MOIZEAU
> Head of Technical Information Department
> 
> L-ACOUSTICS
> Tel : +33 1 69 63 23 99
> 
> www.l-acoustics.com [2]
> 
> Links:
> ------
> [1]
> file:///C:\Program%20Files\Oxygen%20XML%20Editor%2019\refactoring\insert-element.xq
> [2] http://www.l-acoustics.com/
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user

From lionel.moizeau at l-acoustics.com  Tue Jul 11 04:52:53 2017
From: lionel.moizeau at l-acoustics.com (Lionel MOIZEAU)
Date: Tue, 11 Jul 2017 09:52:53 +0000
Subject: [oXygen-user] Fatal error when using refactoring action
In-Reply-To: <886900c7150da6cc0fbbf3c74fe695c8@oxiane.com>
References: <AM5PR0101MB24202F654F3AA192A9E5CC79D1AE0@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>
 <886900c7150da6cc0fbbf3c74fe695c8@oxiane.com>
Message-ID: <AM5PR0101MB2420F1AD82B31B5A0DB66B03D1AE0@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>

Of course, it is attached. It is the one in the Oxygen installation folder.

Lionel MOIZEAU
Head of Technical Information Department

L-Acoustics
Tel : +33 1 69 63 23 99

www.l-acoustics.com
-----Message d'origine-----
De : cmarchand at oxiane.com [mailto:cmarchand at oxiane.com] 
Envoyé : mardi 11 juillet 2017 11:51
À : Lionel MOIZEAU <lionel.moizeau at l-acoustics.com>
Cc : 'oXygen-user at oxygenxml.com' <oXygen-user at oxygenxml.com>
Objet : Re: [oXygen-user] Fatal error when using refactoring action

Could you post your insert-element.xq ?

Best,
Christophe

Le 2017-07-11 11:46, Lionel MOIZEAU a écrit :
> Hi,
> 
> When I use a refactoring action such as Insert element, I get the 
> following error !
> 
> DESCRIPTION
> 
> java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace
> 
> SEVERITY
> 
> Fatal
> 
> SYSTEM ID
> 
> C:\Program Files\Oxygen XML Editor 19\refactoring\insert-element.xq 
> [1]
> 
> With the following trace.
> 
> java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace
> 
>          at
> net.sf.saxon.query.StaticQueryContext.declareNamespace(StaticQueryCont
> ext.java:750)
> 
> 
>          at
> net.sf.saxon.s9api.XQueryCompiler.declareNamespace(XQueryCompiler.java
> :365)
> 
> 
>          at ro.sync.exml.xmlrefactory.c.c.d.p(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.c.c.d.g(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.c.d.k(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.c.c.c(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.c.c.b(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.ui.i.j(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.ui.i.k(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.ui.i.i(Unknown Source)
> 
>          at ro.sync.exml.xmlrefactory.ui.i$_b.rhe(Unknown Source)
> 
>          at ro.sync.ui.application.nb.run(Unknown Source)
> 
> I tried to add a <test> element under the <foo> element in a file like
> this:
> 
> <?xml version="1.0" encoding="UTF-8"?> <root>
>     <foo/>
> </root>
> 
> Can you help me?
> 
> Best regards,
> 
> Lionel MOIZEAU
> Head of Technical Information Department
> 
> L-ACOUSTICS
> Tel : +33 1 69 63 23 99
> 
> www.l-acoustics.com [2]
> 
> Links:
> ------
> [1]
> file:///C:\Program%20Files\Oxygen%20XML%20Editor%2019\refactoring\inse
> rt-element.xq
> [2] http://www.l-acoustics.com/
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
> .oxygenxml.com%2Fmailman%2Flistinfo%2Foxygen-user&data=02%7C01%7Clione
> l.moizeau%40l-acoustics.com%7C85963b803c9e489b3f3208d4c8425611%7C68e43
> 1e8d632483eae79f28a7b4c69e6%7C1%7C0%7C636353634615231909&sdata=fwpDsTi
> oz8WrcornBBzZ1kt8IDy4XNcZkPJgQtPyFNY%3D&reserved=0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: insert-element.xq
Type: application/octet-stream
Size: 1915 bytes
Desc: insert-element.xq
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20170711/4caddca6/attachment.obj>

From support at oxygenxml.com  Tue Jul 11 05:39:47 2017
From: support at oxygenxml.com (Oxygen XML Editor Support (Radu Coravu) )
Date: Tue, 11 Jul 2017 13:39:47 +0300
Subject: [oXygen-user] Fatal error when using refactoring action
In-Reply-To: <AM5PR0101MB2420F1AD82B31B5A0DB66B03D1AE0@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>
References: <AM5PR0101MB24202F654F3AA192A9E5CC79D1AE0@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>
 <886900c7150da6cc0fbbf3c74fe695c8@oxiane.com>
 <AM5PR0101MB2420F1AD82B31B5A0DB66B03D1AE0@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>
Message-ID: <a5723dd2-aefa-0932-d223-ed6a07b56b35@oxygenxml.com>

Hi Lionel,

In the Preferences->"XML / XSLT-FO-XQuery / XPath" page there is a 
prefix-namespace mapping list. That list of mappings is given to the 
Saxon processor when it applies the XQuery operation.

For example if in that list of mappings you bind a prefix like "stuff" 
to the XML namespace "http://www.w3.org/2000/xmlns/" Saxon will report 
this error because the XML namespace can only be bound to the "xml" 
prefix. Or if you bind a prefix called "xmlns" to any namespace...
So possibly you have something similar in your mapping list. You can try 
to use "Restore defaults" in the preferences page.

Regards,
Radu

Radu Coravu
<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 7/11/2017 12:52 PM, Lionel MOIZEAU wrote:
> Of course, it is attached. It is the one in the Oxygen installation folder.
>
> Lionel MOIZEAU
> Head of Technical Information Department
>
> L-Acoustics
> Tel : +33 1 69 63 23 99
>
> www.l-acoustics.com
> -----Message d'origine-----
> De : cmarchand at oxiane.com [mailto:cmarchand at oxiane.com]
> Envoyé : mardi 11 juillet 2017 11:51
> À : Lionel MOIZEAU <lionel.moizeau at l-acoustics.com>
> Cc : 'oXygen-user at oxygenxml.com' <oXygen-user at oxygenxml.com>
> Objet : Re: [oXygen-user] Fatal error when using refactoring action
>
> Could you post your insert-element.xq ?
>
> Best,
> Christophe
>
> Le 2017-07-11 11:46, Lionel MOIZEAU a écrit :
>> Hi,
>>
>> When I use a refactoring action such as Insert element, I get the
>> following error !
>>
>> DESCRIPTION
>>
>> java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace
>>
>> SEVERITY
>>
>> Fatal
>>
>> SYSTEM ID
>>
>> C:\Program Files\Oxygen XML Editor 19\refactoring\insert-element.xq
>> [1]
>>
>> With the following trace.
>>
>> java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace
>>
>>          at
>> net.sf.saxon.query.StaticQueryContext.declareNamespace(StaticQueryCont
>> ext.java:750)
>>
>>
>>          at
>> net.sf.saxon.s9api.XQueryCompiler.declareNamespace(XQueryCompiler.java
>> :365)
>>
>>
>>          at ro.sync.exml.xmlrefactory.c.c.d.p(Unknown Source)
>>
>>          at ro.sync.exml.xmlrefactory.c.c.d.g(Unknown Source)
>>
>>          at ro.sync.exml.xmlrefactory.c.d.k(Unknown Source)
>>
>>          at ro.sync.exml.xmlrefactory.c.c.c(Unknown Source)
>>
>>          at ro.sync.exml.xmlrefactory.c.c.b(Unknown Source)
>>
>>          at ro.sync.exml.xmlrefactory.ui.i.j(Unknown Source)
>>
>>          at ro.sync.exml.xmlrefactory.ui.i.k(Unknown Source)
>>
>>          at ro.sync.exml.xmlrefactory.ui.i.i(Unknown Source)
>>
>>          at ro.sync.exml.xmlrefactory.ui.i$_b.rhe(Unknown Source)
>>
>>          at ro.sync.ui.application.nb.run(Unknown Source)
>>
>> I tried to add a <test> element under the <foo> element in a file like
>> this:
>>
>> <?xml version="1.0" encoding="UTF-8"?> <root>
>>     <foo/>
>> </root>
>>
>> Can you help me?
>>
>> Best regards,
>>
>> Lionel MOIZEAU
>> Head of Technical Information Department
>>
>> L-ACOUSTICS
>> Tel : +33 1 69 63 23 99
>>
>> www.l-acoustics.com [2]
>>
>> Links:
>> ------
>> [1]
>> file:///C:\Program%20Files\Oxygen%20XML%20Editor%2019\refactoring\inse
>> rt-element.xq
>> [2] http://www.l-acoustics.com/
>> _______________________________________________
>> oXygen-user mailing list
>> oXygen-user at oxygenxml.com
>> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww
>> .oxygenxml.com%2Fmailman%2Flistinfo%2Foxygen-user&data=02%7C01%7Clione
>> l.moizeau%40l-acoustics.com%7C85963b803c9e489b3f3208d4c8425611%7C68e43
>> 1e8d632483eae79f28a7b4c69e6%7C1%7C0%7C636353634615231909&sdata=fwpDsTi
>> oz8WrcornBBzZ1kt8IDy4XNcZkPJgQtPyFNY%3D&reserved=0
>>
>>
>> _______________________________________________
>> oXygen-user mailing list
>> oXygen-user at oxygenxml.com
>> https://www.oxygenxml.com/mailman/listinfo/oxygen-user

From lionel.moizeau at l-acoustics.com  Wed Jul 12 03:05:50 2017
From: lionel.moizeau at l-acoustics.com (Lionel MOIZEAU)
Date: Wed, 12 Jul 2017 08:05:50 +0000
Subject: [oXygen-user] Fatal error when using refactoring action
In-Reply-To: <a5723dd2-aefa-0932-d223-ed6a07b56b35@oxygenxml.com>
References: <AM5PR0101MB24202F654F3AA192A9E5CC79D1AE0@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>
 <886900c7150da6cc0fbbf3c74fe695c8@oxiane.com>
 <AM5PR0101MB2420F1AD82B31B5A0DB66B03D1AE0@AM5PR0101MB2420.eurprd01.prod.exchangelabs.com>
 <a5723dd2-aefa-0932-d223-ed6a07b56b35@oxygenxml.com>
Message-ID: <DB6PR0101MB2422C63C0873FD37A2908FE0D1AF0@DB6PR0101MB2422.eurprd01.prod.exchangelabs.com>

Hi Radu,



It was the problem !



Xmlns was bound to « namespace.uri » …



Removing that solved the problem.



Thanks !



[cid:image001.png at 01D2FAF6.6F9C78B0]







Lionel MOIZEAU

Head of Technical Information Department



L-Acoustics

Tel : +33 1 69 63 23 99



www.l-acoustics.com

-----Message d'origine-----
De : oXygen-user [mailto:oxygen-user-bounces at oxygenxml.com] De la part de Oxygen XML Editor Support (Radu Coravu)
Envoyé : mardi 11 juillet 2017 12:40
À : oxygen-user at oxygenxml.com
Objet : Re: [oXygen-user] Fatal error when using refactoring action



Hi Lionel,



In the Preferences->"XML / XSLT-FO-XQuery / XPath" page there is a prefix-namespace mapping list. That list of mappings is given to the Saxon processor when it applies the XQuery operation.



For example if in that list of mappings you bind a prefix like "stuff"

to the XML namespace "https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2000%2Fxmlns%2F&data=02%7C01%7Clionel.moizeau%40l-acoustics.com%7Cfb8c77f02fd54f1a754b08d4c849401f%7C68e431e8d632483eae79f28a7b4c69e6%7C1%7C0%7C636353664314495987&sdata=8FBlmWWfu%2BiVi%2BgVmu441Rc4%2FC8Za%2FNElwoZK%2B5aubU%3D&reserved=0" Saxon will report this error because the XML namespace can only be bound to the "xml"

prefix. Or if you bind a prefix called "xmlns" to any namespace...

So possibly you have something similar in your mapping list. You can try to use "Restore defaults" in the preferences page.



Regards,

Radu



Radu Coravu

<oXygen/>  XML Editor, Schema Editor and XSLT Editor/Debugger

https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.oxygenxml.com&data=02%7C01%7Clionel.moizeau%40l-acoustics.com%7Cfb8c77f02fd54f1a754b08d4c849401f%7C68e431e8d632483eae79f28a7b4c69e6%7C1%7C0%7C636353664314495987&sdata=M5gl4JcKu%2BP264CkZ%2FrCPnc9GjJQG1iU5lcyVv12H9A%3D&reserved=0



On 7/11/2017 12:52 PM, Lionel MOIZEAU wrote:

> Of course, it is attached. It is the one in the Oxygen installation folder.

>

> Lionel MOIZEAU

> Head of Technical Information Department

>

> L-Acoustics

> Tel : +33 1 69 63 23 99

>

> www.l-acoustics.com<http://www.l-acoustics.com>

> -----Message d'origine-----

> De : cmarchand at oxiane.com<mailto:cmarchand at oxiane.com> [mailto:cmarchand at oxiane.com] Envoyé : mardi

> 11 juillet 2017 11:51 À : Lionel MOIZEAU

> <lionel.moizeau at l-acoustics.com<mailto:lionel.moizeau at l-acoustics.com>> Cc : 'oXygen-user at oxygenxml.com'

> <oXygen-user at oxygenxml.com<mailto:oXygen-user at oxygenxml.com>> Objet : Re: [oXygen-user] Fatal error when

> using refactoring action

>

> Could you post your insert-element.xq ?

>

> Best,

> Christophe

>

> Le 2017-07-11 11:46, Lionel MOIZEAU a écrit :

>> Hi,

>>

>> When I use a refactoring action such as Insert element, I get the

>> following error !

>>

>> DESCRIPTION

>>

>> java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace

>>

>> SEVERITY

>>

>> Fatal

>>

>> SYSTEM ID

>>

>> C:\Program Files\Oxygen XML Editor 19\refactoring\insert-element.xq

>> [1]

>>

>> With the following trace.

>>

>> java.lang.IllegalArgumentException: Misdeclaration of xmlns namespace

>>

>>          at

>> net.sf.saxon.query.StaticQueryContext.declareNamespace(StaticQueryCon

>> t

>> ext.java:750)

>>

>>

>>          at

>> net.sf.saxon.s9api.XQueryCompiler.declareNamespace(XQueryCompiler.jav

>> a

>> :365)

>>

>>

>>          at ro.sync.exml.xmlrefactory.c.c.d.p(Unknown Source)

>>

>>          at ro.sync.exml.xmlrefactory.c.c.d.g(Unknown Source)

>>

>>          at ro.sync.exml.xmlrefactory.c.d.k(Unknown Source)

>>

>>          at ro.sync.exml.xmlrefactory.c.c.c(Unknown Source)

>>

>>          at ro.sync.exml.xmlrefactory.c.c.b(Unknown Source)

>>

>>          at ro.sync.exml.xmlrefactory.ui.i.j(Unknown Source)

>>

>>          at ro.sync.exml.xmlrefactory.ui.i.k(Unknown Source)

>>

>>          at ro.sync.exml.xmlrefactory.ui.i.i(Unknown Source)

>>

>>          at ro.sync.exml.xmlrefactory.ui.i$_b.rhe(Unknown Source)

>>

>>          at ro.sync.ui.application.nb.run(Unknown Source)

>>

>> I tried to add a <test> element under the <foo> element in a file

>> like

>> this:

>>

>> <?xml version="1.0" encoding="UTF-8"?> <root>

>>     <foo/>

>> </root>

>>

>> Can you help me?

>>

>> Best regards,

>>

>> Lionel MOIZEAU

>> Head of Technical Information Department

>>

>> L-ACOUSTICS

>> Tel : +33 1 69 63 23 99

>>

>> www.l-acoustics.com<http://www.l-acoustics.com> [2]

>>

>> Links:

>> ------

>> [1]

>> file:///C:\Program%20Files\Oxygen%20XML%20Editor%2019\refactoring\ins

>> e

>> rt-element.xq

>> [2] http://www.l-acoustics.com/

>> _______________________________________________

>> oXygen-user mailing list

>> oXygen-user at oxygenxml.com<mailto:oXygen-user at oxygenxml.com>

>> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww

>> w

>> .oxygenxml.com%2Fmailman%2Flistinfo%2Foxygen-user&data=02%7C01%7Clion

>> e

>> l.moizeau%40l-acoustics.com%7C85963b803c9e489b3f3208d4c8425611%7C68e4

>> 3

>> 1e8d632483eae79f28a7b4c69e6%7C1%7C0%7C636353634615231909&sdata=fwpDsT

>> i

>> oz8WrcornBBzZ1kt8IDy4XNcZkPJgQtPyFNY%3D&reserved=0

>>

>>

>> _______________________________________________

>> oXygen-user mailing list

>> oXygen-user at oxygenxml.com<mailto:oXygen-user at oxygenxml.com>

>> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww

>> w.oxygenxml.com%2Fmailman%2Flistinfo%2Foxygen-user&data=02%7C01%7Clio

>> nel.moizeau%40l-acoustics.com%7Cfb8c77f02fd54f1a754b08d4c849401f%7C68

>> e431e8d632483eae79f28a7b4c69e6%7C1%7C0%7C636353664314495987&sdata=p59

>> 7U3Ty%2FnypcQA6MUSmkXSNbA%2Bv02YLJB%2FqiMgkNUM%3D&reserved=0

_______________________________________________

oXygen-user mailing list

oXygen-user at oxygenxml.com<mailto:oXygen-user at oxygenxml.com>

https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.oxygenxml.com%2Fmailman%2Flistinfo%2Foxygen-user&data=02%7C01%7Clionel.moizeau%40l-acoustics.com%7Cfb8c77f02fd54f1a754b08d4c849401f%7C68e431e8d632483eae79f28a7b4c69e6%7C1%7C0%7C636353664314495987&sdata=p597U3Ty%2FnypcQA6MUSmkXSNbA%2Bv02YLJB%2FqiMgkNUM%3D&reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20170712/11e0bc8e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 72282 bytes
Desc: image001.png
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20170712/11e0bc8e/attachment-0001.png>

From bernhard.kleine at gmx.net  Tue Jul 25 03:36:42 2017
From: bernhard.kleine at gmx.net (Bernhard Kleine)
Date: Tue, 25 Jul 2017 10:36:42 +0200
Subject: [oXygen-user] olink verification
Message-ID: <dd5fe9c3-d2df-cb87-e7ea-2bd9ea01e254@gmx.net>

The olinking does not work: I have a document and glossar. The links to
the glossar are via olink. At some time this has been working, but I do
not know what I have changed so that it does work any further. Linking
to the Glossartest.xml document or to the xml:id="Glossartest" did not
work either. What is wrong?

the respective error messages:

>      [xslt] : Warning! Failure reading
> file:/K:/BuchprojektSpringer/xlm/olinkdb.xml Cause:
> java.io.FileNotFoundException: K:\BuchprojektSpringer\xlm\olinkdb.xml
> (Das System kann die angegebene Datei nicht finden)
>      [xslt] Olink error: could not open target database 'olinkdb.xml'.
>      [xslt] Error: unresolved olink: targetdoc/targetptr =
> 'Glossartest/glo.Bsx'.
I have seen a faintly similar thread about olinking, but that did not
help me.

BTW Glossartest.xml and newbooktest.xml validate just fine.

Regards Bernhard

spitzhalde9
D-79853 lenzkirch
bernhard.kleine at gmx.net
www.b-kleine.com, www.urseetal.net
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Glossartest.xml
Type: text/xml
Size: 12062 bytes
Desc: not available
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20170725/8590786c/attachment.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: newbooktest.xml
Type: text/xml
Size: 1930 bytes
Desc: not available
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20170725/8590786c/attachment-0001.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20170725/8590786c/attachment.sig>

From bobs at sagehill.net  Tue Jul 25 10:10:15 2017
From: bobs at sagehill.net (Bob Stayton)
Date: Tue, 25 Jul 2017 08:10:15 -0700
Subject: [oXygen-user] olink verification
In-Reply-To: <dd5fe9c3-d2df-cb87-e7ea-2bd9ea01e254@gmx.net>
References: <dd5fe9c3-d2df-cb87-e7ea-2bd9ea01e254@gmx.net>
Message-ID: <01ed9421-dd32-fd9e-74c9-b1a737e45921@sagehill.net>

The error says it cannot open olinkdb.xml, which was not included in the 
attachments.  Is the file in that location, and can Oxygen open it 
without error?

Bob Stayton
Sagehill Enterprises
bobs at sagehill.net

On 7/25/2017 1:36 AM, Bernhard Kleine wrote:
> The olinking does not work: I have a document and glossar. The links to
> the glossar are via olink. At some time this has been working, but I do
> not know what I have changed so that it does work any further. Linking
> to the Glossartest.xml document or to the xml:id="Glossartest" did not
> work either. What is wrong?
> 
> the respective error messages:
> 
>>       [xslt] : Warning! Failure reading
>> file:/K:/BuchprojektSpringer/xlm/olinkdb.xml Cause:
>> java.io.FileNotFoundException: K:\BuchprojektSpringer\xlm\olinkdb.xml
>> (Das System kann die angegebene Datei nicht finden)
>>       [xslt] Olink error: could not open target database 'olinkdb.xml'.
>>       [xslt] Error: unresolved olink: targetdoc/targetptr =
>> 'Glossartest/glo.Bsx'.
> I have seen a faintly similar thread about olinking, but that did not
> help me.
> 
> BTW Glossartest.xml and newbooktest.xml validate just fine.
> 
> Regards Bernhard
> 
> spitzhalde9
> D-79853 lenzkirch
> bernhard.kleine at gmx.net
> www.b-kleine.com, www.urseetal.net
> -
> thunderbird mit enigmail
> GPG schlüssel: D5257409
> fingerprint:
> 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
> 
> 
> 
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
> 

From bernhard.kleine at gmx.net  Tue Jul 25 11:30:27 2017
From: bernhard.kleine at gmx.net (Bernhard Kleine)
Date: Tue, 25 Jul 2017 18:30:27 +0200
Subject: [oXygen-user] olink verification
In-Reply-To: <01ed9421-dd32-fd9e-74c9-b1a737e45921@sagehill.net>
References: <dd5fe9c3-d2df-cb87-e7ea-2bd9ea01e254@gmx.net>
 <01ed9421-dd32-fd9e-74c9-b1a737e45921@sagehill.net>
Message-ID: <1769bb02-65b1-541c-51c9-76ad4906be21@gmx.net>

The file is not in that folder.

This folder where it looks for olinkdb.xml is a private folder for my
project. I would not expect that I have to copy an obviously public file
like olinkdb.xml into each folder where I want an xml file transformed.
I can do this. I do not think that is the correct way, only the least
troublesome. BTW where is olinkdb.xml?

Bernhard Kleine


Am 25.07.2017 um 17:10 schrieb Bob Stayton:
> The error says it cannot open olinkdb.xml, which was not included in
> the attachments.  Is the file in that location, and can Oxygen open it
> without error?
>
> Bob Stayton
> Sagehill Enterprises
> bobs at sagehill.net
>
> On 7/25/2017 1:36 AM, Bernhard Kleine wrote:
>> The olinking does not work: I have a document and glossar. The links to
>> the glossar are via olink. At some time this has been working, but I do
>> not know what I have changed so that it does work any further. Linking
>> to the Glossartest.xml document or to the xml:id="Glossartest" did not
>> work either. What is wrong?
>>
>> the respective error messages:
>>
>>>       [xslt] : Warning! Failure reading
>>> file:/K:/BuchprojektSpringer/xlm/olinkdb.xml Cause:
>>> java.io.FileNotFoundException: K:\BuchprojektSpringer\xlm\olinkdb.xml
>>> (Das System kann die angegebene Datei nicht finden)
>>>       [xslt] Olink error: could not open target database 'olinkdb.xml'.
>>>       [xslt] Error: unresolved olink: targetdoc/targetptr =
>>> 'Glossartest/glo.Bsx'.
>> I have seen a faintly similar thread about olinking, but that did not
>> help me.
>>
>> BTW Glossartest.xml and newbooktest.xml validate just fine.
>>
>> Regards Bernhard
>>
>> spitzhalde9
>> D-79853 lenzkirch
>> bernhard.kleine at gmx.net
>> www.b-kleine.com, www.urseetal.net
>> -
>> thunderbird mit enigmail
>> GPG schlüssel: D5257409
>> fingerprint:
>> 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
>>
>>
>>
>> _______________________________________________
>> oXygen-user mailing list
>> oXygen-user at oxygenxml.com
>> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
>>
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user

-- 
spitzhalde9
D-79853 lenzkirch
bernhard.kleine at gmx.net
www.b-kleine.com, www.urseetal.net
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://www.oxygenxml.com/pipermail/oxygen-user/attachments/20170725/836f82cf/attachment.sig>

From bobs at sagehill.net  Wed Jul 26 00:19:58 2017
From: bobs at sagehill.net (Bob Stayton)
Date: Tue, 25 Jul 2017 22:19:58 -0700
Subject: [oXygen-user] olink verification
In-Reply-To: <1769bb02-65b1-541c-51c9-76ad4906be21@gmx.net>
References: <dd5fe9c3-d2df-cb87-e7ea-2bd9ea01e254@gmx.net>
 <01ed9421-dd32-fd9e-74c9-b1a737e45921@sagehill.net>
 <1769bb02-65b1-541c-51c9-76ad4906be21@gmx.net>
Message-ID: <91c1e46b-cf99-b30d-c45d-eb0217ca8eb9@sagehill.net>

Hi Berhhard,
The olinkdb.xml file does not come with the DocBook XSL distribution, 
but must be created specifically for your document set.  The steps for 
getting olinking working are described here:

http://www.sagehill.net/docbookxsl/Olinking.html

You said that olinking was working before, so you must have had the file 
before. The name and location of the file is specified with a stylesheet 
parameter named 'target.database.document', which must have been set in 
your earlier setup.  If the parameter is not set, the stylesheet 
defaults the filename 'olinkdb.xml' and in the same location as the 
document being processed, which is the behavior you are seeing.

If you don't have access to your old olinkdb.xml file and the parameter 
setting, you will need to recreate them.  The documentation mentioned 
above covers those details.

Bob Stayton
Sagehill Enterprises
bobs at sagehill.net

On 7/25/2017 9:30 AM, Bernhard Kleine wrote:
> The file is not in that folder.
> 
> This folder where it looks for olinkdb.xml is a private folder for my
> project. I would not expect that I have to copy an obviously public file
> like olinkdb.xml into each folder where I want an xml file transformed.
> I can do this. I do not think that is the correct way, only the least
> troublesome. BTW where is olinkdb.xml?
> 
> Bernhard Kleine
> 
> 
> Am 25.07.2017 um 17:10 schrieb Bob Stayton:
>> The error says it cannot open olinkdb.xml, which was not included in
>> the attachments.  Is the file in that location, and can Oxygen open it
>> without error?
>>
>> Bob Stayton
>> Sagehill Enterprises
>> bobs at sagehill.net
>>
>> On 7/25/2017 1:36 AM, Bernhard Kleine wrote:
>>> The olinking does not work: I have a document and glossar. The links to
>>> the glossar are via olink. At some time this has been working, but I do
>>> not know what I have changed so that it does work any further. Linking
>>> to the Glossartest.xml document or to the xml:id="Glossartest" did not
>>> work either. What is wrong?
>>>
>>> the respective error messages:
>>>
>>>>        [xslt] : Warning! Failure reading
>>>> file:/K:/BuchprojektSpringer/xlm/olinkdb.xml Cause:
>>>> java.io.FileNotFoundException: K:\BuchprojektSpringer\xlm\olinkdb.xml
>>>> (Das System kann die angegebene Datei nicht finden)
>>>>        [xslt] Olink error: could not open target database 'olinkdb.xml'.
>>>>        [xslt] Error: unresolved olink: targetdoc/targetptr =
>>>> 'Glossartest/glo.Bsx'.
>>> I have seen a faintly similar thread about olinking, but that did not
>>> help me.
>>>
>>> BTW Glossartest.xml and newbooktest.xml validate just fine.
>>>
>>> Regards Bernhard
>>>
>>> spitzhalde9
>>> D-79853 lenzkirch
>>> bernhard.kleine at gmx.net
>>> www.b-kleine.com, www.urseetal.net
>>> -
>>> thunderbird mit enigmail
>>> GPG schlüssel: D5257409
>>> fingerprint:
>>> 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
>>>
>>>
>>>
>>> _______________________________________________
>>> oXygen-user mailing list
>>> oXygen-user at oxygenxml.com
>>> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
>>>
>> _______________________________________________
>> oXygen-user mailing list
>> oXygen-user at oxygenxml.com
>> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
> 
> 
> 
> _______________________________________________
> oXygen-user mailing list
> oXygen-user at oxygenxml.com
> https://www.oxygenxml.com/mailman/listinfo/oxygen-user
>