Skip to content

update German translation (Hotkeys) - #2190

Merged
justinclift merged 1 commit into
sqlitebrowser:v3.12.xfrom
horst-p-w-neubauer:v3.12.x
Apr 18, 2020
Merged

justinclift merged 1 commit into
sqlitebrowser:v3.12.xfrom
horst-p-w-neubauer:v3.12.x

Conversation

@horst-p-w-neubauer

Copy link
Copy Markdown
Member

update German translation (Hotkeys)

some missing Ctrl to Strg and Shift to Umschalt
Trying to replace Return with Enter and Space with Leertaste.

update German translation (Hotkeys)

some missing Ctrl to Strg and Shift to Umschalt
Trying to replace Return with Enter and Space with Leertaste.
@justinclift

Copy link
Copy Markdown
Member

Awesome, thanks @horst-p-w-neubauer.

@FriedrichFroebel I'm merging this in now. If something in it needs changing though, let us know. 😄

@justinclift
justinclift merged commit 5757736 into sqlitebrowser:v3.12.x Apr 18, 2020
@FriedrichFroebel

Copy link
Copy Markdown
Contributor

As long as it works better with it (or just improves understandability without breaking anything), I am fine with it. From time to time I may miss some strings or parts of it (or mis-translate it) and I usually do not test the complete DB4S application with the translations - so some of the German translations may need fixes like in this PR.

@horst-p-w-neubauer

Copy link
Copy Markdown
Member Author

@FriedrichFroebel , I'm preparing an update where I consequently translate 'record' to 'Datensatz'. Actually it switches between 'Zeile' and 'Eintrag'. That update would bring a lot of changes to the translation and I'd prefer to discuss it in advance. I absolutely vote for strict 1:1 transaltion for technical terms like record or row. But I swing between 'Datensatz' or 'Eintrag'. What would You prefer?

@FriedrichFroebel

Copy link
Copy Markdown
Contributor

I would probably prefer the term "Datensatz" in this case. (As I did the translations across multiple days and for different releases, some other translations might be inconsistent as well.)

@horst-p-w-neubauer

Copy link
Copy Markdown
Member Author

I agree. Is there a possibility to share a dictionary and other translation-decissions? That would help to work in teams and to be strict over time and releases.

@mgrojo

mgrojo commented Apr 18, 2020 •

Copy link
Copy Markdown
Member

For the Spanish translation, I like to take a look at the hints and glossary of the KDE Spanish Translation Project. There is an equivalent German project too, which seems very interesting and complete. It includes even a "visual dictionary". Of course, very specific terms used in DB4S should be agreed separately, because they might be missing in KDE.

@FriedrichFroebel

Copy link
Copy Markdown
Contributor

As I do not have any overview about my decisions, I cannot share a dictionary for now. But feel free to create one if you have enough time - either as a working draft inside a dedicated issue, inside the wiki on a page regarding translations in general or by contacting me using e-mail to discuss it (my e-mail is should be available from my commits when viewed locally.)

@justinclift justinclift added this to the 3.13.0 - Future release milestone Apr 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants