FreeBSD Doc/books_fdp-primer — Portuguese (Brazil) @ Weblate: Testing a new manual page can be challenging. Fortunately there …

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

Translation

Content

Source change

Testing a new manual page can be challenging ~~when it is not located in the normal manual page search path.~~. Fortunately there are some tools that can assist in the task. Some of them, like <citerefentry><refentrytitle>man</refentrytitle><manvolnum>1</manvolnum></citerefentry> ~~also~~, does not look in the current directory. I~~f the new manual page is in the current directory, prefix the filename with a <literal>./</literal>:~~t is a good idea to prefix the filename with <literal>./</literal> if the new manual page is in the current directory. An absolute path can also be used.

Source string comment (itstool) path: sect1/para

English

Testing a new manual page can be challenging. Fortunately there are some tools that can assist in the task. Some of them, like <citerefentry><refentrytitle>man</refentrytitle><manvolnum>1</manvolnum></citerefentry>, do not look in the current directory. It is a good idea to prefix the filename with <literal>./</literal> if the new manual page is in the current directory. An absolute path can also be used.

Portuguese (Brazil)

Needs editing

Context	English	Portuguese (Brazil)	State
	Name. Called with a name as a parameter on the first use, then used later without the parameter to display the name that has already been defined.	Name. Chamado com um nome como parâmetro no primeiro uso, usado depois sem o parâmetro para exibir o nome que já foi definido.
	<literal>.Pa</literal>	<literal>.Pa</literal>
	Path to a file. Used to mark up filenames and directory paths.	Path to a file (Caminho para um arquivo). Usado para marcar nomes de arquivos e caminhos de diretório.
	Sample Manual Page Structures	Exemplo de Estruturas de Página de Manual
	This section shows minimal desired man page contents for several common categories of manual pages.	Esta seção mostra o conteúdo mínimo desejável para um página de manual para várias categorias comuns de páginas de manual.
	Section 1 or 8 Command	Seção 1 ou 8 sobre um comando
	The preferred basic structure for a section 1 or 8 command:	A estrutura básica preferida para uma seção 1 ou 8 sobre um comando:
	.Dd August 25, 2017 .Dt EXAMPLECMD 8 .Os .Sh NAME .Nm examplecmd .Nd "command to demonstrate section 1 and 8 man pages" .Sh SYNOPSIS .Nm .Op Fl v .Sh DESCRIPTION The .Nm utility does nothing except demonstrate a trivial but complete manual page for a section 1 or 8 command. .Sh SEE ALSO .Xr exampleconf 5 .Sh AUTHORS .An Firstname Lastname Aq Mt flastname@example.com	.Dd August 25, 2017 .Dt EXAMPLECMD 8 .Os .Sh NAME .Nm examplecmd .Nd "command to demonstrate section 1 and 8 man pages" .Sh SYNOPSIS .Nm .Op Fl v .Sh DESCRIPTION The .Nm utility does nothing except demonstrate a trivial but complete manual page for a section 1 or 8 command. .Sh SEE ALSO .Xr exampleconf 5 .Sh AUTHORS .An Firstname Lastname Aq Mt flastname@example.com
	Section 4 Device Driver	Seção 4 sobre um Driver de Dispositivo
	The preferred basic structure for a section 4 device driver:	A estrutura básica preferida para a seção 4 sobre um driver de dispositivo:
	.Dd August 25, 2017 .Dt EXAMPLEDRIVER 4 .Os .Sh NAME .Nm exampledriver .Nd "driver to demonstrate section 4 man pages" .Sh SYNOPSIS To compile this driver into the kernel, add this line to the kernel configuration file: .Bd -ragged -offset indent .Cd "device exampledriver" .Ed .Pp To load the driver as a module at boot, add this line to .Xr loader.conf 5 : .Bd -literal -offset indent exampledriver_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides an opportunity to show a skeleton or template file for section 4 manual pages. .Sh HARDWARE The .Nm driver supports these cards from the aptly-named Nonexistent Technologies: .Pp .Bl -bullet -compact .It NT X149.2 (single and dual port) .It NT X149.8 (single port) .El .Sh DIAGNOSTICS .Bl -diag .It "flashing green light" Something bad happened. .It "flashing red light" Something really bad happened. .It "solid black light" Power cord is unplugged. .El .Sh SEE ALSO .Xr example 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 49.2 . .Sh AUTHORS .An Firstname Lastname Aq Mt flastname@example.com	.Dd August 25, 2017 .Dt EXAMPLEDRIVER 4 .Os .Sh NAME .Nm exampledriver .Nd "driver to demonstrate section 4 man pages" .Sh SYNOPSIS To compile this driver into the kernel, add this line to the kernel configuration file: .Bd -ragged -offset indent .Cd "device exampledriver" .Ed .Pp To load the driver as a module at boot, add this line to .Xr loader.conf 5 : .Bd -literal -offset indent exampledriver_load="YES" .Ed .Sh DESCRIPTION The .Nm driver provides an opportunity to show a skeleton or template file for section 4 manual pages. .Sh HARDWARE The .Nm driver supports these cards from the aptly-named Nonexistent Technologies: .Pp .Bl -bullet -compact .It NT X149.2 (single and dual port) .It NT X149.8 (single port) .El .Sh DIAGNOSTICS .Bl -diag .It "flashing green light" Something bad happened. .It "flashing red light" Something really bad happened. .It "solid black light" Power cord is unplugged. .El .Sh SEE ALSO .Xr example 8 .Sh HISTORY The .Nm device driver first appeared in .Fx 49.2 . .Sh AUTHORS .An Firstname Lastname Aq Mt flastname@example.com
	Section 5 Configuration File	Seção 5 sobre um Arquivo de Configuração
	The preferred basic structure for a section 5 configuration file:	A estrutura básica preferida para a seção 5 sobre um arquivo de configuração:
	.Dd August 25, 2017 .Dt EXAMPLECONF 5 .Os .Sh NAME .Nm example.conf .Nd "config file to demonstrate section 5 man pages" .Sh DESCRIPTION .Nm is an example configuration file. .Sh SEE ALSO .Xr example 8 .Sh AUTHORS .An Firstname Lastname Aq Mt flastname@example.com	.Dd August 25, 2017 .Dt EXAMPLECONF 5 .Os .Sh NAME .Nm example.conf .Nd "config file to demonstrate section 5 man pages" .Sh DESCRIPTION .Nm is an example configuration file. .Sh SEE ALSO .Xr example 8 .Sh AUTHORS .An Firstname Lastname Aq Mt flastname@example.com
	Testing	Traduzindo
	Testing a new manual page can be challenging. Fortunately there are some tools that can assist in the task. Some of them, like <citerefentry><refentrytitle>man</refentrytitle><manvolnum>1</manvolnum></citerefentry>, do not look in the current directory. It is a good idea to prefix the filename with <literal>./</literal> if the new manual page is in the current directory. An absolute path can also be used.	O teste de uma nova página de manual pode ser um desafio quando o arquivo não está localizado no caminho de pesquisa normal da páginas de manual. <citerefentry><refentrytitle>man</refentrytitle><manvolnum>1</manvolnum></citerefentry> também não procura no diretório atual. Se a nova página de manual estiver no diretório atual, prefixe o nome do arquivo com um <literal>./</literal>:
	Use <citerefentry><refentrytitle>mandoc</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s linter to check for parsing errors:	<citerefentry><refentrytitle>mandoc</refentrytitle><manvolnum>1</manvolnum></citerefentry>
	<prompt>%</prompt> <userinput>mandoc -T lint ./mynewmanpage.8</userinput>	<prompt>%</prompt> <userinput>man ./mynewmanpage.8</userinput>
	Use <package>textproc/igor</package> to proofread the manual page:
	<prompt>%</prompt> <userinput>igor ./mynewmanpage.8</userinput>	<prompt>%</prompt> <userinput>man ./mynewmanpage.8</userinput>
	Use <citerefentry><refentrytitle>man</refentrytitle><manvolnum>1</manvolnum></citerefentry> to check the final result of your changes:	Utilize <citerefentry><refentrytitle>su</refentrytitle><manvolnum>1</manvolnum></citerefentry> para assumir outro nome de usuário.
	<prompt>%</prompt> <userinput>man ./mynewmanpage.8</userinput>	<prompt>%</prompt> <userinput>man ./mynewmanpage.8</userinput>
	You can use <citerefentry><refentrytitle>col</refentrytitle><manvolnum>1</manvolnum></citerefentry> to filter the output of <citerefentry><refentrytitle>man</refentrytitle><manvolnum>1</manvolnum></citerefentry> and get rid of the backspace characters before loading the result in your favorite editor for spell checking:	Use<citerefentry><refentrytitle>tar</refentrytitle><manvolnum>1</manvolnum></citerefentry> e <citerefentry><refentrytitle>gzip</refentrytitle><manvolnum>1</manvolnum></citerefentry> para compactar sua documentação e enviá-lo para o projeto.
	<prompt>%</prompt> <userinput>man ./mynewmanpage.8 \| col -b \| vim -R -</userinput>	<prompt>%</prompt> <userinput>man ./mynewmanpage.8</userinput>
	Spell-checking with fully-featured dictionaries is encouraged, and can be accomplished by using <package>textproc/hunspell</package> or <package>textproc/aspell</package> combined with <package>textproc/en-hunspell</package> or <package>textproc/en-aspell</package>, respectively. For instance:
	<prompt>%</prompt> <userinput>aspell check --lang=en --mode=nroff ./mynewmanpage.8</userinput>	<prompt>%</prompt> <userinput>man ./mynewmanpage.8</userinput>
	Example Manual Pages to Use as Templates	Exemplos de páginas de manuais para usar como modelos
	Some manual pages are suitable as in-depth examples.	Algumas destas páginas de manual são adequadas para serem usadas como exemplos detalhados.
	Manual Page	Página Manual
	Path to Source Location	Caminho para o local de origem
	<filename>/usr/src/bin/cp/cp.1</filename>	<filename>/usr/src/bin/cp/cp.1</filename>