Kazuko O. wrote:
I have a question about XXE 9.0 and markdown files.
My company edits the DITA source files with using XXE, and publishes them into
PDF with DITA-OT (+AH Formatter).
Please note that XMLmind DITA Converter (ditac for short;
https://www.xmlmind.com/ditac/), our clean room implementation of a DITA
processor, supports the Antenna House Formatter
(https://www.antennahouse.com/formatter/) too.
Example:
---
ditac -ahf "C:\AHFv6\AHFCmd.exe" out/manual.pdf manual.ditamap
---
See
https://www.xmlmind.com/ditac/_distrib/doc/manual/commandLine.html#commandLine__option-ahf
I know that the XXE V9.0 enhanced the following.
* When the "Edit source" add-on is installed (which is the case by
default), XXE may be used to edit plain text files. XXE now understand
the GNU Emacs file variable[1] called "coding". In absence of a BOM,
variable coding may be used to specify the encoding of a text file.
Markdown example:
---
<!-- -*- coding: iso-8859-1 -*- -->
The markdown files that do not have BOM and that contain Japanese characters
are displayed without incorrect characters in the XXE now.
I added the line "<!-- -*- coding: UTF-8 -*- -->" in the beginning of the text
in each md file.
But, the publication by DITA-OT fails because of the line "<!-- -*- coding: UTF-8 -*-
-->"
in each md file. Without "<!-- -*- coding: UTF-8 -*- -->," the publication will
be successful.
Is this a known restriction?
Please note that here at XMLmind Software, we don't use the DITA-OT at
all. Thus we don't test anything we do against the DITA-OT.
I would say that you should report this issue to DITA-OT as a bug
because John Gruber, the inventor of Markdown, writes:
---
For any markup that is not covered by Markdown’s syntax, you simply use
HTML itself. There’s no need to preface it or delimit it to indicate
that you’re switching from Markdown to HTML; you just use the tags.
---
https://daringfireball.net/projects/markdown/syntax#html
--> Anyway, please try to find a Markdown syntax which is ignored by the
DITA-OT implementation and which could contain this string:
-*- coding: UTF-8 -*-
then add it as the first line of your ".md" files. Any of the few first
lines, not necessarily the very first one, should be OK too.
Our implementation does not care about the opening "<!--" and closing
"-->". It just searches for
-*- coding: ENCODING -*-
anywhere at the beginning of the Markdown file:
Some (https://stackoverflow.com/questions/4823468/comments-in-markdown)
say that the following trick:
---
[comment]: # (-*- coding: UTF-8 -*-)
---
is OK with works most Markdown implementations. I've tested this trick
and it indeed works fine with all XMLmind products. See attached sample.
Please keep us informed about the solution you have found.
Markdown extensions
===================
[comment]: # (-*- coding: iso-8859-15 -*-)
Abbreviations
-------------
Converts plain text abbreviations (e.g. IBM) to `<abbr>` elements.
Oh le bel été que voilà ma bonne dame! Un été à 1000000¤! Ça c'est bien vrai!
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
https://www.xmlmind.com/mailman/listinfo/xmleditor-support
