* lang/*:

- New variables for SQL Parser error messages

lang/afrikaans-iso-8859-1.inc.php3

@@ -422,4 +422,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/afrikaans-utf-8.inc.php3

@@ -423,4 +423,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/albanian-iso-8859-1.inc.php3

@@ -421,4 +421,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/albanian-utf-8.inc.php3

@@ -422,4 +422,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/arabic-utf-8.inc.php3

@@ -422,4 +422,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/arabic-windows-1256.inc.php3

@@ -421,4 +421,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/brazilian_portuguese-iso-8859-1.inc.php3

@@ -419,4 +419,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/brazilian_portuguese-utf-8.inc.php3

@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/bulgarian-koi8-r.inc.php3

@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/bulgarian-utf-8.inc.php3

@@ -421,4 +421,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/bulgarian-windows-1251.inc.php3

@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/catalan-iso-8859-1.inc.php3

@@ -415,4 +415,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/catalan-utf-8.inc.php3

@@ -416,4 +416,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/chinese_big5-utf-8.inc.php3

@@ -81,7 +81,6 @@ $strCheckDbPriv = '檢查資料庫權限';
 $strCheckTable = '檢查資料表';
 $strChoosePage = '請選擇需要編輯的頁碼';
 $strColComFeat = '顯示欄位註解';
-$strCreatePdfFeat = '建立 PDF';
 $strColumn = '欄位';
 $strColumnNames = '欄位名稱';
 $strComments = '註解';
@@ -98,6 +97,7 @@ $strCreateIndexTopic = '新增一組索引';
 $strCreateNewDatabase = '建立新資料庫';
 $strCreateNewTable = '建立新資料表於資料庫 %s';
 $strCreatePage = '建立新一頁';
+$strCreatePdfFeat = '建立 PDF';
 $strCriteria = '篩選';
 
 $strData = '資料';
@@ -422,4 +422,13 @@ $strZip = '"zipped"';
 
 // To translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/chinese_big5.inc.php3

@@ -421,4 +421,13 @@ $strZip = '"zipped"';
 
 // To translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/chinese_gb-utf-8.inc.php3

@@ -419,4 +419,13 @@ $strZip = '"zipped"';
 
 // To translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/chinese_gb.inc.php3

@@ -418,4 +418,13 @@ $strZip = '"zipped"';
 
 // To translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/croatian-iso-8859-2.inc.php3

@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/croatian-utf-8.inc.php3

@@ -421,4 +421,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/croatian-windows-1250.inc.php3

@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/czech-iso-8859-2.inc.php3

@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/czech-utf-8.inc.php3

@@ -421,4 +421,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/czech-windows-1250.inc.php3

@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/danish-iso-8859-1.inc.php3

@@ -414,4 +414,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/danish-utf-8.inc.php3

@@ -415,4 +415,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/dutch-iso-8859-1.inc.php3

@@ -416,4 +416,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/dutch-utf-8.inc.php3

@@ -417,4 +417,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/english-iso-8859-1.inc.php3

@@ -51,6 +51,8 @@ $strAtEndOfTable = 'At End of Table';
 $strAttr = 'Attributes';
 
 $strBack = 'Back';
+$strBeginCut = 'BEGIN CUT'; 
+$strBeginRaw = 'BEGIN RAW';
 $strBinary = 'Binary';
 $strBinaryDoNotEdit = 'Binary - do not edit';
 $strBookmarkDeleted = 'The bookmark has been deleted.';
@@ -132,6 +134,8 @@ $strEmpty = 'Empty';
 $strEmptyResultSet = 'MySQL returned an empty result set (i.e. zero rows).';
 $strEnabled = 'Enabled';
 $strEnd = 'End';
+$strEndCut = 'END CUT'; 
+$strEndRaw = 'END RAW';
 $strEnglishPrivileges = ' Note: MySQL privilege names are expressed in English ';
 $strError = 'Error';
 $strExport = 'Export';
@@ -355,8 +359,13 @@ $strSort = 'Sort';
 $strSpaceUsage = 'Space usage';
 $strSplitWordsWithSpace = 'Words are separated by a space character (" ").';
 $strSQL = 'SQL';
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';
 $strSQLQuery = 'SQL-query';
 $strSQLResult = 'SQL result';
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  
+$strSQPBugUnclosedQuote = 'Unclosed quote';
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';
 $strStatement = 'Statements';
 $strStrucCSV = 'CSV data';
 $strStrucData = 'Structure and data';

lang/english-utf-8.inc.php3

@@ -52,6 +52,8 @@ $strAtEndOfTable = 'At End of Table';
 $strAttr = 'Attributes';
 
 $strBack = 'Back';
+$strBeginCut = 'BEGIN CUT'; 
+$strBeginRaw = 'BEGIN RAW';
 $strBinary = 'Binary';
 $strBinaryDoNotEdit = 'Binary - do not edit';
 $strBookmarkDeleted = 'The bookmark has been deleted.';
@@ -68,7 +70,6 @@ $strCantRenameIdxToPrimary = 'Can\'t rename index to PRIMARY!';
 $strCantUseRecodeIconv = 'Can not use iconv nor libiconv nor recode_string function while extension reports to be loaded. Check your php configuration.';
 $strCardinality = 'Cardinality';
 $strCarriage = 'Carriage return: \\r';
-$strCharsetOfFile = 'Character set of the file:';
 $strChange = 'Change';
 $strChangeDisplay = 'Choose Field to display';
 $strChangePassword = 'Change password';
@@ -134,6 +135,8 @@ $strEmpty = 'Empty';
 $strEmptyResultSet = 'MySQL returned an empty result set (i.e. zero rows).';
 $strEnabled = 'Enabled';
 $strEnd = 'End';
+$strEndCut = 'END CUT'; 
+$strEndRaw = 'END RAW';
 $strEnglishPrivileges = ' Note: MySQL privilege names are expressed in English ';
 $strError = 'Error';
 $strExport = 'Export';
@@ -357,8 +360,13 @@ $strSort = 'Sort';
 $strSpaceUsage = 'Space usage';
 $strSplitWordsWithSpace = 'Words are separated by a space character (" ").';
 $strSQL = 'SQL';
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';
 $strSQLQuery = 'SQL-query';
 $strSQLResult = 'SQL result';
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  
+$strSQPBugUnclosedQuote = 'Unclosed quote';
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';
 $strStatement = 'Statements';
 $strStrucCSV = 'CSV data';
 $strStrucData = 'Structure and data';

lang/estonian-iso-8859-1.inc.php3

@@ -417,4 +417,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/estonian-utf-8.inc.php3

@@ -418,4 +418,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/finnish-iso-8859-1.inc.php3

@@ -418,4 +418,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/finnish-utf-8.inc.php3

@@ -419,4 +419,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/french-iso-8859-1.inc.php3

@@ -413,4 +413,13 @@ $strWrongUser = 'Erreur d\'utilisateur/mot de passe. Acc
 $strYes = 'Oui';
 
 $strZip = '"zipp<70>"';
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/french-utf-8.inc.php3

@@ -71,7 +71,7 @@ $strCarriage = 'Retour de chariot : \\r';
 $strChange = 'Modifier';
 $strChangeDisplay = 'Champ à afficher';
 $strChangePassword = 'Modifier le mot de passe';
-$strCharsetOfFile = 'Jeu de caract<EFBFBD>res du fichier:';
+$strCharsetOfFile = 'Jeu de caractères du fichier:';
 $strCheckAll = 'Tout cocher';
 $strCheckDbPriv = 'Afficher les privilèges sur';
 $strCheckTable = 'Vérifier la table';
@@ -414,4 +414,13 @@ $strWrongUser = 'Erreur d\'utilisateur/mot de passe. Accès refusé';
 $strYes = 'Oui';
 
 $strZip = '"zippé"';
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/galician-iso-8859-1.inc.php3

@@ -419,4 +419,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/galician-utf-8.inc.php3

@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/georgian-utf-8.inc.php3

@@ -397,4 +397,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/german-iso-8859-1.inc.php3

@@ -423,4 +423,13 @@ $strYes = 'Ja';
 $strZip = 'Zip komprimiert';
 
 // To translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/german-utf-8.inc.php3

@@ -424,4 +424,13 @@ $strYes = 'Ja';
 $strZip = 'Zip komprimiert';
 
 // To translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/greek-iso-8859-7.inc.php3

@@ -391,4 +391,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/greek-utf-8.inc.php3

@@ -392,4 +392,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/hebrew-iso-8859-8-i.inc.php3

@@ -415,4 +415,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/hungarian-iso-8859-2.inc.php3

@@ -417,4 +417,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/hungarian-utf-8.inc.php3

@@ -418,4 +418,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/indonesian-iso-8859-1.inc.php3

@@ -417,4 +417,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/indonesian-utf-8.inc.php3

@@ -418,4 +418,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/italian-iso-8859-1.inc.php3

@@ -421,4 +421,13 @@ $strZip = '"compresso con zip"';
 
 // To translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/italian-utf-8.inc.php3

@@ -71,7 +71,7 @@ $strCantLoadMySQL = 'impossibile caricare l\'estensione MySQL,<br />controlla la
 $strCantLoadRecodeIconv = 'Impossibile caricare l\'estensione iconv o recode necessaria per la conversione del set di caratteri, configurare il PHP per permettere di utilizzare queste estenzioni o disabilitare la conversione dei set di caratteri in phpMyAdmin.';
 $strCantRenameIdxToPrimary = 'Impossibile rinominare l\'indice a PRIMARIO!';
 $strCantUseRecodeIconv = 'Impossibile utilizzare le funzioni iconv o libiconv o recode_string in quanto l\'estensione deve essere caricata. Controllare la configurazione del PHP.';
-$strCardinality = 'Cardinalit<EFBFBD> ';
+$strCardinality = 'Cardinalità';
 $strCarriage = 'Ritorno carrello: \\r';
 $strChange = 'Modifica';
 $strChangeDisplay = 'Scegli il campo da mostrare';
@@ -285,7 +285,7 @@ $strPrimaryKeyName = 'Il nome della chiave primaria deve essere... PRIMARY!';
 $strPrimaryKeyWarning = '("PRIMARY" <b>deve</b> essere il nome di, e <b>solo di</b>, una chiave primaria!)';
 $strPrintView = 'Visualizza per stampa';
 $strPrivileges = 'Privilegi';
-$strProperties = 'Propriet<EFBFBD> ';
+$strProperties = 'Proprietà';
 
 $strQBE = 'Query da esempio';
 $strQBEDel = 'Cancella';
@@ -293,7 +293,7 @@ $strQBEIns = 'Aggiungi';
 $strQueryOnDb = 'SQL-query sul database <b>%s</b>:';
 
 $strRecords = 'Record';
-$strReferentialIntegrity = 'Controlla l\'integrit<EFBFBD>  delle referenze:';
+$strReferentialIntegrity = 'Controlla l\'integrità delle referenze:';
 $strRelationNotWorking = 'Le caratteristiche aggiuntive sono state disattivate per funzionare con le tabelle linkate. Per scoprire perchè clicca %squi%s.';
 $strRelationView = 'Vedi relazioni';
 $strReloadFailed = 'Riavvio di MySQL fallito.';
@@ -316,7 +316,7 @@ $strRows = 'Righe';
 $strRowsFrom = 'righe a partire da';
 $strRowSize = 'Dimensione riga';
 $strRowsModeHorizontal = ' orizzontale ';
-$strRowsModeOptions = ' in modalit<EFBFBD>  %s e ripeti gli headers dopo %s celle ';
+$strRowsModeOptions = ' in modalità %s e ripeti gli headers dopo %s celle ';
 $strRowsModeVertical = ' verticale ';
 $strRowsStatistic = 'Statistiche righe';
 $strRunning = 'in esecuzione su %s';
@@ -422,4 +422,13 @@ $strZip = '"compresso con zip"';
 
 // To translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/japanese-euc.inc.php3

@@ -424,4 +424,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/japanese-sjis.inc.php3

@@ -424,4 +424,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/japanese-utf-8.inc.php3

@@ -425,4 +425,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/korean-ks_c_5601-1987.inc.php3

@@ -416,4 +416,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/latvian-utf-8.inc.php3

@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/latvian-windows-1257.inc.php3

@@ -419,4 +419,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/lithuanian-utf-8.inc.php3

@@ -416,4 +416,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/lithuanian-windows-1257.inc.php3

@@ -415,4 +415,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/norwegian-iso-8859-1.inc.php3

@@ -419,4 +419,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/norwegian-utf-8.inc.php3

@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/polish-iso-8859-2.inc.php3

@@ -415,4 +415,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/polish-utf-8.inc.php3

@@ -416,4 +416,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/portuguese-iso-8859-1.inc.php3

@@ -418,4 +418,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/portuguese-utf-8.inc.php3

@@ -419,4 +419,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/romanian-iso-8859-1.inc.php3

@@ -415,4 +415,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/romanian-utf-8.inc.php3

@@ -415,4 +415,14 @@ $strNoValidateSQL = 'Skip Validate SQL';  //to translate
 $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
+$strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/russian-koi8-r.inc.php3

@@ -419,4 +419,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/russian-utf-8.inc.php3

@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/russian-windows-1251.inc.php3

@@ -419,4 +419,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/serbian-utf-8.inc.php3

@@ -422,4 +422,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/serbian-windows-1250.inc.php3

@@ -421,4 +421,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/slovak-iso-8859-2.inc.php3

@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/slovak-utf-8.inc.php3

@@ -421,4 +421,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/slovak-windows-1250.inc.php3

@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/slovenian-iso-8859-2.inc.php3

@@ -418,4 +418,13 @@ $strZip = '"zipano"';
 
 // To translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/slovenian-utf-8.inc.php3

@@ -418,4 +418,13 @@ $strZip = '"zipano"';
 
 // To translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/slovenian-windows-1250.inc.php3

@@ -418,4 +418,13 @@ $strZip = '"zipano"';
 
 // To translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/spanish-iso-8859-1.inc.php3

@@ -412,4 +412,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/spanish-utf-8.inc.php3

@@ -413,4 +413,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/swedish-iso-8859-1.inc.php3

@@ -415,4 +415,13 @@ $strZip = '"zippad"';
 
 // To translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/swedish-utf-8.inc.php3

@@ -416,4 +416,13 @@ $strZip = '"zippad"';
 
 // To translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/thai-tis-620.inc.php3

@@ -417,4 +417,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/thai-utf-8.inc.php3

@@ -418,4 +418,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/turkish-iso-8859-9.inc.php3

@@ -417,4 +417,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/turkish-utf-8.inc.php3

@@ -418,4 +418,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/ukrainian-utf-8.inc.php3

@@ -418,4 +418,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>

lang/ukrainian-windows-1251.inc.php3

@@ -417,4 +417,13 @@ $strValidateSQL = 'Validate SQL';  //to translate
 $strNoExplain = 'Skip Explain SQL';  //to translate
 $strExplain = 'Explain SQL';  //to translate
 $strCharsetOfFile = 'Character set of the file:'; //to translate
+$strBeginCut = 'BEGIN CUT';  //to translate
+$strEndCut = 'END CUT';  //to translate
+$strSQPBugInvalidIdentifer = 'Invalid Identifer';  //to translate
+$strSQPBugUnknownPunctation = 'Unknown Punctation String';  //to translate
+$strSQPBugUnclosedQuote = 'Unclosed quote';  //to translate
+$strBeginRaw = 'BEGIN RAW';  //to translate
+$strEndRaw = 'END RAW';  //to translate
+$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:';  //to translate
+$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem';  //to translate
 ?>