It seems that revision 1465678, that included changes in many strings, had the small side effect of joining a Base error message with the second line of a comment ("x-comment").

$ svn diff -r1465677:1465678 main/dbaccess/source/ui/querydesign/query.src 
Index: main/dbaccess/source/ui/querydesign/query.src
===================================================================
--- main/dbaccess/source/ui/querydesign/query.src	(revision 1465677)
+++ main/dbaccess/source/ui/querydesign/query.src	(revision 1465678)
@@ -367,20 +367,17 @@
 String STR_QUERY_SAVEMODIFIED
 {
 	Text [ en-US ] = "$object$ has been changed.\nDo you want to save the changes?" ;
-    Text [ x-comment ] = "For $object$, one of the values of the RSC_QUERY_OBJECT_TYPE resource will be inserted.";
 };
 
 String STR_ERROR_PARSING_STATEMENT
 {
-    Text [ en-US ] = "$object$ is based on an SQL command which could not be parsed.";
-    Text [ x-comment ] = "For $object$, one of the values of the RSC_QUERY_OBJECT_TYPE resource "
+    Text [ en-US ] = "$object$ is based on an SQL command which could not be parsed."
         "(except \"SQL command\", which doesn't make sense here) will be inserted.";
 };
 
 String STR_INFO_OPENING_IN_SQL_VIEW
 {
-    Text [ en-US ] = "$object$ will be opened in SQL view.";
-    Text [ x-comment ] = "For $object$, one of the values of the RSC_QUERY_OBJECT_TYPE resource "
+    Text [ en-US ] = "$object$ will be opened in SQL view."
         "(except \"SQL command\", which doesn't make sense here) will be inserted.";
 };

The right solution is probably to remove the extra line, i.e.,
  "(except..."
from both occurrences. This has l10n implications, so it should be done on trunk before the next string update in Pootle.