2 # Translators, if you are not familiar with the PO format, gettext
3 # documentation is worth reading, especially sections dedicated to
4 # this format, e.g. by running:
5 # info -n '(gettext)PO Files'
6 # info -n '(gettext)Header Entry'
8 # Some information specific to po-debconf are available at
9 # /usr/share/doc/po-debconf/README-trans
10 # or http://www.debian.org/intl/l10n/po-debconf/README-trans
12 # Developers do not need to manually edit POT or PO files.
17 "Project-Id-Version: beep 1.2.2-16\n"
18 "Report-Msgid-Bugs-To: beep@packages.debian.org\n"
19 "POT-Creation-Date: 2005-06-14 00:09+0200\n"
20 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
21 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
22 "Language-Team: LANGUAGE <LL@li.org>\n"
24 "Content-Type: text/plain; charset=CHARSET\n"
25 "Content-Transfer-Encoding: 8bit\n"
31 "suid root for all, suid root with only group audio executable, not suid at "
38 msgid "How do you want to handle suid root for the beep program?"
45 "beep must be run as root since it needs to access the speaker hardware. "
46 "There are several posibilities to make the program usable: Either only for "
47 "root (no suid bit at all), executable only by users of the group audio, or "
55 "Since each program set as suid root can be a security risk this is not done "
56 "by default. However, the program is quite small (~150 lines of code), so it "
57 "is fairly easy to verify the safety of the code yourself, if you don't trust "