[HS] make sure that "Map|Check map" reports no fatal errors ...

[NGN] Diligently used Map > Check map already this morning, as part of 
upgrading a document from conrefs to keywords; I try to learn.


[NGN] I'm surprised to learn that I must have tried to set up a conref by hand!

[HS] There is misunderstanding here. I never suggested that you should try to 
set up a conref by hand. On the contrary.

[NGN] Double misunderstanding :-} Neither you nor I would suggest trying to set 
up a conref by hand ... it's just that the error you found suggests I did :-}

N

-----Original Message-----
From: Hussein Shafie [mailto:huss...@xmlmind.com]
Sent: woensdag 14 maart 2018 16:56
To: Grundtvig Nielsen Niels
Cc: 'xmleditor-support@xmlmind.com'
Subject: Re: [XXE] something odd happening with WebHelp

On 03/14/2018 02:01 PM, Grundtvig Nielsen Niels wrote:
> I'm surprised to learn that I must have tried to set up a conref by hand!
>

There is misunderstanding here. I never suggested that you should try to set up 
a conref by hand. On the contrary.

I found this in your task_sitesFuzzy.dita:

<ul conref="site_overview.dita#xnth_94ve27/fuzzySearch"/>

which could NOT have been created using XXE, because XXE creates this:

---
<ul conref="site_overview.dita#xnth_94ve27/fuzzySearch">
   <li/>
</ul>
---





> As for the capitalisation, it seems it is possible for user to be misled ... 
> when I opened one of the problem files to check, the capitalisation in the 
> XXE title bar did not match the capitalisation on the tab. I dare say we can 
> point the finger at Windows here. More worryingly, I was able to see a title 
> displayed in the bookmap even when there was a capitalisation mismatch 
> between the filename in the href and the filename in Windows Explorer ... as 
> you say, letting XXE do (even more of) the work will help.
>


The fact that character capitalization is meaningful in URIs and not meaningful 
in Windows filenames is a real problem. For now, we haven't found a way to 
workaround this problem. Sorry for that.

(Of course, on my Linux box where character capitalization is meaningful in 
filenames, I don't have this problem.)

*********************************************************************
This being said, I dare to heavily insist: in the future, please make sure that 
"Map|Check map" reports no fatal errors before sending support requests related 
to the conversion of DITA documents to xmleditor-support@xmlmind.com
*********************************************************************




---
PS: Even after fixing all the errors in your xntHelps.ditamap, including 
character capitalization ones, I still get:

---
[1] :::
"file:/home/hussein/tmp/xntHelps/concept_rarelyConnected.dita#xnth_90je48",
href points outside processed topics
[2] Document "/home/hussein/tmp/xntHelps/xntHelps.ditamap" has 1 errors or 
warnings. None of them are fatal errors.
---

This one comes from the fact that topic concept_rarelyConnected.dita exists but 
is referenced in map xntHelps.ditamap only in the last reltable and never in 
the topicref hierarchy.




*********************************************************************************************
Worldline SA/NV - Chaussee de Haecht 1442 Haachtsesteenweg
- 1130 Brussels - Belgium
RPM-RPR Bruxelles-Brussel - TVA-BTW BE 0418.547.872
Bankrekening-Compte Bancaire-Bank Account 310-0269424-44
BIC BBRUBEBB - IBAN BE55 3100 2694 2444

"The information contained in this e-mail and any attachment there to be 
confidential and may contain information which is protected by intellectual 
property rights.
This information is intended for the exclusive use of the recipient(s) named 
above.
This e-mail does not constitute any binding relationship or offer toward any of 
the addressees.
If you are not one of the addressees , one of their employees or a proxy holder 
entitled to hand over this message to the addressee(s), any use of the 
information contained herein (e.g. reproduction, divulgation, communication or 
distribution,...) is prohibited.
If you have received this message in error, please notify the sender and 
destroy it immediately after.
The integrity and security of this message cannot be guaranteed and it may be 
subject to data corruption, interception and unauthorized amendment, for which 
we accept no liability."

--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Reply via email to