From d6ffaf7aa5b48826bad1437264705eb5b8b1fbcd Mon Sep 17 00:00:00 2001 From: Maxim Sobolev Date: Wed, 9 Jan 2002 02:49:58 +0000 Subject: [PATCH] Change all embedded HTML lags to lowercase. Also, fix a few typos. --- en/gnome/docs/faq.sgml | 266 ++++++++++++++++++------------------- en/gnome/docs/porting.sgml | 56 ++++---- 2 files changed, 161 insertions(+), 161 deletions(-) diff --git a/en/gnome/docs/faq.sgml b/en/gnome/docs/faq.sgml index 3dcbf29ab0..897a843e81 100644 --- a/en/gnome/docs/faq.sgml +++ b/en/gnome/docs/faq.sgml @@ -24,74 +24,74 @@

Full Text

- - + + - - + +

This last step is optional, but these lines enable other ports, + such as XMMS, to take advantage of the GNOME installation.

+ - + - - + + - - + + the output of the failed compilation.

+ - + - - + + - - + +

A full list of GNOME applications that have been ported to FreeBSD can + be found here.

+ - + - - + + - - + + + - + - - + + - - + +

You can read more about KDE on FreeBSD at + http://freebsd.kde.org.

+ - + - - + + - - + + before using any of the themes from themes.org.

+ - + - - + + - - + + + - +
+ 1. - - How do I get GNOME for FreeBSD? - + How do I get GNOME for FreeBSD? +

-

There are two ways to install GNOME on FreeBSD. One way is to use - packages, and the other way is to use ports.

+
+

There are two ways to install GNOME on FreeBSD. One way is to use + packages, and the other way is to use ports.

-

To install GNOME from packages, use the command:

+

To install GNOME from packages, use the command:

- # pkg_add -r gnome + # pkg_add -r gnome -

This will download the latest GNOME packages from the FreeBSD FTP - site, and proceed to intall them on your system. Note: As of +

This will download the latest GNOME packages from the FreeBSD FTP + site, and proceed to intall them on your system. Note: As of 4.4-RELEASE, installing GNOME from packages contained on a release - CDROM is broken. You should instead use the ports method below.

+ CDROM is broken. You should instead use the ports method below.

-

To build and install GNOME from ports, you should first - cvsup the latest ports tree. Then:

+

To build and install GNOME from ports, you should first + cvsup the latest ports tree. Then:

- 
+	  
 # cd /usr/ports/x11/gnome
 # make clean
 # make install clean
-	  

+
-

Currently, building from ports is the preferred method for installing +

Currently, building from ports is the preferred method for installing GNOME on FreeBSD, however FreeBSD GNOME team is working on improving - situation with pre-buit packages.

+ situation with pre-buit packages.

-

After GNOME is installed, you should edit /etc/make.conf, +

After GNOME is installed, you should edit /etc/make.conf, and add the following lines. If /etc/make.conf does not - exist, create the file, then add the following lines:

+ exist, create the file, then add the following lines:

- 
+      
 WITH_GTK=yes
 WITH_ESOUND=yes
 WITH_GNOME=yes
-      

+
-

This last step is optional, but these lines enable other ports, - such as XMMS, to take advantage of the GNOME installation.

-



- 2. - GNOME is failing to build from ports. What do I do? - + 2. + GNOME is failing to build from ports. What do I do? +

-

The majority of GNOME compilation problems can be solved by making +


+

The majority of GNOME compilation problems can be solved by making sure all the necessary GNOME components are up-to-date. All GNOME - applications require the following core components to build:

+ applications require the following core components to build:

- 
+	   
 pkg-config
 glib
 gettext
@@ -101,180 +101,180 @@ Imlib
 esound
 gnomelibs
 gnomecore
-       

+
-

Verify all those components are up-to-date, then try building +

Verify all those components are up-to-date, then try building GNOME or your GNOME application again. If you're trying to build one of those core components, and it is failing, or if, after updating all your components, you still have trouble; please send email to &email;@FreeBSD.ORG with - the output of the failed compilation.

-



- 3. - I installed GNOME, but I'm missing application foo. What gives? - + 3. + I installed GNOME, but I'm missing application foo. What gives? +

-

Only the core components, and a few extras, are included in the +


+

Only the core components, and a few extras, are included in the gnome package. There is another meta-port called gnome-fifth-toe that includes some more popular (and bigger) GNOME applications. gnome-fifth-toe includes Galeon, Pan, Gnumeric, AbiWord, GNUCash, Evolution, Gimp, Dia, and - more.

+ more.

-

To install gnome-fifth-toe from packages. Note: +

To install gnome-fifth-toe from packages. Note: Installing gnome-fifth-toe from packages is currently broken on - 4.4-RELEASE.

+ 4.4-RELEASE.

- # pkg_add -r gnome-fifth-toe + # pkg_add -r gnome-fifth-toe -

To build gnome-fifth-toe from ports: +

To build gnome-fifth-toe from ports:

- 
+	   
 # cd /usr/ports/x11/gnome-fifth-toe
 # make clean
 # make install clean
-	   

+
-

A full list of GNOME applications that have been ported to FreeBSD can - be found here.

-



- 4. - What's the best way to upgrade GNOME? - + 4. + What's the best way to upgrade GNOME? +

-

I find that /usr/ports/sysutils/portupgrade - works really well. For example:

+
+

I find that /usr/ports/sysutils/portupgrade + works really well. For example:

- # portupgrade -r ORBit + # portupgrade -r ORBit -

This will upgrade ORBit and every other port that depends on it - (that needs updating).

+

This will upgrade ORBit and every other port that depends on it + (that needs updating).

-

However, sometimes so much changes that it becomes +

However, sometimes so much changes that it becomes necessary to do a little housekeeping first. In that case, this - usually works:

+ usually works:

- 
+		
 # pkg_delete -r ORBit
 # cd /usr/ports/x11/gnome
 # make clean
 # make install clean
-		

-



- 5. - What is the difference between GNOME and KDE? - + 5. + What is the difference between GNOME and KDE? +

-

GNOME and KDE are both desktop environments. GNOME is based on +


+

GNOME and KDE are both desktop environments. GNOME is based on the GTK+ widget set, and is primarily written in C. KDE on the other - hand is based on the QT widget set, and is primarily written in C++.

+ hand is based on the QT widget set, and is primarily written in C++.

-

Both environments offer a wide range of applications from toys and - games to full-blow office suites. Both are actively developed and +

Both environments offer a wide range of applications from toys and + games to full-blown office suites. Both are actively developed and ported to FreeBSD. If you're trying to decide which one to call your - own, try them both, and see which one you like better.

+ own, try them both, and see which one you like better.

-

You can read more about KDE on FreeBSD at - http://freebsd.kde.org.

-



- 6. - Where can I get more themes for GNOME? - + 6. + Where can I get more themes for GNOME? +

-

If you're tired of the default themes that come with GNOME, you +


+

If you're tired of the default themes that come with GNOME, you do have options. First, FreeBSD's ports collection comes with a rather large collection of GTK themes for GNOME. To install these - from packages, run:

+ from packages, run:

- # pkg_add -r gtk-engines-collection + # pkg_add -r gtk-engines-collection -

To install the themes from ports, do:

+

To install the themes from ports, do:

- 
+		
 # cd /usr/ports/x11-toolkits/gtk-engines-collection
 # make all install clean
-		

+
-

If you want even more themes, checkout +

If you want even more themes, checkout http://gtk.themes.org. Note, you will probably need to install the gtk-engines-collection - before using any of the themes from themes.org.

-



- 7. - What window managers work well with GNOME? - + 7. + What window managers work well with GNOME? +

-

The gnome meta-port installs the +


+

The gnome meta-port installs the Sawfish window manager by default. However, there are other window managers you can use with - GNOME. These include:

+ GNOME. These include:

- -


@@ -282,5 +282,5 @@ gnomecore &footer; - - + + diff --git a/en/gnome/docs/porting.sgml b/en/gnome/docs/porting.sgml index 314b1cccd8..7ba633e5b7 100644 --- a/en/gnome/docs/porting.sgml +++ b/en/gnome/docs/porting.sgml @@ -11,56 +11,56 @@
-

General instructions can be found in the FreeBSD Porter's Handbook. -

For ports that require GNOME, you should define the following in your -port's Makefile:

+

General instructions can be found in the FreeBSD Porter's Handbook. +

For ports that require GNOME, you should define the following in your +port's Makefile:

-
+
 USE_GNOME=	yes
 USE_X_PREFIX=	yes
-

+
-

These will take care of the install prefix and requiring all the core GNOME +

These will take care of the install prefix and requiring all the core GNOME dependencies. If your port can use GNOME, but it isn't required, you can -define the following in your Makefile:

+define the following in your Makefile:

-
+
 WANT_GNOME=	yes
-

+
-

If the user has defined WITH_GNOME in their /etc/make.conf +

If the user has defined WITH_GNOME in their /etc/make.conf then GNOME components will be built. Other useful GNOME-related macros -that can be define in your port's Makefile include:

+that can be define in your port's Makefile include:

-
    -

  • USE_GLIB (WANT_GLIB) : The application requires (can use) Glib. +

      +

    • USE_GLIB (WANT_GLIB) : The application requires (can use) Glib. Defining USE_GNOME or USE_GTK takes care of this option -automatically.

      • -

    • USE_GTK (WANT_GTK) : The application may not be GNOME-compliant, but +automatically.

      • +

    • USE_GTK (WANT_GTK) : The application may not be GNOME-compliant, but requires GTK+ widgets. This will take care of those dependencies. Note, this -option should not be defined if USE_GNOME is defined.

      • -

    • USE_ESOUND (WANT_ESOUND) : The application requires (can use) +option should not be defined if USE_GNOME is defined.

      • +

    • USE_ESOUND (WANT_ESOUND) : The application requires (can use) Esound. Normally, Esound support is added by specifying USE_GNOME. -

      • -

    • USE_IMLIB (WANT_IMLIB) : The application requires (can use) the +

      • +

    • USE_IMLIB (WANT_IMLIB) : The application requires (can use) the Imlib image library. This is not needed if USE_GNOME is defined. -

      • -

    • USE_GNOMELIBS (WANT_GNOMELIBS) : The application requires (can use) +

      • +

    • USE_GNOMELIBS (WANT_GNOMELIBS) : The application requires (can use) GNOME libraries. This does not import as many dependencies as USE_GNOME and should be used for applications that use GNOME, but do not need the GNOME Control Center, the GNOME capplet library, or -anything from the GNOME Core.

      • -

    • USE_GNOMECTRL (WANT_GNOMECTRL) : The application requires +anything from the GNOME Core.

      • +

    • USE_GNOMECTRL (WANT_GNOMECTRL) : The application requires (can use) all the GNOME libraries and the GNOME Control Center, but does not use anything from GNOME Core. This option is usually used for backend APIs. -

      • -
    +

    • +
-

The more ported applications we have, the better. +

The more ported applications we have, the better.

&footer; - - + +