The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

(itstool) path: row/entry
Context English State
The names of files.
Edit <filename>.login</filename>.
On-screen computer output.
You have mail.
What the user types, contrasted with on-screen computer output.
<prompt>%</prompt> <userinput>date +"The time is %H:%M"</userinput>
The time is 09:18
Manual page references.
Use <citerefentry><refentrytitle>su</refentrytitle><manvolnum>1</manvolnum></citerefentry> to change user identity.
User and group names.
Only <systemitem class="username">root</systemitem> can do this.
Emphasis.
The user <emphasis>must</emphasis> do this.
Text that the user is expected to replace with the actual text.
To search for a keyword in the manual pages, type <command>man -k <replaceable>keyword</replaceable></command>
Environment variables.
<envar>$HOME</envar> is set to the user's home directory.
Notes, Tips, Important Information, Warnings, and Examples
Notes, warnings, and examples appear within the text.
Notes are represented like this, and contain information to take note of, as it may affect what the user does.
Tips are represented like this, and contain information helpful to the user, like showing an easier way to do something.
Important information is represented like this. Typically, these show extra steps the user may need to take.
Warnings are represented like this, and contain information warning about possible damage if the instructions are not followed. This damage may be physical, to the hardware or the user, or it may be non-physical, such as the inadvertent deletion of important files.
A Sample Example
Examples are represented like this, and typically contain examples showing a walkthrough, or the results of a particular action.
Acknowledgments
My thanks to Sue Blake, Patrick Durusau, Jon Hamilton, Peter Flynn, and Christopher Maden, who took the time to read early drafts of this document and offer many valuable comments and criticisms.
Overview
Welcome to the FreeBSD Documentation Project (<acronym>FDP</acronym>). Quality documentation is crucial to the success of FreeBSD, and we value your contributions very highly.
This document describes how the <acronym>FDP</acronym> is organized, how to write and submit documentation, and how to effectively use the available tools.
Everyone is welcome to contribute to the <acronym>FDP</acronym>. Willingness to contribute is the only membership requirement.
This primer shows how to:

Loading…

No matching activity found.

Browse all component changes

Source information

Source string comment
(itstool) path: row/entry
Flags
read-only
Source string location
book.translate.xml:261
String age
a year ago
Source string age
a year ago
Translation file
books/fdp-primer.pot, string 43