> The tree view, styled view and Attributes tool do not display this space > character. Moreover this space character does not cause a validation error > because when using the DITA DTD, the value type of the "href" attribute is "string". So this kind of mistake is quite hard to spot.
Excellent analysis! thank-you. I managed to make the necessary corrections and can already keep my colleagues quiet by delivering the update. Just for information, I had to make the correction via the attributes panel in XXE: I couldn't see the stray space in xml view. I also opened a topic file in NotePad++, and was a little surprised to see Unix(LF) ANSI in the status line. The header says <?xml version="1.0" encoding="UTF-8"?>) – is this something I need to check? Thanks again for quick and effective support! N -----Original Message----- From: Hussein Shafie [mailto:huss...@xmlmind.com] Sent: vrijdag 22 juni 2018 11:00 To: Grundtvig Nielsen Niels Cc: 'xmleditor-support@xmlmind.com' Subject: Re: [XXE] not seen this problem before! On 06/22/2018 08:55 AM, Grundtvig Nielsen Niels wrote: > Good morning! I feel I should apologise for frequently running into > problems on a Friday … it’s not the intention to put you under extra > stress before the weekend :-} > > > > I’ve attached two files, a small DITA topic and the log file from XXE. > Let me know if you need any additional information, and which address > I should use to send it. > > > > · the DITA file includes an external xref > > > > <related-links> > > <link href=" > https://source.android.com/security/verifiedboot/index.html"; > scope="external" type="html"> > > <linktext>Android documentation about secure boot > verification</linktext> > > </link> > > </related-links> > > > > · the log file shows that XXE wasn’t happy > > > > [FOP ERROR] Error while rendering page 1: java.net.URISyntaxException: > Illegal character in scheme name at index 0: > https://source.android.com/security/verifiedboot/index.html > > FOP XSL-FO processor error: > > javax.xml.transform.TransformerException: > java.lang.IllegalStateException: java.net.URISyntaxException: Illegal > character in scheme name at index 0: > https://source.android.com/security/verifiedboot/index.html > > > > This is strange, because up till now I’ve not had any problems > converting this page. Note that the same issue is (consistently, which > is a good thing) affecting other topics later in the book that use the > same construct. " https://source.android.com/security/verifiedboot/index.html"; has a space character just before the "https:". See attached screenshot of the XML source view. The tree view, styled view and Attributes tool do not display this space character. Moreover this space character does not cause a validation error because when using the DITA DTD, the value type of the "href" attribute is "string". So this kind of mistake is quite hard to spot. > > > > By the way: thanks for the improved output logs! the reference to an > output page number made it a lot easier to locate the topic which > triggered the error among the 325 topics in the map :-} > You're welcome. ********************************************************************************************* 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
