Skip to content

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

Merged
merged 14 commits into from
May 2, 2020

Conversation

horst-p-w-neubauer
Copy link
Member

update German translation

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

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
@horst-p-w-neubauer
Copy link
Member Author

Please, take this pullrequest as a draft for an open discussion.
I' have some concerns with some of my suggestions as well.
e.g. 'Prüfbechräunkung' for 'check constraint'

Copy link
Contributor

@FriedrichFroebel FriedrichFroebel left a 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.

@horst-p-w-neubauer
Copy link
Member Author

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 agree with "UNIQUE-Beschränkung" and "CHECK-Beschränkung" - great solution!
I disagree with "WITHOUT Rowid" as it is also a dialog checkbox label where it might look like a not translated foreign part.

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
@horst-p-w-neubauer
Copy link
Member Author

Allright. No more commits for today.

@justinclift
Copy link
Member

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'
@horst-p-w-neubauer
Copy link
Member Author

Now I've checked all items on my todo list.
I suggest to add a manualy updated dictionary as design-document for the translation-process.
I've attached mine as a draft. I don't know how you use to handle design-documents.
Maybe Excel isn't first choice for erveryone.
dictionary_de.xlsx

@mgrojo
Copy link
Member

mgrojo commented Apr 19, 2020

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:

Quelle Kontext Übersetzung Bemerkungen
bar Diagramme Säulen Säulendiagramme ordnen die Werte von oben nach unten, Balkendiagramme von rechts nach links
bar toolbar Werkzeugleiste siehe: https://community.kde.org/KDE_Localization/de/StandardUebersetzungen
Check-Constraint   CHECK-Beschränkung siehe: #2193
clause SQL Anweisung  
Collation   Sortierung  
commit   abschließen  
Constraint   Beschränkung siehe: #2193
Log   Protokoll siehe: https://community.kde.org/KDE_Localization/de/StandardUebersetzungen
Message from database [engine]DB says   DB meldet Vorschlag: horst-p-w-neubauer
pattern regulärer Ausdruck Suchmuster  
Query   Abfrage  
Record   Datensatz  
Row   Zeile oder Datenbankzeile  
Statement   Anweisung  
stop   abbrechen  
Toolbar   Werkzeugleiste siehe: https://community.kde.org/KDE_Localization/de/StandardUebersetzungen
Unique-Constraint   UNIQUE-Beschränkung siehe: #2193
Vacuum   Komprimierung  

@FriedrichFroebel
Copy link
Contributor

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.

@horst-p-w-neubauer
Copy link
Member Author

Great idea. I love wikis!

@horst-p-w-neubauer
Copy link
Member Author

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.

@mgrojo
Copy link
Member

mgrojo commented Apr 19, 2020

Awesome!

I've updated the wiki page with the information Martin wrote in #182 (comment)

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.

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.

@horst-p-w-neubauer
Copy link
Member Author

horst-p-w-neubauer commented Apr 20, 2020

I'm not sure what is the process that comes up with this message:
<location filename="../sqlitedb.cpp" line="1816"/>
'... Here's the SQL statement which you might want to fix and execute manually:'

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)
@horst-p-w-neubauer
Copy link
Member Author

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?

@horst-p-w-neubauer
Copy link
Member Author

If we find this working for german - we should do it for the other langs too.

@FriedrichFroebel
Copy link
Contributor

You should probably remove .project, .settings/org.eclipse.core.resources.prefs and src/MainWindow.ui.autosave introduced during your last commit from the PR. Maybe we should add these files/directories/file extensions to the .gitignore as well to avoid pushing them again.

@scottfurry
Copy link
Contributor

definitely remove IDE-specific files

update German translation

done:
* single SQL as feminin form
* 'Panel' to 'Fenster'

some clarifications, one typo
update German translation

done:
* 'String' to 'Zeichenkette'
* 'Modifier' to 'Modifizierer'
* 'Timestring' to 'Zeit-Zeichenkette'
@justinclift
Copy link
Member

What's the state of this now? Is it ready to merge? 😄

@justinclift
Copy link
Member

I'd like to merge this now, if people feel this is ready?

@horst-p-w-neubauer
Copy link
Member Author

the conflicted line allready vanished with #2224
Is there anything, I can do?

@justinclift
Copy link
Member

I'm ok to merge this, if you feel it's ready?

@horst-p-w-neubauer
Copy link
Member Author

I'd say: ready enough to merge.

@justinclift justinclift merged commit 912abd1 into sqlitebrowser:v3.12.x May 2, 2020
@justinclift
Copy link
Member

Awesome, thanks heaps for this too @horst-p-w-neubauer. 😄

@horst-p-w-neubauer horst-p-w-neubauer deleted the v3.12.x branch May 2, 2020 18:47
@justinclift justinclift changed the title update German translation Update German translation Jun 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants