Fix incorrectly renamed strings
(cherry picked from commit 69975e8e2ce57a37a587a1e4c76bac82895b0117)

diff --git a/lib/compatibility/tdemdi/qextmdi/tdemdimainfrm.h b/lib/compatibility/tdemdi/qextmdi/tdemdimainfrm.h
index 590a153..c1a0f1d 100644
--- a/lib/compatibility/tdemdi/qextmdi/tdemdimainfrm.h
+++ b/lib/compatibility/tdemdi/qextmdi/tdemdimainfrm.h
@@ -86,7 +86,7 @@
  * \ref KMdiChildView.
  *
  * \par General usage
- * 
+ *
  * Your program mainwidget should inherit KMdiMainFrm. Then usually you'll just need
  * addWindow() and removeWindowFromMdi() to control the views.
  * \code
@@ -108,14 +108,14 @@
  *
  * KMdiMainFrm will provide the "Window" menu needed in common MDI applications. Just
  * insert it in your main menu:
- * 
+ *
  * \code
  * 		if ( !isFakingSDIApplication() )
  * 		{
  * 			menuBar()->insertItem( i18n( "&Window" ), windowMenu() );
  * 		}
  * \endcode
- * 
+ *
  * To synchronize the positions of the MDI control buttons inserted in your mainmenu:
  * \code
  * 		void B_MainModuleWidget::initMenuBar()
@@ -129,15 +129,15 @@
  *			setSysButtonsAtMenuPosition();
  *		}
  * \endcode
- * 
+ *
  * \par Dynamic mode switching
- * 
+ *
  * Dynamic switching of the MDI mode can be done via the following functions:
  * - switchToChildframeMode()
  * - switchToToplevelMode()
  * - switchToTabPageMode()
  * - switchToIDEAlMode()
- * 
+ *
  * The MDI mode can be gotten using mdiMode(). If you need to fake the look of an SDI application
  * use fakeSDIApplication() to fake it and isFakingSDIApplication() to query whether or not an SDI
  * interface is being faked.
@@ -177,7 +177,7 @@
  * The maximized-Childframe mode means that currently all views are maximized in Childframe mode's application desktop.
  *
  * \par Managing views
- * 
+ *
  * This class provides placing algorithms in Childframe mode. The following is a list of the window placement functions
  * - tilePragma() - Tile the windows and allow them to overlap
  * - tileAnodine() - Tile the windows but don't allow them to overlap
@@ -198,7 +198,7 @@
  * Note: KMdiChildViews can be added in 2 meanings: Either as a normal child view (usually containing
  * user document views) or as a tool-view (usually containing status, info or control widgets).
  * The tool-views can be added as floating dockwidgets or as stay-on-top desktop windows in tool style.
- * 
+ *
  * Also, pay attention to the fact that when you click on the close button of MDI views that their
  * close event should be redirected to closeWindow(). Otherwise the mainframe class will
  * not get noticed about the deleted view and a dangling pointer will remain in the MDI control. The
@@ -210,19 +210,19 @@
  * \code
  *		m_mapOfMdiWidgets.insert( pWnd, mh );
  *		unsigned int mdiFlags = KMdi::StandardAdd;
- *	
+ *
  * 		if ( !show )
  *			mdiFlags |= KMdi::Hide;
- *	
+ *
  * 		if ( !attach )
  *			mdiFlags |= KMdi::Detach;
- *	
+ *
  * 		if ( minimize )
  *			mdiFlags |= KMdi::Minimize;
- *	
+ *
  * 		if ( bToolWindow)
  *			mdiFlags |= KMdi::ToolWindow;
- * 
+ *
  *		if ( m_pMdiMainFrm->isFakingSDIApplication() )
  *		{
  *			if ( attach ) //fake an SDI app
@@ -241,7 +241,7 @@
 	friend class KMdiChildView;
 	friend class KMdiTaskBar;
 	Q_OBJECT
-  
+
 
 	friend class KMdiToolViewAccessor;
 	// attributes
@@ -312,17 +312,17 @@
 	 * Returns whether the application's MDI views are in maximized state or not.
 	 */
 	bool isInMaximizedChildFrmMode() { return m_bMaximizedChildFrmMode; }
-	
+
 	/**
 	 * Returns the MDI mode. This can be one of the enumerations KMdi::MdiMode.
 	 */
 	KMdi::MdiMode mdiMode() { return m_mdiMode; }
-	
+
 	/**
 	 * Returns the focused attached MDI view.
 	 */
 	KMdiChildView* activeWindow();
-	
+
 	/**
 	 * Returns a popup menu filled according to the MDI view state. You can override this
 	 * method to insert additional entries there. The popup menu is usually popuped when the user
@@ -331,29 +331,29 @@
 	 * menu called Operations.
 	 */
 	virtual TQPopupMenu * taskBarPopup( KMdiChildView *pWnd, bool bIncludeWindowPopup = false );
-	
+
 	/**
 	 * Returns a popup menu with only a title "Window". You can fill it with own operations entries
 	 * on the MDI view. This popup menu is inserted as last menu item in taskBarPopup() .
 	 */
 	virtual TQPopupMenu * windowPopup( KMdiChildView *pWnd, bool bIncludeTaskbarPopup = true );
-	
+
 	/**
 	 * Called in the constructor (forces a resize of all MDI views)
 	 */
 	virtual void applyOptions();
-	
+
 	/**
 	 * Returns the KMdiChildView belonging to the given caption string.
 	 */
 	KMdiChildView * findWindow( const TQString& caption );
-	
+
 	enum ExistsAs {DocumentView, ToolView, AnyView};
 	/**
-	 * Returns whether this MDI child view is under MDI control (using addWindow() ) or not. 
+	 * Returns whether this MDI child view is under MDI control (using addWindow() ) or not.
 	 */
 	bool windowExists( KMdiChildView *pWnd, ExistsAs as );
-	
+
 	/**
 	 * Catches certain TQt events and processes it here.
 	 * Currently, here this catches only the KMdiViewCloseEvent (a KMdi user event) which is sent
@@ -367,12 +367,12 @@
 	 * This method calls TQMainWindow::event , additionally.
 	 */
 	virtual bool event( TQEvent* e );
-	
+
 	/**
 	 * If there's a main menubar given, it will create the 4 maximize mode buttons there (undock, minimize, restore, close).
 	 */
 	virtual void setSysButtonsAtMenuPosition();
-	
+
 	/**
 	 * Returns the height of the taskbar.
 	 */
@@ -383,12 +383,12 @@
 	 * is visually moved on the desktop by this offset.
 	 */
 	virtual void setUndockPositioningOffset( TQPoint offset ) { m_undockPositioningOffset = offset; }
-	
+
 	/**
 	 * If you don't want to know about the inner structure of the KMdi system, you can use
 	 * this iterator to handle with the MDI view list in a more abstract way.
 	 * The iterator hides what special data structure is used in KMdi.
-	 */ 
+	 */
 	// FIXME And what exactly are we supposed to fix? -mattr
 	KMdiIterator<KMdiChildView*>* createIterator()
 	{
@@ -401,7 +401,7 @@
 			return new KMdiListIterator<KMdiChildView>( *m_pDocumentViews );
 		}
 	}
-	
+
 	/**
 	 * Deletes an KMdiIterator created in the KMdi library (needed for the windows dll problem).
 	 */
@@ -409,40 +409,40 @@
 	{
 		delete pIt;
 	}
-	
+
 	/**
 	 * Returns a popup menu that contains the MDI controlled view list.
 	 * Additionally, this menu provides some placing actions for these views.
 	 * Usually, you insert this popup menu in your main menubar as "Window" menu.
 	 */
 	TQPopupMenu* windowMenu() const  { return m_pWindowMenu; };
-	
+
 	/**
 	 * Sets a background color for the MDI view area widget.
 	 */
 	virtual void setBackgroundColor( const TQColor &c ) { m_pMdi->setBackgroundColor( c ); }
-	
+
 	/**
 	 * Sets a background pixmap for the MDI view area widget.
 	 */
 	virtual void setBackgroundPixmap( const TQPixmap &pm ) { m_pMdi->setBackgroundPixmap( pm ); }
-	
+
 	/**
 	 * Sets a size that is used as the default size for a newly to the MDI system added KMdiChildView .
 	 *  By default this size is 600x400. So all non-resized added MDI views appear in that size.
 	 */
 	void setDefaultChildFrmSize( const TQSize& sz ) { m_pMdi->m_defaultChildFrmSize = sz; }
-	
+
 	/**
 	 * Returns the default size for a newly added KMdiChildView. See setDefaultChildFrmSize() .
 	 */
 	TQSize defaultChildFrmSize() { return m_pMdi->m_defaultChildFrmSize; }
-	
+
 	/**
 	 * Do nothing when in Toplevel mode
 	 */
 	virtual void setMinimumSize( int minw, int minh );
-	
+
 	/**
 	 * Returns the Childframe mode height of this. Makes only sense when in Toplevel mode.
 	 */
@@ -459,7 +459,7 @@
 	 * @return the decoration of the window frame of docked (attached) MDI views
 	 */
 	static int frameDecorOfAttachedViews() { return m_frameDecoration; }
-	
 ** Diff limit reached (max: 250 lines) **