TQt4 port koffice

This should enable compilation under both Qt3 and Qt4; fixes for any missed components will be forthcoming


git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/applications/koffice@1238284 283d02a7-25f6-0310-bc7c-ecb5cbfe19da

11 files changed, 60 insertions, 60 deletions

diff --git a/kexi/doc/common/kde-default.css b/kexi/doc/common/kde-default.css
index 032a00db5..59366d386 100644
--- a/kexi/doc/common/kde-default.css
+++ b/kexi/doc/common/kde-default.css
@@ -90,7 +90,7 @@ DIV.INFORMALEXAMPLE { border-style: dotted;
 TABLE.programlisting
 TABLE.screen { border-style: none;
                background-color: rgb(224,224,224);
-               table-layout: auto; /* 100%? */
+               table-tqlayout: auto; /* 100%? */
                color: rgb(0,0,0); /* should be inherit */
                }
 
@@ -99,7 +99,7 @@ TABLE.screen { border-style: none;
 TABLE[class~=programlisting]
 TABLE[class~=screen] { border-style: none;
                        background-color: rgb(224,224,224);
-                       table-layout: auto;
+                       table-tqlayout: auto;
                        color: inherit;
                        }
 */
diff --git a/kexi/doc/common/kde-web.css b/kexi/doc/common/kde-web.css
index e61fa32a0..dfd98e8b2 100644
--- a/kexi/doc/common/kde-web.css
+++ b/kexi/doc/common/kde-web.css
@@ -85,7 +85,7 @@ DIV.INFORMALEXAMPLE { border-style: dotted;
 TABLE.programlisting
 TABLE.screen { border-style: none;
                background-color: rgb(224,224,224);
-               table-layout: auto; /* 100%? */
+               table-tqlayout: auto; /* 100%? */
                color: rgb(0,0,0); /* should be inherit */
                }
 
@@ -94,7 +94,7 @@ TABLE.screen { border-style: none;
 TABLE[class~=programlisting]
 TABLE[class~=screen] { border-style: none;
                        background-color: rgb(224,224,224);
-                       table-layout: auto;
+                       table-tqlayout: auto;
                        color: inherit;
                        }
 */
diff --git a/kexi/doc/dev/kexi_guidelines.txt b/kexi/doc/dev/kexi_guidelines.txt
index 7c2dfaba3..ab713e34c 100644
--- a/kexi/doc/dev/kexi_guidelines.txt
+++ b/kexi/doc/dev/kexi_guidelines.txt
@@ -19,7 +19,7 @@ Focus on:
   convert to QString only on data displaying)
 
 Idea 3
-Directories layout:
+Directories tqlayout:
 dialogs/
 +-altertable/
 +-datatable/
diff --git a/kexi/doc/dev/kexi_issues.txt b/kexi/doc/dev/kexi_issues.txt
index 62292f2d7..f6a27b7ff 100644
--- a/kexi/doc/dev/kexi_issues.txt
+++ b/kexi/doc/dev/kexi_issues.txt
@@ -17,7 +17,7 @@
 	Easy example: form and report depends on table/query (or more tables and queries).
 
 	This dependency can be called inheriting when we wnat to reuse as many 
-	as possible properties of parent 'object' in child 'object'.
+	as possible properties of tqparent 'object' in child 'object'.
 
 	Examples of these properties: table colors, columns widths, etc. can be 
 	reused in forms/reports that use this its data.
diff --git a/kexi/doc/dev/kexidb_issues.txt b/kexi/doc/dev/kexidb_issues.txt
index 0dd945c69..576a64dee 100644
--- a/kexi/doc/dev/kexidb_issues.txt
+++ b/kexi/doc/dev/kexidb_issues.txt
@@ -191,7 +191,7 @@ kexi__querydata
 	q_sql varchar, //raw sql text - stored in the unchanged form entered by a user (or generated)
 	q_valid boolean, //query schema may be invalid (syntactically or logically, 
 	                //but still can be stored)
-	q_parent_tab integer REFERENCES kexi__objects(o_id) //parent table of this query
+	q_parent_tab integer REFERENCES kexi__objects(o_id) //tqparent table of this query
 
 //This table contains information about fields defined in select queries
 kexi__queryfields
diff --git a/kexi/doc/handbook/html.tmp/01_02_00_db_spreadsheet.html b/kexi/doc/handbook/html.tmp/01_02_00_db_spreadsheet.html
index e7959df74..b7b62ab97 100644
--- a/kexi/doc/handbook/html.tmp/01_02_00_db_spreadsheet.html
+++ b/kexi/doc/handbook/html.tmp/01_02_00_db_spreadsheet.html
@@ -168,7 +168,7 @@ In this case the very way the spreadsheet works is problematic. Fields for data
 <a name="reports"></a>
 <h4>Reports</h4>
 <p>
-Databases enable grouping, limiting and summing up data in a form of a <em>report</em>. Spreadsheets are usually printed in a form of small tables without fully automatic control over page divisions and the layout of fields.
+Databases enable grouping, limiting and summing up data in a form of a <em>report</em>. Spreadsheets are usually printed in a form of small tables without fully automatic control over page divisions and the tqlayout of fields.
 </p>
 
 <a name="programming"></a>
diff --git a/kexi/doc/handbook/html.tmp/02_04_00_differences.html b/kexi/doc/handbook/html.tmp/02_04_00_differences.html
index 6e0c3ccd4..19865a973 100644
--- a/kexi/doc/handbook/html.tmp/02_04_00_differences.html
+++ b/kexi/doc/handbook/html.tmp/02_04_00_differences.html
@@ -31,7 +31,7 @@ English terms are bracketed.
 <td>Validation rule</td> <td>Validation rule</td> <td><i>PICTURE/VALID</i> Clause</td> <td><i>ValChecks</i></td> 
 </tr>
 <tr>
-<td>Query (<i>Query</i>)</td> <td>Query</td> <td><i>Query, QBE, View</i></td> <td><i>Query</i></td>
+<td>Query (<i>Query</i>)</td> <td>Query</td> <td><i>Query, TQBE, View</i></td> <td><i>Query</i></td>
 </tr>
 <tr>
 <td>Form (<i>Form</i>)</td> <td>Form</td> <td>Screen</td> <td><i>Forms</i></td> 
diff --git a/kexi/doc/handbook/html.tmp/05_01_00_table_designing.html b/kexi/doc/handbook/html.tmp/05_01_00_table_designing.html
index 14c0b5113..2953a0f05 100644
--- a/kexi/doc/handbook/html.tmp/05_01_00_table_designing.html
+++ b/kexi/doc/handbook/html.tmp/05_01_00_table_designing.html
@@ -2,7 +2,7 @@
 <H2>5.1. Designing Database Tables</H2>
 
 <p>
-First, there will be two tables added to your database: <em>persons</em> and <em>phone_numbers</em>. These are exactly the same tables as described in chapter <a href="01_02_00_db_spreadsheet.html">1.2. A database and a spreadsheet</a>. A layout for <em>Persons</em> can be found in section <a href="01_02_00_db_spreadsheet.html#data_integrity">Data integrity and validity</a> in that chapter.
+First, there will be two tables added to your database: <em>persons</em> and <em>phone_numbers</em>. These are exactly the same tables as described in chapter <a href="01_02_00_db_spreadsheet.html">1.2. A database and a spreadsheet</a>. A tqlayout for <em>Persons</em> can be found in section <a href="01_02_00_db_spreadsheet.html#data_integrity">Data integrity and validity</a> in that chapter.
 </p>
 
 <p>
diff --git a/kexi/doc/handbook/html.tmp/05_04_00_form_designing.html b/kexi/doc/handbook/html.tmp/05_04_00_form_designing.html
index 9cb671d13..bca5a3874 100644
--- a/kexi/doc/handbook/html.tmp/05_04_00_form_designing.html
+++ b/kexi/doc/handbook/html.tmp/05_04_00_form_designing.html
@@ -82,7 +82,7 @@ Additional toolbars are also available:
 <a name="widgets_tab"></a>
 <H3>5.4.4. Using the &quot;Widgets&quot; tab</H3>
 <p>
-The "Widgets" tab in the Property pane provides a list of form widgets and their hierarchy. Each widget is presented within the hierarchy beside other widgets being on the same level (the same parent container). Child widgets (inside containers) are presented using indented names.
+The "Widgets" tab in the Property pane provides a list of form widgets and their hierarchy. Each widget is presented within the hierarchy beside other widgets being on the same level (the same tqparent container). Child widgets (inside containers) are presented using indented names.
 </p>
 
 <p>
@@ -196,7 +196,7 @@ It is right moment for testing your form. Click the <nobr><img src="icons/state_
 To make it easier for the form's user to identify meaning of every field widget, these should have added text labels with appropriate titles. To create text labels <nobr><img src="icons/label.png" class="icon"> <em>Label</em></nobr> widget is used.
 </p>
 <p>
-Insert three text label widgets onto the form, placing them on the left hand of the text fields (or on the right hand if your operating system uses right-to-left layout). On inserting every new label, a text cursor appears inside where you can enter desired title. Enter consecutively: <em>Name</em>, <em>Surname</em> and <em>Street</em>. Additionally, on the top of the form insert another label displaying name of the form, i.e. &quot;Persons&quot;. Enlarge this label's size and set larger font using <a href="aa_00_00_menu.html#menu_format_font">Format -&gt; Font</a> menu command.
+Insert three text label widgets onto the form, placing them on the left hand of the text fields (or on the right hand if your operating system uses right-to-left tqlayout). On inserting every new label, a text cursor appears inside where you can enter desired title. Enter consecutively: <em>Name</em>, <em>Surname</em> and <em>Street</em>. Additionally, on the top of the form insert another label displaying name of the form, i.e. &quot;Persons&quot;. Enlarge this label's size and set larger font using <a href="aa_00_00_menu.html#menu_format_font">Format -&gt; Font</a> menu command.
 </p>
 <p>
  <br><img src="img/05_04_06_form_with_labels.png">
@@ -246,7 +246,7 @@ After switching to the form's <em>data view</em> you can try whether the action
 </ul>
 
 <a name="form_layouts"></a>
-<H3>5.4.9. Widget layouts</H3>
+<H3>5.4.9. Widget tqlayouts</H3>
 <p>
 In most cases form widgets should be reasonable placed and aligned. Positioning, aligning and resizing widgets by hand is not easy and these parameters are not adjusted when the user resizes the form. In fact the situation is even worse because you cannot assume a given form requires a given space because users have different font sizes and display resolutions.
 </p>
@@ -256,50 +256,50 @@ The following example presents a form where text fields and labels were placed b
  <br>An example form with widgets that cannot not fit in the window<br><br>
 </p>
 <p>
-Using special tool called <em>widget layouts</em> can help to automatically lay out the form widgets. Widget layout is an action of grouping two or more widgets so these are well positioned and have appropriate sizes.
+Using special tool called <em>widget tqlayouts</em> can help to automatically lay out the form widgets. Widget tqlayout is an action of grouping two or more widgets so these are well positioned and have appropriate sizes.
 </p>
 <p>
-Using layout in this form improves alignment. Moreover, its space is better developed. Text fields are closer each other, spacing is constant.
+Using tqlayout in this form improves tqalignment. Moreover, its space is better developed. Text fields are closer each other, spacing is constant.
  <br>
  <br><img src="img/05_04_08_form_well_fit.png">
- <br>Example form with layout used<br><br>
+ <br>Example form with tqlayout used<br><br>
 </p>
 <p>
-There are two methods to create widget layout.
+There are two methods to create widget tqlayout.
 <ul>
-<li>Select two or more widgets that should be placed in a common layout, and select one of the layout types from the context menu item <a href="aa_00_00_menu.html#menu_format_layout">Layout Widgets</a>.</li>
-<li>Click a <a hrf="widget_containers">container widget</a> (or a form surface itself), where widgets are inserted and select one of the layout types from the context menu item <a href="aa_00_00_menu.html#menu_format_layout">Layout Widgets</a>. All widgets existing within the container or within the form, being on the same level will be put into a single common layout.</li>
+<li>Select two or more widgets that should be placed in a common tqlayout, and select one of the tqlayout types from the context menu item <a href="aa_00_00_menu.html#menu_format_layout">Layout Widgets</a>.</li>
+<li>Click a <a hrf="widget_containers">container widget</a> (or a form surface itself), where widgets are inserted and select one of the tqlayout types from the context menu item <a href="aa_00_00_menu.html#menu_format_layout">Layout Widgets</a>. All widgets existing within the container or within the form, being on the same level will be put into a single common tqlayout.</li>
 </ul>
 In each of these cases you can also use <em>Format -&gt; Layout Widgets</em> menu. 
 </p>
 <p>
  <img src="img/05_04_08_form_layout_selecting.png">
- <br>Selecting widgets that will be put into a layout<br>
+ <br>Selecting widgets that will be put into a tqlayout<br>
  <br><img src="img/05_04_08_form_layout_selected.png">
  <br>Four widgets are selected<br><br>
  <br><img src="img/05_04_08_form_layout_popup.png"><br>
- <br>Using the context menu for putting the widgets into a grid layout<br><br>
+ <br>Using the context menu for putting the widgets into a grid tqlayout<br><br>
 </p>
 <p>
-Widget layout is presented in the design view using a blue, green or red box drawn with broken line. This line is displayed only in the form's design view.
+Widget tqlayout is presented in the design view using a blue, green or red box drawn with broken line. This line is displayed only in the form's design view.
 </p>
 <p>
  <br>
  <br><img src="img/05_04_08_form_layout_grid.png">
- <br>Widgets within a grid layout<br><br>
+ <br>Widgets within a grid tqlayout<br><br>
 </p>
 <p>
-Besides the grid type, there are other widget layout types.
+Besides the grid type, there are other widget tqlayout types.
 <ul>
 <li>vertical
  <br>
  <br><img src="img/05_04_08_form_layout_vertical.png">
- <br>Vertical widget layout<br><br>
+ <br>Vertical widget tqlayout<br><br>
 </li>
 <li>horizontal
  <br>
  <br><img src="img/05_04_08_form_layout_horizontal.png">
- <br>Horizontal widget layout<br><br>
+ <br>Horizontal widget tqlayout<br><br>
 </li>
 <!-- TODO podzia³ poziomy / pionowy 
  <br><img src="img/05_04_08_form_layout_vertical_splitter.png">
@@ -311,9 +311,9 @@ Besides the grid type, there are other widget layout types.
 </p>
 
 <a name="form_springs"></a>
-<H4>Springs in widget layouts</H4>
+<H4>Springs in widget tqlayouts</H4>
 <p>
-A <em>spring</em> in widget layouts is a special, invisible element allowing to adjust widget's position and size within layouts. Such a spring stretches or squeezes a widget on the right, top, bottom or left hand, so it can have desired size and position.
+A <em>spring</em> in widget tqlayouts is a special, invisible element allowing to adjust widget's position and size within tqlayouts. Such a spring stretches or squeezes a widget on the right, top, bottom or left hand, so it can have desired size and position.
 </p>
 <p>To use a spring:
 <ol>
@@ -322,64 +322,64 @@ A <em>spring</em> in widget layouts is a special, invisible element allowing to
 </ol>
 </p>
 <p>
-For the following example, the spring has been inserted on the left hand of the text label &quot;Persons&quot;. The label is thus displayed on the right hand of the form. To make the spring work, it has been put into a common horizontal layout with the label.
+For the following example, the spring has been inserted on the left hand of the text label &quot;Persons&quot;. The label is thus displayed on the right hand of the form. To make the spring work, it has been put into a common horizontal tqlayout with the label.
  <br><img src="img/05_04_08_form_spring.png">
- <br>Horizontal layout containing a spring and a text label<br><br>
+ <br>Horizontal tqlayout containing a spring and a text label<br><br>
 </p>
 <p>
-To make springs work you need to create a global widget layout i.e. a layout for the form itself. Then, springs can use edges of the form as a boundary for expanding.
+To make springs work you need to create a global widget tqlayout i.e. a tqlayout for the form itself. Then, springs can use edges of the form as a boundary for expanding.
 </p>
 
 <a name="advanced_form_layouts"></a>
-<H4>Advanced widget layouts</H4>
+<H4>Advanced widget tqlayouts</H4>
 <p>
-Widget layouts can be combined (or nested). On the following example you can identify two nested layouts:
+Widget tqlayouts can be combined (or nested). On the following example you can identify two nested tqlayouts:
 </p>
 <p>
 <ol>
-<li>horizontal layout with a spring, aligning the &quot;Persons&quot; text label to the right</li>
-<li>grid layout grouping widgets on the whole form</li>
+<li>horizontal tqlayout with a spring, aligning the &quot;Persons&quot; text label to the right</li>
+<li>grid tqlayout grouping widgets on the whole form</li>
 </ol>
 </p>
 <p>
  <img src="img/05_04_08_form_advanced_layout.png">
- <br>Two widget layouts combined: horizontal layout inside of a grid layout<br><br>
+ <br>Two widget tqlayouts combined: horizontal tqlayout inside of a grid tqlayout<br><br>
 </p>
 <p>
-The horizontal layout is treat in the example as a single widget by the grid layout - it takes exactly one &quot;cell&quot; of the grid.
+The horizontal tqlayout is treat in the example as a single widget by the grid tqlayout - it takes exactly one &quot;cell&quot; of the grid.
 After opening a form designed this way in the data view, you can notice (by resizing the form) that:
 </p>
 <ul>
 <li>&quot;Persons&quot; text label thanks to the spring used is constantly aligned to the to the right side of the form</li>
-<li>text fields take all of the available width thanks to putting them into the grid layout</li>
+<li>text fields take all of the available width thanks to putting them into the grid tqlayout</li>
 <li>all the form's widgets are pushed to the top thanks to the spring used at the bottom of the form</li>
 </ul>
 <p>
  <img src="img/05_04_08_form_advanced_layout_view.png">
- <br>The form using the two layouts displayed in data view<br><br>
+ <br>The form using the two tqlayouts displayed in data view<br><br>
 </p>
 
-<a name="layout_breaking"></a>
-<H4>Removing widget layouts</H4>
+<a name="tqlayout_breaking"></a>
+<H4>Removing widget tqlayouts</H4>
 <p>
-To remove widget layout without removing widgets, perform one of these actions:
+To remove widget tqlayout without removing widgets, perform one of these actions:
 <ul>
-<li>click with the &RMB; on the layout's border and select <em>Break Layout</em> command from the context menu</li>
-<li>click with the &LMB; on the layout's border and select <em>Format -&gt; Break Layout</em> menu command</li>
+<li>click with the &RMB; on the tqlayout's border and select <em>Break Layout</em> command from the context menu</li>
+<li>click with the &LMB; on the tqlayout's border and select <em>Format -&gt; Break Layout</em> menu command</li>
 </ul>
 </p>
 
 <H4>Notes</H4>
-<p>Removing widget layout using the <em>Break Layout</em> command will not remove widgets contained in the layout. If you want to remove the widgets as well, just select the layout by clicking on its border and press <kbd>Delete</kbd> key or use <nobr><em>Edit -&gt <img src="icons/editdelete.png" class="icon"> Delete</em></nobr> menu command or context menu command.
+<p>Removing widget tqlayout using the <em>Break Layout</em> command will not remove widgets contained in the tqlayout. If you want to remove the widgets as well, just select the tqlayout by clicking on its border and press <kbd>Delete</kbd> key or use <nobr><em>Edit -&gt <img src="icons/editdelete.png" class="icon"> Delete</em></nobr> menu command or context menu command.
 </p>
 
-<a name="layout_size_types"></a>
-<H4>Size policies for widgets within a layout</H4>
+<a name="tqlayout_size_types"></a>
+<H4>Size policies for widgets within a tqlayout</H4>
 <p>
 Instead of setting a fixed size for your widgets, in &kexi; you can choose between various widget's <em>size policies</em>. A size policy is a flexible strategy for controlling how a widget is stretched (or shrunk) depending on other neighbouring widgets and space available within the form.
 </p>
 <p>
-After putting widgets into a <em>layout</em>, typically each widget gets a proportional (<em>Preferred</em>) size policy. These widgets will be automatically resized with preferred settings, depending on their type and size of the entire layout itself. For example, three buttons put into the horizontal layout will be resized to fit their visible text.
+After putting widgets into a <em>tqlayout</em>, typically each widget gets a proportional (<em>Preferred</em>) size policy. These widgets will be automatically resized with preferred settings, depending on their type and size of the entire tqlayout itself. For example, three buttons put into the horizontal tqlayout will be resized to fit their visible text.
 </p>
 <p>
 For each widget inserted into the form, there are settings for size policy available in the <em>Property Editor</em>. The settings are presented as a group of properties called <em>Size Policy</em>.
@@ -387,7 +387,7 @@ For each widget inserted into the form, there are settings for size policy avail
  <br><img src="img/05_04_09_size_policy_properties.png">
  <br>A group of properties for defining a widget's size policy<br><br>
 
-This group of properties contains:
+This group of properties tqcontains:
 <ul>
 <li><b>Horizontal Size Policy</b> defining horizontal size of the widget,</li>
 <li><b>Vertical Size Policy</b> defining vertical size of the widget,</li>
@@ -403,12 +403,12 @@ There are following values available on the drop down list for <em>Horizontal Si
 <li><b>Fixed</b> value means that the widget cannot be automatically resized; it should maintain the constant size defined on design time (width or height),</li>
 <li><p><b>Minimum</b> value means that the original size of the widget is set as minimal allowed, it is sufficient and there is no need for expanding the widget, but the widget will be expanded if needed. This type of policy can be used to force widget to be expanded to the whole width or height, especially if you set a <em>stretch</em> value greater than 0.
  <br><img src="img/05_04_09_size_policy_minimum.png">
- <br>Text field and two buttons within a grid layout (<em>Minimum</em> horizontal size policy is set for both buttons, so these are slightly wider than needed)<br><br>
+ <br>Text field and two buttons within a grid tqlayout (<em>Minimum</em> horizontal size policy is set for both buttons, so these are slightly wider than needed)<br><br>
 </p></li>
 <li><b>Maximum</b> value means that the original size of the widget is set as maximum allowed and can be decreased without breaking the widget's usability and readability if other widgets need more space,</li>
 <li><p><b>Preferred</b> value means that the original size of the widget is the best and preferred; the widget can be shrunk or expanded however and it will stay readable,
  <br><img src="img/05_04_09_size_policy_preferred.png">
- <br>Text field and two buttons within a grid layout (<em>Preferred</em> horizontal size policy is set for both buttons)<br><br>
+ <br>Text field and two buttons within a grid tqlayout (<em>Preferred</em> horizontal size policy is set for both buttons)<br><br>
 </p></li>
 <li><b>Expanding</b> value means that the original size of the widget is reasonable but the widget can be also shrunk; it can be expanded as well to take as much space as possible,</li>
 <li><b>Minimum Expanding</b> value means that the original size of the widget is allowed; it can be expanded to take as much space as possible,</li>
@@ -432,7 +432,7 @@ The most frequently used size policies are <em>Preferred</em>, <em>Minimum</em>
 <a name="widget_adjusting"></a>
 <H3>5.4.10. Setting widgets size and position by hand</H3>
 <p>
-In case when your form has no main layout set for auto-positioning and auto-resizing its widgets, you will probably want to align widget's position and size so the form can look cleaner and be easier to use. The &kexi; form designer simplifies this task by offering the following groups of commands:
+In case when your form has no main tqlayout set for auto-positioning and auto-resizing its widgets, you will probably want to align widget's position and size so the form can look cleaner and be easier to use. The &kexi; form designer simplifies this task by offering the following groups of commands:
 </p>
 <ul>
 <li><p>Adjusting sizes of selected widgets. The commands are available in the <em>Format -&gt; Adjust Widgets Size</em> submenu of the Menubar and in the <em>Adjust Widgets Size</em> submenu of the context menu. Toolbar's drop down button <nobr><img src="icons/aogrid.png" class="icon"> <em>Adjust Widgets Size</em></nobr> is also available.
@@ -497,7 +497,7 @@ To change tab order, either:
 <li>Click a selected widget name on the widgets list and drag it to a desired position (up or down) using the mouse.
 </li>
 <li>Click a selected widget name on the widgets list and use <em>Move Up</em> or <em>Move Down</em> buttons, to move the widgets to a desired position.</li>
-<li>Click the <em>Handle tab stops automatically</em> check box to set the automatic tab order for the form. If this option has been switched on, any changes made to the list of widgets by hand are not taken into account - &kexi; will be handling the tab orders on its own. The automatic ordering means that the top-left widget will be focused first (or the top-right if your operating system uses right-to-left layout), and the order comes from the left to right (from the right to left, appropriately) and from the top to bottom.
+<li>Click the <em>Handle tab stops automatically</em> check box to set the automatic tab order for the form. If this option has been switched on, any changes made to the list of widgets by hand are not taken into account - &kexi; will be handling the tab orders on its own. The automatic ordering means that the top-left widget will be focused first (or the top-right if your operating system uses right-to-left tqlayout), and the order comes from the left to right (from the right to left, appropriately) and from the top to bottom.
  <br><img src="img/05_04_11_auto_tab_stop.png">
  <br>Automatic tab order for a form<br><br>
 </li>
diff --git a/kexi/doc/handbook/translation-status.txt b/kexi/doc/handbook/translation-status.txt
index acc00d000..278770d82 100644
--- a/kexi/doc/handbook/translation-status.txt
+++ b/kexi/doc/handbook/translation-status.txt
@@ -68,11 +68,11 @@ DONE    5.4.6. Assigning data sources
 DONE    5.4.7. Inserting text labels
 DONE    5.4.8. Actions
 DONE      * Assigning actions to form buttons
-DONE    5.4.9. Widget layouts
-DONE      * Springs in widget layouts
-DONE      * Advanced widget layouts
-DONE      * Removing widget layouts
-DONE      * Size policies for widgets within a layout
+DONE    5.4.9. Widget tqlayouts
+DONE      * Springs in widget tqlayouts
+DONE      * Advanced widget tqlayouts
+DONE      * Removing widget tqlayouts
+DONE      * Size policies for widgets within a tqlayout
 DONE    5.4.10. Setting widgets size and position by hand
 DONE    5.4.11. Setting the tab order
 DONE  5.5. Entering data using forms
diff --git a/kexi/doc/kexidb/kexidb.doxygen b/kexi/doc/kexidb/kexidb.doxygen
index ebfa7741a..5abed26b7 100644
--- a/kexi/doc/kexidb/kexidb.doxygen
+++ b/kexi/doc/kexidb/kexidb.doxygen
@@ -72,8 +72,8 @@ EXCLUDE                = ../../kexidb/parser/sqlparser.h \
 			 ../../kexidb/parser/sqlparser.cpp \
                          ../../kexidb/parser/sqlscanner.cpp
 EXCLUDE_SYMLINKS       = NO
-EXCLUDE_PATTERNS       = *.moc.* \
-                         moc* \
+EXCLUDE_PATTERNS       = *.tqmoc.* \
+                         tqmoc* \
                          *.all_cpp.* \
                          *unload.* \
                          */test/* \