Repository navigation
Update Turkish translation - #4252
Merged
Merged
Conversation
Run lupdate against the current source and translate the 56 strings added since v3.13.1: the WSL warnings, the drag and drop/clipboard options, the column search in the table browser, the JSON key sorting and word wrap options, and the descriptions of the newer SQL functions (concat, format, unhex, string_agg and so on).
mgrojo
requested changes
Nov 7, 2026
| @@ -4,105 +4,105 @@ | |||
| <context> | |||
| <name>AboutDialog</name> | |||
| <message> | |||
| <location filename="../AboutDialog.ui" line="14"/> | |||
| <location filename="../home/emin/oss/sqlitebrowser/src/AboutDialog.ui" line="14"/> | |||
Member
There was a problem hiding this comment.
This change is probably the consequence of the way of running lupdate. Could you fix it manually or running lupdate again in the usual path. If it isn't already obsolete, the procedure described in https://github.com/sqlitebrowser/sqlitebrowser/wiki/Release-process#update-translation-strings should do it.
Contributor
Author
There was a problem hiding this comment.
Fixed in 8bf5a0f: I regenerated the file with the command from the release process wiki. The paths are back to ../AboutDialog.ui and so on, and the translations are the same as before.
The previous commit ran lupdate with the output outside src/translations, so every location got an absolute-looking path. Run it the way the release process describes (lupdate src/*.cpp src/*.ui src/*.h -ts src/translations/sqlb_tr.ts) and put the same translations back.
Member
|
Thanks @emincan2000. It's merged now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I ran lupdate against the current source. It added 58 strings to sqlb_tr.ts that were new since the v3.13.1 update. lupdate filled two of them from identical existing texts (JSON and Copy), and I translated the other 56.
The translations cover the WSL warnings and the drag and drop and clipboard options. I also translated the column search in the table browser, the JSON key sorting and cell word wrap options, and the read-only refresh and .db4s.env options. The remaining texts describe the newer SQL functions (concat, concat_ws, format, likelihood, likely, unlikely, octet_length, unhex, string_agg). I kept the wording already used in the file, such as ifade for statement, salt okunur for read-only and günlük modu for journal mode.
Most of the diff comes from lupdate updating line numbers. lrelease reports 1428 finished and none unfinished.
I built current master with Qt 6 and checked the File menu and the General, Database and Data Browser pages of the preferences in Turkish. The new texts show up and fit. The two line "Salt Okunur Son Dosya Kısayolları" label wraps the same way the English one does.