On 08/08/2012 12:14 PM, Jennita Catherine wrote: > > Consider the following table created in xml: > > <para><table> > <title>Map00 Address Mapping</title> > > <tgroup cols="3"> > <thead> > <row> > <entry align="center">Address Bits</entry> > > <entry align="center">Name</entry> > > <entry align="center">Description</entry> > </row> > </thead> > > <tbody> > <row condition="not.FLASH_BANK_LOC_29_27"> > <entry condition="FLASH_BANK_LOC_25_24">31:28</entry> > > <entry condition="FLASH_BANK_LOC_26_24">31:29</entry> > > <entry condition="FLASH_BANK_LOC_27_26">31:30</entry> > > <entry condition="FLASH_BANK_LOC_28_26">31</entry> > > <entry>port_int_add</entry> > > <entry><para>The host interface port address.</para></entry> > </row> > > <row> > <entry condition="FLASH_BANK_LOC_25_24">27:26</entry> > > <entry condition="FLASH_BANK_LOC_26_24">28:27</entry> > > <entry condition="FLASH_BANK_LOC_27_26">29:28</entry> > > <entry condition="FLASH_BANK_LOC_28_26">30:29</entry> > > <entry condition="FLASH_BANK_LOC_29_27">31:30</entry> > > <entry>CMD_MAP</entry> > > <entry>00 = Read or Write of the Page Buffer</entry> > </row> > > <row> > <entry condition="FLASH_BANK_LOC_25_24">25:24</entry> > > <entry condition="FLASH_BANK_LOC_26_24">26:24</entry> > > <entry condition="FLASH_BANK_LOC_27_26">27:26</entry> > > <entry condition="FLASH_BANK_LOC_28_26">28:26</entry> > > <entry condition="FLASH_BANK_LOC_29_27">29:27</entry> > > <entry>BANK_SEL</entry> > > <entry><para>Selects the bank for this > access.</para></entry> > </row> > > <row condition="not.INDEXED_ADDRESSING"> > <entry condition="not.FLASH_24BIT_BLK_PG_ADDR">23:16</entry> > > <entry condition="FLASH_24BIT_BLK_PG_ADDR">25:16</entry> > > <entry>Reserved</entry> > > <entry>These bits should be tied low.</entry> > </row> > > <row condition="INDEXED_ADDRESSING"> > <entry condition="not.FLASH_BANK_LOC_29_27">23:16</entry> > > <entry condition="FLASH_BANK_LOC_29_27">26:16</entry> > > <entry>Reserved</entry> > > <entry>These bits should be tied low.</entry> > </row> > > <row> > <entry>15:R</entry> > > <entry>BUFF_ADDR</entry> > > <entry><para>The host interface data bus width-aligned > buffer address on the memory device. </para></entry> > </row> > > <row> > <entry>(R-1):0</entry> > > <entry>Reserved</entry> > > <entry><para>These bits should be tied low.</para> <para>If > the controller slave interface data bus width is 16 : R > Value is 1</para> <para>If the controller slave interface > data bus width is 32 : R Value is 2</para> <para>If the > controller slave interface data bus width is 64 : R > Value is > 3</para> <para>If the controller slave interface data bus > width is 128: R Value is 4</para></entry> > </row> > </tbody> > </tgroup> > </table></para>
------------------------------------- Not directly related to your question ------------------------------------- You table is inside a para, which is allowed by the DocBook DTD, but does not make sense. Please use "Insert After" and not plain "Insert" to add tables to your document. Even simpler, please use the "Table" button found in the DocBook toolbar. Tutorials: * Basic editing http://www.xmlmind.com/xmleditor/_tutorial/basic_edit/index.html * Easier editing http://www.xmlmind.com/xmleditor/_tutorial/easy_edit/index.html ------------------------------------- > > When I try to generate a pdf, I could see many extra columns to this > table, instead of just 3 as specified. > when I reopen the xml file, I could see that the number of tgroup has > also changed automatically, i.e. 6. At XML document editing time, your table has indeed 6 columns and not 3. Therefore XMLmind XML Editor automatically changes your <tgroup cols="3"> to <tgroup cols="6">. > Why does it work this way? Is there a problem with the setup or am I > doing something wrong? > What you have done cannot work nicely with the combination XMLmind XML Editor/Apache FOP (which is used to generate the PDF) because [a] XMLmind XML Editor automatically fixes incorrect column count (6 before conditional processing) [b] Apache FOP (but not RenderX XEP, a commercial product) really requires a correct column count (3 after conditional processing). [1] Please change your table as follows: --- <tbody> <row condition="not.FLASH_BANK_LOC_29_27"> <entry> <para condition="FLASH_BANK_LOC_25_24">31:28</para> <para condition="FLASH_BANK_LOC_26_24">31:29</para> <para condition="FLASH_BANK_LOC_27_26">31:30</para> <para condition="FLASH_BANK_LOC_28_26">31</para> </entry> <entry>port_int_add</entry> <entry><para>The host interface port address.</para></entry> </row> --- Notice that by using the above trick, your table have 3 columns before and after conditional processing. (Full modified table sent as an attachment of our next email.) [2] ***FORGOT THIS IN MY FIRST ANSWER*** Please select the ``profiling XSLT stylesheets'' using "Options|Customize Configuration|Change Document Conversion Stylesheets" (requires XMLmind XML Editor v5.3). See http://www.xmlmind.com/xmleditor/_distrib/doc/help/ConversionStylesheetsEditor_reference.html [3] Please specify parameter profile.condition=XXXX to filter out some of the above paragraphs. See http://www.sagehill.net/docbookxsl/Profiling.html You can do this from within XMLmind XML Editor by: [a] Selecting "Options|Customize Configuration|Change Document Conversion Parameters". See http://www.xmlmind.com/xmleditor/_distrib/doc/help/customizeConfigurationMenu.html [b] Specifying parameter profile.condition=XXXX in the "Change Document Conversion Parameters" dialog box. See http://www.xmlmind.com/xmleditor/_distrib/doc/help/com.xmlmind.xmleditapp.kit.part.ConversionParametersEditor.html --- PS: This level of support is reserved to our customers. See http://www.xmlmind.com/xmleditor/support.html#xmleditor_support_policy Therefore, we are sorry but we won't be able to answer to any of your further questions. -- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
