From 19ca5b971fa7e54e5dc54faee25979c02e3bcf9a Mon Sep 17 00:00:00 2001 From: Murray Stokely Date: Mon, 2 Aug 2004 05:43:34 +0000 Subject: [PATCH] Follow the rule set down in this book and use American English spelling. Translators can ignore. PR: docs/54999 Submitted by: Steven James Huwig --- .../books/fdp-primer/examples/appendix.sgml | 2 +- .../books/fdp-primer/sgml-markup/chapter.sgml | 16 +++++----- .../books/fdp-primer/sgml-primer/chapter.sgml | 32 +++++++++---------- .../books/fdp-primer/structure/chapter.sgml | 4 +-- .../books/fdp-primer/stylesheets/chapter.sgml | 2 +- .../fdp-primer/translations/chapter.sgml | 6 ++-- 6 files changed, 31 insertions(+), 31 deletions(-) diff --git a/en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml b/en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml index 7833d5d0bc..56648ee540 100644 --- a/en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml @@ -48,7 +48,7 @@ To avoid confusion, these examples use the standard DocBook 4.1 DTD rather than the FreeBSD extension. They also use the stock stylesheets - distributed by Norm Walsh, rather than any customisations made to those + distributed by Norm Walsh, rather than any customizations made to those stylesheets by the FreeBSD Documentation Project. This makes them more useful as generic DocBook examples. diff --git a/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml index ee88a035c6..1f0a8d076f 100644 --- a/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml @@ -466,7 +466,7 @@ In-line elements - Emphasising information + Emphasizing information You have two levels of emphasis available in HTML, em and strong. @@ -482,8 +482,8 @@ Use: - This has been emphasised, while - this has been strongly emphasised.

]]> + This has been emphasized, while + this has been strongly emphasized.

]]> @@ -716,7 +716,7 @@ Formal Public Identifier (FPI) In compliance with the DocBook guidelines for writing FPIs for - DocBook customisations, the FPI for the FreeBSD extended DocBook DTD + DocBook customizations, the FPI for the FreeBSD extended DocBook DTD is; PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" @@ -731,7 +731,7 @@ A book is organized into chapters. This is a mandatory requirement. There may be parts between - the book and the chapter to provide another layer of organisation. + the book and the chapter to provide another layer of organization. The Handbook is arranged in this way. A chapter may (or may not) contain one or more sections. These @@ -954,7 +954,7 @@ Subdividing using <sgmltag>part</sgmltag>s - You can introduce another layer of organisation between + You can introduce another layer of organization between book and chapter with one or more parts. This cannot be done in an article. @@ -2579,7 +2579,7 @@ IMAGES= chapter1/fig1.png in .]]> The text of the link will be generated automatically, and will - look like (emphasised text indicates the text + look like (emphasized text indicates the text that will be the link);
@@ -2620,7 +2620,7 @@ IMAGES= chapter1/fig1.png this section.]]> This will generate the following - (emphasised text indicates the text that will + (emphasized text indicates the text that will be the link);
diff --git a/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml index f15c01370b..4fed581e95 100644 --- a/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml @@ -90,7 +90,7 @@ The extra information stored in the markup adds value to the document. Adding the markup to the document must typically be done by a person—after all, if computers could - recognise the text sufficiently well to add the markup then there would + recognize the text sufficiently well to add the markup then there would be no need to add it in the first place. This increases the cost (i.e., the effort required) to create the document. @@ -199,7 +199,7 @@ A tag is used to identify where a particular element starts, and where the element ends. The tag is not part of the element itself. Because each DTD was normally written to mark up - specific types of information, each one will recognise different + specific types of information, each one will recognize different elements, and will therefore have different names for the tags. For an element called element-name the @@ -251,7 +251,7 @@ Elements within elements; <sgmltag>em</sgmltag> This is a simple paragraph where some - of the words have been emphasised.

]]> + of the words have been emphasized.

]]> The DTD will specify the rules detailing which elements can contain @@ -643,7 +643,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished ISO 9070:1991 defines how registered names are generated; it might be derived from the number of an ISO publication, an ISBN - code, or an organisation code assigned according to ISO 6523. + code, or an organization code assigned according to ISO 6523. In addition, a registration authority could be created in order to assign registered names. The ISO council delegated this to the American National Standards Institute (ANSI). @@ -796,7 +796,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished your document. Everything between these delimiters is SGML syntax as you might find within a DTD. - As you may just have realised, the As you may just have realized, the DOCTYPE declaration is an example of SGML syntax that you need to include in your document… @@ -1051,7 +1051,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished Load example.sgml into your web browser (you may need to copy it to example.html - before your browser recognises it as an HTML document). + before your browser recognizes it as an HTML document). Unless your browser is very advanced, you will not see the entity reference &version; replaced with the @@ -1064,10 +1064,10 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished - The solution is to normalise your - document using an SGML normaliser. The normaliser reads in valid + The solution is to normalize your + document using an SGML normalizer. The normalizer reads in valid SGML and outputs equally valid SGML which has been transformed in - some way. One of the ways in which the normaliser transforms the + some way. One of the ways in which the normalizer transforms the SGML is to expand all the entity references in the document, replacing the entities with the text that they represent. @@ -1075,7 +1075,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished &prompt.user; sgmlnorm example.sgml > example.html - You should find a normalised (i.e., entity references + You should find a normalized (i.e., entity references expanded) copy of your document in example.html, ready to load into your web browser. @@ -1156,7 +1156,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished entities. Suppose that you had many chapters in your document, and you - reused these chapters in two different books, each book organising the + reused these chapters in two different books, each book organizing the chapters in a different fashion. You could list the entities at the top of each book, but this @@ -1242,7 +1242,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished - Produce example.html by normalising + Produce example.html by normalizing example.sgml. &prompt.user; sgmlnorm -d example.sgml > example.html @@ -1299,7 +1299,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished - Produce example.html by normalising + Produce example.html by normalizing example.sgml. &prompt.user; sgmlnorm -d example.sgml > example.html @@ -1542,7 +1542,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished - Normalise this file using &man.sgmlnorm.1; and examine the + Normalize this file using &man.sgmlnorm.1; and examine the output. Notice which paragraphs have appeared, which have disappeared, and what has happened to the content of the CDATA marked section. @@ -1551,7 +1551,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished Change the definition of the text.output entity from INCLUDE to - IGNORE. Re-normalise the file, and examine the + IGNORE. Re-normalize the file, and examine the output to see what has changed. @@ -1564,7 +1564,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished That is the conclusion of this SGML primer. For reasons of space and complexity several things have not been covered in depth (or at all). However, the previous sections cover enough SGML for you to be - able to follow the organisation of the FDP documentation. + able to follow the organization of the FDP documentation. diff --git a/en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml index 344ee2b915..3d9b8b2f5e 100644 --- a/en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml @@ -45,7 +45,7 @@ promote consistency between the different documentation - organisations, to make it easier to switch between working on + organizations, to make it easier to switch between working on different documents @@ -76,7 +76,7 @@ Contains files that are not specific to the various translations and encodings of the documentation. Contains subdirectories to - further categorise the information. For example, the files that + further categorize the information. For example, the files that comprise the &man.make.1; infrastructure are in share/mk, while the additional SGML support files (such as the FreeBSD extended DocBook DTD) are in diff --git a/en_US.ISO8859-1/books/fdp-primer/stylesheets/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/stylesheets/chapter.sgml index 528fed3ed9..f934740724 100644 --- a/en_US.ISO8859-1/books/fdp-primer/stylesheets/chapter.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/stylesheets/chapter.sgml @@ -55,7 +55,7 @@ found in doc/share/sgml/freebsd.dsl. It is well commented, and pending completion of this section you are encouraged to examine that file to see how some of the available options in the - standard stylesheets have been configured in order to customise the + standard stylesheets have been configured in order to customize the output for the FreeBSD Documentation Project. That file also contains examples showing how to extend the elements that the stylesheet understands, which is how the FreeBSD specific elements have been diff --git a/en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml b/en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml index 28f76af819..b4de7e6d24 100644 --- a/en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml +++ b/en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml @@ -66,8 +66,8 @@ i18n means - internationalisation and l10n - means localisation. They are just a convenient + internationalization and l10n + means localization. They are just a convenient shorthand. i18n can be read as i followed by @@ -178,7 +178,7 @@ First, decide whether or not you have got the time to spare. Since you are the only person working on your language at the moment it is - going to be your responsibility to publicise your work and + going to be your responsibility to publicize your work and coordinate any volunteers that might want to help you. Write an e-mail to the Documentation Project mailing list,