source: non-gtk/mailman/bg/300-499.po@ 1831

Last change on this file since 1831 was 1831, checked in by Александър Шопов, 16 years ago

mailman: Разпределяне на съобщенията по брой знаци на съобщение. Името на файла указва броя знаци.

File size: 18.9 KB
Line 
1# Bulgarian translation for GNU MailMan 2.1.12
2# Copyright (C) 2004, 2005, 2006, 2007, 2009 Free Software Foundation, Inc.
3# Alexander Shopov <ash@contact.bg>, 2004, 2005, 2006, 2007, 2009.
4#
5#
6msgid ""
7msgstr ""
8"Project-Id-Version: GNU MailMan 2.1.12\n"
9"POT-Creation-Date: Sun Jan 11 08:28:57 2009\n"
10"PO-Revision-Date: 2009-07-14 08:34+0300\n"
11"Last-Translator: Alexander Shopov <ash@contact.bg>\n"
12"Language-Team: Bulgarian <dict@fsa-bg.org>\n"
13"MIME-Version: 1.0\n"
14"Content-Type: text/plain; charset=UTF-8\n"
15"Content-Transfer-Encoding: 8bit\n"
16"Generated-By: pygettext.py 1.4\n"
17"Plural-Forms: nplurals=2; plural=n != 1;\n"
18
19#: Mailman/Commands/cmd_unsubscribe.py:17
20msgid ""
21"\n"
22" unsubscribe [password] [address=<address>]\n"
23" Unsubscribe from the mailing list. If given, your password must "
24"match\n"
25" your current password. If omitted, a confirmation email will be "
26"sent\n"
27" to the unsubscribing address. If you wish to unsubscribe an address\n"
28" other than the address you sent this request from, you may specify\n"
29" `address=<address>' (no brackets around the email address, and no\n"
30" quotes!)\n"
31msgstr ""
32
33#: Mailman/Gui/Bounce.py:107
34msgid ""
35"How many <em>Your Membership Is Disabled</em> warnings a\n"
36" disabled member should get before their address is removed "
37"from\n"
38" the mailing list. Set to 0 to immediately remove an address "
39"from\n"
40" the list once their bounce score exceeds the threshold. This\n"
41" value must be an integer."
42msgstr ""
43
44#: Mailman/Gui/ContentFilter.py:98
45msgid ""
46"Use this option to remove each message attachment that does\n"
47" not have a matching content type. Requirements and formats "
48"are\n"
49" exactly like <a href=\"?VARHELP=contentfilter/filter_mime_types"
50"\"\n"
51" >filter_mime_types</a>.\n"
52"\n"
53" <p><b>Note:</b> if you add entries to this list but don't add\n"
54" <tt>multipart</tt> to this list, any messages with attachments\n"
55" will be rejected by the pass filter."
56msgstr ""
57
58#: Mailman/Gui/General.py:68
59msgid ""
60"The capitalization of this name can be changed to make it\n"
61" presentable in polite company as a proper noun, or to make an\n"
62" acronym part all upper case, etc. However, the name will be\n"
63" advertised as the email address (e.g., in subscribe "
64"confirmation\n"
65" notices), so it should <em>not</em> be otherwise altered. "
66"(Email\n"
67" addresses are not case sensitive, but they are sensitive to\n"
68" almost everything else :-)"
69msgstr ""
70
71#: Mailman/Gui/General.py:137
72msgid ""
73"The text will be treated as html <em>except</em> that\n"
74" newlines will be translated to &lt;br&gt; - so you can use "
75"links,\n"
76" preformatted text, etc, but don't put in carriage returns "
77"except\n"
78" where you mean to separate paragraphs. And review your changes "
79"-\n"
80" bad html (like some unterminated HTML constructs) can prevent\n"
81" display of the entire listinfo page."
82msgstr ""
83
84#: Mailman/Gui/General.py:244
85msgid ""
86"Set this to yes when this list is intended to cascade only\n"
87" to other mailing lists. When set, meta notices like\n"
88" confirmations and password reminders will be directed to an\n"
89" address derived from the member's address - it will have the\n"
90" value of \"umbrella_member_suffix\" appended to the member's\n"
91" account name."
92msgstr ""
93
94#: Mailman/Gui/General.py:312
95msgid ""
96"List moderators (and list administrators) are sent daily\n"
97" reminders of requests pending approval, like subscriptions to "
98"a\n"
99" moderated list, or postings that are being held for one reason "
100"or\n"
101" another. Setting this option causes notices to be sent\n"
102" immediately on the arrival of new requests as well."
103msgstr ""
104
105#: Mailman/Gui/General.py:353
106msgid ""
107"Administrivia tests will check postings to see whether it's\n"
108" really meant as an administrative request (like subscribe,\n"
109" unsubscribe, etc), and will add it to the the administrative\n"
110" requests queue, notifying the administrator of the new "
111"request,\n"
112" in the process."
113msgstr ""
114
115#: Mailman/Gui/General.py:370
116msgid ""
117"The \"host_name\" is the preferred name for email to\n"
118" mailman-related addresses on this host, and generally should "
119"be\n"
120" the mail host's exchanger address, if any. This setting can "
121"be\n"
122" useful for selecting among alternative names of a host that "
123"has\n"
124" multiple addresses."
125msgstr ""
126
127#: Mailman/Gui/General.py:448
128msgid ""
129"The <b>info</b> attribute you saved\n"
130"contains suspicious HTML that could potentially expose your users to cross-"
131"site\n"
132"scripting attacks. This change has therefore been rejected. If you still "
133"want\n"
134"to make these changes, you must have shell access to your Mailman server.\n"
135"This change can be made with bin/withlist or with bin/config_list by "
136"setting\n"
137"mlist.info.\n"
138" "
139msgstr ""
140
141#: Mailman/Gui/Language.py:72
142msgid ""
143"This is the default natural language for this mailing list.\n"
144" If <a href=\"?VARHELP=language/available_languages\">more than "
145"one\n"
146" language</a> is supported then users will be able to select "
147"their\n"
148" own preferences for when they interact with the list. All "
149"other\n"
150" interactions will be conducted in the default language. This\n"
151" applies to both web-based and email-based messages, but not to\n"
152" email posted by list members."
153msgstr ""
154
155#: Mailman/Gui/NonDigest.py:155
156msgid ""
157"The list addresses should be written in full mail address\n"
158" format (e.g. mailman@example.com). Do not specify this list\n"
159" address mutually in the exclude list configuration page of the\n"
160" other list, or members of both lists won't get any message.\n"
161" Note also that the site administrator may prohibit cross "
162"domain\n"
163" siblings."
164msgstr ""
165
166#: Mailman/Gui/Privacy.py:103
167msgid ""
168"This section allows you to configure subscription and\n"
169" membership exposure policy. You can also control whether this\n"
170" list is public or not. See also the\n"
171" <a href=\"%(admin)s/archive\">Archival Options</a> section for\n"
172" separate archive-related privacy settings."
173msgstr ""
174
175#: Mailman/Gui/Privacy.py:152
176msgid ""
177"Setting this option causes member email addresses to be\n"
178" transformed when they are presented on list web pages (both in\n"
179" text and as links), so they're not trivially recognizable as\n"
180" email addresses. The intention is to prevent the addresses\n"
181" from being snarfed up by automated web scanners for use by\n"
182" spammers."
183msgstr ""
184
185#: Mailman/Gui/Privacy.py:248
186msgid ""
187"Postings from any of these non-members will be automatically\n"
188" accepted with no further moderation applied. Add member\n"
189" addresses one per line; start the line with a ^ character to\n"
190" designate a regular expression match. A line consisting of\n"
191" the @ character followed by a list name specifies another\n"
192" Mailman list in this installation, all of whose member\n"
193" addresses will be accepted for this list."
194msgstr ""
195
196#: Mailman/Gui/Privacy.py:260
197msgid ""
198"Postings from any of these non-members will be immediately\n"
199" and automatically held for moderation by the list moderators.\n"
200" The sender will receive a notification message which will "
201"allow\n"
202" them to cancel their held message. Add member addresses one "
203"per\n"
204" line; start the line with a ^ character to designate a regular\n"
205" expression match."
206msgstr ""
207
208#: Mailman/Gui/Topics.py:85
209msgid ""
210"Each topic keyword is actually a regular expression, which is\n"
211" matched against certain parts of a mail message, specifically "
212"the\n"
213" <code>Keywords:</code> and <code>Subject:</code> message "
214"headers.\n"
215" Note that the first few lines of the body of the message can "
216"also\n"
217" contain a <code>Keywords:</code> and <code>Subject:</code>\n"
218" \"header\" on which matching is also performed."
219msgstr ""
220
221#: Mailman/Gui/Usenet.py:41
222msgid ""
223"This value may be either the name of your news server, or\n"
224" optionally of the format name:port, where port is a port "
225"number.\n"
226"\n"
227" The news server is not part of Mailman proper. You have to\n"
228" already have access to an NNTP server, and that NNTP server "
229"must\n"
230" recognize the machine this mailing list runs on as a machine\n"
231" capable of reading and posting news."
232msgstr ""
233
234#: Mailman/Gui/Usenet.py:95
235msgid ""
236"Mailman prefixes <tt>Subject:</tt> headers with\n"
237" <a href=\"?VARHELP=general/subject_prefix\">text you can\n"
238" customize</a> and normally, this prefix shows up in messages\n"
239" gatewayed to Usenet. You can set this option to <em>No</em> "
240"to\n"
241" disable the prefix on gated messages. Of course, if you turn "
242"off\n"
243" normal <tt>Subject:</tt> prefixes, they won't be prefixed for\n"
244" gated messages either."
245msgstr ""
246
247#: Mailman/Gui/Usenet.py:107
248msgid ""
249"When you tell Mailman to perform a catchup on the newsgroup,\n"
250" this means that you want to start gating messages to the "
251"mailing\n"
252" list with the next new message found. All earlier messages on\n"
253" the newsgroup will be ignored. This is as if you were reading\n"
254" the newsgroup yourself, and you marked all current messages as\n"
255" <em>read</em>. By catching up, your mailing list members will\n"
256" not see any of the earlier messages."
257msgstr ""
258
259#: Mailman/HTMLFormatter.py:152
260msgid ""
261"<p>%(note)s\n"
262"\n"
263" <p>You may have disabled list delivery intentionally,\n"
264" or it may have been triggered by bounces from your email\n"
265" address. In either case, to re-enable delivery, change the\n"
266" %(link)s option below. Contact %(mailto)s if you have any\n"
267" questions or need assistance."
268msgstr ""
269
270#: Mailman/HTMLFormatter.py:164
271msgid ""
272"<p>We have received some recent bounces from your\n"
273" address. Your current <em>bounce score</em> is %(score)s out of "
274"a\n"
275" maximum of %(total)s. Please double check that your subscribed\n"
276" address is correct and that there are no problems with delivery "
277"to\n"
278" this address. Your bounce score will be automatically reset if\n"
279" the problems are corrected soon."
280msgstr ""
281
282#: Mailman/HTMLFormatter.py:194
283msgid ""
284"You will be sent email requesting confirmation, to\n"
285" prevent others from gratuitously subscribing you. Once\n"
286" confirmation is received, your request will be held for "
287"approval\n"
288" by the list moderator. You will be notified of the moderator's\n"
289" decision by email."
290msgstr ""
291
292#: Mailman/Handlers/Hold.py:276
293msgid ""
294"If you reply to this message, keeping the Subject: header intact, Mailman "
295"will\n"
296"discard the held message. Do this if the message is spam. If you reply to\n"
297"this message and include an Approved: header with the list password in it, "
298"the\n"
299"message will be approved for posting to the list. The Approved: header can\n"
300"also appear in the first line of the body of the reply."
301msgstr ""
302
303#: Mailman/MTA/Manual.py:66
304msgid ""
305"The mailing list `%(listname)s' has been created via the through-the-web\n"
306"interface. In order to complete the activation of this mailing list, the\n"
307"proper /etc/aliases (or equivalent) file must be updated. The program\n"
308"`newaliases' may also have to be run.\n"
309"\n"
310"Here are the entries for the /etc/aliases file:\n"
311msgstr ""
312
313#: Mailman/MTA/Manual.py:113
314msgid ""
315"The mailing list `%(listname)s' has been removed via the through-the-web\n"
316"interface. In order to complete the de-activation of this mailing list, "
317"the\n"
318"appropriate /etc/aliases (or equivalent) file must be updated. The program\n"
319"`newaliases' may also have to be run.\n"
320"\n"
321"Here are the entries in the /etc/aliases file that should be removed:\n"
322msgstr ""
323
324#: bin/b4b5-archfix:19
325msgid ""
326"Fix the MM2.1b4 archives.\n"
327"\n"
328"Usage: %(PROGRAM)s [options] file ...\n"
329"\n"
330"Where options are:\n"
331" -h / --help\n"
332" Print this help message and exit.\n"
333"\n"
334"Only use this to `fix' some archive database files that may have gotten\n"
335"written in Mailman 2.1b4 with some bogus data. Use like this from your\n"
336"$PREFIX directory\n"
337"\n"
338"%% %(PROGRAM)s `grep -l _mlist archives/private/*/database/*-article`\n"
339"\n"
340"(note the backquotes are required)\n"
341"\n"
342"You will need to run `bin/check_perms -f' after running this script.\n"
343msgstr ""
344
345#: bin/change_pw:190
346msgid ""
347"The site administrator at %(hostname)s has changed the password for your\n"
348"mailing list %(listname)s. It is now\n"
349"\n"
350" %(notifypassword)s\n"
351"\n"
352"Please be sure to use this for all future list administration. You may "
353"want\n"
354"to log in now to your list and change the password to something more to "
355"your\n"
356"liking. Visit your list admin page at\n"
357"\n"
358" %(adminurl)s\n"
359msgstr ""
360
361#: bin/genaliases:19
362msgid ""
363"Regenerate Mailman specific aliases from scratch.\n"
364"\n"
365"The actual output depends on the value of the `MTA' variable in your mm_cfg."
366"py\n"
367"file.\n"
368"\n"
369"Usage: genaliases [options]\n"
370"Options:\n"
371"\n"
372" -q/--quiet\n"
373" Some MTA output can include more verbose help text. Use this to "
374"tone\n"
375" down the verbosity.\n"
376"\n"
377" -h/--help\n"
378" Print this message and exit.\n"
379msgstr ""
380
381#: bin/list_admins:20
382msgid ""
383"List all the owners of a mailing list.\n"
384"\n"
385"Usage: %(program)s [options] listname ...\n"
386"\n"
387"Where:\n"
388"\n"
389" --all-vhost=vhost\n"
390" -v=vhost\n"
391" List the owners of all the mailing lists for the given virtual "
392"host.\n"
393"\n"
394" --all\n"
395" -a\n"
396" List the owners of all the mailing lists on this system.\n"
397"\n"
398" --help\n"
399" -h\n"
400" Print this help message and exit.\n"
401"\n"
402"`listname' is the name of the mailing list to print the owners of. You can\n"
403"have more than one named list on the command line.\n"
404msgstr ""
405
406#: bin/list_lists:19
407msgid ""
408"List all mailing lists.\n"
409"\n"
410"Usage: %(program)s [options]\n"
411"\n"
412"Where:\n"
413"\n"
414" -a / --advertised\n"
415" List only those mailing lists that are publically advertised\n"
416"\n"
417" --virtual-host-overview=domain\n"
418" -V domain\n"
419" List only those mailing lists that are homed to the given virtual\n"
420" domain. This only works if the VIRTUAL_HOST_OVERVIEW variable is\n"
421" set.\n"
422"\n"
423" -b / --bare\n"
424" Displays only the list name, with no description.\n"
425"\n"
426" -h / --help\n"
427" Print this text and exit.\n"
428"\n"
429msgstr ""
430
431#: bin/mailmanctl:232
432msgid ""
433"The master qrunner lock could not be acquired, because it appears as if "
434"some\n"
435"process on some other host may have acquired it. We can't test for stale\n"
436"locks across host boundaries, so you'll have to do this manually. Or, if "
437"you\n"
438"know the lock is stale, re-run mailmanctl with the -s flag.\n"
439"\n"
440"Lock file: %(LOCKFILE)s\n"
441"Lock host: %(status)s\n"
442"\n"
443"Exiting."
444msgstr ""
445
446#: bin/reset_pw.py:21
447msgid ""
448"Reset the passwords for members of a mailing list.\n"
449"\n"
450"This script resets all the passwords of a mailing list's members. It can "
451"also\n"
452"be used to reset the lists of all members of all mailing lists, but it is "
453"your\n"
454"responsibility to let the users know that their passwords have been "
455"changed.\n"
456"\n"
457"This script is intended to be run as a bin/withlist script, i.e.\n"
458"\n"
459"% bin/withlist -l -r reset_pw listname [options]\n"
460"\n"
461"Options:\n"
462" -v / --verbose\n"
463" Print what the script is doing.\n"
464msgstr ""
465
466#: bin/rmlist:19
467msgid ""
468"Remove the components of a mailing list with impunity - beware!\n"
469"\n"
470"This removes (almost) all traces of a mailing list. By default, the lists\n"
471"archives are not removed, which is very handy for retiring old lists.\n"
472"\n"
473"Usage:\n"
474" rmlist [-a] [-h] listname\n"
475"\n"
476"Where:\n"
477" --archives\n"
478" -a\n"
479" Remove the list's archives too, or if the list has already been\n"
480" deleted, remove any residual archives.\n"
481"\n"
482" --help\n"
483" -h\n"
484" Print this help message and exit.\n"
485"\n"
486msgstr ""
487
488#: bin/transcheck:19
489msgid ""
490"\n"
491"Check a given Mailman translation, making sure that variables and\n"
492"tags referenced in translation are the same variables and tags in\n"
493"the original templates and catalog.\n"
494"\n"
495"Usage:\n"
496"\n"
497"cd $MAILMAN_DIR\n"
498"%(program)s [-q] <lang>\n"
499"\n"
500"Where <lang> is your country code (e.g. 'it' for Italy) and -q is\n"
501"to ask for a brief summary.\n"
502msgstr ""
503
504#: bin/unshunt:20
505msgid ""
506"Move a message from the shunt queue to the original queue.\n"
507"\n"
508"Usage: %(PROGRAM)s [options] [directory]\n"
509"\n"
510"Where:\n"
511"\n"
512" -h / --help\n"
513" Print help and exit.\n"
514"\n"
515"Optional `directory' specifies a directory to dequeue from other than\n"
516"qfiles/shunt. *** Warning *** Do not unshunt messages that weren't\n"
517"shunted to begin with. For example, running unshunt on qfiles/out/\n"
518"will result in losing all the messages in that queue.\n"
519msgstr ""
520
521#: bin/update:19
522msgid ""
523"Perform all necessary upgrades.\n"
524"\n"
525"Usage: %(PROGRAM)s [options]\n"
526"\n"
527"Options:\n"
528" -f/--force\n"
529" Force running the upgrade procedures. Normally, if the version "
530"number\n"
531" of the installed Mailman matches the current version number (or a\n"
532" `downgrade' is detected), nothing will be done.\n"
533"\n"
534" -h/--help\n"
535" Print this text and exit.\n"
536"\n"
537"Use this script to help you update to the latest release of Mailman from\n"
538"some previous version. It knows about versions back to 1.0b4 (?).\n"
539msgstr ""
540
541#: bin/update:254
542msgid ""
543"\n"
544"%(listname)s has both public and private mbox archives. Since this list\n"
545"currently uses private archiving, I'm installing the private mbox archive\n"
546"-- %(o_pri_mbox_file)s -- as the active archive, and renaming\n"
547" %(o_pub_mbox_file)s\n"
548"to\n"
549" %(o_pub_mbox_file)s.preb6\n"
550"\n"
551"You can integrate that into the archives if you want by using the 'arch'\n"
552"script.\n"
553msgstr ""
554
555#: bin/update:807
556msgid ""
557"\n"
558"ERROR:\n"
559"\n"
560"The locks for some lists could not be acquired. This means that either\n"
561"Mailman was still active when you upgraded, or there were stale locks in "
562"the\n"
563"%(lockdir)s directory.\n"
564"\n"
565"You must put Mailman into a quiescent state and remove all stale locks, "
566"then\n"
567"re-run \"make update\" manually. See the INSTALL and UPGRADE files for "
568"details.\n"
569msgstr ""
Note: See TracBrowser for help on using the repository browser.