From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Davis Subject: Still trying to get DocBook output Date: Mon, 07 Nov 2016 16:21:58 -0500 Message-ID: <1478553718.3411834.780382289.6049CAE6@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="_----------=_147855371834118344"; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53429) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c3rMm-0005M9-HW for emacs-orgmode@gnu.org; Mon, 07 Nov 2016 16:22:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c3rMi-0002ig-Cg for emacs-orgmode@gnu.org; Mon, 07 Nov 2016 16:22:08 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:57243) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c3rMi-0002iN-8V for emacs-orgmode@gnu.org; Mon, 07 Nov 2016 16:22:04 -0500 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org This is a multi-part message in MIME format. --_----------=_147855371834118344 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" Since DocBook XML is not supported by the new org-mode export architecture, I tried following the recommendation here: http://orgmode.org/worg/exporters/ox-overview.html exporting to texi and then using makeinfo to convert to DocBook XML. This worked reasonably smoothly, though it still required some hand editing. In particular, there are a number of constructs that seem to be completely different in org->makeinfo generated XML vs. the DocBook XML my team is using. I'm not sure this is exhaustive, but here's what I've found so far: Effect MakeInfo XML output Desired DocBook XML id strings Mixed_Case_Section_Title XXXX_lower_case_section_title chapter, sect labels label="n.n" *n/a* Code example ... ... Graphic Definition list ... ... ... ... ... ... I hope this HTML table comes through. I'm assuming I could create a fairly simple XSLT script to convert the makeinfo output to the desired XML, but I'm wondering if there's a way to pass a stylefile, DTD or schema to makeinfo to do this automatically. Anyone know? I looked at the help for makeinfo, but didn't see anything I recognized as a way to do this. Thanks, -pd -- Peter Davis www.techcurmudgeon.com --_----------=_147855371834118344 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"

Since DocBook XML is not supported = by the new org-mode export architecture, I tried following the recommendati= on here:

http://orgmode.org/worg/exporters/ox-over= view.html

exporting to texi and then using makeinfo= to convert to DocBook XML. This worked reasonably smoothly, though it stil= l required some hand editing. In particular, there are a number of construc= ts that seem to be completely different in org->makeinfo generated XML v= s. the DocBook XML my team is using. I'm not sure this is exhaustive, but h= ere's what I've found so far:

= Effect	MakeInfo XML output	Desired DocBook XML <= /th>
id strings	Mix= ed_Case_Section_Title	XXXX_lower_case_s= ection_title
chapter, sect labels	<= span class=3D"font" style=3D"font-family:menlo,consolas,"courier new&q= uot;,monospace">label=3D"n.n"	n/a
Code example	<screen>...</scree= n>	<programlisting>...</pro= gramlisting>
Graphic	<informalfigure> =E2=80=83<mediaobject> =E2=80=83= =E2=80=83<imageobject> =E2=80=83=E2=80=83=E2=80=83<imagedata fi= leref=3D"..." format=3D"..."></imagedata> =E2=80=83=E2=80=83<= ;/imageobject> =E2=80=83</mediaobject> </informalfigure&g= t;	<para><graphic fileref=3D"..." = format=3D"..."/><para>
Definition list=	<variablelist> =E2=80=83<varliste= ntry> =E2=80=83=E2=80=83<term>...</term> =E2=80=83=E2= =80=83<listitem> =E2=80=83=E2=80=83=E2=80=83<para>...</pa= ra> =E2=80=83=E2=80=83</listitem> =E2=80=83</varlistentry= > =E2=80=83... </variablelist>	<glosslist> =E2=80=83<glossentry> =E2=80=83=E2=80=83&l= t;glossterm>...</glossterm> =E2=80=83=E2=80=83<glossdef>&= lt;para>...</para></glossdef> =E2=80=83</glossentry>= ; =E2=80=83... </glosslist>

I hope this HTML table comes through.
=

I'm assuming I could create a fairly simp= le XSLT script to convert the makeinfo output to the desired XML, but I'm w= ondering if there's a way to pass a stylefile, DTD or schema to makeinfo to= do this automatically. Anyone know?

I looked at the help for makeinfo, but di= dn't see anything I recognized as a way to do this.

Thanks,

-pd

Peter Davis

www.techcurmudgeon.com

--_----------=_147855371834118344--