Browsing Persian translation

This is a special format message.  Please read the full translator
documentation before translating this message.  The documentation
is maintained as part of the stylesheet documentation in DocBook.
For your convenience, it has also been converted to an HTML file
named STYLESHEETS.xml in the i18n directory.

citetitle - An inline bibliographic reference to another published work
http://docbook.org/tdg/en/html/citation.html

This is a format message used to format inline citations to other
published works.  The content is typically an abbreviation of the
authors' last names.  In English, this abbreviation is usually
written inside [square brackets].

Special elements in the message will be replaced with the
appropriate content, as follows:

citation - The text content of the citation element, possibly
as a link to an entry in the bibliography

These should be written as empty XML elements.  Due to limitations
in intltool, I can't write XML content in translator comments.  To
insert the citation, simply write left angle bracket, citation,
slash, right angle bracket.

Additionally, format messages can use the i, b, and tt markup tags
to mark text as italic, bold, and monospace.

This is a special format message.  Please read the full translator
documentation before translating this message.  The documentation
is maintained as part of the stylesheet documentation in DocBook.
For your convenience, it has also been converted to an HTML file
named STYLESHEETS.xml in the i18n directory.

citetitle - The title of a cited work
http://docbook.org/tdg/en/html/citetitle.html

This is a format message used to format inline title citations.
This template uses roles to control how the citation is formatted.
The role indicates the type of work being cited, and is taken from
the pubwork attribute of the citetitle element.

Special elements in the message will be replaced with the
appropriate content, as follows:

node - The text content of the citetitle element

These should be written as empty XML elements.  Due to limitations
in intltool, I can't write XML content in translator comments.  To
insert the node, simply write left angle bracket, node, slash,
right angle bracket.

Additionally, format messages can use the i, b, and tt markup tags
to mark text as italic, bold, and monospace.

This is a special format message.  Please read the full translator
documentation before translating this message.  The documentation
is maintained as part of the stylesheet documentation in DocBook.
For your convenience, it has also been converted to an HTML file
named STYLESHEETS.xml in the i18n directory.

comment - Editorial comments
cite    - The source of a comment
http://projectmallard.org/1.0/mal_block_comment.html
http://projectmallard.org/1.0/mal_block_cite.html

This is a format message used to format the citation of a comment
made by an editor of a document. This appears on a new line after
the title of the comment, if a title is present, or as the first
line if a title is not present.

This string is used when both the name and the date are supplied.
In English, a title together with this format string might produce
something like this:

Some Comment Title
from Shaun McCance on 2010-06-03

Here is the text of the comment.

If only a name is supplied, and no date, then comment.cite.name.format
is used instead of this string.

Special elements in the message will be replaced with the
appropriate content, as follows:

comment.name - The name of the person making the comment
comment.date - The date the comment was made

These should be written as empty XML elements, e.g. <comment.name/>

Additionally, format messages can use the i, b, and tt markup tags
to mark text as italic, bold, and monospace.

This is a special format message.  Please read the full translator
documentation before translating this message.  The documentation
is maintained as part of the stylesheet documentation in DocBook.
For your convenience, it has also been converted to an HTML file
named STYLESHEETS.xml in the i18n directory.

comment - Editorial comments
cite    - The source of a comment
http://projectmallard.org/1.0/mal_block_comment.html
http://projectmallard.org/1.0/mal_block_cite.html

This is a format message used to format the citation of a comment
made by an editor of a document. This appears on a new line after
the title of the comment, if a title is present, or as the first
line if a title is not present.

This string is used when only the name of the commenter is supplied.
In English, a title together with this format string might produce
something like this:

Some Comment Title
from Shaun McCance

Here is the text of the comment.

If a date is also supplied, then comment.cite.name-date.format
is used instead of this string.

Special elements in the message will be replaced with the
appropriate content, as follows:

comment.name - The name of the person making the comment

These should be written as empty XML elements, e.g. <comment.name/>

Additionally, format messages can use the i, b, and tt markup tags
to mark text as italic, bold, and monospace.

This is a special format message.  Please read the full translator
documentation before translating this message.  The documentation
is maintained as part of the stylesheet documentation in DocBook.
For your convenience, it has also been converted to an HTML file
named STYLESHEETS.xml in the i18n directory.

This is a format message used to format tooltips on mailto: links
created from DocBook's email element.

Special elements in the message will be replaced with the
appropriate content, as follows:

string - The linked-to email address

These should be written as empty XML elements.  Due to limitations
in intltool, I can't write XML content in translator comments.  To
insert the email address, simply write left angle bracket, string,
slash, right angle bracket.

Additionally, format messages can use the i, b, and tt markup tags
to mark text as italic, bold, and monospace.

This is a special format message.  Please read the full translator
documentation before translating this message.  The documentation
is maintained as part of the stylesheet documentation in DocBook.
For your convenience, it has also been converted to an HTML file
named STYLESHEETS.xml in the i18n directory.

glossentry - A entry in a glossary or glosslist
http://www.docbook.org/tdg/en/html/glossentry.html

This is a format message used to format the abbreviations of terms
in glossary entries.  An abbreviation for a glossary term can be
provided by an 'acronym' or an 'abbrev' element.  For example, a
glossary entry for HTML might look like this:

Hypertext Markup Language (HTML)
Definition goes here....

Special elements in the message will be replaced with the
appropriate content, as follows:

node - The content of the acronym or abbrev element

These should be written as empty XML elements.  Due to limitations
in intltool, I can't write XML content in translator comments.  To
insert the content, simply write left angle bracket, node, slash,
right angle bracket.

Additionally, format messages can use the i, b, and tt markup tags
to mark text as italic, bold, and monospace.

This is a special format message.  Please read the full translator
documentation before translating this message.  The documentation
is maintained as part of the stylesheet documentation in DocBook.
For your convenience, it has also been converted to an HTML file
named STYLESHEETS.xml in the i18n directory.

This is a format message used to format tooltips on cross references
to glossary entries.

Special elements in the message will be replaced with the
appropriate content, as follows:

glossterm - The term being defined by the glossary entry

These should be written as empty XML elements.  Due to limitations
in intltool, I can't write XML content in translator comments.  To
insert the glossterm, simply write left angle bracket, glossterm,
slash, right angle bracket.

Additionally, format messages can use the i, b, and tt markup tags
to mark text as italic, bold, and monospace.

This is a special format message.  Please read the full translator
documentation before translating this message.  The documentation
is maintained as part of the stylesheet documentation in DocBook.
For your convenience, it has also been converted to an HTML file
named STYLESHEETS.xml in the i18n directory.

This is a format message used to format cross references to glossary
entries.  Multiple roles can be provided to allow document translators to
select how to format each cross reference using the xrefstyle attribute.
If your language needs to provide different cross reference formattings
for different parts of speech, you should provide multiple roles for
cross reference formatters.

In addition, the 'glosssee' role will be used for cross references
from glosssee or glossseealso elements.  These are used in other
glossary entries to direct the user to the linked-to entry.

Special elements in the message will be replaced with the
appropriate content, as follows:

glossterm - The term being defined by the glossary entry

These should be written as empty XML elements.  Due to limitations
in intltool, I can't write XML content in translator comments.  To
insert the glossterm, simply write left angle bracket, glossterm,
slash, right angle bracket.

Additionally, format messages can use the i, b, and tt markup tags
to mark text as italic, bold, and monospace.

This is a special format message.  Please read the full translator
documentation before translating this message.  The documentation
is maintained as part of the stylesheet documentation in DocBook.
For your convenience, it has also been converted to an HTML file
named STYLESHEETS.xml in the i18n directory.

glosssee - A cross reference from one glossentry to another
http://docbook.org/tdg/en/html/glosssee.html

This is a format message used to format glossary cross references.
This format message controls the sentence used to present the cross
reference, not the link itself.  For the formatting of the actual
link, see the message glossentry.xref.

One or more glosssee elements are presented as a links to the user
in the glossary, formatted as a single prose sentence.  For example,
if the user is being directed to the entry "foo", the glosssee may
be formatted as "See foo."

Special elements in the message will be replaced with the
appropriate content, as follows:

glosssee - The actual link or links of the cross reference

These should be written as empty XML elements.  Due to limitations
in intltool, I can't write XML content in translator comments.  To
insert the glosssee, simply write left angle bracket, glosssee,
slash, right angle bracket.

Additionally, format messages can use the i, b, and tt markup tags
to mark text as italic, bold, and monospace.

This is a special format message.  Please read the full translator
documentation before translating this message.  The documentation
is maintained as part of the stylesheet documentation in DocBook.
For your convenience, it has also been converted to an HTML file
named STYLESHEETS.xml in the i18n directory.

glossseealso - A cross reference from one glossentry to another
http://docbook.org/tdg/en/html/glossseealso.html

This is a format message used to format glossary cross references.
This format message controls the sentence used to present the cross
reference, not the link itself.  For the formatting of the actual
link, see the message glossentry.xref.

One or more glossseealso elements are presented as a links to the
user in the glossary, formatted as a single prose sentence.  For
example, if the user is being directed to the entries "foo", "bar",
and "baz", the glossseealso may be formatted as "See also foo, bar,
baz."

Special elements in the message will be replaced with the
appropriate content, as follows:

glosssee - The actual link or links of the cross reference

These should be written as empty XML elements.  Due to limitations
in intltool, I can't write XML content in translator comments.  To
insert the glosssee, simply write left angle bracket, glosssee,
slash, right angle bracket.

Additionally, format messages can use the i, b, and tt markup tags
to mark text as italic, bold, and monospace.