1# translation of uz@cyrillic.po to Uzbek
2# This file is distributed under the same license as the PACKAGE package.
3#
4# Nurali Abdurahmonov <mavnur@gmail.com>, 2007.
5msgid ""
6msgstr ""
7"Project-Id-Version: uz@cyrillic\n"
8"Report-Msgid-Bugs-To: \n"
9"POT-Creation-Date: 2007-11-13 10:40+0500\n"
10"PO-Revision-Date: 13.11.2007 10:45\n"
11"Last-Translator: Nurali Abdurahmonov <mavnur@gmail.com>\n"
12"Language-Team: Uzbek\n"
13"Language: uz\n"
14"MIME-Version: 1.0\n"
15"Content-Type: text/plain; charset=UTF-8\n"
16"Content-Transfer-Encoding: 8bit\n"
17"X-Generator: KBabel 1.11.4\n"
18
19#.
20#. This is used as a list item seperator for inline lists of exactly two
21#. elements.  A list of two names would be formatted as "Tom and Dick".
22#.
23#: ../xslt/gettext/l10n.xml.in.h:5
24msgid " and "
25msgstr " va "
26
27#.
28#. This is used to offset an inline description from a title.  This is
29#. typically used on title and refpurpose of a refentry element, which
30#. models the structure of a man page.
31#.
32#: ../xslt/gettext/l10n.xml.in.h:11
33msgid " — "
34msgstr " — "
35
36#.
37#. This is used a simple list item seperator in places where simple
38#. inline lists have to be constructed dynamically.  Using the default
39#. string of ", ", a list would look like this: A, B, C, D.  Using the
40#. nonsensical string " - ", a list would look like this: A - B - C - D.
41#.
42#: ../xslt/gettext/l10n.xml.in.h:18
43msgid ", "
44msgstr ", "
45
46#.
47#. This is used as the final separator in an inline list of three or
48#. more elements.  The string ", " will be used to separate all but
49#. the last pair of elements.  Using these two strings, a list of
50#. names would be formatted as "Tom, Dick, and Harry".
51#.
52#: ../xslt/gettext/l10n.xml.in.h:25
53msgid ", and "
54msgstr ", va "
55
56#.
57#. The number formatter used for appendix numbers.  This can be one of
58#. "1", "A", "a", "I", or "i", without the quotes.  These formatters
59#. provide the following results:
60#.
61#. 1    2    3    4    5    6    7    8    9   10   11   12   13   14
62#. A    B    C    D    E    F    G    H    I    J    K    L    M    N
63#. a    b    c    d    e    f    g    h    i    j    k    l    m    n
64#. I   II  III   IV    V   VI  VII VIII   IX    X   XI  XII XIII  XIV
65#. i   ii  iii   iv    v   vi  vii viii   ix    x   xi  xii xiii  xiv
66#.
67#. Non-Western languages probably need additional formatters.  Please
68#. contact the maintainers about adding formatters for your language.
69#.
70#: ../xslt/gettext/l10n.xml.in.h:40
71msgid "<msgid>appendix.digit</msgid> <msgstr>A</msgstr>"
72msgstr ""
73
74#.
75#. This is a special format message.  Please read the full translator
76#. documentation before translating this message.  The documentation
77#. is maintained as part of the stylesheet documentation in DocBook.
78#. For your convenience, it has also been converted to an HTML file
79#. named STYLESHEETS.xml in the i18n directory.
80#.
81#. This is a format message used to format labels for appendices.  Labels
82#. are used before the title in places like headers and table of contents
83#. listings.  Multiple roles can be used to provide different formattings
84#. for different uses of labels.  The following roles may be used with
85#. this format message:
86#.
87#. header - Used for labels in headers
88#. li     - Used for labels in table of contents listings
89#.
90#. Special elements in the message will be replaced with the
91#. appropriate content, as follows:
92#.
93#. title       - The title of the appendix
94#. titleabbrev - The titleabbrev of the appendix, or just the title
95#. if no titleabbrev exists
96#. number      - The full number of the appendix, possibly including
97#. the number of the parent element
98#.
99#. These should be written as empty XML elements.  Due to limitations
100#. in intltool, I can't write XML content in translator comments.  To
101#. insert the title, simply write left angle bracket, title, slash,
102#. right angle bracket.
103#.
104#. Additionally, format messages can use the i, b, and tt markup tags
105#. to mark text as italic, bold, and monospace.
106#.
107#: ../xslt/gettext/l10n.xml.in.h:74
108msgid ""
109"<msgid>appendix.label</msgid> <msgstr role='header'><number/>.&#x2003;</"
110"msgstr> <msgstr role='li'><number/>.&#x2002;</msgstr> <msgstr>Appendix "
111"<number/></msgstr>"
112msgstr ""
113
114#.
115#. This is a special format message.  Please read the full translator
116#. documentation before translating this message.  The documentation
117#. is maintained as part of the stylesheet documentation in DocBook.
118#. For your convenience, it has also been converted to an HTML file
119#. named STYLESHEETS.xml in the i18n directory.
120#.
121#. This is a format message used to format numbers for appendices.  Numbers
122#. are used in labels, cross references, and any other place where the
123#. appendix might be referenced.  The number for an appendix includes the
124#. number for its parent element, if applicable.  For example, the number
125#. 4.B indicates the second appendix in the fourth top-level element.  In
126#. this example, 4 is referred to as the parent number, and B is referred
127#. to as the appendix digit.  This format message constructs a full number
128#. from a parent number and an appendix digit.
129#.
130#. Special elements in the message will be replaced with the
131#. appropriate content, as follows:
132#.
133#. parent - The full number of the appendix's parent element
134#. digit  - The number of the appendix in its parent element,
135#. not including any leading numbers from the parent
136#. element
137#.
138#. These should be written as empty XML elements.  Due to limitations
139#. in intltool, I can't write XML content in translator comments.  To
140#. insert the digit, simply write left angle bracket, digit, slash,
141#. right angle bracket.
142#.
143#. Additionally, format messages can use the i, b, and tt markup tags
144#. to mark text as italic, bold, and monospace.
145#.
146#: ../xslt/gettext/l10n.xml.in.h:107
147msgid "<msgid>appendix.number</msgid> <msgstr><parent/>.<digit/></msgstr>"
148msgstr ""
149
150#.
151#. This is a special format message.  Please read the full translator
152#. documentation before translating this message.  The documentation
153#. is maintained as part of the stylesheet documentation in DocBook.
154#. For your convenience, it has also been converted to an HTML file
155#. named STYLESHEETS.xml in the i18n directory.
156#.
157#. This is a format message used to format cross references to appendices.
158#. Multiple roles can be provided to allow document translators to select
159#. how to format each cross reference using the xrefstyle attribute.  If
160#. your language needs to provide different cross reference formattings
161#. for different parts of speech, you should provide multiple roles for
162#. cross reference formatters.
163#.
164#. Special elements in the message will be replaced with the
165#. appropriate content, as follows:
166#.
167#. title       - The title of the appendix
168#. titleabbrev - The titleabbrev of the appendix, or just the title
169#. if no titleabbrev exists
170#. number      - The full number of the appendix, possibly including
171#. the number of the parent element
172#.
173#. These should be written as empty XML elements.  Due to limitations
174#. in intltool, I can't write XML content in translator comments.  To
175#. insert the title, simply write left angle bracket, title, slash,
176#. right angle bracket.
177#.
178#. Additionally, format messages can use the i, b, and tt markup tags
179#. to mark text as italic, bold, and monospace.
180#.
181#: ../xslt/gettext/l10n.xml.in.h:139
182msgid "<msgid>appendix.xref</msgid> <msgstr>Appendix <number/> ― <title/></msgstr>"
183msgstr ""
184
185#.
186#. This is a special format message.  Please read the full translator
187#. documentation before translating this message.  The documentation
188#. is maintained as part of the stylesheet documentation in DocBook.
189#. For your convenience, it has also been converted to an HTML file
190#. named STYLESHEETS.xml in the i18n directory.
191#.
192#. This is a format message used to format tooltips on cross references
193#. to bibliography entries.
194#.
195#. Special elements in the message will be replaced with the
196#. appropriate content, as follows:
197#.
198#. label - The term being defined by the glossary entry
199#.
200#. These should be written as empty XML elements.  Due to limitations
201#. in intltool, I can't write XML content in translator comments.  To
202#. insert the label, simply write left angle bracket, label,  slash,
203#. right angle bracket.
204#.
205#. Additionally, format messages can use the i, b, and tt markup tags
206#. to mark text as italic, bold, and monospace.
207#.
208#: ../xslt/gettext/l10n.xml.in.h:163
209msgid ""
210"<msgid>biblioentry.tooltip</msgid> <msgstr>View the bibliography entry "
211"<label/>.</msgstr>"
212msgstr ""
213
214#.
215#. This is a special format message.  Please read the full translator
216#. documentation before translating this message.  The documentation
217#. is maintained as part of the stylesheet documentation in DocBook.
218#. For your convenience, it has also been converted to an HTML file
219#. named STYLESHEETS.xml in the i18n directory.
220#.
221#. This is a format message used to format cross references to bibliographies.
222#. Multiple roles can be provided to allow document translators to select
223#. how to format each cross reference using the xrefstyle attribute.  If
224#. your language needs to provide different cross reference formattings
225#. for different parts of speech, you should provide multiple roles for
226#. cross reference formatters.
227#.
228#. Special elements in the message will be replaced with the
229#. appropriate content, as follows:
230#.
231#. title       - The title of the figure
232#. titleabbrev - The titleabbrev of the figure, or just the title
233#. if no titleabbrev exists
234#.
235#. These should be written as empty XML elements.  Due to limitations
236#. in intltool, I can't write XML content in translator comments.  To
237#. insert the title, simply write left angle bracket, title, slash,
238#. right angle bracket.
239#.
240#. Note that authors are not required to provide explicit titles for
241#. bibliographies.  If the author does not provide a title, the
242#. translatable string 'Bibliography' is used as a default.
243#.
244#. Additionally, format messages can use the i, b, and tt markup tags
245#. to mark text as italic, bold, and monospace.
246#.
247#: ../xslt/gettext/l10n.xml.in.h:197
248msgid "<msgid>bibliography.xref</msgid> <msgstr><title/></msgstr>"
249msgstr ""
250
251#.
252#. This is a special format message.  Please read the full translator
253#. documentation before translating this message.  The documentation
254#. is maintained as part of the stylesheet documentation in DocBook.
255#. For your convenience, it has also been converted to an HTML file
256#. named STYLESHEETS.xml in the i18n directory.
257#.
258#. biblioentry - An entry in a bibliography
259#. bibliomixed - An entry in a bibliography
260#. http://www.docbook.org/tdg/en/html/biblioentry.html
261#. http://www.docbook.org/tdg/en/html/bibliomixed.html
262#.
263#. This is a format message used to format the labels for entries in
264#. a bibliography.  The content of the label is often an abbreviation
265#. of the authors' names and the year of publication.  In English,
266#. these are generally formatted with [square brackets] surrounding
267#. them.
268#.
269#. This string is similar to citation.format, but they are used in
270#. different places.  The citation formatter is used when referencing
271#. a bibliography entry in running prose.  This formatter is used for
272#. the actual bibliography entry.  You may use the same formatting for
273#. both, but you don't have to.
274#.
275#. Special elements in the message will be replaced with the
276#. appropriate content, as follows:
277#.
278#. bibliolabel - The text content of the bibliography label
279#.
280#. These should be written as empty XML elements.  Due to limitations
281#. in intltool, I can't write XML content in translator comments.  To
282#. insert the label, simply write left angle bracket, bibliolabel,
283#. slash, right angle bracket.
284#.
285#. Additionally, format messages can use the i, b, and tt markup tags
286#. to mark text as italic, bold, and monospace.
287#.
288#: ../xslt/gettext/l10n.xml.in.h:235
289msgid "<msgid>bibliolabel.format</msgid> <msgstr>[<bibliolabel/>]</msgstr>"
290msgstr ""
291
292#.
293#. The number formatter used for book numbers.  This can be one of
294#. "1", "A", "a", "I", or "i", without the quotes.  These formatters
295#. provide the following results:
296#.
297#. 1    2    3    4    5    6    7    8    9   10   11   12   13   14
298#. A    B    C    D    E    F    G    H    I    J    K    L    M    N
299#. a    b    c    d    e    f    g    h    i    j    k    l    m    n
300#. I   II  III   IV    V   VI  VII VIII   IX    X   XI  XII XIII  XIV
301#. i   ii  iii   iv    v   vi  vii viii   ix    x   xi  xii xiii  xiv
302#.
303#. Non-Western languages probably need additional formatters.  Please
304#. contact the maintainers about adding formatters for your language.
305#.
306#: ../xslt/gettext/l10n.xml.in.h:250
307msgid "<msgid>book.digit</msgid> <msgstr>1</msgstr>"
308msgstr ""
309
310#.
311#. This is a special format message.  Please read the full translator
312#. documentation before translating this message.  The documentation
313#. is maintained as part of the stylesheet documentation in DocBook.
314#. For your convenience, it has also been converted to an HTML file
315#. named STYLESHEETS.xml in the i18n directory.
316#.
317#. This is a format message used to format cross references to books.
318#. Multiple roles can be provided to allow document translators to select
319#. how to format each cross reference using the xrefstyle attribute.  If
320#. your language needs to provide different cross reference formattings
321#. for different parts of speech, you should provide multiple roles for
322#. cross reference formatters.
323#.
324#. Special elements in the message will be replaced with the
325#. appropriate content, as follows:
326#.
327#. title       - The title of the book
328#. titleabbrev - The titleabbrev of the book, or just the title
329#. if no titleabbrev exists
330#.
331#. These should be written as empty XML elements.  Due to limitations
332#. in intltool, I can't write XML content in translator comments.  To
333#. insert the title, simply write left angle bracket, title, slash,
334#. right angle bracket.
335#.
336#. Additionally, format messages can use the i, b, and tt markup tags
337#. to mark text as italic, bold, and monospace.
338#.
339#: ../xslt/gettext/l10n.xml.in.h:280
340msgid "<msgid>book.xref</msgid> <msgstr><title/></msgstr>"
341msgstr ""
342
343#.
344#. The number formatter used for chapter numbers.  This can be one of
345#. "1", "A", "a", "I", or "i", without the quotes.  These formatters
346#. provide the following results:
347#.
348#. 1    2    3    4    5    6    7    8    9   10   11   12   13   14
349#. A    B    C    D    E    F    G    H    I    J    K    L    M    N
350#. a    b    c    d    e    f    g    h    i    j    k    l    m    n
351#. I   II  III   IV    V   VI  VII VIII   IX    X   XI  XII XIII  XIV
352#. i   ii  iii   iv    v   vi  vii viii   ix    x   xi  xii xiii  xiv
353#.
354#. Non-Western languages probably need additional formatters.  Please
355#. contact the maintainers about adding formatters for your language.
356#.
357#: ../xslt/gettext/l10n.xml.in.h:295
358msgid "<msgid>chapter.digit</msgid> <msgstr>1</msgstr>"
359msgstr ""
360
361#.
362#. This is a special format message.  Please read the full translator
363#. documentation before translating this message.  The documentation
364#. is maintained as part of the stylesheet documentation in DocBook.
365#. For your convenience, it has also been converted to an HTML file
366#. named STYLESHEETS.xml in the i18n directory.
367#.
368#. This is a format message used to format labels for chapters.  Labels
369#. are used before the title in places like headers and table of contents
370#. listings.  Multiple roles can be used to provide different formattings
371#. for different uses of labels.  The following roles may be used with
372#. this format message:
373#.
374#. header - Used for labels in headers
375#. li     - Used for labels in table of contents listings
376#.
377#. Special elements in the message will be replaced with the
378#. appropriate content, as follows:
379#.
380#. title       - The title of the chapter
381#. titleabbrev - The titleabbrev of the chapter, or just the title
382#. if no titleabbrev exists
383#. number      - The full number of the chapter, possibly including
384#. the number of the parent element
385#.
386#. These should be written as empty XML elements.  Due to limitations
387#. in intltool, I can't write XML content in translator comments.  To
388#. insert the title, simply write left angle bracket, title, slash,
389#. right angle bracket.
390#.
391#. Additionally, format messages can use the i, b, and tt markup tags
392#. to mark text as italic, bold, and monospace.
393#.
394#: ../xslt/gettext/l10n.xml.in.h:329
395msgid ""
396"<msgid>chapter.label</msgid> <msgstr role='header'><number/>.&#x2003;</"
397"msgstr> <msgstr role='li'><number/>.&#x2002;</msgstr> <msgstr>Chapter "
398"<number/></msgstr>"
399msgstr ""
400
401#.
402#. This is a special format message.  Please read the full translator
403#. documentation before translating this message.  The documentation
404#. is maintained as part of the stylesheet documentation in DocBook.
405#. For your convenience, it has also been converted to an HTML file
406#. named STYLESHEETS.xml in the i18n directory.
407#.
408#. This is a format message used to format numbers for chapters.  Numbers
409#. are used in labels, cross references, and any other place where the
410#. chapter might be referenced.  The number for a chapter includes the
411#. number for its parent element, if applicable.  For example, the number
412#. 4.2 indicates the second chapter in the fourth top-level element.  In
413#. this example, 4 is referred to as the parent number, and B is referred
414#. to as the chapter digit.  This format message constructs a full number
415#. from a parent number and a chapter digit.
416#.
417#. Special elements in the message will be replaced with the
418#. appropriate content, as follows:
419#.
420#. parent - The full number of the chapter's parent element
421#. digit  - The number of the chapter in its parent element,
422#. not including any leading numbers from the parent
423#. element
424#.
425#. These should be written as empty XML elements.  Due to limitations
426#. in intltool, I can't write XML content in translator comments.  To
427#. insert the digit, simply write left angle bracket, digit, slash,
428#. right angle bracket.
429#.
430#. Additionally, format messages can use the i, b, and tt markup tags
431#. to mark text as italic, bold, and monospace.
432#.
433#: ../xslt/gettext/l10n.xml.in.h:362
434msgid "<msgid>chapter.number</msgid> <msgstr><parent/>.<digit/></msgstr>"
435msgstr ""
436
437#.
438#. This is a special format message.  Please read the full translator
439#. documentation before translating this message.  The documentation
440#. is maintained as part of the stylesheet documentation in DocBook.
441#. For your convenience, it has also been converted to an HTML file
442#. named STYLESHEETS.xml in the i18n directory.
443#.
444#. This is a format message used to format cross references to chapters
445#. Multiple roles can be provided to allow document translators to select
446#. how to format each cross reference using the xrefstyle attribute.  If
447#. your language needs to provide different cross reference formattings
448#. for different parts of speech, you should provide multiple roles for
449#. cross reference formatters.
450#.
451#. Special elements in the message will be replaced with the
452#. appropriate content, as follows:
453#.
454#. title       - The title of the chapter
455#. titleabbrev - The titleabbrev of the chapter, or just the title
456#. if no titleabbrev exists
457#. number      - The full number of the chapter, possibly including
458#. the number of the parent element
459#.
460#. These should be written as empty XML elements.  Due to limitations
461#. in intltool, I can't write XML content in translator comments.  To
462#. insert the title, simply write left angle bracket, title, slash,
463#. right angle bracket.
464#.
465#. Additionally, format messages can use the i, b, and tt markup tags
466#. to mark text as italic, bold, and monospace.
467#.
468#: ../xslt/gettext/l10n.xml.in.h:394
469msgid "<msgid>chapter.xref</msgid> <msgstr>Chapter <number/> ― <title/></msgstr>"
470msgstr ""
471
472#.
473#. This is a special format message.  Please read the full translator
474#. documentation before translating this message.  The documentation
475#. is maintained as part of the stylesheet documentation in DocBook.
476#. For your convenience, it has also been converted to an HTML file
477#. named STYLESHEETS.xml in the i18n directory.
478#.
479#. citetitle - An inline bibliographic reference to another published work
480#. http://docbook.org/tdg/en/html/citation.html
481#.
482#. This is a format message used to format inline citations to other
483#. published works.  The content is typically an abbreviation of the
484#. authors' last names.  In English, this abbreviation is usually
485#. written inside [square brackets].
486#.
487#. Special elements in the message will be replaced with the
488#. appropriate content, as follows:
489#.
490#. citation - The text content of the citation element, possibly
491#. as a link to an entry in the bibliography
492#.
493#. These should be written as empty XML elements.  Due to limitations
494#. in intltool, I can't write XML content in translator comments.  To
495#. insert the citation, simply write left angle bracket, citation,
496#. slash, right angle bracket.
497#.
498#. Additionally, format messages can use the i, b, and tt markup tags
499#. to mark text as italic, bold, and monospace.
500#.
501#: ../xslt/gettext/l10n.xml.in.h:424
502msgid "<msgid>citation.format</msgid> <msgstr>[<citation/>]</msgstr>"
503msgstr ""
504
505#.
506#. This is a special format message.  Please read the full translator
507#. documentation before translating this message.  The documentation
508#. is maintained as part of the stylesheet documentation in DocBook.
509#. For your convenience, it has also been converted to an HTML file
510#. named STYLESHEETS.xml in the i18n directory.
511#.
512#. citetitle - The title of a cited work
513#. http://docbook.org/tdg/en/html/citetitle.html
514#.
515#. This is a format message used to format inline title citations.
516#. This template uses roles to control how the citation is formatted.
517#. The role indicates the type of work being cited, and is taken from
518#. the pubwork attribute of the citetitle element.
519#.
520#. Special elements in the message will be replaced with the
521#. appropriate content, as follows:
522#.
523#. node - The text content of the citetitle element
524#.
525#. These should be written as empty XML elements.  Due to limitations
526#. in intltool, I can't write XML content in translator comments.  To
527#. insert the node, simply write left angle bracket, node, slash,
528#. right angle bracket.
529#.
530#. Additionally, format messages can use the i, b, and tt markup tags
531#. to mark text as italic, bold, and monospace.
532#.
533#: ../xslt/gettext/l10n.xml.in.h:453
534msgid ""
535"<msgid>citetitle.format</msgid> <msgstr role='article'>“<node/>”</msgstr> "
536"<msgstr><i><node/></i></msgstr>"
537msgstr ""
538
539#.
540#. This is a special format message.  Please read the full translator
541#. documentation before translating this message.  The documentation
542#. is maintained as part of the stylesheet documentation in DocBook.
543#. For your convenience, it has also been converted to an HTML file
544#. named STYLESHEETS.xml in the i18n directory.
545#.
546#. This is a format message used to format tooltips on mailto: links
547#. created from DocBook's email element.
548#.
549#. Special elements in the message will be replaced with the
550#. appropriate content, as follows:
551#.
552#. string - The linked-to email address
553#.
554#. These should be written as empty XML elements.  Due to limitations
555#. in intltool, I can't write XML content in translator comments.  To
556#. insert the email address, simply write left angle bracket, string,
557#. slash, right angle bracket.
558#.
559#. Additionally, format messages can use the i, b, and tt markup tags
560#. to mark text as italic, bold, and monospace.
561#.
562#: ../xslt/gettext/l10n.xml.in.h:477
563msgid "<msgid>email.tooltip</msgid> <msgstr>Send email to ‘<string/>’.</msgstr>"
564msgstr ""
565
566#.
567#. The number formatter used for example numbers.  This can be one of
568#. "1", "A", "a", "I", or "i", without the quotes.  These formatters
569#. provide the following results:
570#.
571#. 1    2    3    4    5    6    7    8    9   10   11   12   13   14
572#. A    B    C    D    E    F    G    H    I    J    K    L    M    N
573#. a    b    c    d    e    f    g    h    i    j    k    l    m    n
574#. I   II  III   IV    V   VI  VII VIII   IX    X   XI  XII XIII  XIV
575#. i   ii  iii   iv    v   vi  vii viii   ix    x   xi  xii xiii  xiv
576#.
577#. Non-Western languages probably need additional formatters.  Please
578#. contact the maintainers about adding formatters for your language.
579#.
580#: ../xslt/gettext/l10n.xml.in.h:492
581msgid "<msgid>example.digit</msgid> <msgstr>1</msgstr>"
582msgstr ""
583
584#.
585#. This is a special format message.  Please read the full translator
586#. documentation before translating this message.  The documentation
587#. is maintained as part of the stylesheet documentation in DocBook.
588#. For your convenience, it has also been converted to an HTML file
589#. named STYLESHEETS.xml in the i18n directory.
590#.
591#. This is a format message used to format labels for examples.  Labels
592#. are used before the title in places like headers and table of contents
593#. listings.  Multiple roles can be used to provide different formattings
594#. for different uses of labels.  The following roles may be used with
595#. this format message:
596#.
597#. header - Used for labels in headers
598#. li     - Used for labels in table of contents listings
599#.
600#. Special elements in the message will be replaced with the
601#. appropriate content, as follows:
602#.
603#. title       - The title of the example
604#. titleabbrev - The titleabbrev of the example, or just the title
605#. if no titleabbrev exists
606#. number      - The full number of the example, possibly including
607#. the number of the parent element
608#.
609#. These should be written as empty XML elements.  Due to limitations
610#. in intltool, I can't write XML content in translator comments.  To
611#. insert the title, simply write left angle bracket, title, slash,
612#. right angle bracket.
613#.
614#. Additionally, format messages can use the i, b, and tt markup tags
615#. to mark text as italic, bold, and monospace.
616#.
617#: ../xslt/gettext/l10n.xml.in.h:526
618msgid ""
619"<msgid>example.label</msgid> <msgstr role='header'><i>Example <number/></"
620"i>&#x2003;</msgstr> <msgstr role='li'>Example <number/>&#x2002;</msgstr> "
621"<msgstr>Example <number/></msgstr>"
622msgstr ""
623
624#.
625#. This is a special format message.  Please read the full translator
626#. documentation before translating this message.  The documentation
627#. is maintained as part of the stylesheet documentation in DocBook.
628#. For your convenience, it has also been converted to an HTML file
629#. named STYLESHEETS.xml in the i18n directory.
630#.
631#. This is a format message used to format numbers for example.  Numbers
632#. are used in labels, cross references, and any other place where the
633#. example might be referenced.  The number for an example includes the
634#. number for its parent element, if applicable.  For example, the number
635#. 4-3 indicates the third example in the fourth top-level chapter.  In
636#. this example, 4 is referred to as the parent number, and 3 is referred
637#. to as the example digit.  This format message constructs a full number
638#. from a parent number and an example digit.
639#.
640#. Special elements in the message will be replaced with the
641#. appropriate content, as follows:
642#.
643#. parent - The full number of the example's parent element
644#. digit  - The number of the example in its parent element,
645#. not including any leading numbers from the parent
646#. element
647#.
648#. These should be written as empty XML elements.  Due to limitations
649#. in intltool, I can't write XML content in translator comments.  To
650#. insert the digit, simply write left angle bracket, digit, slash,
651#. right angle bracket.
652#.
653#. Additionally, format messages can use the i, b, and tt markup tags
654#. to mark text as italic, bold, and monospace.
655#.
656#: ../xslt/gettext/l10n.xml.in.h:559
657msgid "<msgid>example.number</msgid> <msgstr><parent/>-<digit/></msgstr>"
658msgstr ""
659
660#.
661#. This is a special format message.  Please read the full translator
662#. documentation before translating this message.  The documentation
663#. is maintained as part of the stylesheet documentation in DocBook.
664#. For your convenience, it has also been converted to an HTML file
665#. named STYLESHEETS.xml in the i18n directory.
666#.
667#. This is a format message used to format cross references to examples.
668#. Multiple roles can be provided to allow document translators to select
669#. how to format each cross reference using the xrefstyle attribute.  If
670#. your language needs to provide different cross reference formattings
671#. for different parts of speech, you should provide multiple roles for
672#. cross reference formatters.
673#.
674#. Special elements in the message will be replaced with the
675#. appropriate content, as follows:
676#.
677#. title       - The title of the example
678#. titleabbrev - The titleabbrev of the example, or just the title
679#. if no titleabbrev exists
680#. number      - The full number of the example, possibly including
681#. the number of the parent element
682#.
683#. These should be written as empty XML elements.  Due to limitations
684#. in intltool, I can't write XML content in translator comments.  To
685#. insert the title, simply write left angle bracket, title, slash,
686#. right angle bracket.
687#.
688#. Additionally, format messages can use the i, b, and tt markup tags
689#. to mark text as italic, bold, and monospace.
690#.
691#: ../xslt/gettext/l10n.xml.in.h:591
692msgid "<msgid>example.xref</msgid> <msgstr>Example <number/></msgstr>"
693msgstr ""
694
695#.
696#. The number formatter used for figure numbers.  This can be one of
697#. "1", "A", "a", "I", or "i", without the quotes.  These formatters
698#. provide the following results:
699#.
700#. 1    2    3    4    5    6    7    8    9   10   11   12   13   14
701#. A    B    C    D    E    F    G    H    I    J    K    L    M    N
702#. a    b    c    d    e    f    g    h    i    j    k    l    m    n
703#. I   II  III   IV    V   VI  VII VIII   IX    X   XI  XII XIII  XIV
704#. i   ii  iii   iv    v   vi  vii viii   ix    x   xi  xii xiii  xiv
705#.
706#. Non-Western languages probably need additional formatters.  Please
707#. contact the maintainers about adding formatters for your language.
708#.
709#: ../xslt/gettext/l10n.xml.in.h:606
710msgid "<msgid>figure.digit</msgid> <msgstr>1</msgstr>"
711msgstr ""
712
713#.
714#. This is a special format message.  Please read the full translator
715#. documentation before translating this message.  The documentation
716#. is maintained as part of the stylesheet documentation in DocBook.
717#. For your convenience, it has also been converted to an HTML file
718#. named STYLESHEETS.xml in the i18n directory.
719#.
720#. This is a format message used to format labels for figures.  Labels
721#. are used before the title in places like headers and table of contents
722#. listings.  Multiple roles can be used to provide different formattings
723#. for different uses of labels.  The following roles may be used with
724#. this format message:
725#.
726#. header - Used for labels in headers
727#. li     - Used for labels in table of contents listings
728#.
729#. Special elements in the message will be replaced with the
730#. appropriate content, as follows:
731#.
732#. title       - The title of the figure
733#. titleabbrev - The titleabbrev of the figure, or just the title
734#. if no titleabbrev exists
735#. number      - The full number of the figure, possibly including
736#. the number of the parent element
737#.
738#. These should be written as empty XML elements.  Due to limitations
739#. in intltool, I can't write XML content in translator comments.  To
740#. insert the title, simply write left angle bracket, title, slash,
741#. right angle bracket.
742#.
743#. Additionally, format messages can use the i, b, and tt markup tags
744#. to mark text as italic, bold, and monospace.
745#.
746#: ../xslt/gettext/l10n.xml.in.h:640
747msgid ""
748"<msgid>figure.label</msgid> <msgstr role='header'><i>Figure <number/></"
749"i>&#x2003;</msgstr> <msgstr role='li'>Figure <number/>&#x2002;</msgstr> "
750"<msgstr>Figure <number/></msgstr>"
751msgstr ""
752
753#.
754#. This is a special format message.  Please read the full translator
755#. documentation before translating this message.  The documentation
756#. is maintained as part of the stylesheet documentation in DocBook.
757#. For your convenience, it has also been converted to an HTML file
758#. named STYLESHEETS.xml in the i18n directory.
759#.
760#. This is a format message used to format numbers for figure.  Numbers
761#. are used in labels, cross references, and any other place where the
762#. figure might be referenced.  The number for a figure includes the
763#. number for its parent element, if applicable.  For example, the number
764#. 4-3 indicates the third figure in the fourth top-level chapter.  In
765#. this figure, 4 is referred to as the parent number, and 3 is referred
766#. to as the figure digit.  This format message constructs a full number
767#. from a parent number and a figure digit.
768#.
769#. Special elements in the message will be replaced with the
770#. appropriate content, as follows:
771#.
772#. parent - The full number of the figure's parent element
773#. digit  - The number of the figure in its parent element,
774#. not including any leading numbers from the parent
775#. element
776#.
777#. These should be written as empty XML elements.  Due to limitations
778#. in intltool, I can't write XML content in translator comments.  To
779#. insert the digit, simply write left angle bracket, digit, slash,
780#. right angle bracket.
781#.
782#. Additionally, format messages can use the i, b, and tt markup tags
783#. to mark text as italic, bold, and monospace.
784#.
785#: ../xslt/gettext/l10n.xml.in.h:673
786msgid "<msgid>figure.number</msgid> <msgstr><parent/>-<digit/></msgstr>"
787msgstr ""
788
789#.
790#. This is a special format message.  Please read the full translator
791#. documentation before translating this message.  The documentation
792#. is maintained as part of the stylesheet documentation in DocBook.
793#. For your convenience, it has also been converted to an HTML file
794#. named STYLESHEETS.xml in the i18n directory.
795#.
796#. This is a format message used to format cross references to figures.
797#. Multiple roles can be provided to allow document translators to select
798#. how to format each cross reference using the xrefstyle attribute.  If
799#. your language needs to provide different cross reference formattings
800#. for different parts of speech, you should provide multiple roles for
801#. cross reference formatters.
802#.
803#. Special elements in the message will be replaced with the
804#. appropriate content, as follows:
805#.
806#. title       - The title of the figure
807#. titleabbrev - The titleabbrev of the figure, or just the title
808#. if no titleabbrev exists
809#. number      - The full number of the figure, possibly including
810#. the number of the parent element
811#.
812#. These should be written as empty XML elements.  Due to limitations
813#. in intltool, I can't write XML content in translator comments.  To
814#. insert the title, simply write left angle bracket, title, slash,
815#. right angle bracket.
816#.
817#. Additionally, format messages can use the i, b, and tt markup tags
818#. to mark text as italic, bold, and monospace.
819#.
820#: ../xslt/gettext/l10n.xml.in.h:705
821msgid "<msgid>figure.xref</msgid> <msgstr>Figure <number/></msgstr>"
822msgstr ""
823
824#.
825#. This is a special format message.  Please read the full translator
826#. documentation before translating this message.  The documentation
827#. is maintained as part of the stylesheet documentation in DocBook.
828#. For your convenience, it has also been converted to an HTML file
829#. named STYLESHEETS.xml in the i18n directory.
830#.
831#. This is a format message used to format cross references to glossaries.
832#. Multiple roles can be provided to allow document translators to select
833#. how to format each cross reference using the xrefstyle attribute.  If
834#. your language needs to provide different cross reference formattings
835#. for different parts of speech, you should provide multiple roles for
836#. cross reference formatters.
837#.
838#. Special elements in the message will be replaced with the
839#. appropriate content, as follows:
840#.
841#. title       - The title of the figure
842#. titleabbrev - The titleabbrev of the figure, or just the title
843#. if no titleabbrev exists
844#.
845#. These should be written as empty XML elements.  Due to limitations
846#. in intltool, I can't write XML content in translator comments.  To
847#. insert the title, simply write left angle bracket, title, slash,
848#. right angle bracket.
849#.
850#. Note that authors are not required to provide explicit titles for
851#. glossaries.  If the author does not provide a title, the translatable
852#. string 'Glossary' is used as a default.
853#.
854#. Additionally, format messages can use the i, b, and tt markup tags
855#. to mark text as italic, bold, and monospace.
856#.
857#: ../xslt/gettext/l10n.xml.in.h:739
858msgid "<msgid>glossary.xref</msgid> <msgstr><title/></msgstr>"
859msgstr ""
860
861#.
862#. This is a special format message.  Please read the full translator
863#. documentation before translating this message.  The documentation
864#. is maintained as part of the stylesheet documentation in DocBook.
865#. For your convenience, it has also been converted to an HTML file
866#. named STYLESHEETS.xml in the i18n directory.
867#.
868#. glossentry - A entry in a glossary or glosslist
869#. http://www.docbook.org/tdg/en/html/glossentry.html
870#.
871#. This is a format message used to format the abbreviations of terms
872#. in glossary entries.  An abbreviation for a glossary term can be
873#. provided by an 'acronym' or an 'abbrev' element.  For example, a
874#. glossary entry for HTML might look like this:
875#.
876#. Hypertext Markup Language (HTML)
877#. Definition goes here....
878#.
879#. Special elements in the message will be replaced with the
880#. appropriate content, as follows:
881#.
882#. node - The content of the acronym or abbrev element
883#.
884#. These should be written as empty XML elements.  Due to limitations
885#. in intltool, I can't write XML content in translator comments.  To
886#. insert the content, simply write left angle bracket, node, slash,
887#. right angle bracket.
888#.
889#. Additionally, format messages can use the i, b, and tt markup tags
890#. to mark text as italic, bold, and monospace.
891#.
892#: ../xslt/gettext/l10n.xml.in.h:771
893msgid "<msgid>glossentry.abbrev.format</msgid> <msgstr>(<node/>)</msgstr>"
894msgstr ""
895
896#.
897#. This is a special format message.  Please read the full translator
898#. documentation before translating this message.  The documentation
899#. is maintained as part of the stylesheet documentation in DocBook.
900#. For your convenience, it has also been converted to an HTML file
901#. named STYLESHEETS.xml in the i18n directory.
902#.
903#. This is a format message used to format tooltips on cross references
904#. to glossary entries.
905#.
906#. Special elements in the message will be replaced with the
907#. appropriate content, as follows:
908#.
909#. glossterm - The term being defined by the glossary entry
910#.
911#. These should be written as empty XML elements.  Due to limitations
912#. in intltool, I can't write XML content in translator comments.  To
913#. insert the glossterm, simply write left angle bracket, glossterm,
914#. slash, right angle bracket.
915#.
916#. Additionally, format messages can use the i, b, and tt markup tags
917#. to mark text as italic, bold, and monospace.
918#.
919#: ../xslt/gettext/l10n.xml.in.h:795
920msgid ""
921"<msgid>glossentry.tooltip</msgid> <msgstr>Read the definition for "
922"‘<glossterm/>’.</msgstr>"
923msgstr ""
924
925#.
926#. This is a special format message.  Please read the full translator
927#. documentation before translating this message.  The documentation
928#. is maintained as part of the stylesheet documentation in DocBook.
929#. For your convenience, it has also been converted to an HTML file
930#. named STYLESHEETS.xml in the i18n directory.
931#.
932#. This is a format message used to format cross references to glossary
933#. entries.  Multiple roles can be provided to allow document translators to
934#. select how to format each cross reference using the xrefstyle attribute.
935#. If your language needs to provide different cross reference formattings
936#. for different parts of speech, you should provide multiple roles for
937#. cross reference formatters.
938#.
939#. In addition, the 'glosssee' role will be used for cross references
940#. from glosssee or glossseealso elements.  These are used in other
941#. glossary entries to direct the user to the linked-to entry.
942#.
943#. Special elements in the message will be replaced with the
944#. appropriate content, as follows:
945#.
946#. glossterm - The term being defined by the glossary entry
947#.
948#. These should be written as empty XML elements.  Due to limitations
949#. in intltool, I can't write XML content in translator comments.  To
950#. insert the glossterm, simply write left angle bracket, glossterm,
951#. slash, right angle bracket.
952#.
953#. Additionally, format messages can use the i, b, and tt markup tags
954#. to mark text as italic, bold, and monospace.
955#.
956#: ../xslt/gettext/l10n.xml.in.h:827
957msgid ""
958"<msgid>glossentry.xref</msgid> <msgstr role='glosssee'><glossterm/></msgstr> "
959"<msgstr>‘<glossterm/>’</msgstr>"
960msgstr ""
961
962#.
963#. This is a special format message.  Please read the full translator
964#. documentation before translating this message.  The documentation
965#. is maintained as part of the stylesheet documentation in DocBook.
966#. For your convenience, it has also been converted to an HTML file
967#. named STYLESHEETS.xml in the i18n directory.
968#.
969#. glosssee - A cross reference from one glossentry to another
970#. http://docbook.org/tdg/en/html/glosssee.html
971#.
972#. This is a format message used to format glossary cross references.
973#. This format message controls the sentence used to present the cross
974#. reference, not the link itself.  For the formatting of the actual
975#. link, see the message glossentry.xref.
976#.
977#. One or more glosssee elements are presented as a links to the user
978#. in the glossary, formatted as a single prose sentence.  For example,
979#. if the user is being directed to the entry "foo", the glosssee may
980#. be formatted as "See foo."
981#.
982#. Special elements in the message will be replaced with the
983#. appropriate content, as follows:
984#.
985#. glosssee - The actual link or links of the cross reference
986#.
987#. These should be written as empty XML elements.  Due to limitations
988#. in intltool, I can't write XML content in translator comments.  To
989#. insert the glosssee, simply write left angle bracket, glosssee,
990#. slash, right angle bracket.
991#.
992#. Additionally, format messages can use the i, b, and tt markup tags
993#. to mark text as italic, bold, and monospace.
994#.
995#: ../xslt/gettext/l10n.xml.in.h:861
996msgid "<msgid>glosssee.format</msgid> <msgstr>See <glosssee/>.</msgstr>"
997msgstr ""
998
999#.
1000#. This is a special format message.  Please read the full translator
1001#. documentation before translating this message.  The documentation
1002#. is maintained as part of the stylesheet documentation in DocBook.
1003#. For your convenience, it has also been converted to an HTML file
1004#. named STYLESHEETS.xml in the i18n directory.
1005#.
1006#. glossseealso - A cross reference from one glossentry to another
1007#. http://docbook.org/tdg/en/html/glossseealso.html
1008#.
1009#. This is a format message used to format glossary cross references.
1010#. This format message controls the sentence used to present the cross
1011#. reference, not the link itself.  For the formatting of the actual
1012#. link, see the message glossentry.xref.
1013#.
1014#. One or more glossseealso elements are presented as a links to the
1015#. user in the glossary, formatted as a single prose sentence.  For
1016#. example, if the user is being directed to the entries "foo", "bar",
1017#. and "baz", the glossseealso may be formatted as "See also foo, bar,
1018#. baz."
1019#.
1020#. Special elements in the message will be replaced with the
1021#. appropriate content, as follows:
1022#.
1023#. glosssee - The actual link or links of the cross reference
1024#.
1025#. These should be written as empty XML elements.  Due to limitations
1026#. in intltool, I can't write XML content in translator comments.  To
1027#. insert the glosssee, simply write left angle bracket, glosssee,
1028#. slash, right angle bracket.
1029#.
1030#. Additionally, format messages can use the i, b, and tt markup tags
1031#. to mark text as italic, bold, and monospace.
1032#.
1033#: ../xslt/gettext/l10n.xml.in.h:896
1034msgid "<msgid>glossseealso.format</msgid> <msgstr>See also <glosssee/>.</msgstr>"
1035msgstr ""
1036
1037#.
1038#. This is a special format message.  Please read the full translator
1039#. documentation before translating this message.  The documentation
1040#. is maintained as part of the stylesheet documentation in DocBook.
1041#. For your convenience, it has also been converted to an HTML file
1042#. named STYLESHEETS.xml in the i18n directory.
1043#.
1044#. manvolnum - A reference volume number
1045#. http://docbook.org/tdg/en/html/manvolnum.html
1046#.
1047#. This is a format message used to format manvolnum elements.
1048#. A manvolnum is typically a number or short string used to
1049#. identify a section of man pages.  It is typically placed
1050#. inside parentheses.
1051#.
1052#. Special elements in the message will be replaced with the
1053#. appropriate content, as follows:
1054#.
1055#. node - The text content of the manvolnum element
1056#.
1057#. These should be written as empty XML elements.  Due to limitations
1058#. in intltool, I can't write XML content in translator comments.  To
1059#. insert the node, simply write left angle bracket, node, slash,
1060#. right angle bracket.
1061#.
1062#. Additionally, format messages can use the i, b, and tt markup tags
1063#. to mark text as italic, bold, and monospace.
1064#.
1065#: ../xslt/gettext/l10n.xml.in.h:925
1066msgid "<msgid>manvolnum.format</msgid> <msgstr>(<node/>)</msgstr>"
1067msgstr ""
1068
1069#.
1070#. The number formatter used for part numbers.  This can be one of
1071#. "1", "A", "a", "I", or "i", without the quotes.  These formatters
1072#. provide the following results:
1073#.
1074#. 1    2    3    4    5    6    7    8    9   10   11   12   13   14
1075#. A    B    C    D    E    F    G    H    I    J    K    L    M    N
1076#. a    b    c    d    e    f    g    h    i    j    k    l    m    n
1077#. I   II  III   IV    V   VI  VII VIII   IX    X   XI  XII XIII  XIV
1078#. i   ii  iii   iv    v   vi  vii viii   ix    x   xi  xii xiii  xiv
1079#.
1080#. Non-Western languages probably need additional formatters.  Please
1081#. contact the maintainers about adding formatters for your language.
1082#.
1083#: ../xslt/gettext/l10n.xml.in.h:940
1084msgid "<msgid>part.digit</msgid> <msgstr>I</msgstr>"
1085msgstr ""
1086
1087#.
1088#. This is a special format message.  Please read the full translator
1089#. documentation before translating this message.  The documentation
1090#. is maintained as part of the stylesheet documentation in DocBook.
1091#. For your convenience, it has also been converted to an HTML file
1092#. named STYLESHEETS.xml in the i18n directory.
1093#.
1094#. This is a format message used to format labels for parts.  Labels
1095#. are used before the title in places like headers and table of contents
1096#. listings.  Multiple roles can be used to provide different formattings
1097#. for different uses of labels.  The following roles may be used with
1098#. this format message:
1099#.
1100#. header - Used for labels in headers
1101#. li     - Used for labels in table of contents listings
1102#.
1103#. Special elements in the message will be replaced with the
1104#. appropriate content, as follows:
1105#.
1106#. title       - The title of the part
1107#. titleabbrev - The titleabbrev of the part, or just the title
1108#. if no titleabbrev exists
1109#. number      - The full number of the part, possibly including
1110#. the number of the parent element
1111#.
1112#. These should be written as empty XML elements.  Due to limitations
1113#. in intltool, I can't write XML content in translator comments.  To
1114#. insert the title, simply write left angle bracket, title, slash,
1115#. right angle bracket.
1116#.
1117#. Additionally, format messages can use the i, b, and tt markup tags
1118#. to mark text as italic, bold, and monospace.
1119#.
1120#: ../xslt/gettext/l10n.xml.in.h:974
1121msgid ""
1122"<msgid>part.label</msgid> <msgstr role='header'><number/>.&#x2003;</msgstr> "
1123"<msgstr role='li'><number/>.&#x2002;</msgstr> <msgstr>Part <number/></msgstr>"
1124msgstr ""
1125
1126#.
1127#. This is a special format message.  Please read the full translator
1128#. documentation before translating this message.  The documentation
1129#. is maintained as part of the stylesheet documentation in DocBook.
1130#. For your convenience, it has also been converted to an HTML file
1131#. named STYLESHEETS.xml in the i18n directory.
1132#.
1133#. This is a format message used to format cross references to parts
1134#. Multiple roles can be provided to allow document translators to select
1135#. how to format each cross reference using the xrefstyle attribute.  If
1136#. your language needs to provide different cross reference formattings
1137#. for different parts of speech, you should provide multiple roles for
1138#. cross reference formatters.
1139#.
1140#. Special elements in the message will be replaced with the
1141#. appropriate content, as follows:
1142#.
1143#. title       - The title of the part
1144#. titleabbrev - The titleabbrev of the part, or just the title
1145#. if no titleabbrev exists
1146#. number      - The full number of the part, possibly including
1147#. the number of the parent element
1148#.
1149#. These should be written as empty XML elements.  Due to limitations
1150#. in intltool, I can't write XML content in translator comments.  To
1151#. insert the title, simply write left angle bracket, title, slash,
1152#. right angle bracket.
1153#.
1154#. Additionally, format messages can use the i, b, and tt markup tags
1155#. to mark text as italic, bold, and monospace.
1156#.
1157#: ../xslt/gettext/l10n.xml.in.h:1006
1158msgid "<msgid>part.xref</msgid> <msgstr>Part <number/> ― <title/></msgstr>"
1159msgstr ""
1160
1161#.
1162#. This is a special format message.  Please read the full translator
1163#. documentation before translating this message.  The documentation
1164#. is maintained as part of the stylesheet documentation in DocBook.
1165#. For your convenience, it has also been converted to an HTML file
1166#. named STYLESHEETS.xml in the i18n directory.
1167#.
1168#. This is a format message used to format cross references to prefaces.
1169#. Multiple roles can be provided to allow document translators to select
1170#. how to format each cross reference using the xrefstyle attribute.  If
1171#. your language needs to provide different cross reference formattings
1172#. for different parts of speech, you should provide multiple roles for
1173#. cross reference formatters.
1174#.
1175#. Special elements in the message will be replaced with the
1176#. appropriate content, as follows:
1177#.
1178#. title       - The title of the figure
1179#. titleabbrev - The titleabbrev of the figure, or just the title
1180#. if no titleabbrev exists
1181#.
1182#. These should be written as empty XML elements.  Due to limitations
1183#. in intltool, I can't write XML content in translator comments.  To
1184#. insert the title, simply write left angle bracket, title, slash,
1185#. right angle bracket.
1186#.
1187#. Note that authors are not required to provide explicit titles for
1188#. prefaces.  If the author does not provide a title, the translatable
1189#. string 'Preface' is used as a default.
1190#.
1191#. Additionally, format messages can use the i, b, and tt markup tags
1192#. to mark text as italic, bold, and monospace.
1193#.
1194#: ../xslt/gettext/l10n.xml.in.h:1040
1195msgid "<msgid>preface.xref</msgid> <msgstr><title/></msgstr>"
1196msgstr ""
1197
1198#.
1199#. The number formatter used for question numbers.  This can be one of
1200#. "1", "A", "a", "I", or "i", without the quotes.  These formatters
1201#. provide the following results:
1202#.
1203#. 1    2    3    4    5    6    7    8    9   10   11   12   13   14
1204#. A    B    C    D    E    F    G    H    I    J    K    L    M    N
1205#. a    b    c    d    e    f    g    h    i    j    k    l    m    n
1206#. I   II  III   IV    V   VI  VII VIII   IX    X   XI  XII XIII  XIV
1207#. i   ii  iii   iv    v   vi  vii viii   ix    x   xi  xii xiii  xiv
1208#.
1209#. Non-Western languages probably need additional formatters.  Please
1210#. contact the maintainers about adding formatters for your language.
1211#.
1212#: ../xslt/gettext/l10n.xml.in.h:1055
1213msgid "<msgid>question.digit</msgid> <msgstr>1</msgstr>"
1214msgstr ""
1215
1216#.
1217#. This is a special format message.  Please read the full translator
1218#. documentation before translating this message.  The documentation
1219#. is maintained as part of the stylesheet documentation in DocBook.
1220#. For your convenience, it has also been converted to an HTML file
1221#. named STYLESHEETS.xml in the i18n directory.
1222#.
1223#. This is a format message used to format labels for questions in
1224#. question-and-answer sets.  Labels are used before the question
1225#. both in the question-and-answer list and in table of questions
1226#. listings.  Multiple roles can be used to provide different
1227#. formattings for different uses of labels.  The following roles
1228#. may be used with this format message:
1229#.
1230#. header - Used for labels inside the question-and-answer set
1231#. li     - Used for labels in table of questions listings
1232#.
1233#. Special elements in the message will be replaced with the
1234#. appropriate content, as follows:
1235#.
1236#. number - The number of the question in its containing qandaset
1237#.
1238#. These should be written as empty XML elements.  Due to limitations
1239#. in intltool, I can't write XML content in translator comments.  To
1240#. insert the number, simply write left angle bracket, number, slash,
1241#. right angle bracket.
1242#.
1243#. Additionally, format messages can use the i, b, and tt markup tags
1244#. to mark text as italic, bold, and monospace.
1245#.
1246#: ../xslt/gettext/l10n.xml.in.h:1086
1247msgid ""
1248"<msgid>question.label</msgid> <msgstr role='header'><number/>.&#x2003;</"
1249"msgstr> <msgstr role='li'><number/>.&#x2002;</msgstr> <msgstr>Question "
1250"<number/></msgstr>"
1251msgstr ""
1252
1253#.
1254#. This is a special format message.  Please read the full translator
1255#. documentation before translating this message.  The documentation
1256#. is maintained as part of the stylesheet documentation in DocBook.
1257#. For your convenience, it has also been converted to an HTML file
1258#. named STYLESHEETS.xml in the i18n directory.
1259#.
1260#. This is a format message used to format cross references to questions
1261#. in question-and-answer sets.  Multiple roles can be provided to allow
1262#. document translators to select how to format each cross reference
1263#. using the xrefstyle attribute.  If your language needs to provide
1264#. different cross reference formattings for different parts of speech,
1265#. you should provide multiple roles for cross reference formatters.
1266#.
1267#. Special elements in the message will be replaced with the
1268#. appropriate content, as follows:
1269#.
1270#. number - The number of the question in its containing qandaset
1271#.
1272#. These should be written as empty XML elements.  Due to limitations
1273#. in intltool, I can't write XML content in translator comments.  To
1274#. insert the number, simply write left angle bracket, number, slash,
1275#. right angle bracket.
1276#.
1277#. Additionally, format messages can use the i, b, and tt markup tags
1278#. to mark text as italic, bold, and monospace.
1279#.
1280#: ../xslt/gettext/l10n.xml.in.h:1114
1281msgid "<msgid>question.xref</msgid> <msgstr>Question <number/></msgstr>"
1282msgstr ""
1283
1284#.
1285#. This is a special format message.  Please read the full translator
1286#. documentation before translating this message.  The documentation
1287#. is maintained as part of the stylesheet documentation in DocBook.
1288#. For your convenience, it has also been converted to an HTML file
1289#. named STYLESHEETS.xml in the i18n directory.
1290#.
1291#. quote - An inline quotation
1292#. http://docbook.org/tdg/en/html/quote.html
1293#.
1294#. This is a format message used to format inline quotations.  This template
1295#. uses roles to control how the quotation is formatted.  The role indicates
1296#. whether this is an outer or inner quotation.  Quotations nested inside
1297#. another quotation are inner quotations.  Many languages have an alternate
1298#. notation for nested quotations.
1299#.
1300#. These stylesheets only provide two levels of quotation formatting.  If
1301#. quote elements are nested deeper, the stylesheets will alternate between
1302#. the 'outer' and 'inner' roles.  If your language uses different formatting
1303#. for deeper quotations, please contact the maintainers, and we will try to
1304#. implement a more flexible formatting mechanism.
1305#.
1306#. Special elements in the message will be replaced with the
1307#. appropriate content, as follows:
1308#.
1309#. node - The text content of the quote element
1310#.
1311#. These should be written as empty XML elements.  Due to limitations
1312#. in intltool, I can't write XML content in translator comments.  To
1313#. insert the node, simply write left angle bracket, node, slash,
1314#. right angle bracket.
1315#.
1316#. Additionally, format messages can use the i, b, and tt markup tags
1317#. to mark text as italic, bold, and monospace.
1318#.
1319#: ../xslt/gettext/l10n.xml.in.h:1150
1320msgid ""
1321"<msgid>quote.format</msgid> <msgstr role='inner'>‘<node/>’</msgstr> "
1322"<msgstr>“<node/>”</msgstr>"
1323msgstr ""
1324
1325#.
1326#. This is a special format message.  Please read the full translator
1327#. documentation before translating this message.  The documentation
1328#. is maintained as part of the stylesheet documentation in DocBook.
1329#. For your convenience, it has also been converted to an HTML file
1330#. named STYLESHEETS.xml in the i18n directory.
1331#.
1332#. This is a format message used to format cross references to reference
1333#. pages.  Multiple roles can be provided to allow document translators
1334#. to select how to format each cross reference using the xrefstyle
1335#. attribute.  If your language needs to provide different cross
1336#. reference formattings for different parts of speech, you should
1337#. provide multiple roles for cross reference formatters.
1338#.
1339#. Special elements in the message will be replaced with the
1340#. appropriate content, as follows:
1341#.
1342#. title       - The title of the reference page
1343#.
1344#. These should be written as empty XML elements.  Due to limitations
1345#. in intltool, I can't write XML content in translator comments.  To
1346#. insert the title, simply write left angle bracket, title, slash,
1347#. right angle bracket.
1348#.
1349#. Additionally, format messages can use the i, b, and tt markup tags
1350#. to mark text as italic, bold, and monospace.
1351#.
1352#: ../xslt/gettext/l10n.xml.in.h:1178
1353msgid "<msgid>refentry.xref</msgid> <msgstr><title/></msgstr>"
1354msgstr ""
1355
1356#.
1357#. The number formatter used for reference section numbers.  This can
1358#. be one of "1", "A", "a", "I", or "i", without the quotes.  These
1359#. formatters provide the following results:
1360#.
1361#. 1    2    3    4    5    6    7    8    9   10   11   12   13   14
1362#. A    B    C    D    E    F    G    H    I    J    K    L    M    N
1363#. a    b    c    d    e    f    g    h    i    j    k    l    m    n
1364#. I   II  III   IV    V   VI  VII VIII   IX    X   XI  XII XIII  XIV
1365#. i   ii  iii   iv    v   vi  vii viii   ix    x   xi  xii xiii  xiv
1366#.
1367#. Non-Western languages probably need additional formatters.  Please
1368#. contact the maintainers about adding formatters for your language.
1369#.
1370#: ../xslt/gettext/l10n.xml.in.h:1193
1371msgid "<msgid>refsection.digit</msgid> <msgstr>1</msgstr>"
1372msgstr ""
1373
1374#.
1375#. This is a special format message.  Please read the full translator
1376#. documentation before translating this message.  The documentation
1377#. is maintained as part of the stylesheet documentation in DocBook.
1378#. For your convenience, it has also been converted to an HTML file
1379#. named STYLESHEETS.xml in the i18n directory.
1380#.
1381#. This is a format message used to format labels for reference sections.
1382#. Labels are used before the title in places like headers and table of
1383#. contents listings.  Multiple roles can be used to provide different
1384#. formattings for different uses of labels.  The following roles may
1385#. be used with this format message:
1386#.
1387#. header - Used for labels in headers
1388#. li     - Used for labels in table of contents listings
1389#.
1390#. Special elements in the message will be replaced with the
1391#. appropriate content, as follows:
1392#.
1393#. title       - The title of the section
1394#. titleabbrev - The titleabbrev of the section, or just the title
1395#. if no titleabbrev exists
1396#. number      - The full number of the section, possibly including
1397#. the number of the parent element
1398#.
1399#. These should be written as empty XML elements.  Due to limitations
1400#. in intltool, I can't write XML content in translator comments.  To
1401#. insert the title, simply write left angle bracket, title, slash,
1402#. right angle bracket.
1403#.
1404#. Additionally, format messages can use the i, b, and tt markup tags
1405#. to mark text as italic, bold, and monospace.
1406#.
1407#: ../xslt/gettext/l10n.xml.in.h:1227
1408msgid ""
1409"<msgid>refsection.label</msgid> <msgstr role='header'><number/>.&#x2003;</"
1410"msgstr> <msgstr role='li'><number/>.&#x2002;</msgstr> <msgstr>Section "
1411"<number/></msgstr>"
1412msgstr ""
1413
1414#.
1415#. This is a special format message.  Please read the full translator
1416#. documentation before translating this message.  The documentation
1417#. is maintained as part of the stylesheet documentation in DocBook.
1418#. For your convenience, it has also been converted to an HTML file
1419#. named STYLESHEETS.xml in the i18n directory.
1420#.
1421#. This is a format message used to format numbers for reference sections.
1422#. Numbers are used in labels, cross references, and any other place where
1423#. the section might be referenced.  The number for a section includes the
1424#. number for its parent element, if applicable.  For example, the number
1425#. 4.3.9 indicates the ninth section in the third section of the fourth
1426#. top-level section or chapter.  In this example, 4.3 is referred to as
1427#. the parent number, and 9 is referred to as the section digit.  This
1428#. format message constructs a full number from a parent number and a
1429#. section digit.
1430#.
1431#. Special elements in the message will be replaced with the
1432#. appropriate content, as follows:
1433#.
1434#. parent - The full number of the section's parent element
1435#. digit  - The number of the section in its parent element,
1436#. not including any leading numbers from the parent
1437#. element
1438#.
1439#. These should be written as empty XML elements.  Due to limitations
1440#. in intltool, I can't write XML content in translator comments.  To
1441#. insert the digit, simply write left angle bracket, digit, slash,
1442#. right angle bracket.
1443#.
1444#. Additionally, format messages can use the i, b, and tt markup tags
1445#. to mark text as italic, bold, and monospace.
1446#.
1447#: ../xslt/gettext/l10n.xml.in.h:1261
1448msgid "<msgid>refsection.number</msgid> <msgstr><parent/>.<digit/></msgstr>"
1449msgstr ""
1450
1451#.
1452#. This is a special format message.  Please read the full translator
1453#. documentation before translating this message.  The documentation
1454#. is maintained as part of the stylesheet documentation in DocBook.
1455#. For your convenience, it has also been converted to an HTML file
1456#. named STYLESHEETS.xml in the i18n directory.
1457#.
1458#. This is a format message used to format cross references to reference
1459#. sections.  Multiple roles can be provided to allow document translators
1460#. to select how to format each cross reference using the xrefstyle attribute.
1461#. If your language needs to provide different cross reference formattings
1462#. for different parts of speech, you should provide multiple roles for
1463#. cross reference formatters.
1464#.
1465#. Special elements in the message will be replaced with the
1466#. appropriate content, as follows:
1467#.
1468#. title       - The title of the section
1469#. titleabbrev - The titleabbrev of the section, or just the title
1470#. if no titleabbrev exists
1471#. number      - The full number of the section, possibly including
1472#. the number of the parent element
1473#.
1474#. These should be written as empty XML elements.  Due to limitations
1475#. in intltool, I can't write XML content in translator comments.  To
1476#. insert the title, simply write left angle bracket, title, slash,
1477#. right angle bracket.
1478#.
1479#. Additionally, format messages can use the i, b, and tt markup tags
1480#. to mark text as italic, bold, and monospace.
1481#.
1482#: ../xslt/gettext/l10n.xml.in.h:1293
1483msgid "<msgid>refsection.xref</msgid> <msgstr>Section <number/> ― <title/></msgstr>"
1484msgstr ""
1485
1486#.
1487#. The number formatter used for section numbers.  This can be one of
1488#. "1", "A", "a", "I", or "i", without the quotes.  These formatters
1489#. provide the following results:
1490#.
1491#. 1    2    3    4    5    6    7    8    9   10   11   12   13   14
1492#. A    B    C    D    E    F    G    H    I    J    K    L    M    N
1493#. a    b    c    d    e    f    g    h    i    j    k    l    m    n
1494#. I   II  III   IV    V   VI  VII VIII   IX    X   XI  XII XIII  XIV
1495#. i   ii  iii   iv    v   vi  vii viii   ix    x   xi  xii xiii  xiv
1496#.
1497#. Non-Western languages probably need additional formatters.  Please
1498#. contact the maintainers about adding formatters for your language.
1499#.
1500#: ../xslt/gettext/l10n.xml.in.h:1308
1501msgid "<msgid>section.digit</msgid> <msgstr>1</msgstr>"
1502msgstr ""
1503
1504#.
1505#. This is a special format message.  Please read the full translator
1506#. documentation before translating this message.  The documentation
1507#. is maintained as part of the stylesheet documentation in DocBook.
1508#. For your convenience, it has also been converted to an HTML file
1509#. named STYLESHEETS.xml in the i18n directory.
1510#.
1511#. This is a format message used to format labels for sections.  Labels
1512#. are used before the title in places like headers and table of contents
1513#. listings.  Multiple roles can be used to provide different formattings
1514#. for different uses of labels.  The following roles may be used with
1515#. this format message:
1516#.
1517#. header - Used for labels in headers
1518#. li     - Used for labels in table of contents listings
1519#.
1520#. Special elements in the message will be replaced with the
1521#. appropriate content, as follows:
1522#.
1523#. title       - The title of the section
1524#. titleabbrev - The titleabbrev of the section, or just the title
1525#. if no titleabbrev exists
1526#. number      - The full number of the section, possibly including
1527#. the number of the parent element
1528#.
1529#. These should be written as empty XML elements.  Due to limitations
1530#. in intltool, I can't write XML content in translator comments.  To
1531#. insert the title, simply write left angle bracket, title, slash,
1532#. right angle bracket.
1533#.
1534#. Additionally, format messages can use the i, b, and tt markup tags
1535#. to mark text as italic, bold, and monospace.
1536#.
1537#: ../xslt/gettext/l10n.xml.in.h:1342
1538msgid ""
1539"<msgid>section.label</msgid> <msgstr role='header'><number/>.&#x2003;</"
1540"msgstr> <msgstr role='li'><number/>.&#x2002;</msgstr> <msgstr>Section "
1541"<number/></msgstr>"
1542msgstr ""
1543
1544#.
1545#. This is a special format message.  Please read the full translator
1546#. documentation before translating this message.  The documentation
1547#. is maintained as part of the stylesheet documentation in DocBook.
1548#. For your convenience, it has also been converted to an HTML file
1549#. named STYLESHEETS.xml in the i18n directory.
1550#.
1551#. This is a format message used to format numbers for sections.  Numbers
1552#. are used in labels, cross references, and any other place where the
1553#. section might be referenced.  The number for a section includes the
1554#. number for its parent element, if applicable.  For example, the number
1555#. 4.3.9 indicates the ninth section in the third section of the fourth
1556#. top-level section or chapter.  In this example, 4.3 is referred to as
1557#. the parent number, and 9 is referred to as the section digit.  This
1558#. format message constructs a full number from a parent number and a
1559#. section digit.
1560#.
1561#. Special elements in the message will be replaced with the
1562#. appropriate content, as follows:
1563#.
1564#. parent - The full number of the section's parent element
1565#. digit  - The number of the section in its parent element,
1566#. not including any leading numbers from the parent
1567#. element
1568#.
1569#. These should be written as empty XML elements.  Due to limitations
1570#. in intltool, I can't write XML content in translator comments.  To
1571#. insert the digit, simply write left angle bracket, digit, slash,
1572#. right angle bracket.
1573#.
1574#. Additionally, format messages can use the i, b, and tt markup tags
1575#. to mark text as italic, bold, and monospace.
1576#.
1577#: ../xslt/gettext/l10n.xml.in.h:1376
1578msgid "<msgid>section.number</msgid> <msgstr><parent/>.<digit/></msgstr>"
1579msgstr ""
1580
1581#.
1582#. This is a special format message.  Please read the full translator
1583#. documentation before translating this message.  The documentation
1584#. is maintained as part of the stylesheet documentation in DocBook.
1585#. For your convenience, it has also been converted to an HTML file
1586#. named STYLESHEETS.xml in the i18n directory.
1587#.
1588#. This is a format message used to format cross references to sections.
1589#. Multiple roles can be provided to allow document translators to select
1590#. how to format each cross reference using the xrefstyle attribute.  If
1591#. your language needs to provide different cross reference formattings
1592#. for different parts of speech, you should provide multiple roles for
1593#. cross reference formatters.
1594#.
1595#. Special elements in the message will be replaced with the
1596#. appropriate content, as follows:
1597#.
1598#. title       - The title of the section
1599#. titleabbrev - The titleabbrev of the section, or just the title
1600#. if no titleabbrev exists
1601#. number      - The full number of the section, possibly including
1602#. the number of the parent element
1603#.
1604#. These should be written as empty XML elements.  Due to limitations
1605#. in intltool, I can't write XML content in translator comments.  To
1606#. insert the title, simply write left angle bracket, title, slash,
1607#. right angle bracket.
1608#.
1609#. Additionally, format messages can use the i, b, and tt markup tags
1610#. to mark text as italic, bold, and monospace.
1611#.
1612#: ../xslt/gettext/l10n.xml.in.h:1408
1613msgid "<msgid>section.xref</msgid> <msgstr>Section <number/> ― <title/></msgstr>"
1614msgstr ""
1615
1616#.
1617#. This is a special format message.  Please read the full translator
1618#. documentation before translating this message.  The documentation
1619#. is maintained as part of the stylesheet documentation in DocBook.
1620#. For your convenience, it has also been converted to an HTML file
1621#. named STYLESHEETS.xml in the i18n directory.
1622#.
1623#. seealsoie - A “See also” entry in an index, rather than in the text
1624#. http://www.docbook.org/tdg/en/html/seealsoie.html
1625#.
1626#. This is a format message used to format index cross references.
1627#. This format message controls the sentence used to present the cross
1628#. reference, not the link itself.
1629#.
1630#. Special elements in the message will be replaced with the
1631#. appropriate content, as follows:
1632#.
1633#. seeie - The actual link or links of the cross reference
1634#.
1635#. These should be written as empty XML elements.  Due to limitations
1636#. in intltool, I can't write XML content in translator comments.  To
1637#. insert the seeie, simply write left angle bracket, seeie, slash,
1638#. right angle bracket.
1639#.
1640#. Additionally, format messages can use the i, b, and tt markup tags
1641#. to mark text as italic, bold, and monospace.
1642#.
1643#: ../xslt/gettext/l10n.xml.in.h:1436
1644msgid "<msgid>seealsoie.format</msgid> <msgstr>See also <seeie/>.</msgstr>"
1645msgstr ""
1646
1647#.
1648#. This is a special format message.  Please read the full translator
1649#. documentation before translating this message.  The documentation
1650#. is maintained as part of the stylesheet documentation in DocBook.
1651#. For your convenience, it has also been converted to an HTML file
1652#. named STYLESHEETS.xml in the i18n directory.
1653#.
1654#. seeie - A “See” entry in an index, rather than in the text
1655#. http://www.docbook.org/tdg/en/html/seeie.html
1656#.
1657#. This is a format message used to format index cross references.
1658#. This format message controls the sentence used to present the cross
1659#. reference, not the link itself.
1660#.
1661#. Special elements in the message will be replaced with the
1662#. appropriate content, as follows:
1663#.
1664#. seeie - The actual link or links of the cross reference
1665#.
1666#. These should be written as empty XML elements.  Due to limitations
1667#. in intltool, I can't write XML content in translator comments.  To
1668#. insert the seeie, simply write left angle bracket, seeie, slash,
1669#. right angle bracket.
1670#.
1671#. Additionally, format messages can use the i, b, and tt markup tags
1672#. to mark text as italic, bold, and monospace.
1673#.
1674#: ../xslt/gettext/l10n.xml.in.h:1464
1675msgid "<msgid>seeie.format</msgid> <msgstr>See <seeie/>.</msgstr>"
1676msgstr ""
1677
1678#.
1679#. The number formatter used for synopsis numbers.  This can be one of
1680#. "1", "A", "a", "I", or "i", without the quotes.  These formatters
1681#. provide the following results:
1682#.
1683#. 1    2    3    4    5    6    7    8    9   10   11   12   13   14
1684#. A    B    C    D    E    F    G    H    I    J    K    L    M    N
1685#. a    b    c    d    e    f    g    h    i    j    k    l    m    n
1686#. I   II  III   IV    V   VI  VII VIII   IX    X   XI  XII XIII  XIV
1687#. i   ii  iii   iv    v   vi  vii viii   ix    x   xi  xii xiii  xiv
1688#.
1689#. Non-Western languages probably need additional formatters.  Please
1690#. contact the maintainers about adding formatters for your language.
1691#.
1692#: ../xslt/gettext/l10n.xml.in.h:1479
1693msgid "<msgid>synopfragment.digit</msgid> <msgstr>1</msgstr>"
1694msgstr ""
1695
1696#.
1697#. This is a special format message.  Please read the full translator
1698#. documentation before translating this message.  The documentation
1699#. is maintained as part of the stylesheet documentation in DocBook.
1700#. For your convenience, it has also been converted to an HTML file
1701#. named STYLESHEETS.xml in the i18n directory.
1702#.
1703#. This is a format message used to format labels for command synopsis
1704#. fragments, as well as cross references to them.  See the following:
1705#.
1706#. http://www.docbook.org/tdg/en/html/synopfragment.html
1707#. http://www.docbook.org/tdg/en/html/synopfragmentref.html
1708#.
1709#. Special elements in the message will be replaced with the
1710#. appropriate content, as follows:
1711#.
1712#. number - The number of the synopsis fragment, formatted according
1713#. to the synopfragment.digit string
1714#.
1715#. These should be written as empty XML elements.  Due to limitations
1716#. in intltool, I can't write XML content in translator comments.  To
1717#. insert the number, simply write left angle bracket, number, slash,
1718#. right angle bracket.
1719#.
1720#. Additionally, format messages can use the i, b, and tt markup tags
1721#. to mark text as italic, bold, and monospace.
1722#.
1723#: ../xslt/gettext/l10n.xml.in.h:1507
1724msgid "<msgid>synopfragment.label</msgid> <msgstr>(<number/>)</msgstr>"
1725msgstr ""
1726
1727#.
1728#. The number formatter used for table numbers.  This can be one of
1729#. "1", "A", "a", "I", or "i", without the quotes.  These formatters
1730#. provide the following results:
1731#.
1732#. 1    2    3    4    5    6    7    8    9   10   11   12   13   14
1733#. A    B    C    D    E    F    G    H    I    J    K    L    M    N
1734#. a    b    c    d    e    f    g    h    i    j    k    l    m    n
1735#. I   II  III   IV    V   VI  VII VIII   IX    X   XI  XII XIII  XIV
1736#. i   ii  iii   iv    v   vi  vii viii   ix    x   xi  xii xiii  xiv
1737#.
1738#. Non-Western languages probably need additional formatters.  Please
1739#. contact the maintainers about adding formatters for your language.
1740#.
1741#: ../xslt/gettext/l10n.xml.in.h:1522
1742msgid "<msgid>table.digit</msgid> <msgstr>1</msgstr>"
1743msgstr ""
1744
1745#.
1746#. This is a special format message.  Please read the full translator
1747#. documentation before translating this message.  The documentation
1748#. is maintained as part of the stylesheet documentation in DocBook.
1749#. For your convenience, it has also been converted to an HTML file
1750#. named STYLESHEETS.xml in the i18n directory.
1751#.
1752#. This is a format message used to format labels for tables.  Labels
1753#. are used before the title in places like headers and table of contents
1754#. listings.  Multiple roles can be used to provide different formattings
1755#. for different uses of labels.  The following roles may be used with
1756#. this format message:
1757#.
1758#. header - Used for labels in headers
1759#. li     - Used for labels in table of contents listings
1760#.
1761#. Special elements in the message will be replaced with the
1762#. appropriate content, as follows:
1763#.
1764#. title       - The title of the table
1765#. titleabbrev - The titleabbrev of the table, or just the title
1766#. if no titleabbrev exists
1767#. number      - The full number of the table, possibly including
1768#. the number of the parent element
1769#.
1770#. These should be written as empty XML elements.  Due to limitations
1771#. in intltool, I can't write XML content in translator comments.  To
1772#. insert the title, simply write left angle bracket, title, slash,
1773#. right angle bracket.
1774#.
1775#. Additionally, format messages can use the i, b, and tt markup tags
1776#. to mark text as italic, bold, and monospace.
1777#.
1778#: ../xslt/gettext/l10n.xml.in.h:1556
1779msgid ""
1780"<msgid>table.label</msgid> <msgstr role='header'><i>Table <number/></"
1781"i>&#x2003;</msgstr> <msgstr role='li'>Table <number/>&#x2002;</msgstr> "
1782"<msgstr>Table <number/></msgstr>"
1783msgstr ""
1784
1785#.
1786#. This is a special format message.  Please read the full translator
1787#. documentation before translating this message.  The documentation
1788#. is maintained as part of the stylesheet documentation in DocBook.
1789#. For your convenience, it has also been converted to an HTML file
1790#. named STYLESHEETS.xml in the i18n directory.
1791#.
1792#. This is a format message used to format numbers for table.  Numbers
1793#. are used in labels, cross references, and any other place where the
1794#. table might be referenced.  The number for a table includes the
1795#. number for its parent element, if applicable.  For example, the number
1796#. 4-3 indicates the third table in the fourth top-level chapter.  In
1797#. this table, 4 is referred to as the parent number, and 3 is referred
1798#. to as the table digit.  This format message constructs a full number
1799#. from a parent number and a table digit.
1800#.
1801#. Special elements in the message will be replaced with the
1802#. appropriate content, as follows:
1803#.
1804#. parent - The full number of the table's parent element
1805#. digit  - The number of the table in its parent element,
1806#. not including any leading numbers from the parent
1807#. element
1808#.
1809#. These should be written as empty XML elements.  Due to limitations
1810#. in intltool, I can't write XML content in translator comments.  To
1811#. insert the digit, simply write left angle bracket, digit, slash,
1812#. right angle bracket.
1813#.
1814#. Additionally, format messages can use the i, b, and tt markup tags
1815#. to mark text as italic, bold, and monospace.
1816#.
1817#: ../xslt/gettext/l10n.xml.in.h:1589
1818msgid "<msgid>table.number</msgid> <msgstr><parent/>-<digit/></msgstr>"
1819msgstr ""
1820
1821#.
1822#. This is a special format message.  Please read the full translator
1823#. documentation before translating this message.  The documentation
1824#. is maintained as part of the stylesheet documentation in DocBook.
1825#. For your convenience, it has also been converted to an HTML file
1826#. named STYLESHEETS.xml in the i18n directory.
1827#.
1828#. This is a format message used to format cross references to tables.
1829#. Multiple roles can be provided to allow document translators to select
1830#. how to format each cross reference using the xrefstyle attribute.  If
1831#. your language needs to provide different cross reference formattings
1832#. for different parts of speech, you should provide multiple roles for
1833#. cross reference formatters.
1834#.
1835#. Special elements in the message will be replaced with the
1836#. appropriate content, as follows:
1837#.
1838#. title       - The title of the table
1839#. titleabbrev - The titleabbrev of the table, or just the title
1840#. if no titleabbrev exists
1841#. number      - The full number of the table, possibly including
1842#. the number of the parent element
1843#.
1844#. These should be written as empty XML elements.  Due to limitations
1845#. in intltool, I can't write XML content in translator comments.  To
1846#. insert the title, simply write left angle bracket, title, slash,
1847#. right angle bracket.
1848#.
1849#. Additionally, format messages can use the i, b, and tt markup tags
1850#. to mark text as italic, bold, and monospace.
1851#.
1852#: ../xslt/gettext/l10n.xml.in.h:1621
1853msgid "<msgid>table.xref</msgid> <msgstr>Table <number/></msgstr>"
1854msgstr ""
1855
1856#. Used as a header before a list of authors.
1857#: ../xslt/gettext/l10n.xml.in.h:1623
1858msgid "<msgstr form='0'>Author</msgstr> <msgstr form='1'>Authors</msgstr>"
1859msgstr ""
1860
1861#. Used as a header before a list of collaborators.
1862#: ../xslt/gettext/l10n.xml.in.h:1625
1863msgid ""
1864"<msgstr form='0'>Collaborator</msgstr> <msgstr form='1'>Collaborators</"
1865"msgstr>"
1866msgstr ""
1867
1868#. Used as a header before a list of copyrights.
1869#: ../xslt/gettext/l10n.xml.in.h:1627
1870msgid "<msgstr form='0'>Copyright</msgstr> <msgstr form='1'>Copyrights</msgstr>"
1871msgstr ""
1872
1873#. Used as a header before a list of editors.
1874#: ../xslt/gettext/l10n.xml.in.h:1629
1875msgid "<msgstr form='0'>Editor</msgstr> <msgstr form='1'>Editors</msgstr>"
1876msgstr ""
1877
1878#. Used as a header before a list of contributors.
1879#: ../xslt/gettext/l10n.xml.in.h:1631
1880msgid ""
1881"<msgstr form='0'>Other Contributor</msgstr> <msgstr form='1'>Other "
1882"Contributors</msgstr>"
1883msgstr ""
1884
1885#. Used as a header before a list of publishers.
1886#: ../xslt/gettext/l10n.xml.in.h:1633
1887msgid "<msgstr form='0'>Publisher</msgstr> <msgstr form='1'>Publishers</msgstr>"
1888msgstr ""
1889
1890#. Used as a header before a list of translators.
1891#: ../xslt/gettext/l10n.xml.in.h:1635
1892msgid "<msgstr form='0'>Translator</msgstr> <msgstr form='1'>Translators</msgstr>"
1893msgstr ""
1894
1895#.
1896#. http://www.docbook.org/tdg/en/html/qandaentry.html
1897#.
1898#. This is used as a label before answers in a question-and-answer
1899#. set.  Typically, answers are simply numbered and answers are not
1900#. labelled at all.  However, DocBook allows document authors to set
1901#. the labelling style for a qandaset.  If the labelling style is set
1902#. to 'qanda', this string will be used to label answers.
1903#.
1904#: ../xslt/gettext/l10n.xml.in.h:1645
1905msgid "A:&#x2003;"
1906msgstr "J:&#x2003;"
1907
1908#. Used for links to the titlepage.
1909#: ../xslt/gettext/l10n.xml.in.h:1647
1910msgid "About This Document"
1911msgstr "Ushbu hujjat haqida"
1912
1913#.
1914#. http://www.docbook.org/tdg/en/html/affiliation.html
1915#.
1916#. This is used as a label before affiliations when listing
1917#. authors and other contributors to the document.  For example:
1918#.
1919#. Shaun McCance
1920#. Affiliation: GNOME Documentation Project
1921#.
1922#: ../xslt/gettext/l10n.xml.in.h:1657
1923msgid "Affiliation"
1924msgstr ""
1925
1926#. Used as a title for a bibliography.
1927#: ../xslt/gettext/l10n.xml.in.h:1659
1928msgid "Bibliography"
1929msgstr ""
1930
1931#.
1932#. http://www.docbook.org/tdg/en/html/caution.html
1933#. This is used as a default title for caution elements.
1934#.
1935#: ../xslt/gettext/l10n.xml.in.h:1664
1936msgid "Caution"
1937msgstr ""
1938
1939#.
1940#. http://www.docbook.org/tdg/en/html/colophon.html
1941#. This is used as a default title for colophon elements.
1942#.
1943#: ../xslt/gettext/l10n.xml.in.h:1669
1944msgid "Colophon"
1945msgstr ""
1946
1947#. Used as the title of the listing of subsections
1948#: ../xslt/gettext/l10n.xml.in.h:1671
1949msgid "Contents"
1950msgstr "Tarkibi"
1951
1952#.
1953#. http://www.docbook.org/tdg/en/html/dedication.html
1954#. This is used as a default title for dedication elements.
1955#.
1956#: ../xslt/gettext/l10n.xml.in.h:1676
1957msgid "Dedication"
1958msgstr ""
1959
1960#.
1961#. http://www.docbook.org/tdg/en/html/affiliation.html
1962#.
1963#. This is used as a label before email addresses when listing
1964#. authors and other contributors to the document.  For example:
1965#.
1966#. Shaun McCance
1967#. Email: shaunm@gnome.org
1968#.
1969#: ../xslt/gettext/l10n.xml.in.h:1686
1970msgid "Email"
1971msgstr "El. pochta"
1972
1973#.
1974#. http://www.docbook.org/tdg/en/html/glossary.html
1975#. This is used as a default title for glossary elements.
1976#.
1977#: ../xslt/gettext/l10n.xml.in.h:1691
1978msgid "Glossary"
1979msgstr "Glossariy"
1980
1981#.
1982#. http://www.docbook.org/tdg/en/html/important.html
1983#. This is used as a default title for important elements.
1984#.
1985#: ../xslt/gettext/l10n.xml.in.h:1696
1986msgid "Important"
1987msgstr "Muhim"
1988
1989#.
1990#. http://www.docbook.org/tdg/en/html/index.html
1991#. This is used as a default title for index elements.
1992#.
1993#: ../xslt/gettext/l10n.xml.in.h:1701
1994msgid "Index"
1995msgstr ""
1996
1997#.
1998#. http://www.docbook.org/tdg/en/html/legalnotice.html
1999#. This is used as a default title for legalnotice elements.
2000#.
2001#: ../xslt/gettext/l10n.xml.in.h:1706
2002msgid "Legal Notice"
2003msgstr ""
2004
2005#.
2006#. http://www.docbook.org/tdg/en/html/refnamediv.html
2007#. This is used as the title for refnamediv elements.
2008#.
2009#: ../xslt/gettext/l10n.xml.in.h:1711
2010msgid "Name"
2011msgstr "Nomi"
2012
2013#.
2014#. http://www.docbook.org/tdg/en/html/note.html
2015#. This is used as a default title for note elements.
2016#.
2017#: ../xslt/gettext/l10n.xml.in.h:1716
2018msgid "Note"
2019msgstr "Izoh"
2020
2021#.
2022#. http://www.docbook.org/tdg/en/html/preface.html
2023#. This is used as a default title for preface elements.
2024#.
2025#: ../xslt/gettext/l10n.xml.in.h:1721
2026msgid "Preface"
2027msgstr "Kirish"
2028
2029#.
2030#. http://www.docbook.org/tdg/en/html/qandaentry.html
2031#.
2032#. This is used as a label before questions in a question-and-answer
2033#. set.  Typically, questions are simply numbered and answers are not
2034#. labelled at all.  However, DocBook allows document authors to set
2035#. the labelling style for a qandaset.  If the labelling style is set
2036#. to 'qanda', this string will be used to label questions.
2037#.
2038#: ../xslt/gettext/l10n.xml.in.h:1731
2039msgid "Q:&#x2003;"
2040msgstr "S:&#x2003;"
2041
2042#.
2043#. http://www.docbook.org/tdg/en/html/revhistory.html
2044#. This is used as a header before the revision history.
2045#.
2046#: ../xslt/gettext/l10n.xml.in.h:1736
2047msgid "Revision History"
2048msgstr ""
2049
2050#.
2051#. Used for the <see> element.
2052#. FIXME: this should be a format string.
2053#.
2054#: ../xslt/gettext/l10n.xml.in.h:1741
2055msgid "See"
2056msgstr "Qarang"
2057
2058#.
2059#. Used for the <seealso> element.
2060#. FIXME: this should be a format string.
2061#.
2062#: ../xslt/gettext/l10n.xml.in.h:1746
2063msgid "See Also"
2064msgstr ""
2065
2066#.
2067#. http://www.docbook.org/tdg/en/html/refsynopsisdiv.html
2068#. This is used as the default title for refsynopsisdiv elements.
2069#.
2070#: ../xslt/gettext/l10n.xml.in.h:1751
2071msgid "Synopsis"
2072msgstr ""
2073
2074#.
2075#. http://www.docbook.org/tdg/en/html/tip.html
2076#. This is used as a default title for tip elements.
2077#.
2078#: ../xslt/gettext/l10n.xml.in.h:1756
2079msgid "Tip"
2080msgstr ""
2081
2082#.
2083#. http://www.docbook.org/tdg/en/html/warning.html
2084#. This is used as a default title for warning elements.
2085#.
2086#: ../xslt/gettext/l10n.xml.in.h:1761
2087msgid "Warning"
2088msgstr "Ogohlantirish"
2089
2090#.
2091#. Translate to default:RTL if your language should be displayed
2092#. right-to-left, otherwise translate to default:LTR.  Do *not*
2093#. translate it to "predefinito:LTR", if it it isn't default:LTR
2094#. or default:RTL it will not work
2095#.
2096#: ../xslt/gettext/l10n.xml.in.h:1768
2097msgid "default:LTR"
2098msgstr ""
2099
2100#.
2101#. This is an image of the opening quotation character for your language.
2102#. The image is used as a watermark on blockquote elements.  There are a
2103#. number of different quote characters used by various languages, so the
2104#. image name is translatable.  The name of the icon should be of the form
2105#. "watermark-blockquote-XXXX.png", where XXXX is the Unicode code point
2106#. of the opening quote character.  For example, some languages use the
2107#. double angle quotation mark.  Translators for these languages should
2108#. use "watermark-blockquote-00AB.png".
2109#.
2110#. The image, however, is not automatically created.  Do not translate
2111#. this to a value if there isn't a corresponding file in gnome-doc-utils,
2112#. under the directory data/watermarks.
2113#.
2114#. Languages that use guillemets (angle quotation marks) should use either
2115#. 00AB or 00BB, depending on whether the opening quotation is the left
2116#. guillemet or the right guillemet.  Languages that use inverted comma
2117#. quotation marks should use 201C, 201D, or 201E.  Single quotation marks
2118#. don't make very nice watermarks, so if you would normally open a quote
2119#. with single quotation marks in your language, use the corresponding
2120#. double quotation mark for the watermark image.
2121#.
2122#. Translators who have been around Gnome for a while should recognize
2123#. this as nearly the same as the "yelp-watermark-blockquote-201C" string
2124#. once found inside Yelp.  The watermark functionality has been moved to
2125#. gnome-doc-utils.
2126#.
2127#: ../xslt/gettext/l10n.xml.in.h:1796
2128msgid "watermark-blockquote-201C.png"
2129msgstr "watermark-blockquote-201C.png"
2130
2131