After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 555967 - [oss4] clarify some translation strings
[oss4] clarify some translation strings
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other All
: Normal normal
: 0.10.24
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-12 00:29 UTC by Fabricio Godoy
Modified: 2010-06-03 19:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Fabricio Godoy 2008-10-12 00:29:09 UTC 
In file "gst-plugins-bad-0.10.8.2.pt_BR.po" I found below message:

#: sys/oss4/oss4-mixer.c:721
msgid "Low"

Imediatelly after "fast" message.
All appears correct whether these messages are related to quality, fast should be worst quality than low.
To break doubts I read Italian translation of same file and I found translated as lento (slow), antonym of fast.
Comments can help translators to correct translation.
Comment 1 Jan Schmidt 2008-10-12 21:56:26 UTC 
That bit of the code has the comment "/* FIXME: translations for common option strings */", and seems to be an array of some strings provided by the OSS APIs, but the strings aren't necessarily related semantically.

It would be good if someone could mark them up with gettext comments to clarify how they should be translated.
Comment 2 Tim-Philipp Müller 2010-06-03 19:26:27 UTC 
commit 972631ae6d9d6e5b69e2e7ff6368347f16093b04
Author: Tim-Philipp Müller <tim.muller@collabora.co.uk>
Date:   Thu Jun 3 17:52:11 2010 +0100

    oss4: add some comments for translators to clarify meaning of "Low"
    
    "Low" etc. are quality settings here (e.g. for the internal resampler).
    Some day when we use GLib's i18n functions we might want to use
    NC_() and g_dpgettext2() here instead of the comments.
    
    Fixes #555967.