| CARVIEW |
Navigation Menu
-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Update German translation #2193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update German translation #2193
Conversation
update German translatiion this is done * 'record' to 'Datensatz' * 'Constraint' to 'Beschränkungen' in different ways. * 'clause' to 'Anweisung' * strict case-issue 'Rowid' * 'unmittelbar' in stead of 'inline' (context sensitive) * 'vacuum' to 'Komprimierung' * 'commit' to 'abschließen' * don't translate 'Concordance' as it is a trademark * tried to correct or clearify some missunderstandings
|
Please, take this pullrequest as a draft for an open discussion. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure whether not translating some of the strings would be the preferred way. Examples:
- I would tend to rather use "UNIQUE-Beschränkung" instead of translating "unique" into German, as "UNIQUE" is SQL syntax.
- The same for "CHECK-Beschränkung".
- The same for "WITHOUT ROWID".
- I am not sure about whether "Rowid", "rowid" or "ROWID" would be the best choice.
I commented some of the specific findings directly as well.
I agree with "UNIQUE-Beschränkung" and "CHECK-Beschränkung" - great solution! |
upate German translation done: * 'UNIQUE-' and 'CHECK-Beschränkung' * typo * 'collation' to 'Sortierung' * all variaties of 'Message from database [engine]|DB says' to 'DB meldet:'
update German translation done: * 'pattern' to 'Suchmuster' * 'Zu findendes Textpattern unter Einbeziehung der Prüfungen in diesem Fenster' replaced with 'Suchmuster unter Einbeziehung der aktivierten Optionen in diesem Fenster' as I think that is the meaning of 'considering the checks in this frame' but that might be wrong, need help.
update German translation done: * 'Query' to 'Abfrage' * 'Der Syntax' to 'Die Syntax'
update German translation done: * 'stop' to 'abbrechen'
update German translation done: * div. Beugungen * 'Toolbar' to 'Werkzeugleiste'
update German translation done: * 'bar' (context:bar plots) to 'Säule' * bar (context:toolbar) to 'Werkzeugleiste'
update German translation done: * 'log' to 'Protokoll' according to https://community.kde.org/KDE_Localization/de/StandardUebersetzungen
|
Allright. No more commits for today. |
|
Looks like good progress @horst-p-w-neubauer. 😄 |
update German translation done: * 'Statement' to 'Anweisung' * 'Plot' to 'Diagramm' * 'Pane' to 'Fensterbereich' * 'Unterstrichen' instead of 'Unterstreichung' as its siblings are adjectives as well * 'Plain[ ]text' to 'Nur-Text'
|
Now I've checked all items on my todo list. |
|
You have also the possibility of using issues or discussions in our Translators team (which you can join if you want). It's easy to write tables or even paste them from spreadsheets. You lose filtering capabilities, but maybe it is easier to share and edit in group. The wiki would be another option for this kind of coordination, but strangely I could not copy the table there. The syntax is the same, though, so an unsaved issue comment can be used as intermediary for the conversion from spreadsheets to wiki. Another option is using https://dbhub.io/ for storing the dictionary as a DB file. It is then easy to edit it using DB Browser. Here an example:
|
|
I have added a new wiki page at https://github.com/sqlitebrowser/sqlitebrowser/wiki/Translations to maintain the dictionary there. We might want to add a general explanation for the translation workflow as well - if I remember correctly, there have been some discussions regarding the required steps some time ago inside an issue. |
|
Great idea. I love wikis! |
|
Before this pull-request might get merged I wonder, are there any german documentations that rely on the former translations. As this merge is going to change a lot, I don't want to break anything. |
|
Awesome! I've updated the wiki page with the information Martin wrote in #182 (comment)
The only documentation that we have is the wiki (which is currently only English, but it could be translated as well) and the "What's This" information, whose strings are already present in the translation files. |
|
I'm not sure what is the process that comes up with this message: Does it present an artificial produced SQL statement, that might fix the problem or is it the SQL statement that produced the problem and you offer the possibility to fix it and run it manually? |
update German translation * all translated shortcut-Keys set back to root * 'Anzeige des übergenen SQL' to 'Anzeige der übergebenen SQL' as it reffers to 'SQL-Anweisung' (feminin)
|
If there are no more hints I would ask You to commit this request so we can see the translation-result ot the reset shortcuts with the next 3.12 build. BTW - when can we expect to see this? |
|
If we find this working for german - we should do it for the other langs too. |
|
You should probably remove |
|
definitely remove IDE-specific files |
update German translation done: * single SQL as feminin form * 'Panel' to 'Fenster' some clarifications, one typo
This reverts commit ff7f023.
update German translation done: * 'String' to 'Zeichenkette' * 'Modifier' to 'Modifizierer' * 'Timestring' to 'Zeit-Zeichenkette'
|
What's the state of this now? Is it ready to merge? 😄 |
|
I'd like to merge this now, if people feel this is ready? |
|
the conflicted line allready vanished with #2224 |
|
I'm ok to merge this, if you feel it's ready? |
|
I'd say: ready enough to merge. |
|
Awesome, thanks heaps for this too @horst-p-w-neubauer. 😄 |
update German translation
this is done