diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio.ts
index db7e15b07e..2631faa377 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+
@@ -995,530 +995,540 @@
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
-
+
+
-
+
-
+
-
-
+
+
-
+
-
+
-
+
+
+
+
+
+
+
+
+
+
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
-
+
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
@@ -5486,7 +5496,7 @@ find next
-
+
@@ -5497,17 +5507,17 @@ find next
-
+
-
+
-
+
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_af_ZA.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_af_ZA.ts
index 600e5d3592..401f94c591 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_af_ZA.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_af_ZA.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ar_SA.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ar_SA.ts
index 0817bd7364..e9d9483398 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ar_SA.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ar_SA.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ca_ES.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ca_ES.ts
index 5bb32a88c0..13c3012ea6 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ca_ES.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ca_ES.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_cs_CZ.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_cs_CZ.ts
index 3403b40f51..8c5a6ac832 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_cs_CZ.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_cs_CZ.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_da_DK.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_da_DK.ts
index 57985739b2..defbcedc2b 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_da_DK.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_da_DK.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_de_DE.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_de_DE.ts
index 30058bf573..2baa75d308 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_de_DE.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_de_DE.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Konfiguration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>Wenn Daten in das Ergebnisfenster eingelesen werden, dann wird die Breite der Spalten dabei automatisch angepasst. Dieser Wert begrenzt maximale Breite für die automatische Breitenanpassung. Der Anwender kann die Spaltenbreite jedoch manuell über dieses Limit verbreitern.</p>
-
+ Anzahl an Datenzeilen pro Seite:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Neue Zeile im Gitternetz des Datenfensters hinzufügen
-
+ Vor der derzeitig ausgewählten Zeile
-
+ Nach der derzeitig ausgewählten Zeile
-
+ Am Ende der Datenfensters
-
+ Tabellenfenster
-
+ <p>Wenn aktiviert, wird der Reiter "Daten" anstelle des Reiters "Struktur" angezeigt beim öffnen eines Tabellenfensters angezeigt.</p>
-
+ Öffnet das Tabellenfenster mit dem Reiter "Daten" im Vordergrund
-
+ <p>Wenn aktiviert, wird der Reiter "Daten" als erster Reiter angezeigt für jedes Tabellenfenster, anstelle an zweiter Stelle.</p>
-
+ Den Reiter Daten als ersten Reiter im Tabellenfenster anzeigen
-
+ Viewfenster
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Öffnet das Viewfenster mit dem Reiter "Daten" im Vordergrund
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Den Reiter Daten als ersten Reiter im View-Fenster anzeigen
-
+ Datentypen
-
+ Verfügbare Editoren:
-
+ Für diesen Datentyp ausgewählte Editoren:
-
+ Schema
-
+ Maximale Anzahl an DDL Änderungen im Verlauf.
-
+ DDL Verlaufsgröße:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL Abfragen
-
-
+
+ Maximale Anzahl an SQL Abfragen im Verlauf.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ Verlaufsgröße:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Führt nur die Abfrage unter dem Cursor aus
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Prüfe vor dem Start automatisch auf Updates
-
+ Sitzung
-
+ Stelle letzte Sitzung nach dem Start wieder her (aktive MDI Fenster)
-
+ Allow multiple instances of the application at the same time
-
+ Statusfeld
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Den Panel Status immer öffnen, wenn eine neue Meldung ausgegeben wird
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filtere Tastaturkürzel nach Name oder Tastenkombination
-
+ Aktion
-
+ Tastenkombination
-
-
+
+ Sprache
-
+ Die Änderung der Sprache erfordert einen Neustart des Programms.
-
+ Kompaktes Layout
-
+ <p>Das kompakte Layout reduziert alle Lücken und Abstände der Oberfläche auf ein Minimum, um mehr Platz für die Darstellung der Daten zu schaffen. Die Oberfläche sieht dann zwar nicht mehr sehr ästhetisch aus, aber man hat mehr Daten im Überblick.</p>
-
+ Benutze kompaktes Layout
-
+ Dockingbereiche des Hauptfensters
-
+ Linke und rechte Bereiche belegen die Ecken
-
+ Obere und untere Bereiche belegen die Ecken
-
+ Verberge eingebaute Plugins
-
+ Aktueller Stil:
-
+ Vorschau
-
+ Aktiviert
-
+ Deaktiviert
-
+ Aktives Formatierungsplugin
-
+ Schriftart des SQL Editors
-
+ Schriftart der Datenbankliste
-
+ Zusätzliche Bezeichnungen in der Datenbankliste
-
+ Schriftart der Ergebnisansicht
-
+ Schriftart des Statusfelds
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5496,7 +5506,7 @@ find next
-
+ Die Zelle kann nicht editiert. Details: %1
@@ -5507,17 +5517,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_el_GR.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_el_GR.ts
index fcbcf73ce7..1a3192349f 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_el_GR.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_el_GR.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_en_US.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_en_US.ts
index 33f4358a43..13ffc3c8c2 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_en_US.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_en_US.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_es_ES.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_es_ES.ts
index 529afc38b0..683e5b4ee6 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_es_ES.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_es_ES.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuración
@@ -995,530 +995,540 @@
-
+ <p>Número máximo de configuraciones del diálogo de Llenar Tabla almacenados en la configuración. El valor de 100 debería bastar.</p>
-
+ Número de configuraciones de llenado de tabla memorizados
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>Cuando se cargan los datos en la vista de grilla, se ajusta el ancho de las columnas automáticamente. Este valor limita el ancho inicial para el ajuste, pero el usuario puede redimensionar manualmente la columna por encima de este límite.</p>
-
+ Número de filas de datos por página:
-
+ <p>Cuando esto está activado y el usuario deja el puntero del mouse encima de una celda en cualquier vista de datos (resultados de la consulta, una tabla de datos, una vista de datos) un globo de texto aparecerá con detalles sobre la celda - incluye detalles como el tipo de datos de la columna, restricciones, ROWID y otros.</p>
-
+ Mostrar globo de texto con detalles para filas y columnas en la vista de datos
-
+ <p>Al editar una celda que solía contener un valor NULL, ingresando una string vacía como valor nuevo, con esta opción se determina si el nuevo valor debería quedarse como NULL (si esta opción está activada), o debería reemplazarse con un valor de string vacío (si esta opción está desactivada).</p>
-
+ Mantener valor NULL al ingresar un valor vacío
-
+ <html><head/><body><p>Activar esto para forzar siempre el uso del valor DEFAULT al confirmar un valor NULL para una columna con el valor DEFAULT definido, aún así que la columna esté permitida de almacenar valores NULL.</p><p>Desactiva esta opción para usar el valor DEFAULT exclusivamente cuando un valor NULL se confirme a una columna con la restricción NOT NULL.</p></body></html>
-
+ Usar valor DEFAULT (si se ha definido) al confirmar un valor NULL
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Insertar una nueva fila en la cuadrícula de datos
-
+ Antes de la fila actualmente seleccionada
-
+ Después de la fila actualmente seleccionada
-
+ Al final de la vista de datos
-
+ Ventanas de tabla
-
+ <p>Si está activado, Ventanas de Tabla se mostrará con la pestaña datos, en vez de la pestaña estructura.</p>
-
+ Abrir Ventanas de Tabla con la pestaña de datos para iniciar
-
+ <p>Cuando esté activado, la pestaña "Datos" se posicionará como la primera pestaña en cada Ventana Tabla, en vez de estar en el segundo lugar.</p>
-
+ Ubicar la pestaña de datos como la primera pestaña en una Ventana Tabla
-
+ Ver ventanas
-
+ <p>Cuando está activado, Ver Ventanas se mostrará en la pestaña de Datos, en vez de la de Estructura.</p>
-
+ Abrir Ver Ventanas con la pestaña de datos al iniciar
-
+ <p>Cuando esté activado, la pestaña "Datos" se posicionará como la primera pestaña en cada Ventana Tabla, en vez de estar en el segundo lugar.</p>
-
+ Ubicar la pestaña de datos como la primera pestaña en una Ventana Ver
-
+ Tipos de datos
-
+ Editores disponibles:
-
+ Editores seleccionados para este tipo de dato:
-
+ Edición de esquema
-
+ Número de cambios de DDL a mantener en el historial.
-
+ Tamaño del historial DDL:
-
+ No mostrar el diálogo de vista previa del DDL al confirmar cambios del esquema
-
+ Consultas SQL
-
-
+
+ Número de consultas a mantener en el historial.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ Tamaño del historial:
-
-
+
+ <p>Número máximo de parámetros en la consulta (:param, @param, $param, ?) almacenados en el historial. Cuando reusas un parámetro con el mismo nombre/posición, SQLiteStudio lo pre-inicializará con el valor más reciente almacenado en memoria (aún podrás cambiarlo). Un valor de 1000 debería bastar.</p>
-
+ Ejecutar sólo la consulta bajo el cursor
-
+ Número de parámetros de consulta en memoria
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Actualizaciones
-
+ Comprobar actualizaciones automáticamente al inicio
-
+ Sesión
-
+ Restaurar la última sesión (ventana MDI activa) luego de iniciar
-
+ Allow multiple instances of the application at the same time
-
+ Campo de Estado
-
+ <p>Cuando el usuario cierra manualmente el panel de Estado, esta opción se asegura que cualquier nuevo mensaje enviado al panel de Estado se muestre, mostrando de nuevo ese panel. Si se desactiva, el usuario tiene que abrir manualmente el panel de Estado desde el menú "Vista".</p>
-
+ Abrir siempre el panel de Estado cuando un nuevo mensaje se muestre
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filtrar atajos por nombre o combinación de teclas
-
+ Acción
-
+ Combinación de teclas
-
-
+
+ Idioma
-
+ Cambiar el idioma requiere reiniciar la aplicación para que los cambios surtan efecto.
-
+ Diseño compacto
-
+ <p>Compactar diseño reduce todos los márgenes y espaciados de la IU al mínimo, haciendo espacio para mostrar más datos. Le quita algo de belleza a la interfaz, pero permite mostrar más datos.</p>
-
+ Usar diseño compacto
-
+ Áreas de acoplamiento de la ventana principal
-
+ Las áreas izquierda y derecha ocupan las esquinas
-
+ Las áreas superior e inferior ocupan las esquinas
-
+ Ocultar plugins integrados
-
+ Estilo actual:
-
+ Vista previa
-
+ Activado
-
+ Desactivado
-
+ Plugin de formato activo
-
+ Fuente del editor SQL
-
+ Fuente de la lista de bases de datos
-
+ Fuente para la etiqueta adicional de lista de bases de datos
-
+ Fuente del visor de datos
-
+ Fuente del campo de Estado
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_fa_IR.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_fa_IR.ts
index 13161bb334..6f35b2fdb3 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_fa_IR.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_fa_IR.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_fi_FI.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_fi_FI.ts
index 9ea1cfb606..cbc47a9951 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_fi_FI.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_fi_FI.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_fr_FR.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_fr_FR.ts
index c9fe81f287..185dd78e08 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_fr_FR.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_fr_FR.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>Lorsque les données sont lues dans le tableau, la largeur est automatiquement ajustée. Cette valeur limite la largeur initiale pour l’ajustement, mais l’utilisateur peut recadrer les colonnes manuellement au-dessus de cette limite.</p>
-
+ Nombre de lignes de données par page :
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Insertion d'une nouvelle ligne dans la grille de données
-
+ Avant la ligne courante
-
+ Après la ligne courante
-
+ À la fin de la vue de données
-
+ Fenêtres de tables
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Sélectionner l'onglet de données lors de l'ouverture d'une fenêtre de table
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Placer l'onglet Données en premier dans les fenêtres de tables
-
+ Fenêtre de vue
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Sélectionner l'onglet de données lors de l'ouverture d'une fenêtre de vue
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Types de données
-
+ Éditeurs disponibles :
-
+ Éditeur sélectionné pour ce type de données :
-
+ Edition de schéma
-
+ Nombre de DDL modifiés gardés dans l’historique.
-
+ Dimension de l’historique DDL :
-
+ Don't show DDL preview dialog when committing schema changes
-
+ Requêtes SQL
-
-
+
+ Nombre de requêtes gardées dans l’historique.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ Dimension de l’historique :
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Exécuter seulement la requête sous le curseur
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Mises à jour
-
+ Contrôle automatique des mises à jour au lancement
-
+ Session
-
+ Restaurer la dernière session (Fenêtre MDI active) après lancement
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filtre par nom raccourci ou combinaison de touches
-
+ Action
-
+ Combinaison de touches
-
-
+
+ Langage
-
+ Le changement de langage requiert le redémarrage de l’application pour prendre effet.
-
+ Présentation compacte
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Utiliser la présentation compacte
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Cacher des plugins incorporés
-
+ Style actuel :
-
+ Aperçu
-
+ En service
-
+ Hors service
-
+ Plugin de formattage actif
-
+ Police de caractères de l’éditeur SQL
-
+ Liste des polices de caractères de base de données
-
+ Police de caractères additionelle de la liste des bases de données
-
+ Police de caractères des données de vue
-
+ Police de caractères du champ d’état
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5495,7 +5505,7 @@ recherche suivant
-
+ Impossible de modifier cette cellule. Détails : %1
@@ -5506,17 +5516,17 @@ recherche suivant
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_he_IL.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_he_IL.ts
index 013bb88e15..87d5222913 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_he_IL.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_he_IL.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ הגדרות
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>כאשר אפשרות זו מופעלת והמשתמש מחזיק מצביע עכבר מעל תא במצג נתונים כלשהו (תוצאות שאילתה, נתוני טבלה, נתוני תצוגה) יופיע כלי עצה עם פרטים אודות התא - שיכלול פרטים אודות סוג נתוני העמודה, אילוצים, ROWID ועוד</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ סוגי מידע
-
+ עורכים זמינים:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ שאילתות SQL
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ גודל היסטוריה:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ עדכונים
-
+ Automatically check for updates at startup
-
+ מופעים
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ שדה מצב
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ פעולה
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ תצוגה מקדימה
-
+ מופעל
-
+ מושבת
-
+ Active formatter plugin
-
+ גופן עורך SQL
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_hu_HU.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_hu_HU.ts
index 50b6a14d81..f112984322 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_hu_HU.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_hu_HU.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_it_IT.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_it_IT.ts
index 42f2a4964a..4988dd24ec 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_it_IT.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_it_IT.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configurazione
@@ -995,530 +995,540 @@
-
+ <p>Numero massimo di configurazioni della finestra di dialogo Popolazione tabella memorizzate in configurazione. Il valore di 100 dovrebbe essere sufficiente.</p>
-
+ Numero di configurazioni di popolamento delle tabelle memorizzate
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>Quando i dati vengono letti nella griglia la larghezza delle colonne della vista griglia viene automaticamente regolata. Questo valore limita la larghezza iniziale delle colonne a causa dell'aggiustamento, ma l'utente può ancora ridimensionare manualmente la colonna oltre questo limite.</p>
-
+ Numero di righe di dati per pagina:
-
+ <p>Quando questa opzione è abilitata e l'utente tiene il puntatore del mouse su una cella in qualsiasi vista dati (risultati delle interrogazioni, dati di una tabella, una vista dati) apparirà un suggerimento con dettagli circa la cella - includendo dettagli come tipo di colonna di dati, vincoli, ROWID e altri.</p>
-
+ Mostra i dettagli colonna e riga nella vista dati
-
+ <p>Quando si modifica una cella che ha un valore NULL e si inserisce una stringa vuota come nuovo valore, allora questa opzione determina se il nuovo valore debba rimanere NULL (con questa opzione abilitata), o dovrebbe essere sovrascritto con valore di stringa vuota (con questa opzione disabilitata).</p>
-
+ Mantiene il valore NULL quando si inserisce un valore vuoto
-
+ <html><head/><body><p>Abilitare questo per imporre sempre il valore DEFAULT quando si memorizza un valore NULL per una colonna che ha definito il valore di DEFAULT, anche se la colonna può contenere valori NULL.</p><p>Disabilitare questa opzione per utilizzare il valore DEFAULT esclusivamente quando il valore NULL è memorizzato per la colonna con un vincolo NON NULL.</p></body></html>
-
+ Usa il valore DEFAULT (se definito), quando si memorizza un valore NULL
-
+ <html><head/><body><p>Se i risultati della query contengono dozzine (o centinaia) di colonne, è più probabile che esaurirà la memoria libera del Tuo computer caricando parecchi gigabyte di dati contemporaneamente. SQLiteStudio può cercare di limitare il numero di risultati visualizzati su una pagina in tali casi per proteggere il computer. Se sei conscio che non lavori con grandi quantità di record nel database, puoi disabilitare questo limite e vedrai sempre tante righe per pagina così come sono state definite.</p></body></html>
-
+ Limita il numero di righe in caso di dozzine di colonne
-
+ Inserimento di una nuova riga nella griglia dei dati
-
+ Prima della riga attualmente selezionata
-
+ Dopo la riga attualmente selezionata
-
+ Alla fine della vista dati
-
+ Finestra tabelle
-
+ <p>Se abilitata, le finestre della tabella verranno visualizzate con la scheda dati, invece della scheda struttura.</p>
-
+ Apri Finestre Tabella all'avvio con la scheda dati
-
+ <p>Quando abilitata, la scheda "Dati" sarà posizionata come prima scheda in ogni finestra della tabella, invece di essere al secondo posto.</p>
-
+ Posiziona la scheda dati come prima scheda in una finestra della tabella
-
+ Visualizza finestre
-
+ <p>Quando abilitata, Finestra Vista apparirà con la scheda dati, invece della scheda struttura.</p>
-
+ Apri Finestre Tabella all'avvio con la scheda dati
-
+ <p>Quando abilitata, la scheda "Dati" sarà posizionata come prima scheda in ogni Finestra Tabella, invece di essere al secondo posto.</p>
-
+ Posiziona la scheda dati come prima scheda in una Finestra Tabella
-
+ Tipi di dati
-
+ Editor disponibili:
-
+ Editor selezionati per questo tipo di dati:
-
+ Modifica dello schema
-
+ Numero di modifiche DDL conservate nella cronologia.
-
+ Dimensione cronologia DDL:
-
+ Non mostrare la finestra di anteprima DDL quando si salvano le modifiche allo schema
-
+ Query SQL
-
-
+
+ Numero di query conservate nella cronologia.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ Dimensione cronologia:
-
-
+
+ <p>Numero massimo di parametri di interrogazione (:param, @param, $param, ?) memorizzati nella cronologia. Quando riutilizzi il parametro con lo stesso nome/posizione, SQLiteStudio lo preinizializzerà con il valore memorizzato più recente (sarà ancora possibile comunque cambiarlo). Il valore di 1000 dovrebbe essere sufficiente.</p>
-
+ Esegue solo la query sotto il cursore
-
+ Numero di parametri di interrogazione memorizzati
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Aggiornamenti
-
+ Controlla automaticamente gli aggiornamenti all'avvio
-
+ Sessione
-
+ Ripristina l'ultima sessione (finestre MDI attive) dopo l'avvio
-
+ Consenti più istanze dell'applicazione nello stesso tempo
-
+ Campo Stato
-
+ <p>Quando l'utente chiude manualmente il pannello di Stato, questa opzione fa in modo che se un nuovo messaggio viene stampato nel pannello di stato esso venga riaperto. Se è disabilitata, allora il pannello di stato può essere aperto manualmente dall'utente solo dal menu "Visualizza"</p>
-
+ Apri sempre il pannello di stato quando viene stampato un nuovo messaggio
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filtra le scorciatoie per nome o combinazione di tasti
-
+ Azione
-
+ Combinazione di tasti
-
-
+
+ Lingua
-
+ La modifica della lingua richiede il riavvio dell'applicazione per avere effetto.
-
+ Layout compatto
-
+ <p>La disposizione compatta riduce al minimo tutti i margini e la spaziatura dell'interfaccia utente, rendendo lo spazio per visualizzare più dati. Rende l'interfaccia un po' meno estetica, ma permette di visualizzare più dati contemporaneamente.</p>
-
+ Usa layout compatto
-
+ Aree di aggancio della finestra principale
-
+ Le aree sinistra e destra occupano gli angoli
-
+ Le aree superiore e inferiore occupano gli angoli
-
+ Nascondi plugin integrati
-
+ Stile attuale:
-
+ Anteprima
-
+ Abilitato
-
+ Disabilitato
-
+ Plugin formattatore attivo
-
+ Carattere editor SQL
-
+ Carattere elenco database
-
+ Database list carattere etichetta aggiuntivo
-
+ Carattere vista dati
-
+ Carattere campo di stato
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ trova il prossimo
-
+ Impossibile modificare questa cella. Dettagli: %1
@@ -5509,17 +5519,17 @@ trova il prossimo
-
+ La struttura di questa tabella è cambiata da quando sono stati caricati gli ultimi dati. Ricarica i dati per procedere.
-
+ Modificare un ampio contenuto in un editor di celle in linea non è una buona idea. Può diventare lento e scomodo. È meglio modificare tali grandi contenuti in una vista modulo, o in un editor popup (disponibile sotto il menu tasto-destro).
-
+ La chiave esterna per la colonna %2 ha più di %1 valori possibili. Sono troppi per essere visualizzati nell'elenco a discesa. È necessario modificare il valore manualmente.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ja_JP.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ja_JP.ts
index f91621695f..c47f1e2024 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ja_JP.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ja_JP.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ko_KR.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ko_KR.ts
index 69f6eda227..b2a8cd8008 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ko_KR.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ko_KR.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_nl_NL.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_nl_NL.ts
index 5a72b65d78..38d7e75f15 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_nl_NL.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_nl_NL.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_no_NO.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_no_NO.ts
index fb2e1724ab..113c1092aa 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_no_NO.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_no_NO.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_pl_PL.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_pl_PL.ts
index 956ce4aad0..7fe351efce 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_pl_PL.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_pl_PL.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Konfiguracja
@@ -995,530 +995,540 @@
-
+ <p>Maksymalna liczba konfiguracji w oknie dialogowym zaludniania tabeli, która ma być trzymana w konfiguracji. Wartość 100 powinna być wystarczająca.</p>
-
+ Liczba zapamiętanych konfiguracji zaludniania tabeli
-
+ Szerokość kolumny danych
-
+ <html><head/><body><p>Kiedy użytkownik wprowadzi nową wartość do kolumny, a wartość jest większa niż obecna szerokość kolumny, aplikacja powiększy kolumnę w celu dostosowania jej do nowej wartości, ale nie więcej niż limit określony w opcji powyżej.</p></body></html>
-
+ Powiększ kolumnę podczas wprowadzania wartości dłuższej niż obecna szerokość
-
+ <p>Kiedy dane są wczytane do widoku siatki, szerokość kolumn jest automatycznie dostosowywana. Ta wartość ogranicza początkową szerokość tego dostosowywania, ale użytkownik nadal może rozszerzać kolumnę ręcznie poza ten limit.</p>
-
+ Liczba wierszy danych na stronie:
-
+ <p>Gdy to jest włączone i użytkownik zatrzyma kursor myszy nad komórką w widoku siatki danych (wyniki zapytania, dane tabeli, dane widoku), to pojawi się podpowiedź ze szczegółami odnośnie komórki - zawiera ona szczegóły , jak typ danych kolumny, ograniczenia, ROWID i inne.</p>
-
+ Pokazuj podpowiedź ze szczegółami o kolumnie i wierszu w widoku siatki danych
-
+ <p>Kiedy edytowana jest komórka, która miała wartość NULL, a nowa wartość wprowadzona jest pusta, to ta opcja decyduje o tym, czy wartość powinna pozostać NULL (gdy ta opcja jest włączona), czy powinna być nadpisana pustym łańcuchem znaków (gdy ta opcja wyłączona).</p>
-
+ Zachowaj wartość NULL gdy wstawiania jest pusta wartość
-
+ <html><head/><body><p>Włącz to, aby wymusić wartość DEFAULT podczas zatwierdzania wartości NULL dla kolumn, które mają zdefiniowaną wartość DEFAULT, nawet jeśli kolumna dopuszcza wartości NULL.</p><p>Wyłącz tą opcję aby używać wartości DEFAULT tylko i wyłącznie, gdy wartość NULL jest zatwierdzana dla kolumny z ograniczeniem NOT NULL.</p></body></html>
-
+ Używaj wartości DEFAULT (jeśli zdefiniowana), gdy zatwierdzana jest wartość NULL
-
+ <html><head/><body><p>Jeśli wyniki zapytania zawierają dziesiątki (lub setki) kolumn, bardziej prawdopodobne jest, że wyczerpie pamięć komputera ładując kilka gigabajtów danych jednocześnie. SQLiteStudio może próbować ograniczyć liczbę wyników wyświetlanych na jednej stronie w celu ochrony komputera. Jeśli wiesz, że nie pracujesz z dużymi wartościami w bazie danych, możesz wyłączyć ten limit i zawsze zobaczysz tyle wierszy, ile jest zdefiniowanych na stronie.</p></body></html>
-
+ Ogranicz liczbę wierszy w przypadku dziesiątek kolumn
-
+ Wstawianie nowego wiersza w widoku siatki danych.
-
+ Przed aktualnie wybranym wierszem
-
+ Po aktualnie wybranym wierszu.
-
+ Na końcu widoku siatki danych
-
+ Okna tabel
-
+ <p>Gdy włączone, Okna Tabeli będą się otwierać na zakładce danych, zamiast na zakładce struktury.</p>
-
+ Otwieraj Okna Tabeli z zakładką danych na początek
-
+ <p>Gdy włączone, to zakładka "Dane" będzie umieszczona jako pierwsza w każdym Oknie Tabeli, zamiast jako druga.</p>
-
+ Ustaw zakładkę danych jako pierwszą w Oknie Tabeli
-
+ Okna Widoków
-
+ <p>Gdy włączone, Okna Widoku będą się otwierać na zakładce danych, zamiast na zakładce struktury.</p>
-
+ Otwieraj Okna Widoku z zakładką danych na początek
-
+ <p>Gdy włączone, to zakładka "Dane" będzie umieszczona jako pierwsza w każdym Oknie Widoku, zamiast jako druga.</p>
-
+ Ustaw zakładkę danych jako pierwszą w Oknie Widoku
-
+ Type danych
-
+ Dostępne edytory:
-
+ Edytory wybrane dla tego typu danych:
-
+ Edycja schematu
-
+ Liczba zmian DDL trzymanych w historii.
-
+ Rozmiar historii DDL:
-
+ Nie pokazuj okna podglądu DDL podczas zatwierdzania zmian struktury
-
+ Zapytania SQL
-
-
+
+ Liczba zapytań trzymana w historii.
-
+ <html><head/><body><p>Jeśli w oknie edytora SQL jest więcej niż jedno zapytanie, wtedy (jeśli ta opcja jest włączona) zostanie wykonana tylko jedno zapytanie - to pod kursorem wstawiania klawiatury. W przeciwnym razie wszystkie zapytania zostaną wykonane. Zawsze możesz ograniczyć zapytania do wykonania poprzez zaznaczenie tych zapytań przed ich wykonaniem. Możesz również użyć dedykowanych skrótów do wykonywania w jednym lub drugim trybie (obecnie skonfigurowanych pod %1 dla wykonania pojedynczego zapytania i %2 dla wykonania wszystkich zapytań).</p></body></html>
-
+ Rozmiar historii:
-
-
+
+ <p>Maksymalna liczba parametrów zapytania (:param, @param, $param, ?) trzymanych w historii. Kiedy ponownie użyjesz parametru o tej samej nazwie/pozycji, SQLiteStudio wstępnie uzupełni go używając ostatniej zapamiętanej wartości (nadal będzie można ją zmienić). Wartość 100 powinna być wystarczająca.</p>
-
+ Wykonuj tylko zapytania będące pod kursorem
-
+ Liczba zapamiętanych parametrów zapytania
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>Gdy dane są odczytywane w widoku tabeli szerokość kolumn jest automatycznie dostosowywana. Ta wartość ogranicza wstępnie dostosowaną szerokość, ale użytkownik może zmieniać rozmiar kolumny ręcznie powyżej tego limitu. Ta wartość jest również używana podczas powiększania kolumny w przypadku nowej, dłuższej wartości wprowadzonej przez użytkownika (patrz opcja poniżej).</p></body></html>
-
+ Ogranicz automatyczną szerokość kolumny danych do (w pikselach):
-
+ <html><head/><body><p>Początkowa szerokość kolumn danych zostanie ustawiona co najmniej tak, aby pokazać pełne nazwy kolumn w nagłówku. To może być nadpisane przez wstępny limit szerokości kolumny określony w pikselach (ustawienie powyżej).</p></body></html>
-
+ Zachowaj co najmniej szerokość wystarczającą, aby wyświetlić pełną nazwę kolumny
-
+ <html><head/><body><p>Jeśli włączone, linie dłuższe niż szerokość edytora będą zawijane, więc przewijanie poziome nie będzie potrzebne.</p></body></html>
-
+ Zawijaj linie w edytorze SQL
-
+ <html><head/><body><p>Podświetla całe zapytanie, które jest obecnie pod kursorem wstawiania. To jest to samo zapytanie, które zostanie wykonane po naciśnięciu klawisza skrótu lub przycisku "Wykonaj zapytanie" (chyba że skonfigurowano inaczej).</p></body></html>
-
+ Podświetl bieżące zapytanie
-
+ Aktualizacje
-
+ Sprawdzaj aktualizacje automatycznie przy starcie
-
+ Sesje
-
+ Przywróć ostatnią sesję (aktywne okna MDI) po starcie
-
+ Zezwalaj na wiele instancji aplikacji w tym samym czasie
-
+ Pole Statusu
-
+ <p>Kiedy użytkownik ręcznie zamyka panel Statusu, ta opcja zapewnia, że zostanie ono otwarte ponownie, gdy jest wyświetlona nowa wiadomość. Jeśli jest ona wyłączona, to panel Statusu może być otwarte tylko ręcznie z menu "Widok".</p>
-
+ Zawsze otwieraj panel Statusu, gdy wyświetlona jest nowa wiadomość
-
+ Kolory składni kodu
-
+ Słowo kluczowe
-
+ Standardowy tekst
-
+ <html><head/><body><p>W SQL ciągi znaków są zamknięte pomiędzy apostrofami. W innych językach ciąg znaków może być zamknięty pomiędzy podwójnym cudzysłowem lub czymś innym.</p></body></html>
-
+ Łańcuch znaków
-
+ Komentarz
-
+ <html><head/><body><p>Prawidłowe obiekty to nazwy tabel, indeksów, wyzwalaczy lub widoków, które istnieją w bazie danych SQLite. Języki inne niż SQL mogą używać tego ustawienia kolorów dla innych odrębnych części językowych.</p></body></html>
-
+ Prawidłowe obiekty
-
+ <html><head/><body><p>W SQLu bieżące zapytanie jest zaznaczone tym tłem, aby wskazać użytkownikowi, który zapytanie zostanie wykonany w danej chwili.</p></body></html>
-
+ Bieżące tło zapytania
-
+ <html><head/><body><p>Parametry wiążące są symbolami zastępczymi dla wartości, które mają być jeszcze dostarczone przez użytkownika. Przyjmują jedną z form:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Języki inne niż SQL mogą używać tego ustawienia kolorów dla innych odrębnych części składowych.</p></body></html>
-
+ Parametr wiążący
-
+ Tło bieżącej linii
-
+ <html><head/><body><p>Kiedy użytkownik przesunie w kodzie kursor wstawiania na nawias, aplikacja oznaczy ten nawias oraz jego pasującą parę tym kolorem tła.</p></body></html>
-
+ Tło dopasowanych nawiasów
-
+ <html><head/><body><p>Możesz całkowicie wyłączyć podświetlanie bieżącego zapytania na stronie ustawień ogólnych.</p></body></html>
-
+ Liczba
-
+ <html><head/><body><p>Wartości BLOB są wartościami binarnymi reprezentowanymi jako liczby szesnastkowe, na przykład:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ Kolor zawartości BLOB
-
+ Dopasowane nawiasy
-
+ Przywróć ustawienia domyślne
-
+ Filtruj skróty po nazwie, lub kombinacji klawiszy
-
+ Akcja
-
+ Kombinacja klawiszy
-
-
+
+ Język
-
+ Zmiana języka wymaga restartu aplikacji, aby zadziałać.
-
+ Układ kompaktowy
-
+ <p>Układ kompaktowy zmniejsza wszystkie marginesy i odstępy na interfejsie do minimum, robiąc więcej miejsca na wyświetlanie danych. Powoduje to, że interfejs jest nieco mniej estetyczny, ale pozwala to na prezentację większej ilości danych naraz.</p>
-
+ Użyj układu kompaktowego
-
+ Strefy dokowania głównego okna
-
+ Lewa i prawa strefa zajmują rogi
-
+ Górna i dolna strefa zajmują rogi
-
+ Ukryj wtyczki wbudowane
-
+ Aktualny styl:
-
+ Podgląd
-
+ Włączone
-
+ Wyłączone
-
+ Aktywna wtyczka formatera
-
+ Czcionka edytora SQL
-
+ Czcionka listy baz danych
-
+ Czcionka dodatkowych etykiety listy baz danych
-
+ Czcionka widoku danych
-
+ Czcionka pola statusu
-
+ Ustawienia asystenta kodu
-
+ <html><head/><body><p>Jeśli ta opcja jest włączona, asystent kodu zostanie uruchomiony w przypadkach, gdy użytkownik wpisze na przykład <span style=" font-weight:700;">nazwaTabeli.</span>, aby zaproponować nazwy kolumn tabeli. Jeśli opcja jest wyłączona, użytkownik będzie musiał użyć skrót klawiszowy asystenta.</p></body></html>
-
+ Automatycznie wyzwalaj asystenta po wpisaniu kropki po nazwie obiektu
@@ -5498,7 +5508,7 @@ znajdź następny
-
+ Nie można edytować tej komórki. Szczegóły: %1
@@ -5509,17 +5519,17 @@ znajdź następny
-
+ Struktura tej tabeli zmieniła się od ostatniego ładowania danych. Przeładuj dane, aby kontynuować.
-
+ Edytowanie ogromnych ilości danych w podręcznym edytorze nie jest dobrym pomysłem. Może być on powolny i nieporęczny. Lepiej edytować takie duże ilości danych w Widoku Formularza, lub w osobnym oknie edytora (dostępnym w menu prawego kliknięcia myszy).
-
+ Klucz obcy dla kolumny %2 ma więcej niż %1 możliwych wartości. To zbyt wiele, by wyświetlić w liście rozwijanej. Musisz edytować wartość ręcznie.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_pt_BR.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_pt_BR.ts
index 332837f6e6..b705bc3057 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_pt_BR.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_pt_BR.ts
@@ -829,7 +829,7 @@ Key
ConfigDialog
-
+ Configuração
@@ -996,530 +996,540 @@ Key
-
+ <p>O número máximo de configurações da caixa de diálogo Populate Table armazenada na configuração. O valor de 100 deve ser suficiente.</p>
-
+ Número de tabelas memorizadas que preenchem configurações
-
+ Largura da coluna de dados
-
+ <html><head/><body><p>Quando o usuário insere novo valor na coluna e o valor é maior do que a largura da coluna atual, o aplicativo irá ampliar a coluna para caber no novo valor, mas não mais do que o limite definido na opção acima.</p></body></html>
-
+ Ampliar a coluna ao inserir um valor maior que a largura atual
-
+ <p>Quando os dados são lidos na exibição das colunas de grade a largura é automaticamente ajustada. Este valor limita a largura inicial para o ajuste, mas o usuário ainda pode redimensionar a coluna manualmente acima deste limite.</p>
-
+ Número de linhas de dados por página:
-
+ <p>Quando isso está habilitado e o usuário mantém o ponteiro do mouse sobre uma célula em qualquer exibição de dados (resultados de consulta, dados de uma tabela, uma visualização de dados), uma dica será exibida com detalhes sobre a célula - ela inclui detalhes como o tipo de dados da coluna, restrições, ROWID e outros.</p>
-
+ Mostrar dica de detalhes da coluna e linha na visualização de dados
-
+ <p>Ao editar uma célula que usava como novo valor NULL e a entrada de seqüência de caracteres vazios, então esta opção determina se o novo valor deve permanecer NULO (tenha esta opção ativada), ou deve ser substituído pelo valor vazio da string (tenha esta opção desativada).</p>
-
+ Manter valor NULL ao inserir um valor vazio
-
+ <html><head/><body><p>Habilite isso para sempre aplicar o valor DEFAULT ao confirmar um valor NULL para uma coluna que tenha o valor padrão definido, embora a coluna possa conter valores NULL.</p><p>Desativar esta opção para usar valor PADRÃO exclusivamente quando o valor NULL é comprometido para a coluna com restrição NÃO NULL.</p></body></html>
-
+ Usar valor PADRÃO (se definido), ao confirmar o valor NULL
-
+ <html><head/><body><p>Se consultas de resultados contêm dezenas (ou centenas) de colunas, é mais provável que ele esgote a memória livre do seu computador carregando vários gigabytes de dados de uma só vez. SQLiteStudio pode tentar limitar o número de resultados exibidos em uma página para proteger o seu computador. Se você sabe que você don't trabalha com grandes valores no banco de dados, você pode desativar esse limite e sempre verá quantas linhas forem definidas por página.</p></body></html>
-
+ Limitar o número de linhas no caso de dezenas de colunas
-
+ Inserindo nova linha na grade de dados
-
+ Antes da linha selecionada
-
+ Depois da linha selecionada
-
+ No final da visualização de dados
-
+ Janelas da tabela
-
+ <p>Quando ativado, as janelas de tabela serão exibidas na aba de dados, em vez da aba estrutura.</p>
-
+ Janelas em tabela aberta com a guia de dados para iniciar
-
+ <p>Quando ativado a guia "Dados" será colocada como a primeira guia em cada janela de tabela, em vez de estar no segundo lugar.</p>
-
+ Colocar guia de dados como primeira aba em uma janela de tabela
-
+ Ver janelas
-
+ <p>Quando ativado, exibir janelas irá aparecer na aba de dados, em vez da aba estrutura.</p>
-
+ Abra a visualização de janelas com a guia de dados para iniciar
-
+ <p>Quando ativado a guia "Dados" será colocada como a primeira guia em cada exibição de janela, em vez de ser no segundo lugar.</p>
-
+ Colocar guia de dados como primeira aba em uma janela de visualização
-
+ Tipo de dados
-
+ Editores disponíveis:
-
+ Editores selecionados para este tipo de dado:
-
+ Edição do schema
-
+ Número de alterações DDL mantidas no histórico.
-
+ Tamanho do histórico DDL:
-
+ Não mostrar a janela de pré-visualização do DDL ao confirmar alterações de esquema
-
+ Consultas SQL
-
-
+
+ Número de consultas mantidas no histórico.
-
+ <html><head/><body><p>Se houver mais de uma consulta na janela do editor de SQL, então (se essa opção estiver ativada) apenas uma consulta será executada - a que está sob o cursor de inserção do teclado. Caso contrário, todas as consultas serão executadas. Você pode limitar as consultas a serem executadas selecionando essas consultas antes de executar uma chamada. Você também pode usar atalhos dedicados para executar em um modo ou outro (atualmente configurado para %1 para única consulta de execução e %2 para todas as consultas).</p></body></html>
-
+ Tamanho do histórico:
-
-
+
+ <p>Número máximo de parâmetros de consulta (:param, @param, $param, ?) armazenado na história. Quando você usar novamente o parâmetro com o mesmo nome/posição, SQLiteStudio irá pré-inicializá-lo com o valor mais recente memorizado (você ainda poderá alterá-lo). O valor de 1000 deve ser suficiente.</p>
-
+ Executar a consulta em que o cursor está posicionado
-
+ Número de parâmetros de consulta memorizados
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>Quando os dados são lidos na largura de exibição de colunas da grade é automaticamente ajustada. Este valor limita a largura inicial para o ajuste, mas o usuário ainda pode redimensionar a coluna manualmente acima deste limite. Esse valor também é usado quando se amplia a coluna para um novo valor mais longo inserido pelo usuário (veja a opção abaixo).</p></body></html>
-
+ Limitar a largura da coluna de dados inicial em (em pixels):
-
+ <html><head/><body><p>A largura inicial das colunas de dados será definida para pelo menos mostrar o nome completo da coluna no cabeçalho. Isso ainda pode ser substituído pelo limite inicial de largura de coluna especificada em pixels (configuração acima).</p></body></html>
-
+ Mantenha pelo menos a largura para mostrar o nome completo da coluna
-
+ <html><head/><body><p>Se ativado, linhas maiores que a largura do editor serão encapsuladas, então a rolagem horizontal não será necessária.</p></body></html>
-
+ Quebrar linhas no editor SQL
-
+ <html><head/><body><p>Destaca a consulta inteira que está atualmente sob o cursor de inserção.'a mesma consulta que será executada quando você clicar em "Executar consulta" atalho ou botão (a menos que configurado de outra forma).</p></body></html>
-
+ Destacar consulta atual
-
+ Atualizações
-
+ Verificar atualizações automaticamente ao iniciar
-
+ Sessão
-
+ Restaurar última sessão (janelas MDI ativas) após a inicialização
-
+ Permitir várias instâncias do aplicativo ao mesmo tempo
-
+ Campo Status
-
+ Quando o usuário fecha manualmente o painel de Status, esta opção garante que, se alguma nova mensagem for impressa no painel de Status, ela será reaberta. Se desativado, o painel de status só pode ser aberto manualmente pelo usuário a partir do menu
-
+ Sempre abrir painel de Status quando uma nova mensagem é impressa
-
+ Cores de sintaxe
-
+ Palavra-chave em primeiro plano
-
+ Normal primeiro plano
-
+ <html><head/><body><p>Em SQL strings estão anexadas com aspas simples. Em outros idiomas a cadeia de caracteres pode conter aspas duplas ou qualquer outra coisa.</p></body></html>
-
+ Iniciar em primeiro plano
-
+ Comentar primeiro plano
-
+ <html><head/><body><p>Objetos válidos são o nome das tabelas, índices, gatilhos ou views que existem no banco de dados SQLite. Idiomas que não o SQL podem utilizar esta configuração para outras partes distintas do idioma.</p></body></html>
-
+ Objetos válidos em primeiro plano
-
+ <html><head/><body><p>Na consulta SQL atual é destacada com este fundo para indicar ao usuário qual consulta seria executada a determinado momento.</p></body></html>
-
+ Fundo da consulta atual
-
+ <html><head/><body><p>Parâmetros de associação são espaços reservados para valores ainda a serem fornecidos pelo usuário. Eles têm uma das formas:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Idiomas diferentes do SQL podem utilizar esta configuração de cores para outras partes de sintaxe distintas.</p></body></html>
-
+ Vincular parâmetro em primeiro plano
-
+ Fundo da linha atual
-
+ <html><head/><body><p>Quando o usuário move o cursor de inserção em qualquer parêntese no código, o aplicativo irá marcar este parênteses e sua contraparte correspondente com esta cor de fundo.</p></body></html>
-
+ Fundo de parênteses correspondente
-
+ <html><head/><body><p>É possível desativar o destaque das consultas inteiramente na página de configurações gerais.</p></body></html>
-
+ Número primeiro plano
-
+ <html><head/><body><p>Os valores BLOB são valores binários representados como números hexadecimais, curtir:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ Valor BLOB em primeiro plano
-
+ Primeiro plano de parênteses correspondentes
-
+ Redefinir padrões
-
+ Filtrar atalhos por nome ou combinação de teclas
-
+ Acão
-
+ Combinação de teclas
-
-
+
+ Idioma
-
+ Para mudar o idioma é necessário reiniciar o aplicativo para ter efeito.
-
+ Layout compacto
-
+ <p>O layout compacto reduz ao mínimo todas as margens e espaços na interface do usuário, deixando espaço para exibir mais dados. A interface fica um pouco menos estética, mas permite exibir mais dados de uma só vez.</p>
-
+ Usar layout compacto
-
+ Áreas de encaixe da janela principal
-
+ Áreas esquerda e direita ocupam cantos
-
+ Áreas superior e inferior ocupam cantos
-
+ Ocultar plugins integrados
-
+ Estilo atual:
-
+ Pré-visualizar
-
+ Ativado
-
+ Desabilitado
-
+ Plugin formatador ativo
-
+ Fonte do editor SQL
-
+ Fonte da lista do banco de dados
-
+ Fonte de rótulo adicional da lista de banco de dados
-
+ Fonte para visualização de dados
-
+ Fonte do campo status
-
+ Configurações code assistente
-
+ <html><head/><body><p>Se esta opção estiver habilitada, o assistente de código será acionado nos casos, quando tipos de usuário, por exemplo <span style=" font-weight:700;">tableName.</span> para propor colunas da tabela. Se a opção estiver desativada, o usuário terá de apertar explicitamente a chave de atalho assistente.</p></body></html>
-
+ Acionar automaticamente o assistente após um ponto ser digitado após um nome de objeto
@@ -5499,7 +5509,7 @@ encontrar próximo
-
+ Não é possível editar esta célula. Detalhes: %1
@@ -5510,17 +5520,17 @@ encontrar próximo
-
+ A estrutura desta tabela mudou desde a última data foi carregada. Recarregue os dados para continuar.
-
+ Editar um conteúdo enorme em um editor de celular não é uma boa ideia. Pode se tornar lento e inconveniente. É melhor editar conteúdos tão grandes em um Form View ou em um editor pop-up (disponível no menu rick-click).
-
+ Chave estrangeira para a coluna %2 possui mais de %1 valores possíveis.'é muito para ser exibido na lista de seleção. Você precisa editar o valor manualmente.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_pt_PT.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_pt_PT.ts
index 590e146fdd..f417732f9c 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_pt_PT.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_pt_PT.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ro_RO.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ro_RO.ts
index 437f3d7e3e..ca641366f5 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ro_RO.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ro_RO.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ru_RU.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ru_RU.ts
index b8895f244e..859c1648ef 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ru_RU.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_ru_RU.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Конфигурация
@@ -995,530 +995,540 @@
-
+ <p>Максимальное количество конфигураций окна Заполнения таблицы, сохраняемых в конфигурации программы. 100 конфигураций должно хватить.</p>
-
+ Количество запоминаемых конфигураций заполнения таблицы
-
+ Ширина столбца данных
-
+ <html><head/><body><p>Когда пользователь вводит новое значение в столбец, и оно не умещается в ячейке при текущей ширине столбца, приложение расширит столбец, чтобы уместить новое значение, но не превышая лимит, указанный в опции выше.</p></body></html>
-
+ Расширить столбец при вводе значения длиннее текущей ширины
-
+ <p>При загрузке данных в табличный вид ширина столбцов автоматически подстраивается. Этот параметр ограничивает начальную ширину для подстройки, при этом пользователь может вручную изменить ширину столбца сверх данного лимита.</p>
-
+ Количество строк данных на странице:
-
+ <p>Если данная опция активирована и пользователь наводит указатель мыши на ячейку в любом режиме просмотра данных (результаты запроса, данные таблицы, данные представления), то будет отображена всплывающая подсказка с информацией о ячейке, в том числе информация о типе данных столбца, ограничениях, значение ROWID и прочее.</p>
-
+ Показывать всплывающую подсказку с информацией о столбце и строке при просмотре данных
-
+ <p>Если редактируется ячейка, содержащая NULL, и вводится пустая строка в качестве значения, то эта опция определяет, останется ли в качестве значения ячейки NULL (если опция активирована), или значение будет заменено на пустую строку (если эта опция деактивирована).</p>
-
+ Сохранять значение NULL при вводе пустой строки
-
+ <html><head/><body><p>Активируйте эту опцию, чтобы всегда подставлять значение DEFAULT (значение по умолчанию) при записи NULL в столбец, у которого определено значение DEFAULT, даже если столбец может содержать NULL.</p><p>Отключите эту опцию для подстановки значения DEFAULT только в случае записи NULL в столбец с ограничением NOT NULL.</p></body></html>
-
+ Использовать значение DEFAULT (если оно определено) при записи NULL
-
+ <html><head/><body><p>Если результаты запроса содержат десятки (или сотни) столбцов, они вполне вероятно могут исчерпать всю свободную память компьютера, одномоментно загрузив несколько гигабайт данных. В таких случаях, для защиты компьютера SQLiteStudio может попытаться ограничить количество результатов, отображаемых на одной странице. Если вы уверены, что не работаете с большими объемами в базе данных, то можете отключить это ограничение и всегда видеть заданное в настройках количество строк на странице.</p></body></html>
-
+ Ограничить число строк в случае десятков столбцов
-
+ Вставка новой строки в таблице данных
-
+ Перед текущей выделенной строкой
-
+ После текущей выделенной строки
-
+ В конец области просмотра данных
-
+ Окна таблиц
-
+ <p>Если опция активирована, окна таблиц будут открываться на вкладке данных вместо вкладки со структурой.</p>
-
+ Открывать окна таблиц на вкладке данных
-
+ <p>Если опция активирована, вкладка "Данные" в окнах таблиц будет первой, а не второй по порядку.</p>
-
+ Помещать вкладку данных в окнах таблиц первой
-
+ Окна представлений
-
+ <p>Если опция активирована, окна представлений будут открываться на вкладке данных вместо вкладки со структурой.</p>
-
+ Открывать окна представлений на вкладке данных
-
+ <p>Если опция активирована, вкладка "Данные" в окнах представлений будет первой, а не второй по порядку.</p>
-
+ Помещать вкладку данных в окнах представлений первой
-
+ Типы данных
-
+ Доступные редакторы:
-
+ Выбранные редакторы для этого типа данных:
-
+ Редактирование схемы
-
+ Количество сохраняемых в истории изменений DDL.
-
+ Размер истории DDL:
-
+ Не показывать диалог предпросмотра DDL при подтверждении изменений схемы
-
+ SQL запросы
-
-
+
+ Количество сохраняемых в истории запросов.
-
+ <html><head/><body><p>Если в окне редактора SQL более одного запроса, то (если эта опция включена) будет выполняться только один запрос - тот, на котором стоит курсор клавиатуры. В противном случае будут выполнены все запросы. Вы всегда можете указать запросы, подлежащие выполнению, выделив эти запросы перед запуском. Вы также можете использовать специальные сочетания клавиш для выполнения запросов в том или ином режиме (сейчас настроено на %1 для выполнения одного запроса и %2 для выполнения всех запросов).</p></body></html>
-
+ Размер истории:
-
-
+
+ <p>Максимальное количество параметров запроса (:param, @param, $param, ?), сохраняемых в истории. Когда вы повторно используете параметр с тем же именем/расположением, SQLiteStudio предварительно инициализирует его последним запомненным значением (которое затем можно изменить). 1000 параметров должно хватить.</p>
-
+ Выполнять только запрос под курсором
-
+ Количество запоминаемых параметров запроса
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>При загрузке данных в табличном виде ширина столбцов автоматически подстраивается. Это значение ограничивает ширину для автоподстройки, но пользователь может вручную расширить столбец сверх этого лимита. Этот лимит также используется при расширении столбца после ввода нового, более длинного значения пользователем (см. опцию ниже).</p></body></html>
-
+ Ограничить автоматическую ширину столбца данных (в пикселях):
-
+ <html><head/><body><p>Исходная ширина столбцов будет установлена так, чтобы как минимум уместилось полное имя столбца в заголовке. При этом учитывается ограничение на автоматическую ширину столбца, указанное в пикселях (опция выше).</p></body></html>
-
+ Как минимум уместить полное имя столбца в ширину
-
+ <html><head/><body><p>Если опция включена, строки длиннее ширины окна редактора будут перенесены и горизонтальная прокрутка не потребуется.</p></body></html>
-
+ Переносить строки в редакторе SQL
-
+ <html><head/><body><p>Подсвечивать весь запрос, на котором стоит курсор клавиатуры. Это запрос, который будет выполнен при нажатии кнопки или сочетания клавиш "Выполнить запрос" (если не настроено иначе).</p></body></html>
-
+ Подсвечивать текущий запрос
-
+ Обновления
-
+ Автоматически проверять обновления при запуске
-
+ Сессия
-
+ Восстановить предыдущую сессию (активные MDI окна) после запуска
-
+ Разрешить одновременную работу нескольких экземпляров приложения
-
+ Окно статуса
-
+ <p>Если пользователь вручную закрыл окно статуса, включение данной опции гарантирует, что при появлении новых сообщений окно статуса будет автоматически открыто. Если опция отключена, окно статуса может быть заново открыто только пользователем вручную через меню "Вид".</p>
-
+ Всегда открывать окно статуса при появлении нового сообщения
-
+ Синтаксическая расцветка кода
-
+ Цвет ключевого слова
-
+ Стандартный цвет
-
+ <html><head/><body><p>Строки в SQL заключены в символы одинарных кавычек. В других языках строка может быть заключена в двойные кавычки или как-нибудь иначе.</p></body></html>
-
+ Цвет строки
-
+ Цвет комментария
-
+ <html><head/><body><p>Допустимыми объектами являются имена таблиц, индексов, триггеров или представлений, которые имеются в базе данных SQLite. Языки, отличные от SQL, могут использовать этот цвет для других своих элементов.</p></body></html>
-
+ Цвет распознанных объектов
-
+ <html><head/><body><p>В редакторе SQL текущий запрос подсвечивается этим фоном, чтобы указать пользователю, какой запрос будет выполняться в данный момент.</p></body></html>
-
+ Фон текущего запроса
-
+ <html><head/><body><p>Подстановочные параметры определяют места, куда позже будут вставлены значения, переданные пользователем. Они указываются в одной из форм:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Языки, отличные от SQL, могут использовать этот цвет для других своих элементов.</p></body></html>
-
+ Цвет подстановочных параметров
-
+ Фон текущей строки
-
+ <html><head/><body><p>При перемещении курсора клавиатуры к любой скобке в коде, приложение выделит эту скобку и соответствующую ей другую этим цветом фона.</p></body></html>
-
+ Фон парных скобок
-
+ <html><head/><body><p>Вы можете полностью отключить подсветку текущего запроса на странице Общих настроек.</p></body></html>
-
+ Цвет числа
-
+ <html><head/><body><p>Данные типа BLOB — это бинарные данные, представляемые в виде шестнадцатеричных чисел, например:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ Цвет данных типа BLOB
-
+ Цвет парных скобок
-
+ Сбросить к исходным
-
+ Фильтруйте горячие клавиши по имени или комбинации клавиш
-
+ Действие
-
+ Комбинация клавиш
-
-
+
+ Язык
-
+ Для смены языка потребуется перезапустить приложение.
-
+ Компактный режим
-
+ <p>В компактном режиме все поля и отступы в интерфейсе минимизированы для отображения большего количества данных. Интерфейс станет чуть менее эстетичным, однако это позволит уместить больше данных на экране.</p>
-
+ Включить компактный режим
-
+ Области прикрепления вокруг главного окна
-
+ Углы занимают правая и левая области
-
+ Углы занимают верхняя и нижняя области
-
+ Скрыть встроенные модули
-
+ Текущий стиль:
-
+ Предпросмотр
-
+ Активно
-
+ Неактивно
-
+ Активный модуль форматирования
-
+ Шрифт редактора SQL
-
+ Шрифт списка баз данных
-
+ Шрифт дополнительных меток в списке баз данных
-
+ Шрифт просмотра данных
-
+ Шрифт окна статуса
-
+ Настройки автодополнения
-
+ <html><head/><body><p>Если эта опция включена, окно автодополнения будет вызываться в случае, когда пользователь например набирает <span style=" font-weight:700;">tableName.</span> чтобы предложить вставить имя столбца. Если опция отключена, пользователь должен нажать комбинацию клавиш для вызова автодополнения.</p></body></html>
-
+ Автоматически показывать окно автодополнения когда вводится точка после имени объекта
@@ -5495,7 +5505,7 @@ find next
-
+ Невозможно редактировать данную ячейку. Подробности: %1
@@ -5506,17 +5516,17 @@ find next
-
+ Структура этой таблицы изменилась с момента последней загрузки данных. Перезагрузите данные для продолжения.
-
+ Редактирование значений большой длины непосредственно в табличном режиме не рекомендуется. Возможны проблемы с производительностью и удобством работы. Для работы с такими большими значениями рекомендуется использовать режим формы либо отдельное окно редактирования значения (доступно в контекстном меню по щелчку правой кнопкой мыши).
-
+ Внешний ключ для столбца %2 имеет более чем %1 возможных значений. Это слишком много для отображения в выпадающем списке. Вам необходимо ввести значение вручную.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_sk_SK.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_sk_SK.ts
index ce2ab586a1..a9eb234c9b 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_sk_SK.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_sk_SK.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Konfigurácia
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Počet data riadkov na stranu:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Okná tabuľky
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Zobraziť dáta po otvorení tabuľky
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ Okná pohľadov
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Zobraziť dáta po otvorení pohľadu
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Datové typy
-
+ Dostupné editory:
-
+ Editors selected for this data type:
-
+ Úprava schémy
-
+ Počet DDL zmien uchovávaných v histórii.
-
+ Veľkosť DDL histórie:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL dotazy
-
-
+
+ Počet dotazov uchovávaných v histórii.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ Veľkosť SQL histórie:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Vykonať len dotaz, na ktorom stojí kurzor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Aktualizácie
-
+ Kontrolovať aktualizácie pri štarte
-
+ Sedenie
-
+ Obnoviť posledné sedenie (aktívne okná) pri štarte
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filtrovať podľa názvu alebo klávesovej skratky
-
+ Akcia
-
+ Klávesová skratka
-
-
+
+ Jazyk
-
+ Je potrebné reštartovať aplikáciu aby sa zmena jazyka prejavila.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Nezobrazovať interné pluginy
-
+ Aktuálny štýl:
-
+ Náhľad
-
+ Zapnutý
-
+ Vypnutý
-
+ Aktívny formátovací plugin
-
+ Písmo SQL editora
-
+ Font zoznamu databáz
-
+ Font doplnkového popisku
-
+ Font dát
-
+ Font status okna
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ nájsť ďalší
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ nájsť ďalší
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_sr_SP.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_sr_SP.ts
index c18d848696..cbf61717dc 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_sr_SP.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_sr_SP.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_sv_SE.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_sv_SE.ts
index 08b57a53c1..745804b423 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_sv_SE.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_sv_SE.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_tr_TR.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_tr_TR.ts
index 5eb0f519fc..b7a9dc7490 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_tr_TR.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_tr_TR.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Yapılandırma
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ Geçmiş boyutu:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Güncellemeler
-
+ Automatically check for updates at startup
-
+ Oturum
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Eylem
-
+ Anahtar Kombinasyonu
-
-
+
+ Dil
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Ön İzleme
-
+ Etkin
-
+ Devre dışı
-
+ Active formatter plugin
-
+ SQL düzenleyici yazı tipi
-
+ Veritabanı listesi yazı tipi
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_uk_UA.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_uk_UA.ts
index b63f6ca60a..0973b142d8 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_uk_UA.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_uk_UA.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_vi_VN.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_vi_VN.ts
index faa5265218..ad5aa6e24a 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_vi_VN.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_vi_VN.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ Configuration
@@ -995,530 +995,540 @@
-
+ <p>Maximum number of configurations of Populate Table dialog stored in configuration. Value of 100 should be sufficient.</p>
-
+ Number of memorized table populating configurations
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit.</p>
-
+ Number of data rows per page:
-
+ <p>When this is enabled and user holds mouse pointer over a cell in any data view (query results, a table data, a view data) a tooltip will appear with details about the cell - it includes details like column data type, constraints, ROWID and others.</p>
-
+ Show column and row details tooltip in data view
-
+ <p>When editing a cell which used to have NULL value and entering empty string as new value, then this option determinates whether the new value should remain NULL (have this option enabled), or should it be overwritten with empty string value (have this option disabled).</p>
-
+ Keep NULL value when entering empty value
-
+ <html><head/><body><p>Enable this to always enforce DEFAULT value when committing a NULL value for a column that has DEFAULT value defined, even though the column is allowed to contain NULL values.</p><p>Disable this option to use DEFAULT value exclusively when NULL value is committed for column with NOT NULL constraint.</p></body></html>
-
+ Use DEFAULT value (if defined), when committing NULL value
-
+ <html><head/><body><p>If query results contain dozens (or hundreds) of columns, it is more likely that it will exhaust free memory of your computer by loading several gigabytes of data at once. SQLiteStudio may try to limit number of results displayed on one page in such cases to protect your computer. If you know that you don't work with big values in database, you can disable this limit and you will always see as many rows as defined per page.</p></body></html>
-
+ Limit number of rows for in case of dozens of columns
-
+ Inserting new row in data grid
-
+ Before currently selected row
-
+ After currently selected row
-
+ At the end of data view
-
+ Table windows
-
+ <p>When enabled, Table Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open Table Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every Table Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a Table Window
-
+ View windows
-
+ <p>When enabled, View Windows will show up with the data tab, instead of the structure tab.</p>
-
+ Open View Windows with the data tab for start
-
+ <p>When enabled the "Data" tab will be placed as first tab in every View Window, instead of being at second place.</p>
-
+ Place data tab as first tab in a View Window
-
+ Data types
-
+ Available editors:
-
+ Editors selected for this data type:
-
+ Schema editing
-
+ Number of DDL changes kept in history.
-
+ DDL history size:
-
+ Don't show DDL preview dialog when committing schema changes
-
+ SQL queries
-
-
+
+ Number of queries kept in the history.
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ History size:
-
-
+
+ <p>Maximum number of query parameters (:param, @param, $param, ?) stored in history. When you re-use parameter with the same name/position, SQLiteStudio will pre-initialize it with most recent memorized value (you will still be able to change it). Value of 1000 should be sufficient.</p>
-
+ Execute only the query under the cursor
-
+ Number of memorized query parameters
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ Updates
-
+ Automatically check for updates at startup
-
+ Session
-
+ Restore last session (active MDI windows) after startup
-
+ Allow multiple instances of the application at the same time
-
+ Status Field
-
+ <p>When user manually closes the Status panel, this option makes sure that if any new message is printed in the Status panel it will be reopened. If it's disabled, then Status panel can only be open manually by the user from the "View" menu.</p>
-
+ Always open Status panel when new message is printed
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ Filter shortcuts by name or key combination
-
+ Action
-
+ Key combination
-
-
+
+ Language
-
+ Changing language requires application restart to take effect.
-
+ Compact layout
-
+ <p>Compact layout reduces all margins and spacing on the UI to minimum, making space for displaying more data. It makes the interface a little bit less aesthetic, but allows to display more data at once.</p>
-
+ Use compact layout
-
+ Main window dock areas
-
+ Left and right areas occupy corners
-
+ Top and bottom areas occupy corners
-
+ Hide built-in plugins
-
+ Current style:
-
+ Preview
-
+ Enabled
-
+ Disabled
-
+ Active formatter plugin
-
+ SQL editor font
-
+ Database list font
-
+ Database list additional label font
-
+ Data view font
-
+ Status field font
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5498,7 +5508,7 @@ find next
-
+ Cannot edit this cell. Details: %1
@@ -5509,17 +5519,17 @@ find next
-
+ Structure of this table has changed since last data was loaded. Reload the data to proceed.
-
+ Editing a huge contents in an inline cell editor is not a good idea. It can become slow and inconvenient. It's better to edit such big contents in a Form View, or in popup editor (available under rick-click menu).
-
+ Foreign key for column %2 has more than %1 possible values. It's too much to display in drop down list. You need to edit value manually.
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_zh_CN.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_zh_CN.ts
index 5b17927a1d..4cd29cc262 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_zh_CN.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_zh_CN.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ 配置
@@ -995,530 +995,540 @@
-
+ <p>在配置文件中存储,“表填充”对话框中的最大数量。值 100 应已足够。</p>
-
+ 表填充配置中的默认填充行数
-
+ 数据列宽度
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>当数据被加载到网格视图时,列宽会自动调整。此值限制初始化时的列宽度,之后您仍可以手动调整列宽,不受此限制。</p>
-
+ 每页数据行数:
-
+ <p>此项启用后,用户鼠标悬停在任意数据视图(查询结果、表数据、视图数据)的单元格上时,工具提示将显示该单元格的详细信息——包括列数据类型、约束、ROWID 等。</p>
-
+ 在数据视图中展示列与行的详细信息
-
+ <p>编辑一个过去为 NULL 值的单元格且新输入的值为空字符串时,此选项启用则该单元格的值保持 NULL 不变,此选项未启用则空字符串覆盖原 NULL 值。</p>
-
+ 当输入空值时保持 NULL 值
-
+ <html><head/><body><p>启用此选项后,提交一个 NULL 值时,如果该列已定义 DEFAULT 值,即使该列允许包含 NULL 值,也始终采用 DEFAULT 值。</p><p>禁用此选项则仅在列有非空(NOT NULL)约束时将 NULL 值转变为 DEFAULT 值。</p></body></html>
-
+ 提交 NULL 值时使用 DEFAULT 值(如果已定义)
-
+ <html><head/><body><p>如果查询结果包含数十乃至上百个列,则加载可能占用数个 GB 的空闲内存。SQLiteStudio 在这种情况下可能限制一页上显示的结果数量以保护您的计算机。如果您了解自己不会在如此大的数据库上作业,则可以禁用此限制以始终在一页上看到大量的行。</p></body></html>
-
+ 列数过多时限制每页显示的行数
-
+ 网格视图中插入新行时
-
+ 在选中行之前
-
+ 在选中行之后
-
+ 在数据视图的末尾
-
+ 表窗口
-
+ <p>启用后,表窗口将显示数据选项卡,而不是结构选项卡。</p>
-
+ 打开表窗口时显示“数据”选项卡
-
+ <p>启用后,“数据”选项卡将作为第一个选项卡放置在每个表窗口中,而不是位于第二位。</p>
-
+ 将数据作为表窗口的第一项
-
+ 视图窗口
-
+ <p>启用后,视图窗口将显示数据选项卡,而不是结构选项卡。</p>
-
+ 打开视图窗口时显示“数据”选项卡
-
+ <p>启用后,“数据”选项卡将作为第一个选项卡放置在每个视图窗口中,而不是位于第二个位置。</p>
-
+ 将“数据”选项卡放置为视图窗口的首个选项卡
-
+ 数据类型
-
+ 可用的编辑器:
-
+ 已为该数据类型选择的编辑器:
-
+ 结构编辑
-
+ DDL 变更历史的记录数量。
-
+ DDL 历史大小:
-
+ 提交结构更改时不显示 DDL 预览对话框
-
+ SQL 查询
-
-
+
+ 查询历史记录数量。
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ 历史大小:
-
-
+
+ <p>历史记录中存储查询参数(:param, @param, $param, ?)的最大数量。当您重新在同一名称/位置下使用参数时,SQLiteStudio 将使用最近记忆的值预填充初始化它(仍可修改)。值 1000 应已足够。</p>
-
+ 只执行输入符所在行的语句
-
+ 默认的查询参数数量
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ 更新
-
+ 启动时自动检查更新
-
+ 会话
-
+ 启动后恢复上一次会话
-
+ 允许同时打开多个此程序
-
+ 状态栏
-
+ <p>在用户手动关闭了状态面板后,此选项能确保有新消息被出现时状态面板自动被重新开启。如果禁用,状态面板只能由用户手动通过“视图”菜单来重新开启。</p>
-
+ 有新消息输出时就打开状态面板
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ 以名称或按键组合筛选快捷键
-
+ 操作
-
+ 按键组合
-
-
+
+ 语言
-
+ 语言变更在程序重启后生效。
-
+ 紧凑布局
-
+ <p>紧凑布局会将界面中的边框与留白减至最小,然后用这些区域展示更多数据。这会使界面看起来有一点不美观,但将可以同时展示更多的数据。</p>
-
+ 使用紧凑布局
-
+ 主窗口停靠区域
-
+ 左右布局
-
+ 上下布局
-
+ 隐藏内置插件
-
+ 当前风格:
-
+ 预览
-
+ 已启用
-
+ 已禁用
-
+ 启用格式化插件
-
+ SQL 编辑器字体
-
+ 数据库列表字体
-
+ 数据库列表额外信息字体
-
+ 数据视图字体
-
+ 状态栏字体
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5496,7 +5506,7 @@ find next
-
+ 无法编辑此单元格。详情:%1
@@ -5507,17 +5517,17 @@ find next
-
+ 在上次加载数据后,此表的结构已更改。重新加载数据以继续。
-
+ 在内联单元格编辑器中编辑大型内容不是一个好主意。它很可能变得缓慢和不便。最好在表单视图或者弹出式编辑器(从右键菜单打开)中编辑此类大内容。
-
+ 列 %2 的外键有超过 %1 个可能的值。这太多而不能显示在下拉列表。您需要手动编辑值。
diff --git a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_zh_TW.ts b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_zh_TW.ts
index 5bb57b22cc..2960be2174 100644
--- a/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_zh_TW.ts
+++ b/SQLiteStudio3/guiSQLiteStudio/translations/guiSQLiteStudio_zh_TW.ts
@@ -828,7 +828,7 @@
ConfigDialog
-
+ 設定檔
@@ -995,530 +995,540 @@
-
+ <p>在設定檔檔案中儲存,“表填充”對話方塊中的最大數量。值 100 應已足夠。</p>
-
+ 表填充設定檔中的預設填充行數
-
+ Data column width
-
+ <html><head/><body><p>When user enters new value into column and the value is bigger than the current column width, the application will enlarge the column to fit the new value, but not wider than the limit defined in the option above.</p></body></html>
-
+ Enlarge column when entering value longer than current width
-
+ <p>當資料被載入到網格檢視時,列寬會自動調整。此值限制初始化時的列寬度,之後您仍可以手動調整列寬,不受此限制。</p>
-
+ 每頁資料行數:
-
+ <p>此項啟用後,使用者滑鼠懸停在任意資料檢視 (查詢結果、表資料、檢視資料) 的單元格上時,工具提示將顯示該單元格的詳細資訊——包括列資料型別、約束、ROWID 等。</p>
-
+ 在資料檢視中展示列與行的詳細資訊
-
+ <p>編輯一個過去為 NULL 值的單元格且新輸入的值為空字串時,此選項啟用則該單元格的值保持 NULL 不變,此選項未啟用則空字串覆蓋原 NULL 值。</p>
-
+ 當輸入空值時保持 NULL 值
-
+ <html><head/><body><p>啟用此選項後,提交一個 NULL 值時,如果該列已定義 DEFAULT 值,即使該列允許包含 NULL 值,也始終採用 DEFAULT 值。</p><p>禁用此選項則僅在列有非空 (NOT NULL) 約束時將 NULL 值轉變為 DEFAULT 值。</p></body></html>
-
+ 提交 NULL 值時使用 DEFAULT 值 (如果已定義)
-
+ <html><head/><body><p>如果查詢結果包含數十乃至上百個列,則載入可能佔用數個 GB 的空閒記憶體。SQLiteStudio 在這種情況下可能限制一頁上顯示的結果數量以保護您的計算機。如果您瞭解自己不會在如此大的資料庫上作業,則可以禁用此限制以始終在一頁上看到大量的行。</p></body></html>
-
+ 列數過多時限制每頁顯示的行數
-
+ 網格檢視中插入新行時
-
+ 在選中行之前
-
+ 在選中行之後
-
+ 在資料檢視的末尾
-
+ 表視窗
-
+ <p>啟用後,表視窗將顯示資料選項卡,而不是結構選項卡。</p>
-
+ 開啟表視窗時顯示“資料”選項卡
-
+ <p>啟用後,“資料”選項卡將作為第一個選項卡放置在每個表視窗中,而不是位於第二位。</p>
-
+ 將資料作為表視窗的第一項
-
+ 檢視視窗
-
+ <p>啟用後,檢視視窗將顯示資料選項卡,而不是結構選項卡。</p>
-
+ 開啟檢視視窗時顯示“資料”選項卡
-
+ <p>啟用後,“資料”選項卡將作為第一個選項卡放置在每個檢視視窗中,而不是位於第二個位置。</p>
-
+ 將“資料”選項卡放置為檢視視窗的首個選項卡
-
+ 資料型別
-
+ 可用的編輯器:
-
+ 已為該資料型別選擇的編輯器:
-
+ 結構編輯
-
+ DDL 變更歷史的記錄數量。
-
+ DDL 歷史大小:
-
+ 提交結構更改時不顯示 DDL 預覽對話方塊
-
+ SQL 查詢
-
-
+
+ 查詢歷史記錄數量。
-
+ <html><head/><body><p>If there is more than one query in the SQL editor window, then (if this option is enabled) only a single query will be executed - the one under the keyboard insertion cursor. Otherwise all queries will be executed. You can always limit queries to be executed by selecting those queries before calling to execute. You can also use dedicated shortcuts for executing in one mode or the other (currently configured to %1 for single query execution and %2 for all queries execution).</p></body></html>
-
+ 歷史大小:
-
-
+
+ <p>歷史記錄中儲存查詢引數 (:param, @param, $param, ?) 的最大數量。當您重新在同一名稱/位置下使用引數時,SQLiteStudio 將使用最近記憶的值預填充初始化它 (仍可修改)。值 1000 應已足夠。</p>
-
+ 只執行輸入符所在行的語句
-
+ 預設的查詢引數數量
-
+
+
+
+
+
+
+
+
+
+
+ <html><head/><body><p>When the data is read into grid view columns width is automatically adjusted. This value limits the initial width for the adjustment, but user can still resize the column manually over this limit. This value is also used when enlarging column upon new, longer value entered by the user (see option below).</p></body></html>
-
+ Limit automatic data column width to (in pixels):
-
+ <html><head/><body><p>Initial width of data columns will be set to at least show complete name of the column in the header. This can still be overwritten by the initial limit of column width specified in pixels (the setting above).</p></body></html>
-
+ Keep at least the width to show complete column name
-
+ <html><head/><body><p>If enabled, lines longer than the editor width will be wrapped, so horizontal scrolling will not be needed.</p></body></html>
-
+ Wrap lines in SQL editor
-
+ <html><head/><body><p>Highlights entire query that is currently under the insertion cursor. It's the same query that will be executed when you hit "Execute query" hotkey or button (unless configured otherwise).</p></body></html>
-
+ Highlight current query
-
+ 更新
-
+ 啟動時自動檢查更新
-
+ 會話
-
+ 啟動後恢復上一次會話
-
+ 允許同時開啟多個此程式
-
+ 狀態列
-
+ <p>在使用者手動關閉了狀態面板後,此選項能確保有新訊息被出現時狀態面板自動被重新開啟。如果禁用,狀態面板只能由使用者手動透過“檢視”選單來重新開啟。</p>
-
+ 有新訊息輸出時就開啟狀態面板
-
+ Code syntax colors
-
+ Keyword foreground
-
+ Regular foreground
-
+ <html><head/><body><p>In SQL strings are enclosed with single quote characters. In other languages string may be enclosed with double quote, or something else.</p></body></html>
-
+ String foreground
-
+ Comment foreground
-
+ <html><head/><body><p>Valid objects are name of tables, indexes, triggers, or views that exist in the SQLite database. Languages other than SQL may use this color setting for their other, distinct language parts.</p></body></html>
-
+ Valid objects foreground
-
+ <html><head/><body><p>In SQL current query is highlighted with this background to indicate to the user which query would be executed at certain moment.</p></body></html>
-
+ Current query background
-
+ <html><head/><body><p>Bind parameters are placeholders for values yet to be provided by the user. They have one of the forms:</p><p>:param_name</p><p>$param_name</p><p>@param_name</p><p>?</p><p><br/></p><p>Languages other than SQL may use this color setting for their other, distinct syntax parts.</p></body></html>
-
+ Bind parameter foreground
-
+ Current line background
-
+ <html><head/><body><p>When user moves the insertion cursor at any parenthesis in the code, the application will mark this parenthesis and its matched counterparty with this background color.</p></body></html>
-
+ Matched parenthesis background
-
+ <html><head/><body><p>You can disable current query highlighting entirely on the General settings page.</p></body></html>
-
+ Number foreground
-
+ <html><head/><body><p>BLOB values are binary values represented as hexadecimal numbers, like:</p><p>X'12B4'</p><p>x'46A2F4'</p><p><br/></p></body></html>
-
+ BLOB value foreground
-
+ Matched parenthesis foreground
-
+ Reset to defaults
-
+ 以名稱或按鍵組合篩選快捷鍵
-
+ 操作
-
+ 按鍵組合
-
-
+
+ 語言
-
+ 語言變更在程式重啟後生效。
-
+ 緊湊佈局
-
+ <p>緊湊佈局會將介面中的邊框與留白減至最小,然後用這些區域展示更多資料。這會使介面看起來有一點不美觀,但將可以同時展示更多的資料。</p>
-
+ 使用緊湊佈局
-
+ 主視窗停靠區域
-
+ 左右佈局
-
+ 上下佈局
-
+ 隱藏內建外掛
-
+ 當前風格:
-
+ 預覽
-
+ 已啟用
-
+ 已禁用
-
+ 啟用格式化外掛
-
+ SQL 編輯器字型
-
+ 資料庫清單字型
-
+ 資料庫清單額外資訊字型
-
+ 資料檢視字型
-
+ 狀態列字型
-
+ Code assistant settings
-
+ <html><head/><body><p>If this option is enabled, the code assistant will be triggered in cases, when user types for example <span style=" font-weight:700;">tableName.</span> to propose columns of the table. If the option is disabled, user will have to hit the assistant hotkey explicitly.</p></body></html>
-
+ Automatically trigger the assistant after a dot is typed after an object name
@@ -5496,7 +5506,7 @@ find next
-
+ 無法編輯此單元格。詳情:%1
@@ -5507,17 +5517,17 @@ find next
-
+ 在上次載入資料後,此表的結構已更改。重新載入資料以繼續。
-
+ 在內聯單元格編輯器中編輯大型內容不是一個好主意。它很可能變得緩慢和不便。最好在表單檢視或者彈出式編輯器 (從右鍵選單開啟) 中編輯此類大內容。
-
+ 列 %2 的外來鍵有超過 %1 個可能的值。這太多而不能顯示在下拉清單。您需要手動編輯值。