Table validation problem

susannecm
Posts: 67

Table validation problem

Tue Jan 23, 2018 6:09 pm

I have a table in which the first cell of some rows spans the first three columns.
This causes validation errors in Oxygen 19, and I don't know how to fix them.

Here is an excerpt of the code:

Code: Select all

     <table colsep="1" frame="all" id="bk1004692" pgwide="1" rowsep="1">
        <tgroup cols="4">
          <colspec colname="col2" colnum="1" colwidth="1.43*"/>
          <colspec colname="col3" colnum="2" colwidth="3.78*"/>
          <colspec colname="col4" colnum="3" colwidth="1*"/>
          <colspec colname="col5" colnum="4" colwidth="8.79*"/>
          <thead>
            <row>
              <entry colname="col2">
                <p>Schlüssel</p>
              </entry>
              <entry colname="col3">
                <p>Name des Eintrags</p>
              </entry>
              <entry colname="col4">
                <p>Typ</p>
              </entry>
              <entry colname="col5">
                <p>Beschreibung</p>
              </entry>
            </row>
          </thead>
          <tbody product="SmartOffice captureRelease cubeDesigner winCube webCube">
            <row>
              <entry colname="col2" nameend="col4" namest="col2">
                <p><parmname>HKLM\Software\SER\Swa\</parmname></p>
              </entry>
              <entry colname="col5"/>
            </row>
            <row>
              <entry colname="col2"/>
              <entry colname="col3">
                <p><parmname>FormularConfigFile</parmname></p>
              </entry>
              <entry colname="col4">
                <p><keyword>STRING</keyword></p>
              </entry>
              <entry colname="col5">
                <p>Setzt einen Standardpfad für die Datei <filepath>form.ini</filepath>, der
                  ausgelesen wird, falls der Pfad nicht von außen gesetzt wird (wie z.B. bei <ph
                    conref="../../_COMMON/conref_productnames.dita#SERProducts/PD_webCube"
                  />). Setzt ein Client den Pfad über die jeweilige API, wird der Registry-Eintrag
                  ignoriert.</p>
              </entry>
            </row>
            <row>
              <entry colname="col2" nameend="col4" namest="col2">
                <p><parmname>HKCU\Software\Ser\Swa</parmname></p>
                <p><parmname>HKLM\Software\Ser\Swa</parmname></p>
              </entry>
              <entry colname="col5"/>
            </row>
            <row>
              <entry colname="col2"/>
              <entry colname="col3">
                <p><parmname>EditFilesPath</parmname></p>
              </entry>
              <entry colname="col4">
                <p><keyword>STRING</keyword></p>
              </entry>
              <entry colname="col5">
                <p>Legt das Verzeichnis fest, in dem Dokumente zur Bearbeitung in der
                  verknüpften Anwendung von <ph
                    conref="../../_COMMON/conref_productnames.dita#SERProducts/PD_winCube"/>
                  zwischengespeichert werden. Die Existenz dieses Verzeichnisses wird
                  vorausgesetzt.</p>
                <p>Als Wert kann entweder ein absoluter Pfad oder eine Umgebungsvariable im Format
                      <codeph>%<userinput>Variablenname</userinput>%</codeph> angegeben werden.</p>
              </entry>
            </row>


All entries that contain the following are marked as invalid:

Code: Select all

entry colname="col2" nameend="col4" namest="col2"


The error message is: "This cell overlaps one or more previous cells."

I don't understand where the cells are overlapping.
Can anybody help?

Kind regards

Susanne Muris
mihaela
Posts: 190

Re: Table validation problem

Wed Jan 24, 2018 3:58 pm

Hi,

The problem is that you set both colname and namest/nameend properties on these cells.
The colname property specifies the table column name in which the entry is found and by setting the namest/nameend pair you specify a range of cells on which the cell must span. So there is a conflict between the meaning of the properties that are set on the entry.

However, I agree that the error that appears in this case is not clear enough. I have added an improvement request in our internal isuue tracker for this.


Best regards,
Mihaela
Mihaela Calotescu
http://www.oxygenxml.com
susannecm
Posts: 67

Re: Table validation problem

Wed Jan 24, 2018 8:06 pm

Thanks a lot.
I removed the colname attributes from the invalid cells, and now my table is valid again.
Kind regards
Susanne Muris

Return to “DITA (Editing and Publishing DITA Content)”

Who is online

Users browsing this forum: No registered users and 0 guests