source: gnome/gnome-3-0/yelp-xsl.gnome-3-0.bg.po@ 2310

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

yelp-xsl: подаден в master и gnome-3-0

File size: 42.6 KB
Line 
1# Bulgarian translation of yelp-xsl po-file.
2# Copyright (C) 2004, 2006, 2007, 2009, 2011 Free Software Foundation, Inc
3# This file is distributed under the same license as the gnome-doc-utils package.
4# Alexander Shopov <ash@kambanaria.org>, 2004, 2006, 2007, 2009, 2011
5#
6msgid ""
7msgstr ""
8"Project-Id-Version: yelp-xsl gnome-3-0\n"
9"Report-Msgid-Bugs-To: \n"
10"POT-Creation-Date: 2011-05-10 05:53+0300\n"
11"PO-Revision-Date: 2011-05-10 06:44+0300\n"
12"Last-Translator: Alexander Shopov <ash@kambanaria.org>\n"
13"Language-Team: Bulgarian <dict@fsa-bg.org>\n"
14"Language: bg\n"
15"MIME-Version: 1.0\n"
16"Content-Type: text/plain; charset=UTF-8\n"
17"Content-Transfer-Encoding: 8bit\n"
18"Plural-Forms: nplurals=2; plural=n != 1;\n"
19
20#.
21#. This is used as a list item seperator for inline lists of exactly two
22#. elements. A list of two names would be formatted as "Tom and Dick".
23#.
24#: ../xslt/gettext/l10n.xml.in.h:5
25msgid " and "
26msgstr " и "
27
28#.
29#. This is used to offset an inline description from a title. This is
30#. typically used on title and refpurpose of a refentry element, which
31#. models the structure of a man page.
32#.
33#: ../xslt/gettext/l10n.xml.in.h:11
34msgid " — "
35msgstr " — "
36
37#.
38#. This is used a simple list item seperator in places where simple
39#. inline lists have to be constructed dynamically. Using the default
40#. string of ", ", a list would look like this: A, B, C, D. Using the
41#. nonsensical string " - ", a list would look like this: A - B - C - D.
42#.
43#: ../xslt/gettext/l10n.xml.in.h:18
44msgid ", "
45msgstr ", "
46
47#.
48#. This is used as the final separator in an inline list of three or
49#. more elements. The string ", " will be used to separate all but
50#. the last pair of elements. Using these two strings, a list of
51#. names would be formatted as "Tom, Dick, and Harry".
52#.
53#: ../xslt/gettext/l10n.xml.in.h:25
54msgid ", and "
55msgstr " и "
56
57#.
58#. This is a special format message. Please read the full translator
59#. documentation before translating this message. The documentation
60#. is maintained as part of the stylesheet documentation in DocBook.
61#. For your convenience, it has also been converted to an HTML file
62#. named STYLESHEETS.xml in the i18n directory.
63#.
64#. This is a format message used to format tooltips on cross references
65#. to bibliography entries.
66#.
67#. Special elements in the message will be replaced with the
68#. appropriate content, as follows:
69#.
70#. label - The term being defined by the glossary entry
71#.
72#. These should be written as empty XML elements. Due to limitations
73#. in intltool, I can't write XML content in translator comments. To
74#. insert the label, simply write left angle bracket, label, slash,
75#. right angle bracket.
76#.
77#. Additionally, format messages can use the i, b, and tt markup tags
78#. to mark text as italic, bold, and monospace.
79#.
80#: ../xslt/gettext/l10n.xml.in.h:49
81msgid ""
82"<msgid>biblioentry.tooltip</msgid> <msgstr>View the bibliography entry "
83"<label/>.</msgstr>"
84msgstr "<msgstr>Проверете „<label/>“ в библиографията.</msgstr>"
85
86#.
87#. This is a special format message. Please read the full translator
88#. documentation before translating this message. The documentation
89#. is maintained as part of the stylesheet documentation in DocBook.
90#. For your convenience, it has also been converted to an HTML file
91#. named STYLESHEETS.xml in the i18n directory.
92#.
93#. biblioentry - An entry in a bibliography
94#. bibliomixed - An entry in a bibliography
95#. http://www.docbook.org/tdg/en/html/biblioentry.html
96#. http://www.docbook.org/tdg/en/html/bibliomixed.html
97#.
98#. This is a format message used to format the labels for entries in
99#. a bibliography. The content of the label is often an abbreviation
100#. of the authors' names and the year of publication. In English,
101#. these are generally formatted with [square brackets] surrounding
102#. them.
103#.
104#. This string is similar to citation.format, but they are used in
105#. different places. The citation formatter is used when referencing
106#. a bibliography entry in running prose. This formatter is used for
107#. the actual bibliography entry. You may use the same formatting for
108#. both, but you don't have to.
109#.
110#. Special elements in the message will be replaced with the
111#. appropriate content, as follows:
112#.
113#. bibliolabel - The text content of the bibliography label
114#.
115#. These should be written as empty XML elements. Due to limitations
116#. in intltool, I can't write XML content in translator comments. To
117#. insert the label, simply write left angle bracket, bibliolabel,
118#. slash, right angle bracket.
119#.
120#. Additionally, format messages can use the i, b, and tt markup tags
121#. to mark text as italic, bold, and monospace.
122#.
123#: ../xslt/gettext/l10n.xml.in.h:87
124msgid "<msgid>bibliolabel.format</msgid> <msgstr>[<bibliolabel/>]</msgstr>"
125msgstr "<msgstr>[<bibliolabel/>]</msgstr>"
126
127#.
128#. This is a special format message. Please read the full translator
129#. documentation before translating this message. The documentation
130#. is maintained as part of the stylesheet documentation in DocBook.
131#. For your convenience, it has also been converted to an HTML file
132#. named STYLESHEETS.xml in the i18n directory.
133#.
134#. citetitle - An inline bibliographic reference to another published work
135#. http://docbook.org/tdg/en/html/citation.html
136#.
137#. This is a format message used to format inline citations to other
138#. published works. The content is typically an abbreviation of the
139#. authors' last names. In English, this abbreviation is usually
140#. written inside [square brackets].
141#.
142#. Special elements in the message will be replaced with the
143#. appropriate content, as follows:
144#.
145#. citation - The text content of the citation element, possibly
146#. as a link to an entry in the bibliography
147#.
148#. These should be written as empty XML elements. Due to limitations
149#. in intltool, I can't write XML content in translator comments. To
150#. insert the citation, simply write left angle bracket, citation,
151#. slash, right angle bracket.
152#.
153#. Additionally, format messages can use the i, b, and tt markup tags
154#. to mark text as italic, bold, and monospace.
155#.
156#: ../xslt/gettext/l10n.xml.in.h:117
157msgid "<msgid>citation.format</msgid> <msgstr>[<citation/>]</msgstr>"
158msgstr "<msgstr>[<citation/>]</msgstr>"
159
160#.
161#. This is a special format message. Please read the full translator
162#. documentation before translating this message. The documentation
163#. is maintained as part of the stylesheet documentation in DocBook.
164#. For your convenience, it has also been converted to an HTML file
165#. named STYLESHEETS.xml in the i18n directory.
166#.
167#. citetitle - The title of a cited work
168#. http://docbook.org/tdg/en/html/citetitle.html
169#.
170#. This is a format message used to format inline title citations.
171#. This template uses roles to control how the citation is formatted.
172#. The role indicates the type of work being cited, and is taken from
173#. the pubwork attribute of the citetitle element.
174#.
175#. Special elements in the message will be replaced with the
176#. appropriate content, as follows:
177#.
178#. node - The text content of the citetitle element
179#.
180#. These should be written as empty XML elements. Due to limitations
181#. in intltool, I can't write XML content in translator comments. To
182#. insert the node, simply write left angle bracket, node, slash,
183#. right angle bracket.
184#.
185#. Additionally, format messages can use the i, b, and tt markup tags
186#. to mark text as italic, bold, and monospace.
187#.
188#: ../xslt/gettext/l10n.xml.in.h:146
189msgid ""
190"<msgid>citetitle.format</msgid> <msgstr role='article'>“<node/>”</msgstr> "
191"<msgstr><i><node/></i></msgstr>"
192msgstr ""
193"<msgstr role='article'>„<node/>“</msgstr>\n"
194"<msgstr><i><node/></i></msgstr>"
195
196#.
197#. This is a special format message. Please read the full translator
198#. documentation before translating this message. The documentation
199#. is maintained as part of the stylesheet documentation in DocBook.
200#. For your convenience, it has also been converted to an HTML file
201#. named STYLESHEETS.xml in the i18n directory.
202#.
203#. comment - Editorial comments
204#. cite - The source of a comment
205#. http://projectmallard.org/1.0/mal_block_comment.html
206#. http://projectmallard.org/1.0/mal_block_cite.html
207#.
208#. This is a format message used to format the citation of a comment
209#. made by an editor of a document. This appears on a new line after
210#. the title of the comment, if a title is present, or as the first
211#. line if a title is not present.
212#.
213#. This string is used when both the name and the date are supplied.
214#. In English, a title together with this format string might produce
215#. something like this:
216#.
217#. Some Comment Title
218#. from Shaun McCance on 2010-06-03
219#.
220#. Here is the text of the comment.
221#.
222#. If only a name is supplied, and no date, then comment.cite.name.format
223#. is used instead of this string.
224#.
225#. Special elements in the message will be replaced with the
226#. appropriate content, as follows:
227#.
228#. comment.name - The name of the person making the comment
229#. comment.date - The date the comment was made
230#.
231#. These should be written as empty XML elements, e.g. <comment.name/>
232#.
233#. Additionally, format messages can use the i, b, and tt markup tags
234#. to mark text as italic, bold, and monospace.
235#.
236#: ../xslt/gettext/l10n.xml.in.h:187
237msgid ""
238"<msgid>comment.cite.name-date.format</msgid> <msgstr>from <comment.name/> on "
239"<comment.date/></msgstr>"
240msgstr "<msgstr>от <comment.name/> на <comment.date/></msgstr>"
241
242#.
243#. This is a special format message. Please read the full translator
244#. documentation before translating this message. The documentation
245#. is maintained as part of the stylesheet documentation in DocBook.
246#. For your convenience, it has also been converted to an HTML file
247#. named STYLESHEETS.xml in the i18n directory.
248#.
249#. comment - Editorial comments
250#. cite - The source of a comment
251#. http://projectmallard.org/1.0/mal_block_comment.html
252#. http://projectmallard.org/1.0/mal_block_cite.html
253#.
254#. This is a format message used to format the citation of a comment
255#. made by an editor of a document. This appears on a new line after
256#. the title of the comment, if a title is present, or as the first
257#. line if a title is not present.
258#.
259#. This string is used when only the name of the commenter is supplied.
260#. In English, a title together with this format string might produce
261#. something like this:
262#.
263#. Some Comment Title
264#. from Shaun McCance
265#.
266#. Here is the text of the comment.
267#.
268#. If a date is also supplied, then comment.cite.name-date.format
269#. is used instead of this string.
270#.
271#. Special elements in the message will be replaced with the
272#. appropriate content, as follows:
273#.
274#. comment.name - The name of the person making the comment
275#.
276#. These should be written as empty XML elements, e.g. <comment.name/>
277#.
278#. Additionally, format messages can use the i, b, and tt markup tags
279#. to mark text as italic, bold, and monospace.
280#.
281#: ../xslt/gettext/l10n.xml.in.h:227
282msgid ""
283"<msgid>comment.cite.name.format</msgid> <msgstr>from <comment.name/></msgstr>"
284msgstr "<msgstr>от <comment.name/></msgstr>"
285
286#.
287#. This is a special format message. Please read the full translator
288#. documentation before translating this message. The documentation
289#. is maintained as part of the stylesheet documentation in DocBook.
290#. For your convenience, it has also been converted to an HTML file
291#. named STYLESHEETS.xml in the i18n directory.
292#.
293#. This is a format message used to format tooltips on mailto: links
294#. created from DocBook's email element.
295#.
296#. Special elements in the message will be replaced with the
297#. appropriate content, as follows:
298#.
299#. string - The linked-to email address
300#.
301#. These should be written as empty XML elements. Due to limitations
302#. in intltool, I can't write XML content in translator comments. To
303#. insert the email address, simply write left angle bracket, string,
304#. slash, right angle bracket.
305#.
306#. Additionally, format messages can use the i, b, and tt markup tags
307#. to mark text as italic, bold, and monospace.
308#.
309#: ../xslt/gettext/l10n.xml.in.h:251
310msgid ""
311"<msgid>email.tooltip</msgid> <msgstr>Send email to ‘<string/>’.</msgstr>"
312msgstr "<msgstr>Пращане на е-писмо до <b><tt><string/></tt></b>.</msgstr>"
313
314#.
315#. This is a special format message. Please read the full translator
316#. documentation before translating this message. The documentation
317#. is maintained as part of the stylesheet documentation in DocBook.
318#. For your convenience, it has also been converted to an HTML file
319#. named STYLESHEETS.xml in the i18n directory.
320#.
321#. glossentry - A entry in a glossary or glosslist
322#. http://www.docbook.org/tdg/en/html/glossentry.html
323#.
324#. This is a format message used to format the abbreviations of terms
325#. in glossary entries. An abbreviation for a glossary term can be
326#. provided by an 'acronym' or an 'abbrev' element. For example, a
327#. glossary entry for HTML might look like this:
328#.
329#. Hypertext Markup Language (HTML)
330#. Definition goes here....
331#.
332#. Special elements in the message will be replaced with the
333#. appropriate content, as follows:
334#.
335#. node - The content of the acronym or abbrev element
336#.
337#. These should be written as empty XML elements. Due to limitations
338#. in intltool, I can't write XML content in translator comments. To
339#. insert the content, simply write left angle bracket, node, slash,
340#. right angle bracket.
341#.
342#. Additionally, format messages can use the i, b, and tt markup tags
343#. to mark text as italic, bold, and monospace.
344#.
345#: ../xslt/gettext/l10n.xml.in.h:283
346msgid "<msgid>glossentry.abbrev.format</msgid> <msgstr>(<node/>)</msgstr>"
347msgstr "<msgstr>(<node/>)</msgstr>"
348
349#.
350#. This is a special format message. Please read the full translator
351#. documentation before translating this message. The documentation
352#. is maintained as part of the stylesheet documentation in DocBook.
353#. For your convenience, it has also been converted to an HTML file
354#. named STYLESHEETS.xml in the i18n directory.
355#.
356#. This is a format message used to format tooltips on cross references
357#. to glossary entries.
358#.
359#. Special elements in the message will be replaced with the
360#. appropriate content, as follows:
361#.
362#. glossterm - The term being defined by the glossary entry
363#.
364#. These should be written as empty XML elements. Due to limitations
365#. in intltool, I can't write XML content in translator comments. To
366#. insert the glossterm, simply write left angle bracket, glossterm,
367#. slash, right angle bracket.
368#.
369#. Additionally, format messages can use the i, b, and tt markup tags
370#. to mark text as italic, bold, and monospace.
371#.
372#: ../xslt/gettext/l10n.xml.in.h:307
373msgid ""
374"<msgid>glossentry.tooltip</msgid> <msgstr>Read the definition for "
375"‘<glossterm/>’.</msgstr>"
376msgstr "<msgstr>Проверете дефиницията на „<b><glossterm/></b>“.</msgstr>"
377
378#.
379#. This is a special format message. Please read the full translator
380#. documentation before translating this message. The documentation
381#. is maintained as part of the stylesheet documentation in DocBook.
382#. For your convenience, it has also been converted to an HTML file
383#. named STYLESHEETS.xml in the i18n directory.
384#.
385#. This is a format message used to format cross references to glossary
386#. entries. Multiple roles can be provided to allow document translators to
387#. select how to format each cross reference using the xrefstyle attribute.
388#. If your language needs to provide different cross reference formattings
389#. for different parts of speech, you should provide multiple roles for
390#. cross reference formatters.
391#.
392#. In addition, the 'glosssee' role will be used for cross references
393#. from glosssee or glossseealso elements. These are used in other
394#. glossary entries to direct the user to the linked-to entry.
395#.
396#. Special elements in the message will be replaced with the
397#. appropriate content, as follows:
398#.
399#. glossterm - The term being defined by the glossary entry
400#.
401#. These should be written as empty XML elements. Due to limitations
402#. in intltool, I can't write XML content in translator comments. To
403#. insert the glossterm, simply write left angle bracket, glossterm,
404#. slash, right angle bracket.
405#.
406#. Additionally, format messages can use the i, b, and tt markup tags
407#. to mark text as italic, bold, and monospace.
408#.
409#: ../xslt/gettext/l10n.xml.in.h:339
410msgid ""
411"<msgid>glossentry.xref</msgid> <msgstr role='glosssee'><glossterm/></msgstr> "
412"<msgstr>‘<glossterm/>’</msgstr>"
413msgstr ""
414"<msgstr role='glosssee'><b><glossterm/></b></msgstr>\n"
415"<msgstr>„<b><glossterm/></b>“</msgstr>"
416
417#.
418#. This is a special format message. Please read the full translator
419#. documentation before translating this message. The documentation
420#. is maintained as part of the stylesheet documentation in DocBook.
421#. For your convenience, it has also been converted to an HTML file
422#. named STYLESHEETS.xml in the i18n directory.
423#.
424#. glosssee - A cross reference from one glossentry to another
425#. http://docbook.org/tdg/en/html/glosssee.html
426#.
427#. This is a format message used to format glossary cross references.
428#. This format message controls the sentence used to present the cross
429#. reference, not the link itself. For the formatting of the actual
430#. link, see the message glossentry.xref.
431#.
432#. One or more glosssee elements are presented as a links to the user
433#. in the glossary, formatted as a single prose sentence. For example,
434#. if the user is being directed to the entry "foo", the glosssee may
435#. be formatted as "See foo."
436#.
437#. Special elements in the message will be replaced with the
438#. appropriate content, as follows:
439#.
440#. glosssee - The actual link or links of the cross reference
441#.
442#. These should be written as empty XML elements. Due to limitations
443#. in intltool, I can't write XML content in translator comments. To
444#. insert the glosssee, simply write left angle bracket, glosssee,
445#. slash, right angle bracket.
446#.
447#. Additionally, format messages can use the i, b, and tt markup tags
448#. to mark text as italic, bold, and monospace.
449#.
450#: ../xslt/gettext/l10n.xml.in.h:373
451msgid "<msgid>glosssee.format</msgid> <msgstr>See <glosssee/>.</msgstr>"
452msgstr "<msgstr>Виж <b><glosssee/></b>.</msgstr>"
453
454#.
455#. This is a special format message. Please read the full translator
456#. documentation before translating this message. The documentation
457#. is maintained as part of the stylesheet documentation in DocBook.
458#. For your convenience, it has also been converted to an HTML file
459#. named STYLESHEETS.xml in the i18n directory.
460#.
461#. glossseealso - A cross reference from one glossentry to another
462#. http://docbook.org/tdg/en/html/glossseealso.html
463#.
464#. This is a format message used to format glossary cross references.
465#. This format message controls the sentence used to present the cross
466#. reference, not the link itself. For the formatting of the actual
467#. link, see the message glossentry.xref.
468#.
469#. One or more glossseealso elements are presented as a links to the
470#. user in the glossary, formatted as a single prose sentence. For
471#. example, if the user is being directed to the entries "foo", "bar",
472#. and "baz", the glossseealso may be formatted as "See also foo, bar,
473#. baz."
474#.
475#. Special elements in the message will be replaced with the
476#. appropriate content, as follows:
477#.
478#. glosssee - The actual link or links of the cross reference
479#.
480#. These should be written as empty XML elements. Due to limitations
481#. in intltool, I can't write XML content in translator comments. To
482#. insert the glosssee, simply write left angle bracket, glosssee,
483#. slash, right angle bracket.
484#.
485#. Additionally, format messages can use the i, b, and tt markup tags
486#. to mark text as italic, bold, and monospace.
487#.
488#: ../xslt/gettext/l10n.xml.in.h:408
489msgid ""
490"<msgid>glossseealso.format</msgid> <msgstr>See also <glosssee/>.</msgstr>"
491msgstr "<msgstr>Виж също <b><glosssee/></b>.</msgstr>"
492
493#.
494#. This is a special format message. Please read the full translator
495#. documentation before translating this message. The documentation
496#. is maintained as part of the stylesheet documentation in DocBook.
497#. For your convenience, it has also been converted to an HTML file
498#. named STYLESHEETS.xml in the i18n directory.
499#.
500#. manvolnum - A reference volume number
501#. http://docbook.org/tdg/en/html/manvolnum.html
502#.
503#. This is a format message used to format manvolnum elements.
504#. A manvolnum is typically a number or short string used to
505#. identify a section of man pages. It is typically placed
506#. inside parentheses.
507#.
508#. Special elements in the message will be replaced with the
509#. appropriate content, as follows:
510#.
511#. node - The text content of the manvolnum element
512#.
513#. These should be written as empty XML elements. Due to limitations
514#. in intltool, I can't write XML content in translator comments. To
515#. insert the node, simply write left angle bracket, node, slash,
516#. right angle bracket.
517#.
518#. Additionally, format messages can use the i, b, and tt markup tags
519#. to mark text as italic, bold, and monospace.
520#.
521#: ../xslt/gettext/l10n.xml.in.h:437
522msgid "<msgid>manvolnum.format</msgid> <msgstr>(<node/>)</msgstr>"
523msgstr "<msgstr>(<node/>)</msgstr>"
524
525#.
526#. The number formatter used for question numbers. This can be one of
527#. "1", "A", "a", "I", or "i", without the quotes. These formatters
528#. provide the following results:
529#.
530#. 1 2 3 4 5 6 7 8 9 10 11 12 13 14
531#. A B C D E F G H I J K L M N
532#. a b c d e f g h i j k l m n
533#. I II III IV V VI VII VIII IX X XI XII XIII XIV
534#. i ii iii iv v vi vii viii ix x xi xii xiii xiv
535#.
536#. Non-Western languages probably need additional formatters. Please
537#. contact the maintainers about adding formatters for your language.
538#.
539#: ../xslt/gettext/l10n.xml.in.h:452
540msgid "<msgid>question.digit</msgid> <msgstr>1</msgstr>"
541msgstr "<msgstr>1</msgstr>"
542
543#.
544#. This is a special format message. Please read the full translator
545#. documentation before translating this message. The documentation
546#. is maintained as part of the stylesheet documentation in DocBook.
547#. For your convenience, it has also been converted to an HTML file
548#. named STYLESHEETS.xml in the i18n directory.
549#.
550#. This is a format message used to format labels for questions in
551#. question-and-answer sets. Labels are used before the question
552#. both in the question-and-answer list and in table of questions
553#. listings. Multiple roles can be used to provide different
554#. formattings for different uses of labels. The following roles
555#. may be used with this format message:
556#.
557#. header - Used for labels inside the question-and-answer set
558#. li - Used for labels in table of questions listings
559#.
560#. Special elements in the message will be replaced with the
561#. appropriate content, as follows:
562#.
563#. number - The number of the question in its containing qandaset
564#.
565#. These should be written as empty XML elements. Due to limitations
566#. in intltool, I can't write XML content in translator comments. To
567#. insert the number, simply write left angle bracket, number, slash,
568#. right angle bracket.
569#.
570#. Additionally, format messages can use the i, b, and tt markup tags
571#. to mark text as italic, bold, and monospace.
572#.
573#: ../xslt/gettext/l10n.xml.in.h:483
574msgid ""
575"<msgid>question.label</msgid> <msgstr role='header'><number/>.&#x2003;</"
576"msgstr> <msgstr role='li'><number/>.&#x2002;</msgstr> <msgstr>Question "
577"<number/></msgstr>"
578msgstr ""
579"<msgstr role='header'><number/>.&#x2003;</msgstr>\n"
580"<msgstr role='li'><number/>.&#x2002;</msgstr>\n"
581"<msgstr><b>Въпрос №&#x00A0;<number/></b></msgstr>"
582
583#.
584#. This is a special format message. Please read the full translator
585#. documentation before translating this message. The documentation
586#. is maintained as part of the stylesheet documentation in DocBook.
587#. For your convenience, it has also been converted to an HTML file
588#. named STYLESHEETS.xml in the i18n directory.
589#.
590#. This is a format message used to format cross references to questions
591#. in question-and-answer sets. Multiple roles can be provided to allow
592#. document translators to select how to format each cross reference
593#. using the xrefstyle attribute. If your language needs to provide
594#. different cross reference formattings for different parts of speech,
595#. you should provide multiple roles for cross reference formatters.
596#.
597#. Special elements in the message will be replaced with the
598#. appropriate content, as follows:
599#.
600#. number - The number of the question in its containing qandaset
601#.
602#. These should be written as empty XML elements. Due to limitations
603#. in intltool, I can't write XML content in translator comments. To
604#. insert the number, simply write left angle bracket, number, slash,
605#. right angle bracket.
606#.
607#. Additionally, format messages can use the i, b, and tt markup tags
608#. to mark text as italic, bold, and monospace.
609#.
610#: ../xslt/gettext/l10n.xml.in.h:511
611msgid "<msgid>question.xref</msgid> <msgstr>Question <number/></msgstr>"
612msgstr "<msgstr>Въпрос №&#x00A0;<number/></msgstr>"
613
614#.
615#. This is a special format message. Please read the full translator
616#. documentation before translating this message. The documentation
617#. is maintained as part of the stylesheet documentation in DocBook.
618#. For your convenience, it has also been converted to an HTML file
619#. named STYLESHEETS.xml in the i18n directory.
620#.
621#. quote - An inline quotation
622#. http://docbook.org/tdg/en/html/quote.html
623#.
624#. This is a format message used to format inline quotations. This template
625#. uses roles to control how the quotation is formatted. The role indicates
626#. whether this is an outer or inner quotation. Quotations nested inside
627#. another quotation are inner quotations. Many languages have an alternate
628#. notation for nested quotations.
629#.
630#. These stylesheets only provide two levels of quotation formatting. If
631#. quote elements are nested deeper, the stylesheets will alternate between
632#. the 'outer' and 'inner' roles. If your language uses different formatting
633#. for deeper quotations, please contact the maintainers, and we will try to
634#. implement a more flexible formatting mechanism.
635#.
636#. Special elements in the message will be replaced with the
637#. appropriate content, as follows:
638#.
639#. node - The text content of the quote element
640#.
641#. These should be written as empty XML elements. Due to limitations
642#. in intltool, I can't write XML content in translator comments. To
643#. insert the node, simply write left angle bracket, node, slash,
644#. right angle bracket.
645#.
646#. Additionally, format messages can use the i, b, and tt markup tags
647#. to mark text as italic, bold, and monospace.
648#.
649#: ../xslt/gettext/l10n.xml.in.h:547
650msgid ""
651"<msgid>quote.format</msgid> <msgstr role='inner'>‘<node/>’</msgstr> "
652"<msgstr>“<node/>”</msgstr>"
653msgstr ""
654"<msgstr role='inner'>«<node/>»</msgstr>\n"
655"<msgstr>„<node/>“</msgstr>"
656
657#.
658#. This is a special format message. Please read the full translator
659#. documentation before translating this message. The documentation
660#. is maintained as part of the stylesheet documentation in DocBook.
661#. For your convenience, it has also been converted to an HTML file
662#. named STYLESHEETS.xml in the i18n directory.
663#.
664#. seealsoie - A “See also” entry in an index, rather than in the text
665#. http://www.docbook.org/tdg/en/html/seealsoie.html
666#.
667#. This is a format message used to format index cross references.
668#. This format message controls the sentence used to present the cross
669#. reference, not the link itself.
670#.
671#. Special elements in the message will be replaced with the
672#. appropriate content, as follows:
673#.
674#. seeie - The actual link or links of the cross reference
675#.
676#. These should be written as empty XML elements. Due to limitations
677#. in intltool, I can't write XML content in translator comments. To
678#. insert the seeie, simply write left angle bracket, seeie, slash,
679#. right angle bracket.
680#.
681#. Additionally, format messages can use the i, b, and tt markup tags
682#. to mark text as italic, bold, and monospace.
683#.
684#: ../xslt/gettext/l10n.xml.in.h:575
685msgid "<msgid>seealsoie.format</msgid> <msgstr>See also <seeie/>.</msgstr>"
686msgstr "<msgstr>Виж също <b><seeie/></b>.</msgstr>"
687
688#.
689#. This is a special format message. Please read the full translator
690#. documentation before translating this message. The documentation
691#. is maintained as part of the stylesheet documentation in DocBook.
692#. For your convenience, it has also been converted to an HTML file
693#. named STYLESHEETS.xml in the i18n directory.
694#.
695#. seeie - A “See” entry in an index, rather than in the text
696#. http://www.docbook.org/tdg/en/html/seeie.html
697#.
698#. This is a format message used to format index cross references.
699#. This format message controls the sentence used to present the cross
700#. reference, not the link itself.
701#.
702#. Special elements in the message will be replaced with the
703#. appropriate content, as follows:
704#.
705#. seeie - The actual link or links of the cross reference
706#.
707#. These should be written as empty XML elements. Due to limitations
708#. in intltool, I can't write XML content in translator comments. To
709#. insert the seeie, simply write left angle bracket, seeie, slash,
710#. right angle bracket.
711#.
712#. Additionally, format messages can use the i, b, and tt markup tags
713#. to mark text as italic, bold, and monospace.
714#.
715#: ../xslt/gettext/l10n.xml.in.h:603
716msgid "<msgid>seeie.format</msgid> <msgstr>See <seeie/>.</msgstr>"
717msgstr "<msgstr>Виж <b><seeie/></b>.</msgstr>"
718
719#.
720#. The number formatter used for synopsis numbers. This can be one of
721#. "1", "A", "a", "I", or "i", without the quotes. These formatters
722#. provide the following results:
723#.
724#. 1 2 3 4 5 6 7 8 9 10 11 12 13 14
725#. A B C D E F G H I J K L M N
726#. a b c d e f g h i j k l m n
727#. I II III IV V VI VII VIII IX X XI XII XIII XIV
728#. i ii iii iv v vi vii viii ix x xi xii xiii xiv
729#.
730#. Non-Western languages probably need additional formatters. Please
731#. contact the maintainers about adding formatters for your language.
732#.
733#: ../xslt/gettext/l10n.xml.in.h:618
734msgid "<msgid>synopfragment.digit</msgid> <msgstr>1</msgstr>"
735msgstr "<msgstr>1</msgstr>"
736
737#.
738#. This is a special format message. Please read the full translator
739#. documentation before translating this message. The documentation
740#. is maintained as part of the stylesheet documentation in DocBook.
741#. For your convenience, it has also been converted to an HTML file
742#. named STYLESHEETS.xml in the i18n directory.
743#.
744#. This is a format message used to format labels for command synopsis
745#. fragments, as well as cross references to them. See the following:
746#.
747#. http://www.docbook.org/tdg/en/html/synopfragment.html
748#. http://www.docbook.org/tdg/en/html/synopfragmentref.html
749#.
750#. Special elements in the message will be replaced with the
751#. appropriate content, as follows:
752#.
753#. number - The number of the synopsis fragment, formatted according
754#. to the synopfragment.digit string
755#.
756#. These should be written as empty XML elements. Due to limitations
757#. in intltool, I can't write XML content in translator comments. To
758#. insert the number, simply write left angle bracket, number, slash,
759#. right angle bracket.
760#.
761#. Additionally, format messages can use the i, b, and tt markup tags
762#. to mark text as italic, bold, and monospace.
763#.
764#: ../xslt/gettext/l10n.xml.in.h:646
765msgid "<msgid>synopfragment.label</msgid> <msgstr>(<number/>)</msgstr>"
766msgstr "<msgstr>(<number/>)</msgstr>"
767
768#. Used as a header before a list of authors.
769#: ../xslt/gettext/l10n.xml.in.h:648
770msgid "<msgstr form='0'>Author</msgstr> <msgstr form='1'>Authors</msgstr>"
771msgstr ""
772"<msgstr form='0'>Автор</msgstr>\n"
773"<msgstr form='1'>Автори</msgstr>"
774
775#. Used as a header before a list of collaborators.
776#: ../xslt/gettext/l10n.xml.in.h:650
777msgid ""
778"<msgstr form='0'>Collaborator</msgstr> <msgstr form='1'>Collaborators</"
779"msgstr>"
780msgstr ""
781"<msgstr form='0'>Сътрудник</msgstr>\n"
782"<msgstr form='1'>Сътрудници</msgstr>"
783
784#. Used as a header before a list of copyrights.
785#: ../xslt/gettext/l10n.xml.in.h:652
786msgid ""
787"<msgstr form='0'>Copyright</msgstr> <msgstr form='1'>Copyrights</msgstr>"
788msgstr ""
789"<msgstr form='0'>Авторско право</msgstr>\n"
790"<msgstr form='1'>Авторски права</msgstr>"
791
792#. Used as a header before a list of editors.
793#: ../xslt/gettext/l10n.xml.in.h:654
794msgid "<msgstr form='0'>Editor</msgstr> <msgstr form='1'>Editors</msgstr>"
795msgstr ""
796"<msgstr form='0'>Редактор</msgstr>\n"
797"<msgstr form='1'>Редактори</msgstr>"
798
799#. Used as a header before a list of contributors.
800#: ../xslt/gettext/l10n.xml.in.h:656
801msgid ""
802"<msgstr form='0'>Other Contributor</msgstr> <msgstr form='1'>Other "
803"Contributors</msgstr>"
804msgstr ""
805"<msgstr form='0'>Допълнителен сътрудник</msgstr>\n"
806"<msgstr form='1'>Допълнителни сътрудници</msgstr>"
807
808#. Used as a header before a list of publishers.
809#: ../xslt/gettext/l10n.xml.in.h:658
810msgid ""
811"<msgstr form='0'>Publisher</msgstr> <msgstr form='1'>Publishers</msgstr>"
812msgstr ""
813"<msgstr form='0'>Издател</msgstr>\n"
814"<msgstr form='1'>Издатели</msgstr>"
815
816#. Used as a header before a list of translators.
817#: ../xslt/gettext/l10n.xml.in.h:660
818msgid ""
819"<msgstr form='0'>Translator</msgstr> <msgstr form='1'>Translators</msgstr>"
820msgstr ""
821"<msgstr form='0'>Преводач</msgstr>\n"
822"<msgstr form='1'>Преводачи</msgstr>"
823
824#.
825#. http://www.docbook.org/tdg/en/html/qandaentry.html
826#.
827#. This is used as a label before answers in a question-and-answer
828#. set. Typically, answers are simply numbered and answers are not
829#. labelled at all. However, DocBook allows document authors to set
830#. the labelling style for a qandaset. If the labelling style is set
831#. to 'qanda', this string will be used to label answers.
832#.
833#: ../xslt/gettext/l10n.xml.in.h:670
834msgid "A:&#x2003;"
835msgstr "О:&#x00A0;"
836
837#. Used for links to the titlepage.
838#: ../xslt/gettext/l10n.xml.in.h:672
839msgid "About This Document"
840msgstr "Информация за документа"
841
842#.
843#. http://www.docbook.org/tdg/en/html/affiliation.html
844#.
845#. This is used as a label before affiliations when listing
846#. authors and other contributors to the document. For example:
847#.
848#. Shaun McCance
849#. Affiliation: GNOME Documentation Project
850#.
851#: ../xslt/gettext/l10n.xml.in.h:682
852msgid "Affiliation"
853msgstr "Връзка с физически или юридически лица"
854
855#. Used as a title for a bibliography.
856#: ../xslt/gettext/l10n.xml.in.h:684
857msgid "Bibliography"
858msgstr "Библиография"
859
860#.
861#. http://www.docbook.org/tdg/en/html/caution.html
862#. This is used as a default title for caution elements.
863#.
864#: ../xslt/gettext/l10n.xml.in.h:689
865msgid "Caution"
866msgstr "Внимание"
867
868#.
869#. http://www.docbook.org/tdg/en/html/colophon.html
870#. This is used as a default title for colophon elements.
871#.
872#: ../xslt/gettext/l10n.xml.in.h:694
873msgid "Colophon"
874msgstr "Послеслов"
875
876#. Used as the title of the listing of subsections
877#: ../xslt/gettext/l10n.xml.in.h:696
878msgid "Contents"
879msgstr "Съдържание"
880
881#.
882#. http://www.docbook.org/tdg/en/html/dedication.html
883#. This is used as a default title for dedication elements.
884#.
885#: ../xslt/gettext/l10n.xml.in.h:701
886msgid "Dedication"
887msgstr "Посвещение"
888
889#.
890#. This is used as a description for the status of the document.
891#. This will not be visibile to the users.
892#.
893#. Draft: the authors have written all the content, but they still need
894#. to clean up the language or markup.
895#.
896#: ../xslt/gettext/l10n.xml.in.h:709
897msgid "Draft"
898msgstr "Чернова"
899
900#.
901#. http://www.docbook.org/tdg/en/html/affiliation.html
902#.
903#. This is used as a label before email addresses when listing
904#. authors and other contributors to the document. For example:
905#.
906#. Shaun McCance
907#. Email: shaunm@gnome.org
908#.
909#: ../xslt/gettext/l10n.xml.in.h:719
910msgid "Email"
911msgstr "Е-поща"
912
913#.
914#. This is used as a description for the status of the document.
915#. This will not be visibile to the users.
916#.
917#. Final: a senior member of the documentation team has reviewd the
918#. document and approved it.
919#.
920#: ../xslt/gettext/l10n.xml.in.h:727
921msgid "Final"
922msgstr "Завършено"
923
924#. Automatic further reading section and links
925#: ../xslt/gettext/l10n.xml.in.h:729
926msgid "Further Reading"
927msgstr "За повече информация"
928
929#.
930#. http://www.docbook.org/tdg/en/html/glossary.html
931#. This is used as a default title for glossary elements.
932#.
933#: ../xslt/gettext/l10n.xml.in.h:734
934msgid "Glossary"
935msgstr "Речник"
936
937#.
938#. http://www.docbook.org/tdg/en/html/important.html
939#. This is used as a default title for important elements.
940#.
941#: ../xslt/gettext/l10n.xml.in.h:739
942msgid "Important"
943msgstr "Важно"
944
945#.
946#. This is used as a description for the status of the document.
947#. This will not be visibile to the users.
948#.
949#. Incomplete: the document has the basic structure in place, but the
950#. authors have not yet written all the content.
951#.
952#: ../xslt/gettext/l10n.xml.in.h:747
953msgid "Incomplete"
954msgstr "Незавършен"
955
956#.
957#. http://www.docbook.org/tdg/en/html/index.html
958#. This is used as a default title for index elements.
959#.
960#: ../xslt/gettext/l10n.xml.in.h:752
961msgid "Index"
962msgstr "Индекс"
963
964#.
965#. http://www.docbook.org/tdg/en/html/legalnotice.html
966#. This is used as a default title for legalnotice elements.
967#.
968#: ../xslt/gettext/l10n.xml.in.h:757
969msgid "Legal Notice"
970msgstr "Юридическа информация"
971
972#. Automatic more about section and links
973#: ../xslt/gettext/l10n.xml.in.h:759
974msgid "More About"
975msgstr "Допълнителна информация"
976
977#.
978#. http://www.docbook.org/tdg/en/html/refnamediv.html
979#. This is used as the title for refnamediv elements.
980#.
981#: ../xslt/gettext/l10n.xml.in.h:764
982msgid "Name"
983msgstr "Име"
984
985#. Used as link to the next page in a series.
986#: ../xslt/gettext/l10n.xml.in.h:766
987msgid "Next"
988msgstr "Следващо"
989
990#.
991#. http://www.docbook.org/tdg/en/html/note.html
992#. This is used as a default title for note elements.
993#.
994#: ../xslt/gettext/l10n.xml.in.h:771
995msgid "Note"
996msgstr "Бележка"
997
998#.
999#. Used as a tooltip on play/pause buttons for audio and video objects.
1000#.
1001#: ../xslt/gettext/l10n.xml.in.h:775
1002msgid "Pause"
1003msgstr "Пауза"
1004
1005#.
1006#. Used as a tooltip on play/pause buttons for audio and video objects.
1007#.
1008#: ../xslt/gettext/l10n.xml.in.h:779
1009msgid "Play"
1010msgstr "Изпълнение"
1011
1012#.
1013#. http://www.docbook.org/tdg/en/html/preface.html
1014#. This is used as a default title for preface elements.
1015#.
1016#: ../xslt/gettext/l10n.xml.in.h:784
1017msgid "Preface"
1018msgstr "Предговор"
1019
1020#. Used as link to the previous page in a series.
1021#: ../xslt/gettext/l10n.xml.in.h:786
1022msgid "Previous"
1023msgstr "Предишно"
1024
1025#.
1026#. http://www.docbook.org/tdg/en/html/qandaentry.html
1027#.
1028#. This is used as a label before questions in a question-and-answer
1029#. set. Typically, questions are simply numbered and answers are not
1030#. labelled at all. However, DocBook allows document authors to set
1031#. the labelling style for a qandaset. If the labelling style is set
1032#. to 'qanda', this string will be used to label questions.
1033#.
1034#: ../xslt/gettext/l10n.xml.in.h:796
1035msgid "Q:&#x2003;"
1036msgstr "В:&#x00A0;"
1037
1038#.
1039#. This is used as a description for the status of the document.
1040#. This will not be visibile to the users.
1041#.
1042#. Review: the authors consider the document complete.
1043#.
1044#: ../xslt/gettext/l10n.xml.in.h:803
1045msgid "Ready for review"
1046msgstr "За преглед"
1047
1048#.
1049#. http://www.docbook.org/tdg/en/html/revhistory.html
1050#. This is used as a header before the revision history.
1051#.
1052#: ../xslt/gettext/l10n.xml.in.h:808
1053msgid "Revision History"
1054msgstr "История на промените"
1055
1056#.
1057#. Figures can automatically scale images down to fit the page width.
1058#. This is used a tooltip on a link to shrink images back down after
1059#. they've been expanded to full size.
1060#.
1061#: ../xslt/gettext/l10n.xml.in.h:814
1062msgid "Scale images down"
1063msgstr "Намаляване на изображенията"
1064
1065#.
1066#. Used for the <see> element.
1067#. FIXME: this should be a format string.
1068#.
1069#: ../xslt/gettext/l10n.xml.in.h:819
1070msgid "See"
1071msgstr "Виж"
1072
1073#. Automatic see also section and links
1074#: ../xslt/gettext/l10n.xml.in.h:821
1075msgid "See Also"
1076msgstr "Виж също"
1077
1078#.
1079#. This is used as a description for the status of the document.
1080#. This will not be visibile to the users.
1081#.
1082#. Stub: the document has little or basic content, it may have been
1083#. created by developers in order to have it included in the build.
1084#.
1085#: ../xslt/gettext/l10n.xml.in.h:829
1086msgid "Stub"
1087msgstr "Мъниче"
1088
1089#.
1090#. http://www.docbook.org/tdg/en/html/refsynopsisdiv.html
1091#. This is used as the default title for refsynopsisdiv elements.
1092#.
1093#: ../xslt/gettext/l10n.xml.in.h:834
1094msgid "Synopsis"
1095msgstr "Резюме"
1096
1097#.
1098#. http://www.docbook.org/tdg/en/html/tip.html
1099#. This is used as a default title for tip elements.
1100#.
1101#: ../xslt/gettext/l10n.xml.in.h:839
1102msgid "Tip"
1103msgstr "Подсказка"
1104
1105#.
1106#. Figures can automatically scale images down to fit the page width.
1107#. This is used a tooltip on a link to expand images to full size.
1108#.
1109#: ../xslt/gettext/l10n.xml.in.h:844
1110msgid "View images at normal size"
1111msgstr "Нормален размер на изображенията"
1112
1113#.
1114#. http://www.docbook.org/tdg/en/html/warning.html
1115#. This is used as a default title for warning elements.
1116#.
1117#: ../xslt/gettext/l10n.xml.in.h:849
1118msgid "Warning"
1119msgstr "Предупреждение"
1120
1121#.
1122#. Translate to default:RTL if your language should be displayed
1123#. right-to-left, otherwise translate to default:LTR. Do *not*
1124#. translate it to "predefinito:LTR", if it isn't default:LTR
1125#. or default:RTL it will not work
1126#.
1127#: ../xslt/gettext/l10n.xml.in.h:856
1128msgid "default:LTR"
1129msgstr "default:LTR"
1130
1131#.
1132#. This is an image of the opening quotation character for your language.
1133#. The image is used as a watermark on blockquote elements. There are a
1134#. number of different quote characters used by various languages, so the
1135#. image name is translatable. The name of the icon should be of the form
1136#. "yelp-quote-XXXX.png", where XXXX is the Unicode code point of the opening
1137#. quote character. For example, some languages use the double angle quotation
1138#. mark. Translators for these languages should use "yelp-quote-00AB.png".
1139#.
1140#. The image, however, is not automatically created. Do not translate
1141#. this to a value if there isn't a corresponding file in yelp-icons,
1142#. under the directory icons/hicolor/48x48/status.
1143#.
1144#. Languages that use guillemets (angle quotation marks) should use either
1145#. 00AB or 00BB, depending on whether the opening quotation is the left
1146#. guillemet or the right guillemet. Languages that use inverted comma
1147#. quotation marks should use 201C, 201D, or 201E. Single quotation marks
1148#. don't make very nice watermarks, so if you would normally open a quote
1149#. with single quotation marks in your language, use the corresponding
1150#. double quotation mark for the watermark image.
1151#.
1152#: ../xslt/gettext/l10n.xml.in.h:878
1153msgid "yelp-quote-201C.png"
1154msgstr "yelp-quote-201E.png"
Note: See TracBrowser for help on using the repository browser.