I'm afraid I am having a hard time understanding exactly what
your problem is and what you want solved.   I see your output
has the h1, but you say the output doesn't have the h1, which
confuses me.

Are you asking about why some things that look like headers
in the MS Doc don't come out as headers in the XHTML?  Or
are you asking why something that came out as headers in the
XHTML don't come out as titles in the DocBook?  Or something
else?

As for the first question, the answer is that post-processing
does many complex inferences based on the styling in the case
where someone did not use a header style in their Word doc but
just applied changes to some paragraph style, and some of those
inferences may not work in some cases.

As for the second question, the general answer is that the
XHTML to DocBook conversion function is designed to work
on the results of post-processing, and is sensitive to some of
the structuring that gets done there.

Regards

//Mary

On Tue, 08 Dec 2009 04:03:42 -0800, Byomokesh Sahoo <[email protected]> wrote:

---------- Forwarded message ----------
From: Byomokesh Sahoo <[email protected]>
Date: Fri, Dec 4, 2009 at 10:36 AM
Subject: Poor coding Default Convert
To: [email protected]


Thanks Mary...for Reply.

Please see the below XHTML file (ML Default Convert).

<div class="c5">
<p class="pa-0 ca-0">Chapter 2</p>
<p class="pa-0"><a name="_Toc160673573"><span class="ca-1">Creating
and Using DSLs</span></a></p>
<p class="pa-1"><a name="_Toc160673574"><h1
class="ca-2">Introduction</h1></a></p>
<p class="pa-2 ca-3">The purpose of this chapter is to touch on all of
the principal aspects of defining a domain-specific language (DSL)
with the Microsoft DSL Tools. We also introduce an example scenario in
which the DSL Tools are used. The later chapters will then go into
more detail on each topic.</p>
<p class="pa-2 ca-3">This chapter has three sections. First, we
introduce a development group that finds that the DSL Tools improve
its productivity, and we look at why that is so and something of the
process that the group follows to create and use the DSLs. </p>
<p class="pa-2 ca-3">Second, we look at the practical steps of
creating a DSL, touching briefly on each of the topics that will be
discussed in turn in later chapters. </p>

<!-- plz find the attached XHTML file. -->

Converted XML File
===============

<section><sectioninfo><author><othername>Stephen
Cook</othername></author><bibliomisc role="company">Addison Wesley
Longman</bibliomisc><bibliomisc role="createddate">2009/11/23 15:15:00
GMT</bibliomisc><bibliomisc role="reviseddate">2009/11/23 15:16:00
GMT</bibliomisc><bibliomisc role="printdate">2007/2/27 15:25:00
GMT</bibliomisc><bibliomisc role="generator">DMC HTML FILTER
Ver1.1.0</bibliomisc></sectioninfo><title>Domain Specific
Languages</title>
<para/>
<para>Chapter 2</para>
<para id="_Toc160673573">Creating and Using DSLs</para>
<para id="_Toc160673574"/>
<para>The purpose of this chapter is to touch on all of the principal
aspects of defining a domain-specific language (DSL) with the
Microsoft DSL Tools. We also introduce an example scenario in which
the DSL Tools are used. The later chapters will then go into more
detail on each topic.</para>
<para>This chapter has three sections. First, we introduce a
development group that finds that the DSL Tools improve its
productivity, and we look at why that is so and something of the
process that the group follows to create and use the DSLs. </para>

******************

This is DOC to HTML/XML. On this file ML Deafult convert is missing
<h1 class="ca-2"> Text. I have tried to change docbook.xqy file but
when i am add/change any new condition (XPATH) it will not convert to
XML file. I could not get it why this problem is coming..

I would like thankful to you if you give any suggestion. ...


Thanks
Byomokesh


_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general

Reply via email to