1
<?xml version="1.0" encoding="UTF-8"?><!-- -*- indent-tabs-mode: nil -*- -->
3
<l10n xmlns="http://projects.gnome.org/yelp/gettext/">
5
<!-- ======================================================================= -->
6
<!-- == Simple Strings ===================================================== -->
9
<msgid>default:LTR</msgid>
11
Translate to default:RTL if your language should be displayed
12
right-to-left, otherwise translate to default:LTR. Do *not*
13
translate it to "predefinito:LTR", if it isn't default:LTR
14
or default:RTL it will not work
16
<_msg>default:LTR</_msg>
21
This is used a simple list item seperator in places where simple
22
inline lists have to be constructed dynamically. Using the default
23
string of ", ", a list would look like this: A, B, C, D. Using the
24
nonsensical string " - ", a list would look like this: A - B - C - D.
26
<_msg xml:space="preserve">, </_msg>
31
This is used as the final separator in an inline list of three or
32
more elements. The string ", " will be used to separate all but
33
the last pair of elements. Using these two strings, a list of
34
names would be formatted as "Tom, Dick, and Harry".
36
<_msg xml:space="preserve">, and </_msg>
41
This is used as a list item seperator for inline lists of exactly two
42
elements. A list of two names would be formatted as "Tom and Dick".
44
<_msg xml:space="preserve"> and </_msg>
49
This is used to offset an inline description from a title. This is
50
typically used on title and refpurpose of a refentry element, which
51
models the structure of a man page.
53
<_msg xml:space="preserve"> — </_msg>
58
http://www.docbook.org/tdg/en/html/qandaentry.html
60
This is used as a label before answers in a question-and-answer
61
set. Typically, answers are simply numbered and answers are not
62
labelled at all. However, DocBook allows document authors to set
63
the labelling style for a qandaset. If the labelling style is set
64
to 'qanda', this string will be used to label answers.
66
<_msg>A: </_msg>
69
<msgid>About This Document</msgid>
70
<!-- Used for links to the titlepage. -->
71
<_msg>About This Document</_msg>
74
<msgid>Affiliation</msgid>
76
http://www.docbook.org/tdg/en/html/affiliation.html
78
This is used as a label before affiliations when listing
79
authors and other contributors to the document. For example:
82
Affiliation: GNOME Documentation Project
84
<_msg>Affiliation</_msg>
88
<!-- Used as a header before a list of authors. -->
90
<msgstr form='0'>Author</msgstr>
91
<msgstr form='1'>Authors</msgstr>
95
<msgid>Bibliography</msgid>
96
<!-- Used as a title for a bibliography. -->
97
<_msg>Bibliography</_msg>
100
<msgid>Caution</msgid>
102
http://www.docbook.org/tdg/en/html/caution.html
103
This is used as a default title for caution elements.
108
<msgid>Colophon</msgid>
110
http://www.docbook.org/tdg/en/html/colophon.html
111
This is used as a default title for colophon elements.
113
<_msg>Colophon</_msg>
116
<msgid>Collaborator</msgid>
117
<!-- Used as a header before a list of collaborators. -->
119
<msgstr form='0'>Collaborator</msgstr>
120
<msgstr form='1'>Collaborators</msgstr>
124
<msgid>Contents</msgid>
125
<!-- Used as the title of the listing of subsections -->
126
<_msg>Contents</_msg>
129
<msgid>Copyright</msgid>
130
<!-- Used as a header before a list of copyrights. -->
132
<msgstr form='0'>Copyright</msgstr>
133
<msgstr form='1'>Copyrights</msgstr>
137
<msgid>Dedication</msgid>
139
http://www.docbook.org/tdg/en/html/dedication.html
140
This is used as a default title for dedication elements.
142
<_msg>Dedication</_msg>
145
<msgid>Editor</msgid>
146
<!-- Used as a header before a list of editors. -->
148
<msgstr form='0'>Editor</msgstr>
149
<msgstr form='1'>Editors</msgstr>
155
http://www.docbook.org/tdg/en/html/affiliation.html
157
This is used as a label before email addresses when listing
158
authors and other contributors to the document. For example:
161
Email: shaunm@gnome.org
166
<msgid>Glossary</msgid>
168
http://www.docbook.org/tdg/en/html/glossary.html
169
This is used as a default title for glossary elements.
171
<_msg>Glossary</_msg>
174
<msgid>Important</msgid>
176
http://www.docbook.org/tdg/en/html/important.html
177
This is used as a default title for important elements.
179
<_msg>Important</_msg>
184
http://www.docbook.org/tdg/en/html/index.html
185
This is used as a default title for index elements.
190
<msgid>Legal Notice</msgid>
192
http://www.docbook.org/tdg/en/html/legalnotice.html
193
This is used as a default title for legalnotice elements.
195
<_msg>Legal Notice</_msg>
200
http://www.docbook.org/tdg/en/html/refnamediv.html
201
This is used as the title for refnamediv elements.
207
<!-- Used as link to the next page in a series. -->
213
http://www.docbook.org/tdg/en/html/note.html
214
This is used as a default title for note elements.
219
<msgid>Other Contributor</msgid>
220
<!-- Used as a header before a list of contributors. -->
222
<msgstr form='0'>Other Contributor</msgstr>
223
<msgstr form='1'>Other Contributors</msgstr>
229
http://www.docbook.org/tdg/en/html/qandaentry.html
231
This is used as a label before questions in a question-and-answer
232
set. Typically, questions are simply numbered and answers are not
233
labelled at all. However, DocBook allows document authors to set
234
the labelling style for a qandaset. If the labelling style is set
235
to 'qanda', this string will be used to label questions.
237
<_msg>Q: </_msg>
240
<msgid>Preface</msgid>
242
http://www.docbook.org/tdg/en/html/preface.html
243
This is used as a default title for preface elements.
248
<msgid>Previous</msgid>
249
<!-- Used as link to the previous page in a series. -->
250
<_msg>Previous</_msg>
253
<msgid>Publisher</msgid>
254
<!-- Used as a header before a list of publishers. -->
256
<msgstr form='0'>Publisher</msgstr>
257
<msgstr form='1'>Publishers</msgstr>
261
<msgid>Revision History</msgid>
263
http://www.docbook.org/tdg/en/html/revhistory.html
264
This is used as a header before the revision history.
266
<_msg>Revision History</_msg>
271
Used for the <see> element.
272
FIXME: this should be a format string.
277
<msgid>See Also</msgid>
279
Used for the <seealso> element.
280
FIXME: this should be a format string.
282
<_msg>See Also</_msg>
285
<msgid>Synopsis</msgid>
287
http://www.docbook.org/tdg/en/html/refsynopsisdiv.html
288
This is used as the default title for refsynopsisdiv elements.
290
<_msg>Synopsis</_msg>
295
http://www.docbook.org/tdg/en/html/tip.html
296
This is used as a default title for tip elements.
301
<msgid>Translator</msgid>
302
<!-- Used as a header before a list of translators. -->
304
<msgstr form='0'>Translator</msgstr>
305
<msgstr form='1'>Translators</msgstr>
309
<msgid>Warning</msgid>
311
http://www.docbook.org/tdg/en/html/warning.html
312
This is used as a default title for warning elements.
317
<msgid>yelp-quote-201C.png</msgid>
319
This is an image of the opening quotation character for your language.
320
The image is used as a watermark on blockquote elements. There are a
321
number of different quote characters used by various languages, so the
322
image name is translatable. The name of the icon should be of the form
323
"yelp-quote-XXXX.png", where XXXX is the Unicode code point of the opening
324
quote character. For example, some languages use the double angle quotation
325
mark. Translators for these languages should use "yelp-quote-00AB.png".
327
The image, however, is not automatically created. Do not translate
328
this to a value if there isn't a corresponding file in yelp-icons,
329
under the directory icons/hicolor/48x48/status.
331
Languages that use guillemets (angle quotation marks) should use either
332
00AB or 00BB, depending on whether the opening quotation is the left
333
guillemet or the right guillemet. Languages that use inverted comma
334
quotation marks should use 201C, 201D, or 201E. Single quotation marks
335
don't make very nice watermarks, so if you would normally open a quote
336
with single quotation marks in your language, use the corresponding
337
double quotation mark for the watermark image.
339
<_msg>yelp-quote-201C.png</_msg>
342
<msgid>View images at normal size</msgid>
344
Figures can automatically scale images down to fit the page width.
345
This is used a tooltip on a link to expand images to full size.
347
<_msg>View images at normal size</_msg>
350
<msgid>Scale images down</msgid>
352
Figures can automatically scale images down to fit the page width.
353
This is used a tooltip on a link to shrink images back down after
354
they've been expanded to full size.
356
<_msg>Scale images down</_msg>
361
Used as a tooltip on play/pause buttons for audio and video objects.
368
Used as a tooltip on play/pause buttons for audio and video objects.
374
<!-- ======================================================================= -->
375
<!-- == Formatters ========================================================= -->
377
<!-- == biblioentry == -->
379
<msgid>biblioentry.tooltip</msgid>
381
This is a special format message. Please read the full translator
382
documentation before translating this message. The documentation
383
is maintained as part of the stylesheet documentation in DocBook.
384
For your convenience, it has also been converted to an HTML file
385
named STYLESHEETS.xml in the i18n directory.
387
This is a format message used to format tooltips on cross references
388
to bibliography entries.
390
Special elements in the message will be replaced with the
391
appropriate content, as follows:
393
label - The term being defined by the glossary entry
395
These should be written as empty XML elements. Due to limitations
396
in intltool, I can't write XML content in translator comments. To
397
insert the label, simply write left angle bracket, label, slash,
400
Additionally, format messages can use the i, b, and tt markup tags
401
to mark text as italic, bold, and monospace.
404
<msgid>biblioentry.tooltip</msgid>
405
<msgstr>View the bibliography entry <label/>.</msgstr>
409
<!-- == mal:comment == -->
411
<msgid>comment.cite.name-date.format</msgid>
413
This is a special format message. Please read the full translator
414
documentation before translating this message. The documentation
415
is maintained as part of the stylesheet documentation in DocBook.
416
For your convenience, it has also been converted to an HTML file
417
named STYLESHEETS.xml in the i18n directory.
419
comment - Editorial comments
420
cite - The source of a comment
421
http://projectmallard.org/1.0/mal_block_comment.html
422
http://projectmallard.org/1.0/mal_block_cite.html
424
This is a format message used to format the citation of a comment
425
made by an editor of a document. This appears on a new line after
426
the title of the comment, if a title is present, or as the first
427
line if a title is not present.
429
This string is used when both the name and the date are supplied.
430
In English, a title together with this format string might produce
434
from Shaun McCance on 2010-06-03
436
Here is the text of the comment.
438
If only a name is supplied, and no date, then comment.cite.name.format
439
is used instead of this string.
441
Special elements in the message will be replaced with the
442
appropriate content, as follows:
444
comment.name - The name of the person making the comment
445
comment.date - The date the comment was made
447
These should be written as empty XML elements, e.g. <comment.name/>
449
Additionally, format messages can use the i, b, and tt markup tags
450
to mark text as italic, bold, and monospace.
453
<msgid>comment.cite.name-date.format</msgid>
454
<msgstr>from <comment.name/> on <comment.date/></msgstr>
458
<msgid>comment.cite.name.format</msgid>
460
This is a special format message. Please read the full translator
461
documentation before translating this message. The documentation
462
is maintained as part of the stylesheet documentation in DocBook.
463
For your convenience, it has also been converted to an HTML file
464
named STYLESHEETS.xml in the i18n directory.
466
comment - Editorial comments
467
cite - The source of a comment
468
http://projectmallard.org/1.0/mal_block_comment.html
469
http://projectmallard.org/1.0/mal_block_cite.html
471
This is a format message used to format the citation of a comment
472
made by an editor of a document. This appears on a new line after
473
the title of the comment, if a title is present, or as the first
474
line if a title is not present.
476
This string is used when only the name of the commenter is supplied.
477
In English, a title together with this format string might produce
483
Here is the text of the comment.
485
If a date is also supplied, then comment.cite.name-date.format
486
is used instead of this string.
488
Special elements in the message will be replaced with the
489
appropriate content, as follows:
491
comment.name - The name of the person making the comment
493
These should be written as empty XML elements, e.g. <comment.name/>
495
Additionally, format messages can use the i, b, and tt markup tags
496
to mark text as italic, bold, and monospace.
499
<msgid>comment.cite.name.format</msgid>
500
<msgstr>from <comment.name/></msgstr>
504
<!-- == bibliolabel == -->
506
<msgid>bibliolabel.format</msgid>
508
This is a special format message. Please read the full translator
509
documentation before translating this message. The documentation
510
is maintained as part of the stylesheet documentation in DocBook.
511
For your convenience, it has also been converted to an HTML file
512
named STYLESHEETS.xml in the i18n directory.
514
biblioentry - An entry in a bibliography
515
bibliomixed - An entry in a bibliography
516
http://www.docbook.org/tdg/en/html/biblioentry.html
517
http://www.docbook.org/tdg/en/html/bibliomixed.html
519
This is a format message used to format the labels for entries in
520
a bibliography. The content of the label is often an abbreviation
521
of the authors' names and the year of publication. In English,
522
these are generally formatted with [square brackets] surrounding
525
This string is similar to citation.format, but they are used in
526
different places. The citation formatter is used when referencing
527
a bibliography entry in running prose. This formatter is used for
528
the actual bibliography entry. You may use the same formatting for
529
both, but you don't have to.
531
Special elements in the message will be replaced with the
532
appropriate content, as follows:
534
bibliolabel - The text content of the bibliography label
536
These should be written as empty XML elements. Due to limitations
537
in intltool, I can't write XML content in translator comments. To
538
insert the label, simply write left angle bracket, bibliolabel,
539
slash, right angle bracket.
541
Additionally, format messages can use the i, b, and tt markup tags
542
to mark text as italic, bold, and monospace.
545
<msgid>bibliolabel.format</msgid>
546
<msgstr>[<bibliolabel/>]</msgstr>
550
<!-- == citetitle == -->
552
<msgid>citetitle.format</msgid>
554
This is a special format message. Please read the full translator
555
documentation before translating this message. The documentation
556
is maintained as part of the stylesheet documentation in DocBook.
557
For your convenience, it has also been converted to an HTML file
558
named STYLESHEETS.xml in the i18n directory.
560
citetitle - The title of a cited work
561
http://docbook.org/tdg/en/html/citetitle.html
563
This is a format message used to format inline title citations.
564
This template uses roles to control how the citation is formatted.
565
The role indicates the type of work being cited, and is taken from
566
the pubwork attribute of the citetitle element.
568
Special elements in the message will be replaced with the
569
appropriate content, as follows:
571
node - The text content of the citetitle element
573
These should be written as empty XML elements. Due to limitations
574
in intltool, I can't write XML content in translator comments. To
575
insert the node, simply write left angle bracket, node, slash,
578
Additionally, format messages can use the i, b, and tt markup tags
579
to mark text as italic, bold, and monospace.
582
<msgid>citetitle.format</msgid>
583
<msgstr role='article'>“<node/>”</msgstr>
584
<msgstr><i><node/></i></msgstr>
588
<!-- == citation == -->
590
<msgid>citation.format</msgid>
592
This is a special format message. Please read the full translator
593
documentation before translating this message. The documentation
594
is maintained as part of the stylesheet documentation in DocBook.
595
For your convenience, it has also been converted to an HTML file
596
named STYLESHEETS.xml in the i18n directory.
598
citetitle - An inline bibliographic reference to another published work
599
http://docbook.org/tdg/en/html/citation.html
601
This is a format message used to format inline citations to other
602
published works. The content is typically an abbreviation of the
603
authors' last names. In English, this abbreviation is usually
604
written inside [square brackets].
606
Special elements in the message will be replaced with the
607
appropriate content, as follows:
609
citation - The text content of the citation element, possibly
610
as a link to an entry in the bibliography
612
These should be written as empty XML elements. Due to limitations
613
in intltool, I can't write XML content in translator comments. To
614
insert the citation, simply write left angle bracket, citation,
615
slash, right angle bracket.
617
Additionally, format messages can use the i, b, and tt markup tags
618
to mark text as italic, bold, and monospace.
621
<msgid>citation.format</msgid>
622
<msgstr>[<citation/>]</msgstr>
628
<msgid>email.tooltip</msgid>
630
This is a special format message. Please read the full translator
631
documentation before translating this message. The documentation
632
is maintained as part of the stylesheet documentation in DocBook.
633
For your convenience, it has also been converted to an HTML file
634
named STYLESHEETS.xml in the i18n directory.
636
This is a format message used to format tooltips on mailto: links
637
created from DocBook's email element.
639
Special elements in the message will be replaced with the
640
appropriate content, as follows:
642
string - The linked-to email address
644
These should be written as empty XML elements. Due to limitations
645
in intltool, I can't write XML content in translator comments. To
646
insert the email address, simply write left angle bracket, string,
647
slash, right angle bracket.
649
Additionally, format messages can use the i, b, and tt markup tags
650
to mark text as italic, bold, and monospace.
653
<msgid>email.tooltip</msgid>
654
<msgstr>Send email to ‘<string/>’.</msgstr>
658
<!-- == glossentry == -->
660
<msgid>glossentry.abbrev.format</msgid>
662
This is a special format message. Please read the full translator
663
documentation before translating this message. The documentation
664
is maintained as part of the stylesheet documentation in DocBook.
665
For your convenience, it has also been converted to an HTML file
666
named STYLESHEETS.xml in the i18n directory.
668
glossentry - A entry in a glossary or glosslist
669
http://www.docbook.org/tdg/en/html/glossentry.html
671
This is a format message used to format the abbreviations of terms
672
in glossary entries. An abbreviation for a glossary term can be
673
provided by an 'acronym' or an 'abbrev' element. For example, a
674
glossary entry for HTML might look like this:
676
Hypertext Markup Language (HTML)
677
Definition goes here....
679
Special elements in the message will be replaced with the
680
appropriate content, as follows:
682
node - The content of the acronym or abbrev element
684
These should be written as empty XML elements. Due to limitations
685
in intltool, I can't write XML content in translator comments. To
686
insert the content, simply write left angle bracket, node, slash,
689
Additionally, format messages can use the i, b, and tt markup tags
690
to mark text as italic, bold, and monospace.
693
<msgid>glossentry.abbrev.format</msgid>
694
<msgstr>(<node/>)</msgstr>
698
<!-- == glossentry == -->
700
<msgid>glossentry.tooltip</msgid>
702
This is a special format message. Please read the full translator
703
documentation before translating this message. The documentation
704
is maintained as part of the stylesheet documentation in DocBook.
705
For your convenience, it has also been converted to an HTML file
706
named STYLESHEETS.xml in the i18n directory.
708
This is a format message used to format tooltips on cross references
711
Special elements in the message will be replaced with the
712
appropriate content, as follows:
714
glossterm - The term being defined by the glossary entry
716
These should be written as empty XML elements. Due to limitations
717
in intltool, I can't write XML content in translator comments. To
718
insert the glossterm, simply write left angle bracket, glossterm,
719
slash, right angle bracket.
721
Additionally, format messages can use the i, b, and tt markup tags
722
to mark text as italic, bold, and monospace.
725
<msgid>glossentry.tooltip</msgid>
726
<msgstr>Read the definition for ‘<glossterm/>’.</msgstr>
730
<msgid>glossentry.xref</msgid>
732
This is a special format message. Please read the full translator
733
documentation before translating this message. The documentation
734
is maintained as part of the stylesheet documentation in DocBook.
735
For your convenience, it has also been converted to an HTML file
736
named STYLESHEETS.xml in the i18n directory.
738
This is a format message used to format cross references to glossary
739
entries. Multiple roles can be provided to allow document translators to
740
select how to format each cross reference using the xrefstyle attribute.
741
If your language needs to provide different cross reference formattings
742
for different parts of speech, you should provide multiple roles for
743
cross reference formatters.
745
In addition, the 'glosssee' role will be used for cross references
746
from glosssee or glossseealso elements. These are used in other
747
glossary entries to direct the user to the linked-to entry.
749
Special elements in the message will be replaced with the
750
appropriate content, as follows:
752
glossterm - The term being defined by the glossary entry
754
These should be written as empty XML elements. Due to limitations
755
in intltool, I can't write XML content in translator comments. To
756
insert the glossterm, simply write left angle bracket, glossterm,
757
slash, right angle bracket.
759
Additionally, format messages can use the i, b, and tt markup tags
760
to mark text as italic, bold, and monospace.
763
<msgid>glossentry.xref</msgid>
764
<msgstr role='glosssee'><glossterm/></msgstr>
765
<msgstr>‘<glossterm/>’</msgstr>
769
<!-- == glosssee == -->
771
<msgid>glosssee.format</msgid>
773
This is a special format message. Please read the full translator
774
documentation before translating this message. The documentation
775
is maintained as part of the stylesheet documentation in DocBook.
776
For your convenience, it has also been converted to an HTML file
777
named STYLESHEETS.xml in the i18n directory.
779
glosssee - A cross reference from one glossentry to another
780
http://docbook.org/tdg/en/html/glosssee.html
782
This is a format message used to format glossary cross references.
783
This format message controls the sentence used to present the cross
784
reference, not the link itself. For the formatting of the actual
785
link, see the message glossentry.xref.
787
One or more glosssee elements are presented as a links to the user
788
in the glossary, formatted as a single prose sentence. For example,
789
if the user is being directed to the entry "foo", the glosssee may
790
be formatted as "See foo."
792
Special elements in the message will be replaced with the
793
appropriate content, as follows:
795
glosssee - The actual link or links of the cross reference
797
These should be written as empty XML elements. Due to limitations
798
in intltool, I can't write XML content in translator comments. To
799
insert the glosssee, simply write left angle bracket, glosssee,
800
slash, right angle bracket.
802
Additionally, format messages can use the i, b, and tt markup tags
803
to mark text as italic, bold, and monospace.
806
<msgid>glosssee.format</msgid>
807
<msgstr>See <glosssee/>.</msgstr>
811
<!-- == glossseealso == -->
813
<msgid>glossseealso.format</msgid>
815
This is a special format message. Please read the full translator
816
documentation before translating this message. The documentation
817
is maintained as part of the stylesheet documentation in DocBook.
818
For your convenience, it has also been converted to an HTML file
819
named STYLESHEETS.xml in the i18n directory.
821
glossseealso - A cross reference from one glossentry to another
822
http://docbook.org/tdg/en/html/glossseealso.html
824
This is a format message used to format glossary cross references.
825
This format message controls the sentence used to present the cross
826
reference, not the link itself. For the formatting of the actual
827
link, see the message glossentry.xref.
829
One or more glossseealso elements are presented as a links to the
830
user in the glossary, formatted as a single prose sentence. For
831
example, if the user is being directed to the entries "foo", "bar",
832
and "baz", the glossseealso may be formatted as "See also foo, bar,
835
Special elements in the message will be replaced with the
836
appropriate content, as follows:
838
glosssee - The actual link or links of the cross reference
840
These should be written as empty XML elements. Due to limitations
841
in intltool, I can't write XML content in translator comments. To
842
insert the glosssee, simply write left angle bracket, glosssee,
843
slash, right angle bracket.
845
Additionally, format messages can use the i, b, and tt markup tags
846
to mark text as italic, bold, and monospace.
849
<msgid>glossseealso.format</msgid>
850
<msgstr>See also <glosssee/>.</msgstr>
854
<!-- == manvolnum == -->
856
<msgid>manvolnum.format</msgid>
858
This is a special format message. Please read the full translator
859
documentation before translating this message. The documentation
860
is maintained as part of the stylesheet documentation in DocBook.
861
For your convenience, it has also been converted to an HTML file
862
named STYLESHEETS.xml in the i18n directory.
864
manvolnum - A reference volume number
865
http://docbook.org/tdg/en/html/manvolnum.html
867
This is a format message used to format manvolnum elements.
868
A manvolnum is typically a number or short string used to
869
identify a section of man pages. It is typically placed
872
Special elements in the message will be replaced with the
873
appropriate content, as follows:
875
node - The text content of the manvolnum element
877
These should be written as empty XML elements. Due to limitations
878
in intltool, I can't write XML content in translator comments. To
879
insert the node, simply write left angle bracket, node, slash,
882
Additionally, format messages can use the i, b, and tt markup tags
883
to mark text as italic, bold, and monospace.
886
<msgid>manvolnum.format</msgid>
887
<msgstr>(<node/>)</msgstr>
892
<!-- == question == -->
894
<msgid>question.digit</msgid>
896
The number formatter used for question numbers. This can be one of
897
"1", "A", "a", "I", or "i", without the quotes. These formatters
898
provide the following results:
900
1 2 3 4 5 6 7 8 9 10 11 12 13 14
901
A B C D E F G H I J K L M N
902
a b c d e f g h i j k l m n
903
I II III IV V VI VII VIII IX X XI XII XIII XIV
904
i ii iii iv v vi vii viii ix x xi xii xiii xiv
906
Non-Western languages probably need additional formatters. Please
907
contact the maintainers about adding formatters for your language.
910
<msgid>question.digit</msgid>
915
<msgid>question.label</msgid>
917
This is a special format message. Please read the full translator
918
documentation before translating this message. The documentation
919
is maintained as part of the stylesheet documentation in DocBook.
920
For your convenience, it has also been converted to an HTML file
921
named STYLESHEETS.xml in the i18n directory.
923
This is a format message used to format labels for questions in
924
question-and-answer sets. Labels are used before the question
925
both in the question-and-answer list and in table of questions
926
listings. Multiple roles can be used to provide different
927
formattings for different uses of labels. The following roles
928
may be used with this format message:
930
header - Used for labels inside the question-and-answer set
931
li - Used for labels in table of questions listings
933
Special elements in the message will be replaced with the
934
appropriate content, as follows:
936
number - The number of the question in its containing qandaset
938
These should be written as empty XML elements. Due to limitations
939
in intltool, I can't write XML content in translator comments. To
940
insert the number, simply write left angle bracket, number, slash,
943
Additionally, format messages can use the i, b, and tt markup tags
944
to mark text as italic, bold, and monospace.
947
<msgid>question.label</msgid>
948
<msgstr role='header'><number/>. </msgstr>
949
<msgstr role='li'><number/>. </msgstr>
950
<msgstr>Question <number/></msgstr>
954
<msgid>question.xref</msgid>
956
This is a special format message. Please read the full translator
957
documentation before translating this message. The documentation
958
is maintained as part of the stylesheet documentation in DocBook.
959
For your convenience, it has also been converted to an HTML file
960
named STYLESHEETS.xml in the i18n directory.
962
This is a format message used to format cross references to questions
963
in question-and-answer sets. Multiple roles can be provided to allow
964
document translators to select how to format each cross reference
965
using the xrefstyle attribute. If your language needs to provide
966
different cross reference formattings for different parts of speech,
967
you should provide multiple roles for cross reference formatters.
969
Special elements in the message will be replaced with the
970
appropriate content, as follows:
972
number - The number of the question in its containing qandaset
974
These should be written as empty XML elements. Due to limitations
975
in intltool, I can't write XML content in translator comments. To
976
insert the number, simply write left angle bracket, number, slash,
979
Additionally, format messages can use the i, b, and tt markup tags
980
to mark text as italic, bold, and monospace.
983
<msgid>question.xref</msgid>
984
<msgstr>Question <number/></msgstr>
990
<msgid>quote.format</msgid>
992
This is a special format message. Please read the full translator
993
documentation before translating this message. The documentation
994
is maintained as part of the stylesheet documentation in DocBook.
995
For your convenience, it has also been converted to an HTML file
996
named STYLESHEETS.xml in the i18n directory.
998
quote - An inline quotation
999
http://docbook.org/tdg/en/html/quote.html
1001
This is a format message used to format inline quotations. This template
1002
uses roles to control how the quotation is formatted. The role indicates
1003
whether this is an outer or inner quotation. Quotations nested inside
1004
another quotation are inner quotations. Many languages have an alternate
1005
notation for nested quotations.
1007
These stylesheets only provide two levels of quotation formatting. If
1008
quote elements are nested deeper, the stylesheets will alternate between
1009
the 'outer' and 'inner' roles. If your language uses different formatting
1010
for deeper quotations, please contact the maintainers, and we will try to
1011
implement a more flexible formatting mechanism.
1013
Special elements in the message will be replaced with the
1014
appropriate content, as follows:
1016
node - The text content of the quote element
1018
These should be written as empty XML elements. Due to limitations
1019
in intltool, I can't write XML content in translator comments. To
1020
insert the node, simply write left angle bracket, node, slash,
1021
right angle bracket.
1023
Additionally, format messages can use the i, b, and tt markup tags
1024
to mark text as italic, bold, and monospace.
1027
<msgid>quote.format</msgid>
1028
<msgstr role='inner'>‘<node/>’</msgstr>
1029
<msgstr>“<node/>”</msgstr>
1034
<!-- == seeie == -->
1036
<msgid>seeie.format</msgid>
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.
1044
seeie - A “See” entry in an index, rather than in the text
1045
http://www.docbook.org/tdg/en/html/seeie.html
1047
This is a format message used to format index cross references.
1048
This format message controls the sentence used to present the cross
1049
reference, not the link itself.
1051
Special elements in the message will be replaced with the
1052
appropriate content, as follows:
1054
seeie - The actual link or links of the cross reference
1056
These should be written as empty XML elements. Due to limitations
1057
in intltool, I can't write XML content in translator comments. To
1058
insert the seeie, simply write left angle bracket, seeie, slash,
1059
right angle bracket.
1061
Additionally, format messages can use the i, b, and tt markup tags
1062
to mark text as italic, bold, and monospace.
1065
<msgid>seeie.format</msgid>
1066
<msgstr>See <seeie/>.</msgstr>
1070
<!-- == seealsoie == -->
1072
<msgid>seealsoie.format</msgid>
1074
This is a special format message. Please read the full translator
1075
documentation before translating this message. The documentation
1076
is maintained as part of the stylesheet documentation in DocBook.
1077
For your convenience, it has also been converted to an HTML file
1078
named STYLESHEETS.xml in the i18n directory.
1080
seealsoie - A “See also” entry in an index, rather than in the text
1081
http://www.docbook.org/tdg/en/html/seealsoie.html
1083
This is a format message used to format index cross references.
1084
This format message controls the sentence used to present the cross
1085
reference, not the link itself.
1087
Special elements in the message will be replaced with the
1088
appropriate content, as follows:
1090
seeie - The actual link or links of the cross reference
1092
These should be written as empty XML elements. Due to limitations
1093
in intltool, I can't write XML content in translator comments. To
1094
insert the seeie, simply write left angle bracket, seeie, slash,
1095
right angle bracket.
1097
Additionally, format messages can use the i, b, and tt markup tags
1098
to mark text as italic, bold, and monospace.
1101
<msgid>seealsoie.format</msgid>
1102
<msgstr>See also <seeie/>.</msgstr>
1106
<!-- == synopfragment == -->
1108
<msgid>synopfragment.digit</msgid>
1110
The number formatter used for synopsis numbers. This can be one of
1111
"1", "A", "a", "I", or "i", without the quotes. These formatters
1112
provide the following results:
1114
1 2 3 4 5 6 7 8 9 10 11 12 13 14
1115
A B C D E F G H I J K L M N
1116
a b c d e f g h i j k l m n
1117
I II III IV V VI VII VIII IX X XI XII XIII XIV
1118
i ii iii iv v vi vii viii ix x xi xii xiii xiv
1120
Non-Western languages probably need additional formatters. Please
1121
contact the maintainers about adding formatters for your language.
1124
<msgid>synopfragment.digit</msgid>
1129
<msgid>synopfragment.label</msgid>
1131
This is a special format message. Please read the full translator
1132
documentation before translating this message. The documentation
1133
is maintained as part of the stylesheet documentation in DocBook.
1134
For your convenience, it has also been converted to an HTML file
1135
named STYLESHEETS.xml in the i18n directory.
1137
This is a format message used to format labels for command synopsis
1138
fragments, as well as cross references to them. See the following:
1140
http://www.docbook.org/tdg/en/html/synopfragment.html
1141
http://www.docbook.org/tdg/en/html/synopfragmentref.html
1143
Special elements in the message will be replaced with the
1144
appropriate content, as follows:
1146
number - The number of the synopsis fragment, formatted according
1147
to the synopfragment.digit string
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 number, simply write left angle bracket, number, slash,
1152
right angle bracket.
1154
Additionally, format messages can use the i, b, and tt markup tags
1155
to mark text as italic, bold, and monospace.
1158
<msgid>synopfragment.label</msgid>
1159
<msgstr>(<number/>)</msgstr>
1163
<!-- Mallard specific strings -->
1166
<msgid>Further Reading</msgid>
1167
<!-- Automatic further reading section and links -->
1168
<_msg>Further Reading</_msg>
1171
<msgid>More About</msgid>
1172
<!-- Automatic more about section and links -->
1173
<_msg>More About</_msg>
1176
<msgid>See Also</msgid>
1177
<!-- Automatic see also section and links -->
1178
<_msg>See Also</_msg>
1183
This is used as a description for the status of the document.
1184
This will not be visibile to the users.
1186
Stub: the document has little or basic content, it may have been
1187
created by developers in order to have it included in the build.
1192
<msgid>Incomplete</msgid>
1194
This is used as a description for the status of the document.
1195
This will not be visibile to the users.
1197
Incomplete: the document has the basic structure in place, but the
1198
authors have not yet written all the content.
1200
<_msg>Incomplete</_msg>
1203
<msgid>Draft</msgid>
1205
This is used as a description for the status of the document.
1206
This will not be visibile to the users.
1208
Draft: the authors have written all the content, but they still need
1209
to clean up the language or markup.
1214
<msgid>Ready for review</msgid>
1216
This is used as a description for the status of the document.
1217
This will not be visibile to the users.
1219
Review: the authors consider the document complete.
1221
<_msg>Ready for review</_msg>
1224
<msgid>Final</msgid>
1226
This is used as a description for the status of the document.
1227
This will not be visibile to the users.
1229
Final: a senior member of the documentation team has reviewd the
1230
document and approved it.