Changeset 105189 for trunk/doc-new


Ignore:
Timestamp:
Apr 13, 2013, 1:09:55 AM (7 years ago)
Author:
ryandesign@…
Message:

use "quote" tag so we get smart quotes; fix some other tags

Location:
trunk/doc-new/guide/xml
Files:
15 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc-new/guide/xml/installing.xml

    r103302 r105189  
    142142        <para>
    143143          If you wish to create Installer packages with <userinput>port pkg</userinput>,
    144           you will also need to install PackageMaker, which is in the "Auxiliary
    145           Tools for Xcode" package as of Xcode 4.3. The download page for this package
     144          you will also need to install PackageMaker, which is in the <quote>Auxiliary
     145          Tools for Xcode</quote> package as of Xcode 4.3. The download page for this package
    146146          can be opened via the Xcode -> Open Developer Tool -> More Developer Tools...
    147147          menu item. After downloading and mounting the disk image, drag the PackageMaker
  • trunk/doc-new/guide/xml/internals.xml

    r81658 r105189  
    2828
    2929    <para>This capability derives from the fact that a MacPorts port by
    30     default is not installed into its final or "activated" location, but
     30    default is not installed into its final or <quote>activated</quote> location, but
    3131    rather to an intermediate location that is only made available to other
    3232    ports and end-users after an activation phase that extracts all
     
    6969      primitives required for a Portfile to be parsed, queried, and executed.
    7070      It also provides a single procedure call that the MacPorts API uses to
    71       kick off execution: "eval_targets". The port Tcl library supplies these
     71      kick off execution: <code>eval_targets</code>. The port Tcl library supplies these
    7272      procedures, all of which are generated at run-time using the
    7373      <code>options</code> procedure in portutil.tcl.</para>
     
    255255        <listitem>
    256256          <para>Calls the <code>mportsearch</code> function to find all ports
    257           containing "cm3".</para>
     257          containing <quote>cm3</quote>.</para>
    258258        </listitem>
    259259
     
    276276        <listitem>
    277277          <para>Calls the <code>mportsearch</code> function to find the first
    278           port that matches the name "cm3".</para>
     278          port that matches the name <quote>cm3</quote>.</para>
    279279        </listitem>
    280280
  • trunk/doc-new/guide/xml/macports.conf.xml

    r82429 r105189  
    199199        <listitem>
    200200          <para>Number of simultaneous make jobs (commands) to use when
    201           building ports. Using "0" will cause a runtime autodetection to use
    202           all available processor cores.</para>
     201          building ports. Using <quote>0</quote> will cause a runtime
     202          autodetection to use all available processor cores.</para>
    203203
    204204          <para>Default: 0</para>
     
    210210
    211211        <listitem>
    212           <para>Set whether to automatically execute "clean" after "install"
    213           of ports.</para>
     212          <para>Set whether to automatically execute <quote>clean</quote> after
     213          <quote>install</quote> of ports.</para>
    214214
    215215          <para>Default: <option>yes</option></para>
     
    306306        <listitem>
    307307          <para>Options for generated startup items, though this may be
    308           overridden by the "startupitem.type" Portfile key. Options are
    309           "default" option, "SystemStarter", "launchd", or "none". For an
    310           empty or "default" option, a startupitem type appropriate to the
    311           platform is used; if "none", no port startupitems are
     308          overridden by the <code>startupitem.type</code> Portfile key. Options
     309          are <quote>default</quote> option, <quote>SystemStarter</quote>,
     310          <quote>launchd</quote>, or <quote>none</quote>. For an empty or
     311          <quote>default</quote> option, a startupitem type appropriate to the
     312          platform is used; if <quote>none</quote>, no port startupitems are
    312313          installed.</para>
    313314
     
    338339
    339340        <listitem>
    340             <para>Set whether to place a symlink named "work" from your ports tree to
     341            <para>Set whether to place a symlink named <quote>work</quote> from your ports tree to
    341342                the build directory of a port, when the port is being built. This
    342343                is convenient, but may not be ideal if you care about the structure
  • trunk/doc-new/guide/xml/portfile-dependencies.xml

    r80729 r105189  
    121121    preferred for special reasons, or when it is possible for more than one
    122122    port to satisfy a dependency, then file dependencies may be used. An
    123     example of the former is with X11 —Apple's is widely preferred; an example
    124     of the latter is with "-devel" named ports —these ports provide identical
    125     files (though only one can be activated at a time).</para>
     123    example of the former is with ubiquitous utilities like awk, grep, make or
     124    sed, where OS X's versions are often sufficient; an example of the latter
     125    is with <quote>-devel</quote> ports—these ports provide a different
     126    version of the same files (though only one can be activated at a
     127    time).</para>
    126128
    127129    <para>Port dependencies, the preferred type, are specified as shown in
  • trunk/doc-new/guide/xml/portfile-keywords.xml

    r105188 r105189  
    77  <para>MacPorts keywords are used to specify required or optional items
    88  within a Portfile, or to override default options used by MacPorts base for
    9   individual ports. Keywords are to be used within the "global" and "variant"
    10   sections of Portfiles, and not within optional port phase
    11   declarations.</para>
     9  individual ports. Keywords are to be used within the <quote>global</quote>
     10  and <quote>variant</quote> sections of Portfiles, and not within optional
     11  port phase declarations.</para>
    1212
    1313  <para>The global keywords listed below specify information for ports as a
     
    3838        and the like, names should contain only alphanumeric characters,
    3939        underscores, dashes or dots. For projects whose proper names contain
    40         "+" characters, change these to "x" (i.e. "libstdc++" becomes
    41         "libstdcxx").</para>
     40        <quote>+</quote> characters, change these to <quote>x</quote> (i.e.
     41        <quote>libstdc++</quote> becomes <quote>libstdcxx</quote>).</para>
    4242
    4343        <programlisting>name                foo</programlisting>
  • trunk/doc-new/guide/xml/portfile-livecheck.xml

    r92756 r105189  
    9494        including extension. You may use this keyword without
    9595        <code>livecheck.version</code> if you replace the version part of
    96         the name with "<literal>(.*)</literal>".</para>
     96        the name with <quote><literal>(.*)</literal></quote>.</para>
    9797
    9898        <itemizedlist>
  • trunk/doc-new/guide/xml/portfile-phase.xml

    r104056 r105189  
    106106
    107107          <para>Understanding the destroot phase is critical to understanding
    108           MacPorts, because, unlike some port systems, MacPorts "stages" an
    109           installation into an intermediate location —not the final file
    110           destination. MacPorts uses the destroot phase to provide:</para>
     108          MacPorts, because, unlike some package management systems, MacPorts
     109          <quote>stages</quote> an installation into an intermediate location,
     110          not the final file destination. MacPorts uses the destroot phase to
     111          provide:</para>
    111112
    112113          <itemizedlist>
     
    163164    <para>MacPorts keywords are used to specify required or optional items
    164165    within a Portfile, or to override default options used by MacPorts base
    165     for individual ports. Keywords are to be used within the "global" and
    166     "variant" sections of Portfiles, and not within optional port phase
    167     declarations.</para>
     166    for individual ports. Keywords are to be used within the
     167    <quote>global</quote> and <quote>variant</quote> sections of Portfiles,
     168    and not within optional port phase declarations.</para>
    168169
    169170    <para>In other words, port phase keywords are not located within port
  • trunk/doc-new/guide/xml/portfile-startupitem.xml

    r45348 r105189  
    55  <title>StartupItems</title>
    66
    7   <para>A StartupItem is a MacPorts facility to run "daemons," a Unix term for
     7  <para>A StartupItem is a MacPorts facility to run <quote>daemons,</quote> a Unix term for
    88  programs that run continuously in the background, rather than under the
    99  direct control of a user; for example, mail servers, network listeners, etc.
     
    181181
    182182          <note>
    183             <para>Some daemons "daemonize" by detaching themselves from the
     183            <para>Some daemons <quote>daemonize</quote> by detaching themselves from the
    184184            controlling tty before sending themselves to the background, thus
    185185            making themselves a child of the original process. A daemon to be
  • trunk/doc-new/guide/xml/portfile-tcl.xml

    r93794 r105189  
    7373
    7474            <listitem>
    75               <para>Shorthand alternative to "file copy".</para>
     75              <para>Shorthand alternative to <code>file copy</code>.</para>
    7676            </listitem>
    7777          </varlistentry>
     
    8383
    8484            <listitem>
    85               <para>Shorthand alternative to "file rename".</para>
     85              <para>Shorthand alternative to <code>file rename</code>.</para>
    8686            </listitem>
    8787          </varlistentry>
  • trunk/doc-new/guide/xml/portfile-variables.xml

    r73388 r105189  
    134134
    135135      <listitem>
    136         <para>The underlying operating system platform (i.e. "darwin" on Mac OS X, "freebsd", etc.).</para>
     136        <para>The underlying operating system platform (i.e.
     137        <quote>darwin</quote> on OS X, <quote>freebsd</quote>,
     138        etc.).</para>
    137139      </listitem>
    138140    </varlistentry>
     
    142144
    143145      <listitem>
    144         <para>The hardware architecture -- either "powerpc" or "i386".</para>
     146        <para>The hardware architecture -- either <quote>powerpc</quote> or
     147        <quote>i386</quote>.</para>
    145148      </listitem>
    146149    </varlistentry>
     
    150153
    151154      <listitem>
    152         <para>The version number of the host operating system (i.e. "8.11.0" for
    153         Darwin 8.11.0 a.k.a. Mac OS X 10.4.11).</para>
     155        <para>The version number of the host operating system (i.e.
     156        <quote>12.3.0</quote> for Darwin 12.3.0 a.k.a. OS X 10.8.3).</para>
    154157      </listitem>
    155158    </varlistentry>
     
    159162
    160163      <listitem>
    161         <para>Endianness of the processor -- either "big" (on PowerPC systems) or "little" (on Intel systems).</para>
     164        <para>Endianness of the processor -- either <quote>big</quote> (on
     165        PowerPC systems) or <quote>little</quote> (on Intel systems).</para>
    162166      </listitem>
    163167    </varlistentry>
     
    167171
    168172      <listitem>
    169         <para>The major version number of the host operating system (i.e. "8"
    170         for Darwin 8.x).</para>
     173        <para>The major version number of the host operating system (i.e.
     174        <quote>12</quote> for Darwin 12.x).</para>
    171175      </listitem>
    172176    </varlistentry>
  • trunk/doc-new/guide/xml/portfile-variants.xml

    r77495 r105189  
    4242          declaration and not within the variant declaration itself.
    4343          Dependencies and conflicts with other variants in the same port can
    44           be expressed with <quote>requires</quote> and
    45           <quote>conflicts</quote> options as shown below.</para>
     44          be expressed with <literal>requires</literal> and
     45          <literal>conflicts</literal> options as shown below.</para>
    4646
    4747          <itemizedlist>
     
    9191
    9292          <para>Default variants may be suppressed by preceding a variant name
    93           with a "-" as shown in this example.</para>
     93          with a <quote>-</quote> as shown in this example.</para>
    9494
    9595          <programlisting><prompt>%%</prompt> <userinput>port install foo -ssl</userinput></programlisting>
     
    128128
    129129    <para>User-selected variants ought to provide a description, which will be
    130     displayed when using command <quote>port variants foo</quote>. The syntax
    131     used for the description keyword is shown below.</para>
     130    displayed when using command <userinput>port variants foo</userinput>. The
     131    syntax used for the description keyword is shown below.</para>
    132132
    133133    <programlisting>variant bar description {Add IMAP support} {}</programlisting>
     
    138138    with a capitalized first letter and no trailing punctuation. Think of them
    139139    as short labels such as ones you'd find next to a GUI checkbox or radio
    140     button. Thus, it would be better to write "Build with support for foo"
    141     instead of "Builds with support for foo"; "Add support for foo" would be
    142     better than "Adds support for foo". </para>
     140    button. Thus, it would be better to write <quote>Build with support for
     141    foo</quote> instead of <quote>Builds with support for foo</quote>;
     142    <quote>Add support for foo</quote> would be better than <quote>Adds support
     143    for foo</quote>.</para>
    143144
    144145    <para>Variant descriptions are strings, so one should take care not to put
  • trunk/doc-new/guide/xml/portfiledev.xml

    r88723 r105189  
    2525    default installation phase characteristics is by using
    2626    <filename>Portfile</filename> phase declaration(s). If you use Portfile
    27     phase declaration(s), you should know how to identify the "global" section
    28     of a Portfile. Any statements not contained within a phase declaration, no
    29     matter where they are located in a Portfile, are said to be in the global
    30     section of the Portfile; therefore the global section need not be
    31     contiguous. Likewise, to remove statements from the global section they
    32     must be placed within a phase declaration.</para>
     27    phase declaration(s), you should know how to identify the
     28    <quote>global</quote> section of a Portfile. Any statements not contained
     29    within a phase declaration, no matter where they are located in a Portfile,
     30    are said to be in the global section of the Portfile; therefore the global
     31    section need not be contiguous. Likewise, to remove statements from the
     32    global section they must be placed within a phase declaration.</para>
    3333
    3434    <para>The main phases you need to be aware of when making a Portfile are
     
    388388    <para>Variants are a way for port authors to provide options that may be
    389389    invoked at install time. They are declared in the global section of a
    390     Portfile using the "variant" keyword, and should include <link
     390    Portfile using the <quote>variant</quote> keyword, and should include <link
    391391    linkend="reference.variants.descriptions">carefully chosen variant
    392392    descriptions</link>.</para>
     
    526526        <listitem>
    527527          <para>Now use the Unix command <command>diff -u </command>to create
    528           a "unified" diff patch file. Put the name of the port in the
    529           patchfile, for example, Portfile-rrdtool.diff.</para>
     528          a <quote>unified</quote> diff patch file. Put the name of the port in
     529          the patchfile, for example, Portfile-rrdtool.diff.</para>
    530530
    531531          <programlisting><prompt>%%</prompt> <userinput>diff -u Portfile.orig Portfile &gt; Portfile-rrdtool.diff</userinput></programlisting>
     
    533533
    534534        <listitem>
    535           <para>A patch file that is a "unified" diff file is the easiest to
    536           interpret by humans and this type should always be used for ports.
    537           The Portfile patch below will change the version and checksums when
    538           applied.</para>
     535          <para>A patch file that is a <quote>unified</quote> diff file is the
     536          easiest to interpret by humans and this type should always be used
     537          for ports. The Portfile patch below will change the version and
     538          checksums when applied.</para>
    539539
    540540          <programlisting>--- Portfile.orig        2011-07-25 18:52:12.000000000 -0700
     
    618618          <para>Now <command>cd</command> to the top-level directory of the
    619619          unpacked source, and use the Unix command <command>diff -u</command>
    620           to create a "unified" diff patch file.</para>
     620          to create a <quote>unified</quote> diff patch file.</para>
    621621
    622622          <programlisting><prompt>%%</prompt> <userinput>cd ~/Downloads/foo-1.34</userinput>
     
    644644
    645645        <listitem>
    646           <para>A patch file that is a "unified" diff file is the easiest to
    647           interpret by humans and this type should always be used for ports.
    648           See the example below where a patch adds <varname>DESTDIR</varname>
    649           support to a <filename>Makefile.in</filename> file.</para>
     646          <para>A patch file that is a <quote>unified</quote> diff file is the
     647          easiest to interpret by humans and this type should always be used
     648          for ports. See the example below where a patch adds
     649          <varname>DESTDIR</varname> support to a
     650          <filename>Makefile.in</filename> file.</para>
    650651
    651652          <programlisting>--- src/Makefile.in.orig   2007-06-01 16:30:47.000000000 -0700
     
    743744        that reflects the port's primary category (the first category entry in
    744745        the Portfile). For example, to create the directory for a hypothetical
    745         port "bestevergame" and to begin editing its Portfile in TextEdit, you
    746         can use these commands:</para>
     746        port <quote>bestevergame</quote> and to begin editing its Portfile in
     747        TextEdit, you can use these commands:</para>
    747748
    748749        <programlisting><prompt>%%</prompt> <userinput>mkdir -p ~/ports/games/bestevergame</userinput>
     
    823824      <para>Frequently multiple items are necessary in the second column. For
    824825      example, to set multiple source download locations, multiple
    825       "master_sites" must be defined. Unless the second column items are few
    826       and short you should place each additional item on a new line and
    827       separate lines with a backslash. Indent the lines after the first line
    828       to make it clear the items are second column values and also to
    829       emphasize the unity of the block.</para>
     826      <code>master_sites</code> must be defined. Unless the second column
     827      items are few and short you should place each additional item on a new
     828      line and separate lines with a backslash. Indent the lines after the
     829      first line to make it clear the items are second column values and also
     830      to emphasize the unity of the block.</para>
    830831
    831832      <programlisting>destroot.keepdirs    ${destroot}${prefix}/var/run \
     
    866867      <para>If there is the need to replace a port with another port or a
    867868      renaming is necessary for some reason, the port should be marked as
    868       <quote>replaced_by</quote>.</para>
     869      <code>replaced_by</code>.</para>
    869870     
    870       <para>As an illustration of a typical workflow the port 'skrooge-devel'
    871       shall be taken. This port had been used for testing new versions of
    872       skrooge, but it turned out to have become unnecessary due to the fact
    873       that skrooge's developers currently prefer a distribution via port
    874       'skrooge' instead. </para>
     871      <para>As an illustration of a typical workflow the port
     872      <quote>skrooge-devel</quote> shall be taken. This port had been used for
     873      testing new versions of skrooge, but it turned out to have become
     874      unnecessary due to the fact that skrooge's developers currently prefer a
     875      distribution via port <quote>skrooge</quote> instead. </para>
    875876     
    876877      <para>Skrooge's original devel port file looked like this:</para>
     
    916917        <para>The following steps have to be taken to ensure a smooth transition
    917918        for a MacPorts user updating his local installation using
    918         <quote>sudo port upgrade</quote>:</para>
     919        <userinput>sudo port upgrade</userinput>:</para>
    919920
    920921    <orderedlist>
    921922      <listitem>
    922         <para> add the line <quote>replaced_by foo</quote> where foo is the
     923        <para> add the line <code>replaced_by foo</code> where foo is the
    923924        port this one is replaced by; when a user upgrades this port,
    924925        MacPorts will instead install the replacement port</para>
     
    928929      <listitem>
    929930        <para> increase the version, revision, or epoch, so that users who
    930         have this port installed will get notice in <quote>port
    931         outdated</quote> that they should upgrade it and trigger the above
     931        have this port installed will get notice in <code>port
     932        outdated</code> that they should upgrade it and trigger the above
    932933        process</para>
    933934                <programlisting>revision            1</programlisting>
     
    936937      <listitem>
    937938        <para> clear distfiles (have a line reading only
    938         <quote>distfiles</quote>) so that no distfile is downloaded for this
     939        <code>distfiles</code>) so that no distfile is downloaded for this
    939940        stub port</para>
    940941                <programlisting>distfiles</programlisting>
     
    952953
    953954      <listitem>
    954         <para> add a pre-configure block with a <quote>ui_error</quote> and
    955         <quote>return -code error</quote> explaining to users who try to
     955        <para> add a pre-configure block with a <code>ui_error</code> and
     956        <code>return -code error</code> explaining to users who try to
    956957        install this port that the port has been replaced</para>
    957958                <programlisting>pre-configure {
     
    998999distfiles</programlisting>
    9991000
    1000         <para>A user upgrading ports will experience for port 'skrooge-devel'
    1001         the following:</para>
     1001        <para>A user upgrading ports will experience the following for port
     1002  <quote>skrooge-devel</quote>:</para>
    10021003        <programlisting><prompt>%%</prompt> <userinput>sudo port upgrade skrooge-devel</userinput></programlisting>
    10031004        <screen>--->  skrooge-devel is replaced by skrooge
     
    10291030
    10301031        <para>In case a user actually tries to install the obsolete port
    1031         'skrooge-devel' it would be pointed out by an error message that this is
    1032         impossible now:</para>
     1032        <quote>skrooge-devel</quote> it would be pointed out by an error message that
     1033  this is impossible now:</para>
    10331034        <programlisting><prompt>%%</prompt> <userinput>sudo port install skrooge-devel</userinput></programlisting>
    10341035        <screen>--->  Fetching skrooge-devel
  • trunk/doc-new/guide/xml/portgroup-python.xml

    r103894 r105189  
    3030        <listitem>
    3131          <para>Defines the python versions supported by this port. If the
    32           port name starts with "py-", then a subport will be defined for each
    33           version in the list. For example, if a port named "py-foo" declares
    34           "python.versions 26 27", subports "py26-foo" and "py27-foo" will be
     32          port name starts with <quote>py-</quote>, then a subport will be defined for each
     33          version in the list. For example, if a port named <quote>py-foo</quote> declares
     34          <code>python.versions 26 27</code>, subports <quote>py26-foo</quote> and <quote>py27-foo</quote> will be
    3535          created, and will depend on python26 and python27 respectively.</para>
    36           <para>If the port name does not start with "py-", it is interpreted
     36          <para>If the port name does not start with <quote>py-</quote>, it is interpreted
    3737          as an application written in python rather than a python module. In
    38           this case, no subports are defined, and python.versions defaults to
    39           the value of python.default_version, which must be set. For example,
    40           if a port named "mercurial" sets "python.default_version 27", then
    41           python.versions will automatically be set to "27", and a dependency
     38          this case, no subports are defined, and <code>python.versions</code> defaults to
     39          the value of <code>python.default_version</code>, which must be set. For example,
     40          if a port named <quote>mercurial</quote> sets <code>python.default_version 27</code>, then
     41          <code>python.versions</code> will automatically be set to <quote>27</quote>, and a dependency
    4242          on python27 will be added.</para>
    4343
     
    5858
    5959        <listitem>
    60           <para>For modules (i.e. name starts with "py-"), this sets the
    61           subport that will be installed if the user asks to install "py-foo"
    62           rather than e.g. "py26-foo" or "py27-foo". If not explicitly set, a
    63           reasonable default is chosen from the list in python.versions.</para>
    64           <para>For apps (i.e. name does not start with "py-"), this chooses
     60          <para>For modules (i.e. name starts with <quote>py-</quote>), this sets the
     61          subport that will be installed if the user asks to install <quote>py-foo</quote>
     62          rather than e.g. <quote>py26-foo</quote> or <quote>py27-foo</quote>. If not explicitly set, a
     63          reasonable default is chosen from the list in <code>python.versions</code>.</para>
     64          <para>For apps (i.e. name does not start with <quote>py-</quote>), this chooses
    6565          which version of python to use, and must be set. It can be changed
    6666          in variants if desired.</para>
     
    8282
    8383        <listitem>
    84           <para>When yes (the default), tells the PortGroup to automatically
     84          <para>When <quote>yes</quote> (the default), tells the PortGroup to automatically
    8585          link any executable binaries installed in the bin/ directory within
    8686          the framework into
     
    123123          try to pass the correct arch-specific flags during build time
    124124          (via the standard CFLAGS, LDFLAGS, etc environment variables).
    125           Set this to no and setup those variables in build.env manually
     125          Set this to <quote>no</quote> and set up those variables in <code>build.env</code> manually
    126126          if the default does not work.</para>
    127127          <itemizedlist>
     
    152152        <listitem>
    153153          <para>The python version in use in the current subport. This will be
    154           one of the versions listed in python.versions.</para>
     154          one of the versions listed in <code>python.versions</code>.</para>
    155155        </listitem>
    156156      </varlistentry>
     
    161161        <listitem>
    162162          <para>The python version in use in the current subport, in normal
    163           dotted notation. For example, if python.version is "26",
    164           python.branch will be "2.6".</para>
     163          dotted notation. For example, if <code>python.version</code> is <quote>26</quote>,
     164          <code>python.branch</code> will be <quote>2.6</quote>.</para>
    165165        </listitem>
    166166      </varlistentry>
  • trunk/doc-new/guide/xml/project.xml

    r99866 r105189  
    2929            from earlier steps, which can be essential for figuring out why a
    3030            build failed, are not included in the new log; MacPorts prints
    31             "Skipping completed" in the log for each previously-completed phase
    32             that was skipped. Before filing a ticket, "sudo port clean" the
    33             port that failed, then try again.
     31            <quote>Skipping completed</quote> in the log for each
     32            previously-completed phase that was skipped. Before filing a
     33            ticket, <userinput>sudo port clean</userinput> the port that
     34            failed, then try again.
    3435          </para>
    3536        </listitem>
     
    6061          <para>
    6162            In general, application bugs should be reported to the developers of the app
    62             ("upstream"), not MacPorts. An application bug that affects a large number of
     63            (<quote>upstream</quote>), not MacPorts. An application bug that affects a large number of
    6364            MacPorts users might merit a MacPorts bug for informational purposes only, but
    6465            this should be done sparingly.
     
    8586      Follow the Trac ticket guidelines below to fill out the form. If you are
    8687      reporting a failed port install and a log was mentioned in the error,
    87       please use the "I have files to attach to this ticket" checkbox to add
    88       that log file to the ticket.</para>
     88      please use the <guilabel>I have files to attach to this ticket</guilabel>
     89      checkbox to add that log file to the ticket.</para>
    8990
    9091      <screenshot>
     
    145146          ticket pages can become unmanageable. Long output, such as the
    146147          full log from a port build, should be added as an attachment, not
    147           pasted inline. See "I have files to attach to this ticket" below.
    148           </para>
     148          pasted inline. See <guilabel>I have files to attach to this
     149          ticket</guilabel> below.</para>
    149150
    150151        </listitem>
     
    268269          help when searching for tickets. It is not useful to list words here
    269270          that already appear elsewhere in the ticket. Keywords also serve as
    270           tags; for example, use "tiger" if reporting a bug that only
    271           affects OS X 10.4, "haspatch" if a fix is attached to the ticket,
    272           "maintainer" if you are the port's maintainer, or "LP64" if
    273           reporting an issue that only affects 64-bit platforms.</para>
     271          tags; for example, use <quote>tiger</quote> if reporting a bug that
     272          only affects OS X 10.4, <quote>haspatch</quote> if a fix is attached
     273          to the ticket, <quote>maintainer</quote> if you are the port's
     274          maintainer, or <quote>LP64</quote> if reporting an issue that only
     275          affects 64-bit platforms.</para>
    274276        </listitem>
    275277
  • trunk/doc-new/guide/xml/using.xml

    r105007 r105189  
    446446      are optional, and not all ports using variants have them. For ports with
    447447      default variants, you may install a port without them by negating
    448       default variants using "-" as shown.</para>
     448      default variants using <quote>-</quote> as shown.</para>
    449449
    450450      <programlisting><prompt>%%</prompt> <userinput>sudo port install fetchmail -ssl</userinput></programlisting>
     
    689689
    690690      <para>Checking the list of leaves from time to time will help to keep your system
    691             free of too much "garbage". However, keep in mind that some ports may be dependencies
     691            free of too much <quote>garbage</quote>. However, keep in mind that some ports may be dependencies
    692692            only during the installation of a port (library dependencies, installation or
    693693            configuration tools, etc.). So, be careful when removing seemingly unnecessary leaves,
     
    780780
    781781      <para>All packages are placed in a port's work directory,
    782       except for rpms that are placed under the regular "RPMS":</para>
     782      except for rpms that are placed under the regular <quote>RPMS</quote>:</para>
    783783
    784784      <programlisting><prompt>%%</prompt> <userinput>port work pstree</userinput></programlisting>
Note: See TracChangeset for help on using the changeset viewer.