Bug 94781 - Plural forms
Summary: Plural forms
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: misc (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords: i18n, l10n
Depends on:
Blocks:
 
Reported: 2016-04-01 16:18 UTC by Marek Černocký
Modified: 2018-07-30 10:12 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Marek Černocký 2016-04-01 16:18:35 UTC
Messages


"Currently in use: %u blocks containing %s bytes total.\n" (src/utils/pactl.c)

"Allocated during whole lifetime: %u blocks containing %s bytes total.\n" (src/utils/pactl.c)

"Failed to set volume: You tried to set volumes for %d channels, whereas channel/s supported = %d\n" (src/utils/pactl.c)

"snd_pcm_avail() returned a value that is exceptionally large: %lu bytes (%lu ms).\nMost likely this is a bug in the ALSA driver '%s'. Please report this issue to the ALSA developers." (src/modules/alsa/alsa-util.c)

"snd_pcm_delay() returned a value that is exceptionally large: %li bytes (%s%lu ms).\nMost likely this is a bug in the ALSA driver '%s'. Please report this issue to the ALSA developers." (src/modules/alsa/alsa-util.c)

"snd_pcm_mmap_begin() returned a value that is exceptionally large: %lu bytes (%lu ms).\nMost likely this is a bug in the ALSA driver '%s'. Please report this issue to the ALSA developers." (src/modules/alsa/alsa-util.c)

"%s %uch %uHz" (src/pulse/sample.c)


require to use ngettext instead gettext.
Comment 1 GitLab Migration User 2018-07-30 10:12:04 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/263.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.