os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Nuke contractions.

Browse source
This commit is contained in:
Adam Weinberger 2004-08-25 03:31:12 +00:00
parent 35260e2be5
commit 165b71a65c
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=22093
4 changed files with 17 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

12
en/gnome/docs/bugging.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/bugging.sgml,v 1.16 2004/06/06 20:29:46 marcus Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/bugging.sgml,v 1.17 2004/06/06 20:31:09 marcus Exp $">
<!ENTITY title "FreeBSD GNOME Project: Reporting a Bug">
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -45,9 +45,9 @@
<li><p>Your environment (output of <tt>/usr/bin/env</tt>).
<li><p>If you are building from ports, note approximately how
long it has been since you last updated your ports tree. If
it has been more than a day, or if you haven't run
<tt>portupgrade&nbsp;-a</tt>, don't bother sending a bug report
until you've run <tt>cvsup</tt> and <tt>portupgrade</tt>.</p></li>
it has been more than a day, or if you have not run
<tt>portupgrade&nbsp;-a</tt>, do not bother sending a bug report
until you have run <tt>cvsup</tt> and <tt>portupgrade</tt>.</p></li>
<li><p>Information specific for each type of breakage:</p>
<ul>
<li>If a port will not build, provide a full log of the
@ -61,7 +61,7 @@
<p>If you have a solution or a workaround for the problem, then include
it into your report as well, even if you are not quite sure that
it is a proper fix. Even if the fix isn't quite right, it could still
it is a proper fix. Even if the fix is not quite right, it could still
point others in the right direction.
</p>
@ -86,7 +86,7 @@
<a href="http://www.FreeBSD.org/support.html#gnats">FreeBSD bug
reporting system</a>.</p></li>
<li><p>If the problem has to do with an application's
behaviour, report the problem directly to the applicaiton's
behaviour, report the problem directly to the application's
developers through the GNOME project's
<a href="http://bugzilla.gnome.org/">bug tracking system</a></p></li>
<li><p>If the problem is quite serious, not necessarily

4
en/gnome/docs/develfaq.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/develfaq.sgml,v 1.22 2004/06/06 01:26:03 marcus Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/develfaq.sgml,v 1.23 2004/06/15 00:44:29 marcus Exp $">
<!ENTITY title "FreeBSD GNOME Project: GNOME Development Branch FAQ">
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -151,7 +151,7 @@ STRIP=
this applet to <a href="mailto:marcus@FreeBSD.org">
marcus@FreeBSD.org</a>.</p>
<p>Even if you don't like working directly with code, we need
<p>Even if you do not like working directly with code, we need
reports on experiences upgrading from GNOME &gnomever; to GNOME
&gnomedevelver;; we need information on which apps are exhibiting
strange behavior; we need to know in advance everything that an

8
en/gnome/docs/faq2.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.74 2004/08/14 06:01:42 marcus Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.75 2004/08/18 01:30:35 marcus Exp $">
<!ENTITY title "FreeBSD GNOME Project: GNOME &gnomever; FAQ">
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -135,7 +135,7 @@ exec gnome-session
<p><u>Updating solves most problems</u></p>
<p>If you haven't yet followed <a href="#q6">FAQ #6</a>, do so, as
<p>If you have not yet followed <a href="#q6">FAQ #6</a>, do so, as
it will most likely fix the problem you are reading this document
to solve.</p>
@ -226,7 +226,7 @@ options _KPOSIX_PRIORITY_SCHEDULING
<li>The <b>GNOME 2 Hacker Tools</b>
(<tt>devel/gnome2-hacker-tools</tt>) consists of applications
developers would need to create and maintain GNOME software
projects. This includes IDEs, interface builders, ``hacker''
projects. This includes IDEs, interface builders, "hacker"
editors, and code generation tools.</li>
<li>The <b>GNOME 2 Office</b> (<tt>editors/gnome2-office</tt>)
@ -357,7 +357,7 @@ ggv
<p>After running the above commands, you will have to reinstall all
the GNOME applications you desire. This process sounds painful,
but it is actually a great way to clear cruft off of your system.
Just install applications as you need them, and you'll be surprised
Just install applications as you need them, and you will be surprised
how much disk space you have reclaimed. A full rebuild does take
a significant amount of time; fortunately, this measure is only
rarely needed.</p>

10
en/gnome/docs/faq26.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "../../">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq26.sgml,v 1.8 2004/06/06 19:04:35 marcus Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq26.sgml,v 1.9 2004/06/06 19:06:17 marcus Exp $">
<!ENTITY title "FreeBSD GNOME Project: GNOME &gnomever; Upgrading FAQ">
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -102,7 +102,7 @@
<pre>
$ tail -f /path/to/logfile
</pre>
<p>you can watch the entire upgrade process as it unfolds. It's hypnotic!</p>
<p>you can watch the entire upgrade process as it unfolds. It is hypnotic!</p>
</li>
</ol>
</li>
@ -115,14 +115,14 @@ $ tail -f /path/to/logfile
to fail, but it will not cause any lasting damage to your ports tree, unless you have
done something exceptionally creative. Simply download the <tt>gnome_upgrade.sh</tt>
script and run it, and pretend that you ran it in the first place. Nobody needs to know
that you didn't read the directions first!</p>
that you did not read the directions first!</p>
</li>
<!-- Q4 -->
<li style="padding-bottom: 0.5em"><a name="q4"></a>
<p><b>The upgrade failed; what do I do?</b></p>
<!-- A4 -->
<p>Unfortunately, this is not only possible, it's highly probable. There are many possible
<p>Unfortunately, this is not only possible, it is highly probable. There are many possible
valid GNOME configurations, and even more invalid starting points. If the script fails,
follow the instructions in the error message to let the FreeBSD GNOME team know about the
failure.</p>
@ -144,7 +144,7 @@ $ tail -f /path/to/logfile
<li><a href="http://bugzilla.gnome.org/show_bug.cgi?id=139500">
#139500</a>: [bonobo-activation-server] <tt>bonobo-activation-server</tt>
does not terminate after logging out of GNOME. As a consequence of
this, <tt>ssh-add</tt> won't work unless <tt>bonobo-activation-server</tt>
this, <tt>ssh-add</tt> will not work unless <tt>bonobo-activation-server</tt>
is manually killed on a virtual console (<b>UPDATE:</b>
This problem should be resolved in libbonobo-2.6.1).</li>
<li><a href="http://bugzilla.gnome.org/show_bug.cgi?id=132154">