Conversation
Added German Translations (Roland Moschel)
| <location filename="../../aboutdlgbase.ui" line="72"/> | ||
| <source>Copyright (C) 2005-2021 The Jamulus Development Team</source> | ||
| <translation type="unfinished"></translation> | ||
| <translatorcomment>Could also stay in english language, since this is also common in german</translatorcomment> |
There was a problem hiding this comment.
What is the philosophy for this used in the other translation files? Is there a common approach?
There was a problem hiding this comment.
I think this is just a comment and will not be shown in the UI?
There was a problem hiding this comment.
I guess the question with this item is whether "The Jamulus Development Team" is effectively a name that doesn't need translating, or a description that does. It's a new topic because it just used to say Volker Fischer (and others).
There was a problem hiding this comment.
Yes, I should have realised that! :)
I'm tempted to say leave the copyright string untranslated unless there's a legal reason to transform it for compliance. That would still not need to change Jamulus Development Team, if we've adopted that as the copyright holder.
(I am not a lawyer....)
There was a problem hiding this comment.
I translated it into german, but IMHO this is something , which one could leave completely in english since it is a kind of common standard ? Isn´t it ?
There was a problem hiding this comment.
I'd also say: Leave it untranslated.
There was a problem hiding this comment.
I think this is just a comment and will not be shown in the UI?
The source will be shown in the UI (if there is no translation), but the translatorcomment will not, of course.
There was a problem hiding this comment.
I don't have any strong opinion on this. So I don't care if it's translated or not.
ann0see
left a comment
There was a problem hiding this comment.
Thank you very much for your first translation! There are some minor points (I added some comments).
| <location filename="../../aboutdlgbase.ui" line="72"/> | ||
| <source>Copyright (C) 2005-2021 The Jamulus Development Team</source> | ||
| <translation type="unfinished"></translation> | ||
| <translatorcomment>Could also stay in english language, since this is also common in german</translatorcomment> |
There was a problem hiding this comment.
I think this is just a comment and will not be shown in the UI?
|
Just checked: There don't seem to be any untranslated things left, which is good! :)
|
Co-authored-by: Christian Hoffmann <[email protected]>
Co-authored-by: Christian Hoffmann <[email protected]>
Co-authored-by: Christian Hoffmann <[email protected]>
Co-authored-by: Christian Hoffmann <[email protected]>
Co-authored-by: Christian Hoffmann <[email protected]>
ann0see
left a comment
There was a problem hiding this comment.
Great! I‘ll approve this now. Thanks for your work. Have a look at my hint, but I don’t think it’s blocking.
| <location filename="../../clientsettingsdlg.cpp" line="150"/> | ||
| <source>Some sound card drivers do not allow the buffer delay to be changed from within the application. In this case the buffer delay setting is disabled and has to be changed using the sound card driver. On Windows, press the ASIO Device Settings button to open the driver settings panel. On Linux, use the Jack configuration tool to change the buffer size.</source> | ||
| <translation type="unfinished"></translation> | ||
| <translation>Einige Audiotreiber verhindern das Umstellen der Puffer-Verzögerung aus einer Anwendung heraus. In diesem Falle wird die Einstellung der Puffer-Verzögerung in Jamulus deaktiviert und sollte daher im Treiber des Audiointerfaces selbst geändert werden. Unter Windows kann man diese Einstellung über den Knopf "ASIO-Geräte-Einstellungen" erreichen. Unter Linux sollte man das Jack-Configuration-Tool verwenden, um die Puffergrösse zu ändern.</translation> |
There was a problem hiding this comment.
Just a small hint here (not sure how this is handled in other translations): usually the name „Jamulus“ is not part of the translation, rather defined by the code so that it’s easy to change it if someone wanted to rename the application.
pljones
left a comment
There was a problem hiding this comment.
My outstanding comments were more about the English. So not appropriate for this PR.
| </message> | ||
| <message> | ||
| <location filename="../../clientsettingsdlg.cpp" line="183"/> | ||
| <source>Opens the driver settings. Note: </source> |
There was a problem hiding this comment.
Not your issue.
Lines 183 to 185 look wrong... It's probably something I've not considered until reviewing the translations... Would it not be easier for a translator to have the full text with substitutions (so, QString ( tr ( "Hello, %1" ) ).arg( getName() )..., giving the context)? Here there are three pieces, one starting with a measurement unit.
#1097 (comment)
That one was a "real hit" for the issue on those lines.
| <location filename="../../aboutdlgbase.ui" line="72"/> | ||
| <source>Copyright (C) 2005-2021 The Jamulus Development Team</source> | ||
| <translation type="unfinished"></translation> | ||
| <translatorcomment>Could also stay in english language, since this is also common in german</translatorcomment> |
There was a problem hiding this comment.
Yes, I should have realised that! :)
I'm tempted to say leave the copyright string untranslated unless there's a legal reason to transform it for compliance. That would still not need to change Jamulus Development Team, if we've adopted that as the copyright holder.
(I am not a lawyer....)
PR for German Translation