Just wanted to point out a quite significant mistake in the Dutch translation of Jamulus. It's mostly apparent on Windows, because of the way ASIO4All works. If a Windows user goes to Settings, there'll be a Device selection, and an Input and Output Channel selection.
Input channel mapping is correctly translated as Invoerkanaal mapping.
But, for some strange reason, Output channel mapping is translated as Uitvoerkanaal in kaart brengen, which is utterly wrong. I would most certainly like to see this corrected, even though I run most of my systems in English. It just pains me to see this mistake on systems which I cannot run in English...
I fail to see how any translator would fail to see an inconsistency like this. Just goes to show how important proofreading actually is, even for software translation.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Describe the bug
There's a quite significant mistake in the Dutch translation of Jamulus.
It's mostly apparent on Windows, because of the way ASIO4All works. If a
Windows user goes to Settings, there'll be a Device selection, and an Input
and Output Channel selection.
Input channel mapping is correctly translated as Invoerkanaal mapping.
Output channel mapping is translated as Uitvoerkanaal in kaart brengen,
which is wrong.
It should have been translated as: Uitvoerkanaal mapping
To Reproduce
Steps to reproduce the behavior:
Set Jamulus up to work in the Dutch language on a Windows machine using
the ASIO4All driver (to ease reproduction; the mistake is likely there on
all platforms).
Click on Instellingen (Settings)’
See error
Expected behavior Output channel mappingshould be translated as Uitvoerkanaal in kaart
brengen
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: Windows, MacOS, Linux (GUI)
Version: 3.6.1
Unfortunately, I cannot provide screenshots of the bug, as it doesn’t occur
on my personal configuration (MacOS with standard sound chip; no
multichannel capabilities). The bug is easy to reproduce on Windows by
using the steps I described.
Regards,
Coen
PS > The link you sent me points me to forms for filing various issues with
the Jamulus website, whereas this is an issue with the software itself.
Just wanted to point out a quite significant mistake in the Dutch translation of Jamulus. It's mostly apparent on Windows, because of the way ASIO4All works. If a Windows user goes to Settings, there'll be a Device selection, and an Input and Output Channel selection.
Input channel mapping is correctly translated as Invoerkanaal mapping.
But, for some strange reason, Output channel mapping is translated as Uitvoerkanaal in kaart brengen, which is utterly wrong. I would most certainly like to see this corrected, even though I run most of my systems in English. It just pains me to see this mistake on systems which I cannot run in English...
I fail to see how any translator would fail to see an inconsistency like this. Just goes to show how important proofreading actually is, even for software translation.
Hi - thanks for this. Would you be able to open a ticket here?
https://github.com/jamulussoftware/jamuluswebsite/issues
If not i can do so on your behalf.
Hi,
Could you do this on my behalf?
You can use the text below as a guide:
Describe the bug
There's a quite significant mistake in the Dutch translation of Jamulus.
It's mostly apparent on Windows, because of the way ASIO4All works. If a
Windows user goes to Settings, there'll be a Device selection, and an Input
and Output Channel selection.
Input channel mapping is correctly translated as Invoerkanaal mapping.
Output channel mapping is translated as Uitvoerkanaal in kaart brengen,
which is wrong.
It should have been translated as: Uitvoerkanaal mapping
To Reproduce
Steps to reproduce the behavior:
the ASIO4All driver (to ease reproduction; the mistake is likely there on
all platforms).
Expected behavior
Output channel mapping should be translated as Uitvoerkanaal in kaart
brengen
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Unfortunately, I cannot provide screenshots of the bug, as it doesn’t occur
on my personal configuration (MacOS with standard sound chip; no
multichannel capabilities). The bug is easy to reproduce on Windows by
using the steps I described.
Regards,
Coen
PS > The link you sent me points me to forms for filing various issues with
the Jamulus website, whereas this is an issue with the software itself.
On Fri, 11 Dec 2020 at 09:21, Gilgongo gilgongojones@users.sourceforge.net
wrote:
OK sure I'll put that in the Jamulus software issues.