From owner-svn-doc-projects@FreeBSD.ORG Mon Sep 3 19:47:51 2012
Return-Path:
Delivered-To: svn-doc-projects@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
by hub.freebsd.org (Postfix) with ESMTP id B408D1065674;
Mon, 3 Sep 2012 19:47:51 +0000 (UTC)
(envelope-from gabor@FreeBSD.org)
Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:4f8:fff6::2c])
by mx1.freebsd.org (Postfix) with ESMTP id 9F8618FC12;
Mon, 3 Sep 2012 19:47:51 +0000 (UTC)
Received: from svn.freebsd.org (localhost [127.0.0.1])
by svn.freebsd.org (8.14.4/8.14.4) with ESMTP id q83JlpaM034986;
Mon, 3 Sep 2012 19:47:51 GMT (envelope-from gabor@svn.freebsd.org)
Received: (from gabor@localhost)
by svn.freebsd.org (8.14.4/8.14.4/Submit) id q83JlpNh034984;
Mon, 3 Sep 2012 19:47:51 GMT (envelope-from gabor@svn.freebsd.org)
Message-Id: <201209031947.q83JlpNh034984@svn.freebsd.org>
From: Gabor Kovesdan
Date: Mon, 3 Sep 2012 19:47:51 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org
X-SVN-Group: doc-projects
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc:
Subject: svn commit: r39494 - projects/sgml2xml/share/mk
X-BeenThere: svn-doc-projects@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SVN commit messages for doc projects trees
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Mon, 03 Sep 2012 19:47:51 -0000
Author: gabor
Date: Mon Sep 3 19:47:51 2012
New Revision: 39494
URL: http://svn.freebsd.org/changeset/doc/39494
Log:
- The latest version of tidy broke compatibility and expects different
command-line options. It seems that this is the correct fix for the
earlier problems.
Approved by: doceng (implicit)
Modified:
projects/sgml2xml/share/mk/doc.docbook.mk
Modified: projects/sgml2xml/share/mk/doc.docbook.mk
==============================================================================
--- projects/sgml2xml/share/mk/doc.docbook.mk Mon Sep 3 10:20:43 2012 (r39493)
+++ projects/sgml2xml/share/mk/doc.docbook.mk Mon Sep 3 19:47:51 2012 (r39494)
@@ -257,10 +257,11 @@ TOUCH?= /usr/bin/touch
XARGS?= /usr/bin/xargs
GROFF?= groff
-.if empty(LANGCODE:S/./ . /g:MISO8859-1)
-TIDYOPTS?= -wrap 90 -m -raw -preserve -f /dev/null -asxml ${TIDYFLAGS}
+TIDY_VER!= ${TIDY} -v
+.if ${TIDY_VER} == "HTML Tidy for FreeBSD released on 7 December 2008"
+TIDYOPTS?= -wrap 90 -m -raw --preserve-entities yes -f /dev/null -asxml ${TIDYFLAGS}
.else
-TIDYOPTS?= -wrap 90 -m -f /dev/null -asxml ${TIDYFLAGS}
+TIDYOPTS?= -wrap 90 -m -raw -preserve -f /dev/null -asxml ${TIDYFLAGS}
.endif
HTML2TXT?= ${PREFIX}/bin/links
HTML2TXTOPTS?= -dump -width 72 ${HTML2TXTFLAGS}
From owner-svn-doc-projects@FreeBSD.ORG Tue Sep 4 21:35:18 2012
Return-Path:
Delivered-To: svn-doc-projects@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id B0E8B1065670;
Tue, 4 Sep 2012 21:35:18 +0000 (UTC)
(envelope-from gabor@FreeBSD.org)
Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:4f8:fff6::2c])
by mx1.freebsd.org (Postfix) with ESMTP id 97EDE8FC12;
Tue, 4 Sep 2012 21:35:18 +0000 (UTC)
Received: from svn.freebsd.org (localhost [127.0.0.1])
by svn.freebsd.org (8.14.4/8.14.4) with ESMTP id q84LZItc022469;
Tue, 4 Sep 2012 21:35:18 GMT (envelope-from gabor@svn.freebsd.org)
Received: (from gabor@localhost)
by svn.freebsd.org (8.14.4/8.14.4/Submit) id q84LZHwY022444;
Tue, 4 Sep 2012 21:35:17 GMT (envelope-from gabor@svn.freebsd.org)
Message-Id: <201209042135.q84LZHwY022444@svn.freebsd.org>
From: Gabor Kovesdan
Date: Tue, 4 Sep 2012 21:35:17 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org
X-SVN-Group: doc-projects
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc:
Subject: svn commit: r39499 - in projects/sgml2xml:
en_US.ISO8859-1/articles/committers-guide
en_US.ISO8859-1/articles/contributors
en_US.ISO8859-1/articles/problem-reports
en_US.ISO8859-1/books/faq en_US.I...
X-BeenThere: svn-doc-projects@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SVN commit messages for doc projects trees
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Tue, 04 Sep 2012 21:35:18 -0000
Author: gabor
Date: Tue Sep 4 21:35:17 2012
New Revision: 39499
URL: http://svn.freebsd.org/changeset/doc/39499
Log:
- MFH
Approved by: doceng (implicit)
Deleted:
projects/sgml2xml/en_US.ISO8859-1/htdocs/projects/gnats4/
Modified:
projects/sgml2xml/en_US.ISO8859-1/articles/committers-guide/article.sgml
projects/sgml2xml/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml
projects/sgml2xml/en_US.ISO8859-1/articles/problem-reports/article.sgml
projects/sgml2xml/en_US.ISO8859-1/books/faq/book.sgml
projects/sgml2xml/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
projects/sgml2xml/en_US.ISO8859-1/books/handbook/ports/chapter.sgml
projects/sgml2xml/en_US.ISO8859-1/books/porters-handbook/book.sgml
projects/sgml2xml/en_US.ISO8859-1/htdocs/administration.sgml
projects/sgml2xml/en_US.ISO8859-1/htdocs/internal/homepage.pl
projects/sgml2xml/en_US.ISO8859-1/htdocs/multimedia/multimedia-input.xml
projects/sgml2xml/en_US.ISO8859-1/htdocs/platforms/ppc.sgml
projects/sgml2xml/en_US.ISO8859-1/htdocs/ports/index.sgml
projects/sgml2xml/en_US.ISO8859-1/htdocs/releases/9.0R/hardware.html (contents, props changed)
projects/sgml2xml/en_US.ISO8859-1/htdocs/search/search.sgml
projects/sgml2xml/en_US.ISO8859-1/htdocs/search/sitemap.xml
projects/sgml2xml/en_US.ISO8859-1/htdocs/snapshots/index.sgml
projects/sgml2xml/en_US.ISO8859-1/htdocs/support/bugreports.sgml
projects/sgml2xml/ja_JP.eucJP/htdocs/platforms/ppc.sgml
projects/sgml2xml/ja_JP.eucJP/htdocs/search/search.sgml
projects/sgml2xml/ja_JP.eucJP/htdocs/support/bugreports.sgml
projects/sgml2xml/mn_MN.UTF-8/books/handbook/cutting-edge/chapter.sgml
projects/sgml2xml/mn_MN.UTF-8/books/handbook/filesystems/chapter.sgml
projects/sgml2xml/mn_MN.UTF-8/books/handbook/mirrors/chapter.sgml
projects/sgml2xml/mn_MN.UTF-8/books/handbook/ports/chapter.sgml
projects/sgml2xml/mn_MN.UTF-8/books/handbook/users/chapter.sgml
projects/sgml2xml/share/sgml/commercial.consult.xml
projects/sgml2xml/share/sgml/mirrors.xml
projects/sgml2xml/zh_CN.GB2312/books/handbook/geom/chapter.sgml
Directory Properties:
projects/sgml2xml/ (props changed)
Modified: projects/sgml2xml/en_US.ISO8859-1/articles/committers-guide/article.sgml
==============================================================================
--- projects/sgml2xml/en_US.ISO8859-1/articles/committers-guide/article.sgml Tue Sep 4 15:43:44 2012 (r39498)
+++ projects/sgml2xml/en_US.ISO8859-1/articles/committers-guide/article.sgml Tue Sep 4 21:35:17 2012 (r39499)
@@ -1447,7 +1447,7 @@ $target - head/$source:$P,$Q,$R
Practical Example
- As an practical example, consider the following scenario:
+ As a practical example, consider the following scenario:
The changes to netmap.4 in r238987 is
to be merged from CURRENT to 9-STABLE. The file resides in
head/share/man/man4 and
Modified: projects/sgml2xml/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml
==============================================================================
--- projects/sgml2xml/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml Tue Sep 4 15:43:44 2012 (r39498)
+++ projects/sgml2xml/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml Tue Sep 4 21:35:17 2012 (r39499)
@@ -8066,6 +8066,11 @@
+ Paulo Fragoso
+ paulo@nlink.com.br
+
+
+ Paulo Menezes
paulo@isr.uc.pt
Modified: projects/sgml2xml/en_US.ISO8859-1/articles/problem-reports/article.sgml
==============================================================================
--- projects/sgml2xml/en_US.ISO8859-1/articles/problem-reports/article.sgml Tue Sep 4 15:43:44 2012 (r39498)
+++ projects/sgml2xml/en_US.ISO8859-1/articles/problem-reports/article.sgml Tue Sep 4 21:35:17 2012 (r39499)
@@ -650,7 +650,7 @@
adding one or more email addresses to the
Cc: header.
- In the email template you will find the following two
+ In the email template only, you will find the following
single-line fields:
@@ -668,6 +668,48 @@
CVSup.
+
+ Severity: One of
+ non-critical,
+ serious or
+ critical. Do not overreact; refrain
+ from labeling your problem critical
+ unless it really is (e.g., data corruption issues, serious
+ regression from previous functionality in -CURRENT)
+ or serious unless
+ it is something that will affect many users (kernel
+ panics or freezes; problems with
+ particular device drivers or system utilities). &os;
+ developers will not necessarily work on your problem faster
+ if you inflate its importance since there are so many other
+ people who have done exactly that — in fact, some
+ developers pay little attention to this field
+ because of this.
+
+
+ Security problems should not
+ be filed in GNATS, because all GNATS information is public
+ knowledge. Please send such problems according to our
+ security
+ report guidelines.
+
+
+
+
+ Priority: One of
+ low, medium or
+ high. high should
+ be reserved for problems that will affect practically
+ every user of &os; and medium for
+ something that will affect many users.
+
+
+ This field has become so widely abused that it is
+ almost completely meaningless.
+
+
+
+
The next section describes fields that are common to both
@@ -719,46 +761,6 @@
- Severity: One of
- non-critical,
- serious or
- critical. Do not overreact; refrain
- from labeling your problem critical
- unless it really is (e.g. data corruption issues, serious
- regression from previous functionality in -CURRENT)
- or serious unless
- it is something that will affect many users (kernel
- panics or freezes; problems with
- particular device drivers or system utilities). &os;
- developers will not necessarily work on your problem faster
- if you inflate its importance since there are so many other
- people who have done exactly that — in fact, some
- developers pay little attention to this field
- because of this.
-
-
- Major security problems should not
- be filed in GNATS, because all GNATS information is public
- knowledge. Please send such problems in private email to
- &a.security-officer;.
-
-
-
-
- Priority: One of
- low, medium or
- high. high should
- be reserved for problems that will affect practically
- every user of &os; and medium for
- something that will affect many users.
-
-
- This field has become so widely abused that it is
- almost completely meaningless.
-
-
-
- Category: Choose an appropriate
category.
Modified: projects/sgml2xml/en_US.ISO8859-1/books/faq/book.sgml
==============================================================================
--- projects/sgml2xml/en_US.ISO8859-1/books/faq/book.sgml Tue Sep 4 15:43:44 2012 (r39498)
+++ projects/sgml2xml/en_US.ISO8859-1/books/faq/book.sgml Tue Sep 4 21:35:17 2012 (r39499)
@@ -2082,28 +2082,6 @@
shows up before loader is started.
-
-
-
- Installation crashes while booting, what can I do?
-
-
-
- Try disabling ACPI support. When the bootloader loads,
- press the Space key. The system will display
- the following:
-
- OK
-
- Type:
-
- unset acpi_load
-
- And then type:
-
- boot
-
-
@@ -2749,18 +2727,6 @@ bindkey ^[[3~ delete-char # for xterm
-
- How do I disable ACPI?
-
-
-
- Add following line
- hint.acpi.0.disabled="1" into your
- /boot/device.hints file.
-
-
-
- Why does my Micron system hang at boot time?
@@ -10429,20 +10395,6 @@ hint.sio.7.irq="12"
-
- Can you assign a major number for a device driver I have
- written?
-
-
-
- &os; releases after February 2003 has a facility for
- dynamically and automatically allocating major numbers for
- device drivers at runtime (see &man.devfs.5;), so there is
- no need for this.
-
-
-
- What about alternative layout policies for
directories?
Modified: projects/sgml2xml/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
==============================================================================
--- projects/sgml2xml/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml Tue Sep 4 15:43:44 2012 (r39498)
+++ projects/sgml2xml/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml Tue Sep 4 21:35:17 2012 (r39499)
@@ -258,13 +258,13 @@
In Subversion, URLs are used to designate a repository,
taking the form of protocol://hostname/path.
Mirrors may support different protocols as specified below. The
- first component of the path is the FreeBSD repository to access.
+ first component of the path is the &os; repository to access.
There are three different repositories, base
- for the &os; Base system, ports for the
- FreeBSD Ports Collection, and doc for the
- FreeBSD Documentation. For example, the URL
+ for the &os; base system source code, ports
+ for the Ports Collection, and doc for
+ documentation. For example, the URL
svn://svn0.us-east.FreeBSD.org/ports/head/
- specifies the main branch of the &os; ports repository on the
+ specifies the main branch of the ports repository on the
svn0.us-east.FreeBSD.org mirror,
using the svn protocol.
Modified: projects/sgml2xml/en_US.ISO8859-1/books/handbook/ports/chapter.sgml
==============================================================================
--- projects/sgml2xml/en_US.ISO8859-1/books/handbook/ports/chapter.sgml Tue Sep 4 15:43:44 2012 (r39498)
+++ projects/sgml2xml/en_US.ISO8859-1/books/handbook/ports/chapter.sgml Tue Sep 4 21:35:17 2012 (r39499)
@@ -980,6 +980,32 @@ docbook =
+ When installing a port, using only make
+ install from the
+ beginning means there will potentially be many waiting
+ periods between user interaction as the default behaviour
+ is to prompt the user for options. When there are many
+ dependencies, this sometimes makes building a single port
+ a huge hassle. To avoid this, first run make
+ config-recursive to
+ do the configuration in one batch. Then run
+ make install
+ [clean] afterwards.
+
+
+
+ When using config-recursive,
+ the list of ports to configure are gathered by the
+ all-depends-list &man.make.1;
+ target. It is often recommended to run make
+ config-recursive
+ until all dependent ports options have been defined, and
+ ports options &man.dialog.1; screens no longer
+ appear, to be certain all ports options have been
+ configured as intended.
+
+
+ Some shells keep a cache of the commands that are
available in the directories listed in the
PATH environment variable, to speed up
Modified: projects/sgml2xml/en_US.ISO8859-1/books/porters-handbook/book.sgml
==============================================================================
--- projects/sgml2xml/en_US.ISO8859-1/books/porters-handbook/book.sgml Tue Sep 4 15:43:44 2012 (r39498)
+++ projects/sgml2xml/en_US.ISO8859-1/books/porters-handbook/book.sgml Tue Sep 4 21:35:17 2012 (r39499)
@@ -124,12 +124,7 @@
The minimal Makefile would look
something like this:
- # New ports collection makefile for: oneko
-# Date created: 5 December 1994
-# Whom: asami
-#
-# $FreeBSD$
-#
+ # $FreeBSD$
PORTNAME= oneko
PORTVERSION= 1.1b
@@ -145,6 +140,14 @@ USE_IMAKE= yes
.include <bsd.port.mk>
+
+ In some cases, the Makefile of an
+ existing port may contain additional lines in the header,
+ such as the name and email of the person that originally
+ created the port. This additional information has been
+ declared obsolete, and is being phased out.
+
+
See if you can figure it out. Do not worry about the
contents of the $FreeBSD$
line, it will be filled in automatically by SVN when the port
@@ -3415,30 +3418,33 @@ ALWAYS_KEEP_DISTFILES= yes
COMMENTThis is a one-line description of the port.
- Please respect the following rules:
-
+ Please respect the following rules:
+ Try to keep the COMMENT value at no longer than 70
- characters, as this line will be used by the &man.pkg.info.1;
- utility to display a one-line summary of the port;
+ characters, as this line will be used by the
+ &man.pkg.info.1; utility to display a one-line summary
+ of the port;
- Do not include the package name
- (or version number of the software);
+ Do not include the package
+ name (or version number of the software);
- The comment should begin with a capital and end without a
- period;
+ The comment should begin with a capital and end
+ without a period;
- Do not start with an indefinite article (i.e. A or An);
+ Do not start with an indefinite article (i.e.
+ A or An);
- Names are capitalized (e.g. Apache, JavaScript, Perl);
+ Names are capitalized (e.g. Apache, JavaScript,
+ Perl);
- For lists of words use the Oxford comma (e.g. green,
- red, and blue);
+ For lists of words use the Oxford comma (e.g.
+ green, red, and blue);Spell check the text.
@@ -16293,20 +16299,10 @@ IGNORE= POINTYHAT is not supported
Makefile.
[the header...just to make it easier for us to identify the ports.]
-# New ports collection makefile for: xdvi
-[the "version required" line is only needed when the PORTVERSION
- variable is not specific enough to describe the port.]
-# Date created: 26 May 1995
-[this is the person who did the original port to FreeBSD, in particular, the
-person who wrote the first version of this Makefile. Remember, this should
-not be changed when upgrading the port later.]
-# Whom: Satoshi Asami <asami@FreeBSD.org>
-#
# $FreeBSD$
[ ^^^^^^^^^ This will be automatically replaced with RCS ID string by SVN
when it is committed to our repository. If upgrading a port, do not alter
this line back to "$FreeBSD$". SVN deals with it automatically.]
-#
[section to describe the port itself and the master site - PORTNAME
and PORTVERSION are always first, followed by CATEGORIES,
Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/administration.sgml
==============================================================================
--- projects/sgml2xml/en_US.ISO8859-1/htdocs/administration.sgml Tue Sep 4 15:43:44 2012 (r39498)
+++ projects/sgml2xml/en_US.ISO8859-1/htdocs/administration.sgml Tue Sep 4 21:35:17 2012 (r39499)
@@ -57,7 +57,6 @@
The CVS doc/www Repository Managers are allowed to directly modify the
- repository without using the CVS tool. It is their responsibility to
- ensure that technical problems that arise in the repository are
- resolved quickly. The CVS doc/www repository managers have the
- authority to back out commits if this is necessary to resolve a CVS
- technical problem. Repo-copy requests should be directed to the
- repository managers.
Each ``port'' listed here
contains any patches necessary to make the original application source
code compile and run on FreeBSD. Installing an application is as
-simple as downloading the port, unpacking it and typing
+simple as typing
make
-in the port directory. However, the most convenient (and common) method
-is to download the framework for the entire list of ports by installing the
+in the port directory. If you
+download the framework for the entire list of ports by installing the
-
-entire ports hierarchy at FreeBSD installation time, and then have
+
+ports hierarchy, you can have
thousands of applications right at your fingertips.
Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/search/sitemap.xml
==============================================================================
--- projects/sgml2xml/en_US.ISO8859-1/htdocs/search/sitemap.xml Tue Sep 4 15:43:44 2012 (r39498)
+++ projects/sgml2xml/en_US.ISO8859-1/htdocs/search/sitemap.xml Tue Sep 4 21:35:17 2012 (r39499)
@@ -1749,11 +1749,6 @@
- FreeBSD GNATS Upgrade
- &base;/projects/gnats4/index.html
-
-
- FreeBSD Project Ideas&base;/projects/ideas/index.html
Modified: projects/sgml2xml/en_US.ISO8859-1/htdocs/snapshots/index.sgml
==============================================================================
--- projects/sgml2xml/en_US.ISO8859-1/htdocs/snapshots/index.sgml Tue Sep 4 15:43:44 2012 (r39498)
+++ projects/sgml2xml/en_US.ISO8859-1/htdocs/snapshots/index.sgml Tue Sep 4 21:35:17 2012 (r39499)
@@ -25,6 +25,7 @@
These snapshots will be very similar to full releases,
except that they might not include all the bits included in a
full release (such as packages and updated documentation).
+-->
Problem reports may be submitted to the development team using the
send-pr(1)
- command on a &os; system. Another way to submit a problem report is
- to use the web based form,
- or by sending an email message to freebsd-bugs@FreeBSD.org.
- Please note that send-pr is preferred
- since messages sent to the mailing list are not tracked as
+ command on a &os; system or by
+ using the web based form.
+ Please note that
+ messages sent to a mailing list are not tracked as
official problem reports, and may get lost in the noise!
Before submitting a problem report, you might find it useful to
Modified: projects/sgml2xml/ja_JP.eucJP/htdocs/platforms/ppc.sgml
==============================================================================
--- projects/sgml2xml/ja_JP.eucJP/htdocs/platforms/ppc.sgml Tue Sep 4 15:43:44 2012 (r39498)
+++ projects/sgml2xml/ja_JP.eucJP/htdocs/platforms/ppc.sgml Tue Sep 4 21:35:17 2012 (r39499)
@@ -6,7 +6,7 @@
-
+
@@ -240,25 +240,25 @@ OK load /boot/kernel/kernel.save
Modified: projects/sgml2xml/pt_BR.ISO8859-1/articles/Makefile
==============================================================================
--- projects/sgml2xml/pt_BR.ISO8859-1/articles/Makefile Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/articles/Makefile Thu Sep 6 15:20:49 2012 (r39512)
@@ -1,15 +1,21 @@
-# $FreeBSD$
#
# Build the FreeBSD FAQ
#
# The FreeBSD Documentation Project
# The FreeBSD Brazilian Portuguese Documentation Project
#
-# Original revision: 1.36
+# Original revision: r38826
#
+# $FreeBSD$
SUBDIR =
SUBDIR+= contributing
+SUBDIR+= contributing-ports
+SUBDIR+= explaining-bsd
+SUBDIR+= freebsd-questions
+SUBDIR+= linux-users
+SUBDIR+= new-users
+SUBDIR+= problem-reports
DOC_PREFIX?= ${.CURDIR}/../..
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
Modified: projects/sgml2xml/pt_BR.ISO8859-1/articles/Makefile.inc
==============================================================================
--- projects/sgml2xml/pt_BR.ISO8859-1/articles/Makefile.inc Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/articles/Makefile.inc Thu Sep 6 15:20:49 2012 (r39512)
@@ -2,7 +2,7 @@
# The FreeBSD Documentation Project
# The FreeBSD Brazilian Portuguese Documentation Project
#
-# Original revision: 1.4
+# Original revision: r38826
#
# $FreeBSD$
#
Modified: projects/sgml2xml/pt_BR.ISO8859-1/articles/contributing-ports/article.sgml
==============================================================================
--- head/pt_BR.ISO8859-1/articles/contributing-ports/article.sgml Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/articles/contributing-ports/article.sgml Thu Sep 6 15:20:49 2012 (r39512)
@@ -1,3 +1,10 @@
+
+
+%entities;
+]>
+
-
-%articles.ent;
-
-]>
Contribuindo para a Coleção de Ports do
Modified: projects/sgml2xml/pt_BR.ISO8859-1/articles/contributing/Makefile
==============================================================================
--- projects/sgml2xml/pt_BR.ISO8859-1/articles/contributing/Makefile Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/articles/contributing/Makefile Thu Sep 6 15:20:49 2012 (r39512)
@@ -1,16 +1,14 @@
# $FreeBSD$
#
-# Build the FreeBSD FAQ
-#
# The FreeBSD Documentation Project
# The FreeBSD Brazilian Portuguese Documentation Project
#
-# Original revision: 1.4
+# Original revision: r38826
#
DOC?= article
-FORMATS?= html
+FORMATS?= html html-split
INSTALL_COMPRESSED?=gz
INSTALL_ONLY_COMPRESSED?=
Modified: projects/sgml2xml/pt_BR.ISO8859-1/articles/contributing/article.sgml
==============================================================================
--- projects/sgml2xml/pt_BR.ISO8859-1/articles/contributing/article.sgml Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/articles/contributing/article.sgml Thu Sep 6 15:20:49 2012 (r39512)
@@ -9,12 +9,12 @@
The FreeBSD Documentation Project
The FreeBSD Brazilian Portuguese Documentation Project
- Original revision: 1.496
+ Original revision: r38826
$FreeBSD$
-->
-
+Contribuindo para o FreeBSD
@@ -123,9 +123,9 @@
idioma, voc pode ajudar a traduzir novos documentos
ou verificar se as tradu苺es existentes
esto atualizadas. Primeiro, verifique o FAQ sobre
- tradu苺es no &a.ptbr.p.fdpp;.
- Voc no estar se comprometendo a
+ url="&url.books.fdp-primer;/translations.html">FAQ sobre
+ traduções no &a.ptbr.p.fdpp;.
+ Você não estará se comprometendo a
traduzir todos os documentos do FreeBSD fazendo isto
— como um voluntrio, voc pode
traduzir muitos ou poucos documentos, quantos desejar.
@@ -159,7 +159,7 @@
profundo do kernel do FreeBSD; ou, ambos. Entretanto,
tambm existem muitas tarefas teis que
so apropriadas para os hackers de final de
- semana.
+ semana.
@@ -194,14 +194,14 @@
Mova as contribui苺es de
software para
- src/contrib na rvore do
- cdigo fonte.
+ src/contrib
+ na árvore do código fonte.
- Tenha certeza que o cdigo disponvel em
- src/contrib est
- atualizado.
+ Tenha certeza que o código disponível em
+ src/contrib
+ está atualizado.
@@ -220,7 +220,8 @@
Se voc contribuiu com algum dos
- ports, envie suas
+ ports, e teve que fazer alguma
+ mudança específica para o &os;, envie suas
corre苺es de volta aos autores originais
(isto tornar sua vida mais fcil quando
eles lanarem a prxima
@@ -231,9 +232,9 @@
Consiga cpias de padres formais tais
como &posix;. Voc pode obter alguns
links sobre estes
- padres no stio www FreeBSD
- C99 e Projeto de Conformidade com Padres
+ padrões no sítio www FreeBSD
+ C99 e Projeto de Conformidade com Padrões
Posix. Compare o comportamento do FreeBSD
quele requerido pelo padro. Se o
comportamento diferir, particularmente em pontos sutis ou
@@ -256,12 +257,14 @@
Trabalhe no banco de dados de PR
(relatrio de problemas)
- base de dados de relatrios de
- problemas
+
+ base de dados de relatórios de
+ problemas
+ A Lista
- de PRs do FreeBSD mostra todos os
+ url="&url.base;/cgi/query-pr-summary.cgi">Lista
+ de PRs do FreeBSD mostra todos os
relatrios de problemas ativos no momento e os pedidos
de melhoria que foram submetidos pelos usurios do
FreeBSD. O banco de dados inclui tarefas para programadores e
@@ -282,6 +285,18 @@
um patch pronto para ser testado, ou
voc pode discutir novas idias com ele.
+
+
+ Escolha um dos itens da página de
+ idéias
+
+ A lista de projetos
+ do &os; e de idéias para voluntários
+ também está disponível para as pessoas
+ dispostas a contribuir com o projeto &os;. A lista é
+ atualizada regularmente e contém itens sobre cada projeto
+ para programadores e para não programadores.
+
@@ -299,37 +314,37 @@
&a.hackers;. Da mesma forma, pessoas com interesse neste tipo
de assunto (e uma tolerncia para um
alto volume de mensagens!), devem se
- inscrever na &a.hackers; atravs do envio de um e-mail
- para &a.majordomo;. Consulte o &a.ptbr.p.handbook;
- para maiores informa苺es sobre esta e outras
- listas de discusso.
+ inscrever na &a.hackers;. Consulte o &a.ptbr.p.handbook;
+ para maiores informações sobre esta e outras
+ listas de discussão.
Se voc encontrar um erro ou estiver enviando uma
altera艫o especfica; por favor,
faa o relatrio utilizando o programa
&man.send-pr.1; ou a sua interface WWW
+ url="&url.base;/send-pr.html">interface WWW
equivalente. A no ser que ele exceda 65KB,
inclua qualquer patch diretamente no
- relatrio. Se o patch
- destinado a ser aplicado na rvore de cdigo,
- coloque a palavra [PATCH] na sinpse
- do relatrio. Quando incluir um
- patch, no o
- faa utilizando copiar-e-colar porque ao copiar-e-colar
- os tabs sero convertidos para
- espaos, e tornar o patch
- inutilizvel. Se o patch
- ultrapassar 20KB considere a possibilidade de comprimi-lo e
- utilizar o &man.uuencode.1; antes de envi-lo.
+ relatório. Se o patch é
+ destinado a ser aplicado na árvore de código,
+ coloque a palavra [PATCH] na sinópse
+ do relatório. Quando incluir um
+ patch, não o
+ faça utilizando copiar-e-colar porque ao copiar-e-colar
+ os tabs serão convertidos para
+ espaços, e tornará o patch
+ inutilizável. Quando os patches
+ forem muito maiores que 20KB, considere a possibilidade de
+ comprimi-los (por ex. usando &man.gzip.1; or &man.bzip2.1;) e
+ utilize o &man.uuencode.1; para incluir a versão
+ compactada no seu relatório de problema.
Depois de enviar o relatrio, voce deve receber uma
confirma艫o junto com um nmero de
registro. Guarde este nmero de registro, de forma que
voc possa nos manter atualizados sobre o seu problema
- enviando um e-mail para
- bug-followup@FreeBSD.org. Coloque o
+ enviando um e-mail para &a.bugfollowup;. Coloque o
nmero no assunto da mensagem, por ex. "Re:
kern/3377". Informa苺es adicionais
sobre qualquer relatrio de problema
@@ -344,9 +359,9 @@
pode pedir que algum o envie para voc enviando
e-mail para &a.bugs;.
- Consulte tambm este
- artigo sobre como escrever um bom relatrio
+ Consulte também este
+ artigo sobre como escrever um bom relatório
de problema.
@@ -354,16 +369,17 @@
Altera苺es na
Documenta艫o
- Envio de
- documenta艫o
+
+ Envio de documentação
+ Altera苺es na documenta艫o
so administradas pela &a.doc;. Por favor, verifique o
&a.ptbr.p.fdpp;
- para obter instru苺es detalhadas. Envie suas
- colabora苺es e altera苺es
- (inclusive as pequenas so bem vindas!) usando o
+ url="&url.books.fdp-primer;/index.html">&a.ptbr.p.fdpp;
+ para obter instruções detalhadas. Envie suas
+ colaborações e alterações
+ (inclusive as pequenas são bem vindas!) usando o
&man.send-pr.1; como descrito no Relatrios de Erro e
Comentrios em Geral.
@@ -386,8 +402,8 @@
em uma grande variedade de formas para a comodidade dos
desenvolvedores que trabalham ativamente no sistema. Consulte
o &a.ptbr.p.handbook;
- para maiores informa苺es sobre como obter e
+ &url.books.handbook;/current-stable.html">&a.ptbr.p.handbook;
+ para maiores informações sobre como obter e
utilizar o FreeBSD-CURRENT.Trabalhar com verses antigas do cdigo,
@@ -422,19 +438,25 @@
Por exemplo:
-
- &prompt.user; diff -c oldfile newfile
- ou
- &prompt.user; diff -c -r olddir newdir
- geraria o tal conjunto de diffs de contexto
- para um dado arquivo de cdigo ou para uma hierarquia
- de diretrios.
-
- Da mesma forma,
- &prompt.user; diff -u oldfile newfile
- ou
- &prompt.user; diff -u -r olddir newdir
- faria o mesmo, exceto que utilizando o formato de
+ &prompt.user; diff -c oldfile newfile
+
+ ou
+
+ &prompt.user; diff -c -r olddir newdir
+
+ geraria o tal conjunto de diffs de
+ contexto para um dado arquivo de código ou para uma
+ hierarquia de diretórios.
+
+ Da mesma forma,
+
+ &prompt.user; diff -u oldfile newfile
+
+ ou
+
+ &prompt.user; diff -u -r olddir newdir
+
+ faria o mesmo, exceto que utilizando o formato de
diff unificado.Consulte o manual do &man.diff.1; para maiores
@@ -519,7 +541,9 @@
- Licensa BSD
+
+ Licensa BSD
+ Os direitos autorais BSD. Este tipo de licensa
a mais prefervel devido a sua natureza
@@ -532,12 +556,14 @@
- GPLGNU General Public
- License
-
- Licena Pblica Geral GNU
+
+ GPLGNU General Public License
+
+
+ Licença Pública Geral GNU
(GNU General Public
- License)
+ License)
+ A licensa pblica geral GNU, ou
GPL. Esta licensa no
@@ -550,10 +576,11 @@
contribui苺es adicionais sob esta licensa.
O cdigo sob a GPL tambm vai para uma parte
diferente da rvore, mais especificamente para
- /sys/gnu ou
- /usr/src/gnu, de forma que
- muito fcil identific-lo para qualquer um
- que a GPL representa um problema.
+ /sys/gnu ou
+ /usr/src/gnu, de
+ forma que é muito fácil
+ identificá-lo para qualquer um que a GPL
+ representa um problema.
@@ -630,13 +657,15 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE PO
entidade isenta de impostos so freqüentemente
dedutveis dos impostos federais.
- As doa苺es podem ser enviadas
- atravs de cheques para: The FreeBSD
- Foundation 7321 Brockway Dr.
- Boulder, CO
- 80303USA
-
-
+ As doações podem ser enviadas
+ através de cheques para:
+
+ The FreeBSD Foundation
+ 7321 Brockway Dr.
+ Boulder,
+ CO, 80303
+ USA
+ A Funda艫o FreeBSD agora capaz de
receber doa苺es atravs da web com o
@@ -657,17 +686,19 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE PO
Doando Hardware
- doaces
+
+ doacões
+ O projeto de FreeBSD aceita alegremente
doa苺es de
hardware para as quais pode
encontrar bom uso. Se voce estiver interessado em doar
componentes de hardware; por
- favor, contate o Escritrio
- de Relacionamento com Doadores.
-
+ favor, contate o
+ Escritório de
+ Relacionamento com Doadores.
+
Doando Acesso Internet
@@ -676,8 +707,8 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE PO
espelho para os servios de FTP, WWW ou
cvsup. Se voc desejar se tornar
um stio espelho; por favor, consulte o artigo Espelhando o FreeBSD
- para maiores informa苺es.
+ url="&url.articles.hubs;/index.html">Espelhando o
+ FreeBSD para maiores informações.
Modified: projects/sgml2xml/pt_BR.ISO8859-1/articles/explaining-bsd/article.sgml
==============================================================================
--- head/pt_BR.ISO8859-1/articles/explaining-bsd/article.sgml Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/articles/explaining-bsd/article.sgml Thu Sep 6 15:20:49 2012 (r39512)
@@ -1,3 +1,10 @@
+
+
+%entities;
+]>
+
-
-%articles.ent;
-]>
-
Explicando o BSD
Modified: projects/sgml2xml/pt_BR.ISO8859-1/articles/freebsd-questions/article.sgml
==============================================================================
--- head/pt_BR.ISO8859-1/articles/freebsd-questions/article.sgml Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/articles/freebsd-questions/article.sgml Thu Sep 6 15:20:49 2012 (r39512)
@@ -1,3 +1,10 @@
+
+
+%entities;
+]>
+
-
-%articles.ent;
-]>
-
Como obter o melhor resultado para as suas perguntas na
@@ -297,10 +299,10 @@ your options page that will email your c
documentação do FreeBSD (elas estão
instaladas em /usr/doc ou
acessíveis via WWW em http://www.FreeBSD.org),
+ url="http://www.FreeBSD.org"> http://www.FreeBSD.org),
especialmente o handbook e o
- FAQ.
+ url="&url.books.handbook;/index.html">handbook e o
+ FAQ.
@@ -310,22 +312,22 @@ your options page that will email your c
antes. Você pode navegar e/ou realizar buscas no
histórico das listas de discussão nos URLs
http://www.FreeBSD.org/mail
+ url="http://www.FreeBSD.org/mail">http://www.FreeBSD.org/mail
e
+ url="http://www.FreeBSD.org/search/search.html#mailinglists">
http://www.FreeBSD.org/search/search.html#mailinglists
respectivamente. Isto também pode ser feito em
outros locais, como por exemplo em http://marc.theaimsgroup.com
+ url="http://marc.theaimsgroup.com">http://marc.theaimsgroup.com
.
Utilize um mecanismo de busca como o Google ou o Yahoo para procurar
+ url="http://www.google.com">Google ou o Yahoo para procurar
respostas para a sua dúvida. O Google possui uma
- interface especifica
+ interface especifica
para buscas relacionadas aos *BSDs.
@@ -368,7 +370,7 @@ your options page that will email your c
mensagem. Se o assunto da sua mensagem não for
específico o suficiente, as pessoas que podem
responder a sua duvida podem não se interessar em ler
- a sua mensagem.
+ a sua mensagem.
Modified: projects/sgml2xml/pt_BR.ISO8859-1/articles/linux-users/article.sgml
==============================================================================
--- head/pt_BR.ISO8859-1/articles/linux-users/article.sgml Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/articles/linux-users/article.sgml Thu Sep 6 15:20:49 2012 (r39512)
@@ -1,3 +1,10 @@
+
+
+%entities;
+]>
+
-
-%articles.ent;
-]>
-
Guia Rápido do FreeBSD para Usuários
Modified: projects/sgml2xml/pt_BR.ISO8859-1/articles/new-users/article.sgml
==============================================================================
--- head/pt_BR.ISO8859-1/articles/new-users/article.sgml Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/articles/new-users/article.sgml Thu Sep 6 15:20:49 2012 (r39512)
@@ -1,3 +1,10 @@
+
+
+%entities;
+]>
+
-
-%articles.ent;
-]>
-
Para os novatos em FreeBSD e &unix;
Modified: projects/sgml2xml/pt_BR.ISO8859-1/articles/problem-reports/article.sgml
==============================================================================
--- head/pt_BR.ISO8859-1/articles/problem-reports/article.sgml Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/articles/problem-reports/article.sgml Thu Sep 6 15:20:49 2012 (r39512)
@@ -1,3 +1,10 @@
+
+
+%entities;
+]>
+
-
-%articles.ent;
-]>
-
Escrevendo Relatórios de Problema no &os;
@@ -335,7 +337,7 @@
banco de dados com os relatórios de problema do
&os; (GNATS). A menos que o seu problema seja
recente ou muito obscuro, existe uma boa chance dele
- já ter sido reportado.
+ já ter sido reportado.
@@ -432,7 +434,7 @@
de sinopse. (Embora não seja obrigatório
utilizar exatamente esta palavra, por
convenção, é ela que é
- utilizada.)
+ utilizada.)
@@ -642,7 +644,7 @@
relatório. Evite incluir dois ou mais
problemas em um mesmo relatório caso eles
não estejam relacionados. Quando
- você submeter um patch, evite
+ você submeter um patch, evite
adicionar várias funcionalidades ou corrigir
vários bugs em um mesmo PR, a menos que eles
sejam estritamente relacionados — Este tipo de
@@ -797,7 +799,7 @@
de serem incorporados, devem ser colocados em um servidor web
ou de FTP, e a url deve ser incluída no PR ao
invés do patch propriamente dito.
- Os patches dentro de um email tendem a se
+ Os patches dentro de um email tendem a se
deformar, especialmente quando o GNATS está envolvido,
e quanto maior o patch, maior é a dificuldade para
ambas as partes em consertá-lo. Além de que, ao
Modified: projects/sgml2xml/pt_BR.ISO8859-1/books/Makefile
==============================================================================
--- projects/sgml2xml/pt_BR.ISO8859-1/books/Makefile Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/books/Makefile Thu Sep 6 15:20:49 2012 (r39512)
@@ -6,6 +6,7 @@
# $FreeBSD$
SUBDIR+= faq
+SUBDIR+= fdp-primer
DOC_PREFIX?= ${.CURDIR}/../..
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
Modified: projects/sgml2xml/pt_BR.ISO8859-1/books/fdp-primer/book.sgml
==============================================================================
--- head/pt_BR.ISO8859-1/books/fdp-primer/book.sgml Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/books/fdp-primer/book.sgml Thu Sep 6 15:20:49 2012 (r39512)
@@ -1,3 +1,12 @@
+
+
+%entities;
+ %chapters;
+
+]>
+
-
-%books.ent;
- %chapters;
-
-
-]>
-
&a.ptbr.p.fdpp; para novos colaboradores
@@ -69,7 +70,7 @@
$FreeBSD$
- &bookinfo.legalnotice;
+ &legalnotice;
Obrigado por tornar-se parte do Projeto de
Modified: projects/sgml2xml/pt_BR.ISO8859-1/books/fdp-primer/examples/appendix.sgml
==============================================================================
--- head/pt_BR.ISO8859-1/books/fdp-primer/examples/appendix.sgml Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/books/fdp-primer/examples/appendix.sgml Thu Sep 6 15:20:49 2012 (r39512)
@@ -185,12 +185,12 @@
Convertendo de DocBook para HTML (em um único
grande arquivo)
- &prompt.user; jade -V nochunks \
- -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \
+ &prompt.user; jade -V nochunks \
+ -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \
-c /usr/local/share/sgml/docbook/catalog \
-c /usr/local/share/sgml/jade/catalog \
- -d /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl \
- -t sgml file.sgml > file.html
+ -d /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl \
+ -t sgml file.sgml > file.html
@@ -242,11 +242,11 @@
arquivos pequenos)&prompt.user; jade \
- -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \
+ -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \
-c /usr/local/share/sgml/docbook/catalog \
-c /usr/local/share/sgml/jade/catalog \
- -d /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl \
- -t sgml file.sgml
+ -d /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl \
+ -t sgml file.sgml
@@ -301,12 +301,12 @@
O arquivo fonte SGML precisa ser convertido para um
arquivo &tex;.
- &prompt.user; jade -V tex-backend \
- -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \
+ &prompt.user; jade -V tex-backend \
+ -c /usr/local/share/sgml/docbook/dsssl/modular/catalog \
-c /usr/local/share/sgml/docbook/catalog \
-c /usr/local/share/sgml/jade/catalog \
- -d /usr/local/share/sgml/docbook/dsssl/modular/print/docbook.dsl \
- -t tex file.sgml
+ -d /usr/local/share/sgml/docbook/dsssl/modular/print/docbook.dsl \
+ -t tex file.sgml
@@ -387,7 +387,7 @@
realizado quando se converte de DocBook para Postscript,
utilizando a mesma linha de comando para o
jade
- ().
+ ().
Quando o arquivo .tex já
tiver sido gerado, você deve executar o
Modified: projects/sgml2xml/pt_BR.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml
==============================================================================
--- head/pt_BR.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml Thu Sep 6 15:20:49 2012 (r39512)
@@ -1469,12 +1469,12 @@ main(void)
Quando você tivert terminado, seu prograva deve estar assim;
-#include <stdio.h>
+#include <stdio.h>
-int
+int
main(void)
{
- printf("hello, world\n");
+ printf("hello, world\n");
}
@@ -1497,12 +1497,12 @@ main(void)
Quando você tiver terminado, seu programa
deve estar assim;
- #include <stdio.h>
+ #include <stdio.h>
-int
+int
main(void)
{
- printf("hello, world\n");
+ printf("hello, world\n");
}
@@ -2672,17 +2672,17 @@ bom valor para n<mediaobject>
<imageobject>
- <imagedata fileref="fig1">
+ <imagedata fileref="fig1">
</imageobject>
<textobject>
- <literallayout class="monospaced">+---------------+
+ <literallayout class="monospaced">+---------------+
| A |
+---------------+</literallayout>
</textobject>
<textobject>
- <phrase>Uma figura</phrase>
+ <phrase>Uma figura</phrase>
</textobject>
</mediaobject>
@@ -2761,7 +2761,7 @@ IMAGES+= fig3.png
Você precisa ser cuidadoso quando separar a sua
documentação em arquivos menores (veja
- ) em
+ ) em
diretórios diferentes.Suponha que você tenha um livro com três
@@ -2791,7 +2791,7 @@ IMAGES+= fig3.png
<mediaobject>
<imageobject>
- <imagedata fileref="chapter1/fig1">
+ <imagedata fileref="chapter1/fig1">
</imageobject>
…
@@ -2914,10 +2914,10 @@ O qual não irá aparecer no
Maiores informações podem ser encontradas
- em
+ em Informações mais específicas podem ser
- encontradas na .
+ encontradas na .
]]>O texto do link será gerado automaticamente, e
Modified: projects/sgml2xml/pt_BR.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml
==============================================================================
--- head/pt_BR.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml Thu Sep 6 13:53:26 2012 (r39511)
+++ projects/sgml2xml/pt_BR.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml Thu Sep 6 15:20:49 2012 (r39512)
@@ -994,7 +994,7 @@ onsgmls:example.sgml:6:8:E: end tag for
Comentários são uma construção
SGML, e são normalmente válidos apenas dentro de
um DTD. Entretanto, como mostrou a
- , é possível
+ , é possível
utilizar sintaxe SGML com os seus documentos.O delimitador para um comentário SGML é o
Copied: projects/sgml2xml/pt_BR.ISO8859-1/share/sgml/articles.ent (from r39511, head/pt_BR.ISO8859-1/share/sgml/articles.ent)
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ projects/sgml2xml/pt_BR.ISO8859-1/share/sgml/articles.ent Thu Sep 6 15:20:49 2012 (r39512, copy of r39511, head/pt_BR.ISO8859-1/share/sgml/articles.ent)
@@ -0,0 +1,34 @@
+
+
+
+%l10n;
+
+%l10n-common;
+
+%man;
+
+%freebsd;
+
+%authors;
+
+%teams;
+
+%mailing-lists;
+
+%newsgroups;
+
+%trademarks;
+
+%urls;
+
+%words;
+
Copied: projects/sgml2xml/pt_BR.ISO8859-1/share/sgml/books.ent (from r39511, head/pt_BR.ISO8859-1/share/sgml/books.ent)
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ projects/sgml2xml/pt_BR.ISO8859-1/share/sgml/books.ent Thu Sep 6 15:20:49 2012 (r39512, copy of r39511, head/pt_BR.ISO8859-1/share/sgml/books.ent)
@@ -0,0 +1,35 @@
+