Documentation:Tutorial Section 2.2 - Revision history

Jholsenback: omission

2020-02-10T17:41:40Z

omission

Jholsenback: technical correction

2020-02-10T17:34:15Z

technical correction

Jholsenback: link repair after build error

2016-12-17T17:01:08Z

link repair after build error

Clipka: Indexentries fix

2016-12-16T14:07:28Z

Indexentries fix

Clipka: indexentry fix

2016-05-03T22:43:17Z

indexentry fix

Chrisc: /* Using the POVINI Environment Variable */

2013-08-26T14:13:52Z

Using the POVINI Environment Variable

Chrisc: /* Using INI Files */

2013-08-26T14:08:59Z

Using INI Files

Chrisc: /* Setting POV-Ray Options */

2013-08-26T14:02:55Z

Setting POV-Ray Options

Chrisc: /* Using the POVINI Environment Variable */

2013-02-11T05:25:14Z

Using the POVINI Environment Variable

Jholsenback: link correction

2012-07-01T16:02:38Z

link correction

@@ Line 464: / Line 464: @@
 </pre>
-<p>Where <em>IDENTIFIER</em> is a valid identifier and <em>TRANSFORMATION</em> is any valid transformation modifier.</p>
+<p>Where <em>IDENTIFIER</em> is a valid identifier name and <em>TRANSFORMATION</em> is any valid transformation modifier.</p>
 <p>Here is an example...</p>
 <pre>

@@ Line 464: / Line 464: @@
 </pre>
-<p>Where <em>IDENTIFIER</em> is the name of the identifier up to 40 characters
+<p>Where <em>IDENTIFIER</em> is a valid identifier and <em>TRANSFORMATION</em> is any valid transformation modifier.</p>
-long and <em>TRANSFORMATION</em> is any valid transformation modifier. See <!--<linkto "#declare vs. #local">#declare vs. #local</linkto>--->[[Reference:Declare and Local Directives#declare vs. local|#declare vs. #local]] for information on identifier scope. Here is an example...</p>
+<p>Here is an example...</p>
 <pre>
    #declare MyTrans =
@@ Line 477: / Line 477: @@
+     }
 </pre>
+<p>See also: <!--<linkto "Identifiers">Identifiers</linkto>--->[[Reference:Identifiers|Identifiers]] and <!--<linkto "#declare vs. #local">#declare vs. #local</linkto>--->[[Reference:Declare and Local Directives#declare vs. local|#declare vs. #local]] for additional information on identifier naming and scope.</p>
 <p>A transform identifier is invoked by the <code>transform</code> keyword with
 or without brackets as shown here:</p>

@@ Line 531: / Line 531: @@
 <p>Transformations may also be independently applied to pigment patterns and
 surface normal patterns.</p>
-<p class="Note"><strong>Note:</strong> Scaling a normal pattern not only affects the width and spacing. It does also affect the apparent height or depth of the bumps, for how to avoid this see <!--<linkto "Scaling normals">Scaling normals</linkto>--->[[Reference:Normal#Scaling normals|Scaling normals]].</p>
+<p class="Note"><strong>Note:</strong> Scaling a normal pattern not only affects the width and spacing. It does also affect the apparent height or depth of the bumps, for how to avoid this see [[Reference:Scaling normals|Scaling normals]].</p>
 <p>For example:</p>
 <pre>

@@ Line 8: / Line 8: @@
 <!--</wikitalk>--->
 <!--REMOVE--->===Simple Texture Options===<!--THIS--->
 {{#indexentry:Bumpiness, adding}}
 <p>The highlight we have added illustrates how much of our perception depends
 on the reflective properties of an object. Ray-tracing can exploit this by
@@ Line 38: / Line 38: @@
 a sphere of radius 2. The scale makes the bumps 1/5th as wide but does not
 affect their depth.</p>
 {{#indexentry:Color Patterns, creating}}
 {{#indexentry:Color Maps}}
 {{#indexentry:Patterns}}
 {{#indexentry:color_map, tutorial}}
 <p>We can do more than assigning a solid color to an object. We can create
 complex patterns in the pigment block like in these examples:</p>
@@ Line 102: / Line 103: @@
 element unchanged.</p>
 {{#indexentry:Textures, pre-defined}}
 <p>POV-Ray has some very sophisticated textures pre-defined in the standard
 include files <code>glass.inc</code>, <code>metals.inc</code>, <code>stones.inc</code>
@@ Line 142: / Line 143: @@
+   }
 </pre>
 {{#indexentry:Camera, using the}}
-===Using the Camera===
 {{#indexentry:Focal Blur, using}}
 {{#indexentry:focus}}
 <p>Let's construct a simple scene to illustrate the use of focal blur.
 For this example we will use a pink sphere, a green box and a blue cylinder
@@ Line 548: / Line 551: @@
 </pre>
 {{#indexentry:Options, all versions}}
 {{#indexentry:Command-line Options, all versions}}
 {{#indexentry:Command-line Options}}
 <p>
 POV-Ray was originally created as a command-line program for operating
@@ Line 569: / Line 572: @@
 Both are explained in detail in the following sections.</p>
 {{#indexentry:Switches, command-line}}
 {{#indexentry:Options, command-line}}
 <p>Command line switches consist of a <code>+</code> (plus) or <code>
 -</code> (minus) sign, followed by one or more alphabetic characters and
@@ Line 605: / Line 608: @@
 section. A detailed description of each switch is given in the option
 reference section.</p>
 ====Using INI Files====
 {{#indexentry:Options, ini file}}

@@ Line 38: / Line 38: @@
 a sphere of radius 2. The scale makes the bumps 1/5th as wide but does not
 affect their depth.</p>
-{{#indexentry:Color Patterns, creating|Color Maps|Patterns}}
+{{#indexentry:Color Patterns, creating}}
 {{#indexentry:color_map, tutorial}}
 ====Creating Color Patterns====
@@ Line 142: / Line 144: @@
 {{#indexentry:Camera, using the}}
 ===Using the Camera===
-{{#indexentry:Focal Blur, using|focus}}
+{{#indexentry:Focal Blur, using}}
 ====Using Focal Blur====
 <p>Let's construct a simple scene to illustrate the use of focal blur.
@@ Line 545: / Line 548: @@
 </pre>
-{{#indexentry:Options, all versions|Command-line Options, all versions|Command-line Options}}
+{{#indexentry:Options, all versions}}
 ===Setting POV-Ray Options===
 <p>
@@ Line 564: / Line 569: @@
 Both are explained in detail in the following sections.</p>
-{{#indexentry:Switches, command-line|Options, command-line}}
+{{#indexentry:Switches, command-line}}
 ====Command Line Switches====
 <p>Command line switches consist of a <code>+</code> (plus) or <code>
@@ Line 600: / Line 606: @@
 reference section.</p>
 ====Using INI Files====
-{{#indexentry:Options, ini file|INI files, using}}
+{{#indexentry:Options, ini file}}
 <p class="Note"><strong>Note:</strong> Although the term 'INI file' is used by POV-Ray, this was implemented
@@ Line 727: / Line 734: @@
 ====Using the POVINI Environment Variable====
-{{#indexentry:Environment variables, POVRAYINI|Options, POVRAYINI environment variable|POVRAYINI environment variable}}
+{{#indexentry:Environment variables, POVRAYINI}}
 <p>On some platforms the environment variable POVINI is used to specify the location and name
@@ Line 744: / Line 753: @@
 </ol>
-{{#indexentry:Environment variables, POVRAYOPT|Options, POVRAYOPT environment variable|POVRAYOPT environment variable}}
+{{#indexentry:Environment variables, POVRAYOPT}}
 <p class="Note"><b>Note:</b> The POVRAYOPT environment variable supported by some earlier POV-Ray versions is no longer available.</p>
 <!--<wikinav>--->

@@ Line 729: / Line 729: @@
 {{#indexentry:Environment variables, POVRAYINI|Options, POVRAYINI environment variable|POVRAYINI environment variable}}
-<p>The environment variable POVINI is used to specify the location and name
+<p>On some platforms the environment variable POVINI is used to specify the location and name
-of a default INI file that is read every time POV-Ray is executed. If POVINI
+of a default INI file that is read every time POV-Ray is executed. The Unix and Linux versions
-is not specified, or if your computer platform does not use environment
+of POV-Ray, for example, support this whilst the Windows version does not.</p>
-variables, a default INI file may be read. If the specified file does not
+<p>If POVINI is not specified, or if your computer platform does not use environment
-exist, a warning message is printed. To set the environment variable under
+variables, a default INI file may be read; see your platform-specific documentation for information.
-MS-DOS you might put the following line in your <code>autoexec.bat</code>
+</p>
 <p>On most operating systems the sequence of reading options is as
@@ Line 745: / Line 741: @@
 <li>Read options from default INI file specified by the POVINI environment
 variable or platform specific INI file.</li>
-<li>Read switches from command line (this includes reading any specified
+<li>Read switches from command line (this includes reading any specified INI files).</li>
 </ol>
 {{#indexentry:Environment variables, POVRAYOPT|Options, POVRAYOPT environment variable|POVRAYOPT environment variable}}
-<p>The POVRAYOPT environment variable supported by previous POV-Ray versions
+<p class="Note"><b>Note:</b> The POVRAYOPT environment variable supported by some earlier POV-Ray versions is no longer available.</p>
 <!--<wikinav>--->
 <br>

@@ Line 696: / Line 696: @@
 in brackets. For example...</p>
 <pre>
-   POVRAY RES[Med] +Imyfile.pov
+   povray res[Med] +Imyfile.pov
 </pre>
@@ Line 704: / Line 704: @@
 command line then only the unlabeled area at the top of the file is read. If
 a label is specified, the unlabeled area is ignored.</p>
 <p>If a file or path contains blanks the whole file and path specification has
-to be put in quotes. You may either use a double-quote oir a single-quote, but
+to be put in quotes. You may either use a double-quote or a single-quote, but
 you have to use the same at the beginning and end. For example:</p>
 <pre>

@@ Line 551: / Line 551: @@
 systems without graphical interfaces, dialog boxes and pull-down menus. Most
 versions of POV-Ray still use command-line switches to tell it what to do.
-This documentation assumes you are using the command-line version. If you are
+This documentation assumes you are using the command-line version. All graphical
-using Macintosh, MS-Windows or other GUI versions, there will be dialog boxes
+versions of POV-Ray provide a means of using command-line switches and INI files
-or menus which do the same thing. There is system-specific documentation for
+from within the user interface, so you can use the below options in any version
-each system describing the specific commands.</p>
+of POV-Ray. There is system-specific documentation for each system describing which
 {{#indexentry:Options, setting}}
@@ Line 568: / Line 570: @@
 possibly a numeric value. Here is a typical command line with switches.</p>
 <pre>
-   POVRAY +Isimple.pov +V +W80 +H60
+   povray +Isimple.pov +V +W80 +H60
 </pre>
@@ Line 610: / Line 612: @@
 you have the ability to put multiple options in one or more text files. These
 initialization files or INI files have .ini as their default extension.
-Previous versions of POV-Ray called them default files or DEF files. You may
+</p>
 <p>
 The majority of options you use will be stored in INI files. The command
 line switches are recommended for options which you will turn off or on
 frequently as you perform test renderings of a scene you are developing. The
-file <code> povray.ini</code> is automatically read if present. You may
+file <code>povray.ini</code> is automatically read if present in the same
 specify additional INI files on the command-line by simply typing the file
 name on the command line. For example:</p>
 <pre>
-   POVRAY MYOPTS.INI
+   povray myopts.ini
 </pre>
@@ Line 629: / Line 632: @@
 example:</p>
 <pre>
-   POVRAY MYOPTS +V OTHER
+   povray myopts +V other
 </pre>

@@ Line 88: / Line 88: @@
 and from <code>DarkBrown</code> to <code>VeryDarkBrown</code> over the remaining 10%.
 In the second example the colors do not blend from one to an other, but change abrupt.
-The <code><!--<linkto "turbulence">turbulence</linkto>--->[[Reference:Warp#Turbulence|turbulence]]</code> keyword slightly stirs up the pattern so the veins are not perfect circles and the <code><!--<linkto "scale">scale</linkto>--->[[Reference:Transformations#scale|scale]]</code> keyword adjusts the size of the pattern.</p>
+The <code><!--<linkto "turbulence">turbulence</linkto>--->[[Reference:Warp#Turbulence|turbulence]]</code> keyword slightly stirs up the pattern so the veins are not perfect circles and the <code><!--<linkto "scale">scale</linkto>--->[[Reference:Transformations#Scale|scale]]</code> keyword adjusts the size of the pattern.</p>
 <p>
 Most patterns are set up by default to give us one <em>feature</em> across