GNOME Bugzilla – Bug 124701
"Wave" unclear in beast messages
Last modified: 2020-11-17 12:29:03 UTC
#: beast-gtk/bstapp.c:112 msgid "/Wave_s" #: beast-gtk/bstapp.c:114 msgid "/Waves/_Load Wave..." #: beast-gtk/bstapp.c:115 msgid "/Waves/Delete Wave" #: beast-gtk/bstapp.c:116 msgid "/Waves/_Edit Wave..." #: beast-gtk/bstapp.c:121 msgid "/Tools/Wave_s" #: beast-gtk/bstfiledialog.c:497 msgid "Load Wave" #: beast-gtk/bstfiledialog.c:509 beast-gtk/bstfiledialog.c:511 #, c-format msgid "Loading wave `%s'" #. BstWaveRepoShell *self = BST_WAVE_REPO_SHELL (super_shell); #: beast-gtk/bstwavereposhell.c:141 beast-gtk/bstwavereposhell.c:156 msgid "Waves" "Wave" is unclear in these messages -- it could both mean ".WAV file" or a physical wave out of water or sound wave. It would probably be best if these messages were, where appropriate, changed into "wave file", as in other places in beast.
Christian, you are definitly right that the current solution isn't very suitable for translators: Wave refers both to a Wave file and to a virtual audio object called wave. Proposal: Where wave refers to a file, change it to "wave file", where it refers to a virtual object, call it "wave sample", "sample" or something similar - you have to distinguish somehow. regs, Chris
If we have to report beast bugs in bugzilla, then we should really have a beast product... Bug #124696 is also a beast bug.
There're places in beast where, due to screen estate and sometimes context, we really want to say "wave" to two or more things that have different words in other languages. is there *any* way with gettext, to translate a=_("wave") and b=_("wave") in a program so both yield "wave" in the C locale but different strings for a and b in other locales?
Not with gettext itself, but there is functionality allowing message context in glib now (allowing "file format|Wave" and "physical thing on water|Wave", where the thing before the | is not part of the message itself but instead context), see bug 97556 for more information.
*** Bug 168939 has been marked as a duplicate of this bug. ***
This bug report is being closed due to the upcoming shutdown of bugzilla.gnome.org. If this report is still deemed relevant, a new issue can be filed at: https://github.com/tim-janik/beast/issues We apologize for any inconveniences this may cause.