Grundtvig Nielsen Niels | 26 May 11:58 2016

spell-checking and elements

After your explanation last week, I promised I'd keep an eye on the implementation.

This snippet seems to demonstrate slightly unexpected behaviour on my system:
* a single word (for example, unconfineddomain) is flagged as a spelling error even when it's inside a
<codeph> element
* a term containing an underscore (for example, platform_app) is not flagged as a spelling error inside a 
<codeph> element

Hardly grounds for complaint :-} but I thought I'd pass it on.

Niels Grundtvig Nielsen
technical author T&P
you know what you're talking about - I can help you say it

    <dl>
      <dlentry>
        <dt>Unconfined domain</dt>

        <dd>Domain <codeph>unconfineddomain</codeph> contains all the
        potential accesses needed for system processes. System domains
        (<codeph>system_app</codeph>, <codeph>media_app</codeph>,
        <codeph>platform_app</codeph> and so on) inherit its rules.</dd>
      </dlentry>
</dl>

-----Original Message-----
From: Hussein Shafie [mailto:hussein <at> xmlmind.com]
Sent: woensdag 11 mei 2016 8:53
To: Grundtvig Nielsen Niels
Cc: 'xmleditor-support <at> xmlmind.com'
(Continue reading)

Grundtvig Nielsen Niels | 25 May 12:40 2016

document conversion parameters

Given the number of times I've asked you questions about this, I'm now fairly confident at being able to do what I need to; I've even started using xsl.fo cover pages … and saving different sets of conversion parameters for easy re-use.

 

I was wondering, though, if there's a mechanism for associating a saved set of parameters with a .ditamap file permanently/as default. I don't mind selecting/loading a specific set before converting a particular map, but it's the sort of extra step I'm quite capable of forgetting ;-}

 

 

Niels Grundtvig Nielsen

technical author T&P

you know what you’re talking about – I can help you say it

 


*********************************************************************************************
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 <at> xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
Grundtvig Nielsen Niels | 23 May 09:12 2016

DITA reference topic

Good morning!

 

not sure what’s happening here … someone sent me a sample reference topic, which I’ve pasted in below.

 

It opens and validates in XML Mind, but there are problems with the output:

if I try output to XHTML (one page) the result adds an empty column at the right of the table

if I try output to .pdf, the conversion fails with the message The column-number or number of cells in the row overflows the number of fo:table-columns specified for the table.

 

Advice and tips welcome, as always.

 

Niels Grundtvig Nielsen

technical author T&P

you know what you’re talking about – I can help you say it

 

 

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

<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"

"reference.dtd">

<reference id="refTest">

  <title>xSecurity profile version</title>

 

  <refbody>

    <properties id="properties_fs1_fcg_yv">

      <property>

        <proptype>element</proptype>

 

        <propvalue>description</propvalue>

      </property>

 

      <property>

        <proptype>type</proptype>

 

        <propvalue>string</propvalue>

      </property>

 

      <property>

        <proptype>constraint</proptype>

 

        <propvalue>max 255 characters</propvalue>

      </property>

 

      <property>

        <proptype>presence</proptype>

 

        <propvalue>optional</propvalue>

      </property>

 

      <property>

        <proptype>notes</proptype>

 

        <propvalue>With this field the Security Agent has the possibility to

        insert a longer name or explanation of the Security

        Profile</propvalue>

      </property>

    </properties>

 

    <properties id="properties_pwk_tcg_yv">

      <property>

        <proptype>element</proptype>

 

        <propvalue>dateCreated</propvalue>

      </property>

 

      <property>

        <proptype>type</proptype>

 

        <propvalue>datetime string</propvalue>

      </property>

 

      <property>

        <proptype>constraint</proptype>

 

        <propvalue>YYYY-MM-DDTHH:mm:ss</propvalue>

      </property>

 

      <property>

        <proptype>presence</proptype>

 

        <propvalue>required</propvalue>

      </property>

 

      <property>

        <proptype>notes</proptype>

 

        <propvalue>Date and timestamp when the Security Profile was created

        for the first time</propvalue>

      </property>

    </properties>

  </refbody>

</reference>


*********************************************************************************************
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 <at> xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
Hussein Shafie | 20 May 09:54 2016

Re: Validation error when a DocBook 5 "info" element is included from a separate file

Vera S. wrote:
>
> I have found the following problem:
>
> 1.*Book* with element *info* are considered _valid _when the *info*
> element is in the same XML file with the *book* element.
>
> 2.*Book* with element *info* are considered _invalid_ when the *info*
> element is in an included XML file.
>
> I have attached sample DocBook 5 files for the OK and KO case.
>
> Could you please take a look and check whether this is a bug in XMLmind
> XML Editor?

No, this is not a bug. The error reported by XMLmind XML Editor is an 
actual error.

Your KO/info.xml starts with:

---
<info>
    <legalnotice>
    ...
---

The DocBook 5 namespace is missing. Hence your "info" element is not the 
"info" element of DocBook 5.

If you modify KO/info.xml as follows, everything will work fine in 
KO/docbook5-bookSample.xml.

---
<info version="5.0" xmlns="http://docbook.org/ns/docbook">
    <legalnotice>
    ...
---

Note that, according to the DocBook 5 grammar, element "info" may not be 
the root element of a standalone document. That's why 1) you cannot use 
XMLmind XML Editor to create a file like info.xml; 2) if you use XMLmind 
XML Editor to edit a file like info.xml, it will report an error.

However, this should not prevent you from putting all your legal notices 
in a separate file and then including this separate file.

Note that a facility like the Include tool is especially useful for 
putting all kinds of reusable snippets in a single, valid, documented, 
boilerplate file.

See tutorial (with screencast) "Inserting boilerplate content":

http://www.xmlmind.com/xmleditor/_tutorial/insert_boilerplate/index.html

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

Grundtvig Nielsen Niels | 18 May 08:43 2016

profiles and 'paper-based' output

Good morning! I’ve checked your earlier e-mails where you helpfully explained how to use a profile, and set things up as shown in the screenshot. (the text in green is a <dlentry> with status set to ‘new’)

 

I must have missed something, though, because while the conditions are flagged in the editor they are not showing up when I generate a .pdf from the topic.

 

Tips and instructions welcome, as always.

 

 

Niels Grundtvig Nielsen

technical author T&P

you know what you’re talking about – I can help you say it

 

 


*********************************************************************************************
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 <at> xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
Hussein Shafie | 17 May 10:42 2016

Re: Use of an extended DocBook schema

Tekampe, Nils wrote:
> I have a DocBook schema that has been extended by a few elements and that I would like to use with XMLMind.
However, when I open an XML that is created after that schema, XMLMind does not recognize that this is a
DocBook schema and does not enter the editor mode.
>
> Is there any way to make XMLMind learn that this schema is also a DocBook schema?

Sure, but you'll have to write a custom configuration (of course, 
including the stock DocBook configuration) for that.

This custom configuration is just a few lines long and takes 5 minutes 
to create. However in order to do that, you'll have to read a lot of 
long and boring documentation:

XMLmind XML Editor - Configuration and Deployment
http://www.xmlmind.com/xmleditor/_distrib/doc/configure/index.html

That's why if you send me privately (hussein <at> xmlmind.com) a couple of 
samples documents of your along with your custom schema, I'll do it for you.

You'll even get your custom configuration packaged as an easy to install 
add-on.

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

Grundtvig Nielsen Niels | 10 May 16:17 2016

small and unimportant question :-}

When I need feedback from colleagues, it’s often quicker to take a screenshot of a topic in an XXE window than it is to copy the content into an e-mail and painstakingly reformat it. Everyone’s very happy with that way of exchanging information … but given the number of strange terms (including <filepath>, <cmdname> and <codeblock> elements) the content does have an embarrassingly high number of apparent spelling errors.

 

Question: is it possible to turn off highlighting of spelling errors just long enough to take the screenshot?

 

Niels Grundtvig Nielsen

technical author T&P

you know what you’re talking about – I can help you say it

 


*********************************************************************************************
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 <at> xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
Hussein Shafie | 5 May 09:24 2016

Re: Question about parsing markers

Erik B. wrote:
> OK, I'll look into it and try that. If you have any specific examples or tutorials, don't hesitate to send
them though.

I would start by reading this chapter:

5. Customizing an existing configuration

http://www.xmlmind.com/xmleditor/_distrib/doc/configure/customizing.html

and even more carefully this section:

10. Customizing the XSLT style sheets used in the Convert Document submenu

http://www.xmlmind.com/xmleditor/_distrib/doc/configure/customize_xslt.html

However what you want to achieve seems quite simple, so if you send me 2 
or 3 sample documents containing the "[version]" placeholder (for test 
purposes; just to be sure I've really understood the problem), I'll 
*try* to send you back a customization of the stock (DocBook? DocBook 
v5+?) configuration allowing to do what you want.

>
>> xmleditor-support <at> xmlmind.com wrote:
>>
>> Erik B. wrote:
>>>
>>> I've attached an image to explain, I hope that's clearer.
>>
>> Yes. What follows should work and is not difficult to implement:
>>
>> 1) Customize the stylesheet, that is, make your customized stylesheet replace the "[version]"
placeholder by the value of the version parameter.
>>
>> 2) Pass the version number as a custom XSLT stylesheet parameter.

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

Hussein Shafie | 4 May 16:22 2016

Re: Question about parsing markers

Erik B. wrote:
>
> Is it possible to set a marker in a document, e.g.*[version]* and have
> it parsed during conversion by passing a parameter like --version=1.2.3?

Sorry but I'm not sure to understand this.

A conversion is basically running an XSLT stylesheet on the document 
being edited. A customized XSLT stylesheet can indeed find and process 
"markers" found in the document being converted.

It's quite easy to pass any parameter you want to the XSLT stylesheets 
used by XMLmind XML Editor. See 
http://www.xmlmind.com/xmleditor/_distrib/doc/help/conversion_parameters_editor.html

It's also easy to customize the XSLT stylesheets used by XMLmind XML 
Editor. See "Customize Document Conversion Stylesheets" in 
http://www.xmlmind.com/xmleditor/_distrib/doc/help/customizeConfigurationMenu.html

> Or alternatively to use something like <version>...</version> and have
> it replaced with <version>1.2.3</version> during parsing.
>

XMLmind XML Editor allows you to do anything you want in a document 
being created, opened, checked for validity, saved, saved as, etc. 
However you have to program in Java for that.

You need to develop a custom OpenedDocumentHook. A custom 
OpenedDocumentHook is typically declared in a "customize.xxe_gui" XML file.

References:

* 
http://www.xmlmind.com/xmleditor/_distrib/doc/api/com/xmlmind/xmleditapp/kit/OpenedDocumentHook.html

* http://www.xmlmind.com/xmleditor/_distrib/doc/gui/openedDocumentHook.html

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

Hussein Shafie | 4 May 08:37 2016

Re: HTML5 permits content="text/html; charset=UTF-8" in XML

Leif S. wrote:
>
> Currently, XML Editor issues a warning whenever an (X)HTML5 document
> contains this meta element:
>
> |<meta Content-Type="http-equiv" content="text/html; charset=UTF-8" /> |
>
> However, that variation of the Content-Type meta element (that is: a
> meta element of Content-Type="http-equiv" *and* content="text/html;
> charset=UTF-8") *is* permitted, in both HTML and XHTML - *provided* that
> the encoding is "UTF-8":
>
> https://www.w3.org/TR/html51/single-page.html#statedef-http-equiv-content-type
>
> «The encoding declaration state may be used in HTML documents and in XML
> Documents. If the encoding declaration state is used in XML Documents,
> the name of the character encoding must be an ASCII case-insensitive
> match for the string "UTF-8" (and the document is therefore forced to
> use UTF-8 as its encoding).»
>
> Thus, the rules for when
>
> |<meta Content-Type="http-equiv" content="text/html; charset=UTF-8" /> |
>
> and
>
> |<meta charset="UTF-8" /> |
>
> can be used in XML documents, are identical: They can be used when the
> encoding of the document is UTF-8.

XMLmind XML Editor does not report any error or warning for an (X)HTML5 
document containing either:

<meta http-equiv="content-type" content="text/html; charset=UTF-8" />

or:

<meta charset="UTF-8" />

My guess is that you simply made a typo:

Content-Type="http-equiv"

should read:

http-equiv="Content-Type"

However, it's true that XMLmind XML Editor only accepts:

http-equiv="content-type" LOWER CASE

and not:

http-equiv="Content-Type" MIXED CASE

This is a limitation because the values allowed for attribute http-equiv 
should not be case-sensitive.

--
XMLmind XML Editor Support List
xmleditor-support <at> xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
Hussein Shafie | 11 Apr 09:51 2016

Release of XMLmind XML Editor v6.7

XMLmind XML Editor Evaluation Edition v6.7 can be downloaded from
http://www.xmlmind.com/xmleditor/download.shtml

Professional Edition users, please upgrade using this form:
http://www.xmlmind.com/store/download.php

(The above form is usually accessed through
http://www.xmlmind.com/xmleditor/upgrade.html.)

    _____________________________________________

XMLmind XML Editor v6.7 (April 11, 2016)
----------------------------------------

Highlights:

* Partial DITA 1.3 support. (Full DITA 1.3[1] support is
   planned for year 2016.) More information in
   "XMLmind XML Editor - DITA Support"[2].

* Enhanced "DocBook v5.1 configuration (Release Candidate)"
   add-on.

* Improved XInclude 1.1 support in DocBook v5 and v5.1
   configurations.

* Drag&drop of document tabs and tool tabs.

    _____________________________________________

References:

[1] Darwin Information Typing Architecture (DITA) Version 1.3 Part 2: 
Technical Content Edition - OASIS Standard
http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-part2-tech-content.html

[2] XMLmind XML Editor - DITA Support
http://www.xmlmind.com/xmleditor/_distrib/doc/dita/about.html

More information in
http://www.xmlmind.com/xmleditor/changes.html

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


Gmane