Bug 41859

Summary:	translation problem
Product:	PulseAudio	Reporter:	Peter Mráz <etkinator>
Component:	misc	Assignee:	pulseaudio-bugs
Status:	RESOLVED MOVED	QA Contact:	pulseaudio-bugs
Severity:	normal
Priority:	medium	CC:	lennart, piotrdrag, prescott66
Version:	unspecified	Keywords:	i18n, l10n
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Peter Mráz 2011-10-17 01:51:44 UTC

#: ../src/pulse/channelmap.c:484 ../src/pulse/sample.c:170
#: ../src/pulse/volume.c:295 ../src/pulse/volume.c:321
#: ../src/pulse/volume.c:341 ../src/pulse/volume.c:371
msgid "(invalid)"

in Slovak can have word invalid three different gender (neplatný, neplatná, neplatné). Please separate this string (other language can have other gender system) and add comment for translators.

Comment 1 Peter Mráz 2011-10-17 05:54:57 UTC

#: ../src/utils/pactl.c:746 ../src/utils/pactl.c:781
msgid "unknown"
msgstr "neznámy"

same problem is here

Comment 2 Tanu Kaskinen 2015-09-30 11:10:15 UTC

Sorry, this bug was lost and forgotten.

I'm not very familiar with the translation files. How exactly should I do the separation? Where should I put a comment?

Comment 3 Piotr Drąg 2015-09-30 11:19:49 UTC

You should add contexts to these strings, https://wiki.gnome.org/TranslationProject/DevGuidelines/Translation%20contexts

Comment 4 Tanu Kaskinen 2015-09-30 13:03:03 UTC

Thanks, I'll try to fix this. Since we're not a GLib project, we have to define C_() first, and doing that seems to be a bit of a hassle. I'll try to get this done tomorrow, though.

Comment 5 GitLab Migration User 2018-07-30 10:05:51 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/208.

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.