LDP
/
old-www
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
old-www/LDP/intro-linux/html/sect_06_03.html

345 lines
7.5 KiB
HTML
Raw Permalink Blame History

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML
><HEAD
><TITLE
>Linux in the office</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="Introduction to Linux"
HREF="index.html"><LINK
REL="UP"
TITLE="Text editors"
HREF="chap_06.html"><LINK
REL="PREVIOUS"
TITLE="Using the Vim editor"
HREF="sect_06_02.html"><LINK
REL="NEXT"
TITLE="Summary"
HREF="sect_06_04.html"></HEAD
><BODY
CLASS="sect1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Introduction to Linux: </TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="sect_06_02.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 6. Text editors</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="sect_06_04.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="sect_06_03"
></A
>6.3. Linux in the office</H1
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="sect_06_03_01"
></A
>6.3.1. History</H2
><P
>Throughout the last decade the office domain has typically been dominated by <SPAN
CLASS="application"
>MS Office</SPAN
>, and, let's face it: the Microsoft <SPAN
CLASS="application"
>Word</SPAN
>, <SPAN
CLASS="application"
>Excel</SPAN
> and <SPAN
CLASS="application"
>PowerPoint</SPAN
> formats are industry standards that you will have to deal with sooner or later.</P
><P
>This monopoly situation of Microsoft proved to be a big disadvantage for getting new users to Linux, so a group of German developers started the StarOffice project, that was, and is still, aimed at making an MS Office clone. Their company, StarDivision, was acquired by Sun Microsystems by the end of the 1990s, just before the 5.2 release. Sun continues development but restricted access to the sources. Nevertheless, development on the original set of sources continues in the Open Source community, which had to rename the project to <SPAN
CLASS="application"
>OpenOffice</SPAN
>. <SPAN
CLASS="application"
>OpenOffice</SPAN
> is now available for a variety of platforms, including MS Windows, Linux, MacOS and Solaris. There is a screenshot in <A
HREF="sect_01_03.html#sect_01_03_02"
>Section 1.3.2</A
>.</P
><P
>Almost simultaneously, a couple of other quite famous projects took off. Also a very common alternative to using MS Office is <SPAN
CLASS="application"
>KOffice</SPAN
>, the office suite that used to be popular among SuSE users. Like the original, this clone incorporates an MS <SPAN
CLASS="application"
>Word</SPAN
> and <SPAN
CLASS="application"
>Excel</SPAN
> compatible program, and much more.</P
><P
>Smaller projects deal with particular programs of the MS example suite, such as <SPAN
CLASS="application"
>Abiword</SPAN
> and MS <SPAN
CLASS="application"
>Wordview</SPAN
> for compatibility with MS <SPAN
CLASS="application"
>Word</SPAN
> documents, and <SPAN
CLASS="application"
>Gnumeric</SPAN
> for viewing and creating <SPAN
CLASS="application"
>Excel</SPAN
> compatible spreadsheets.</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="sect_06_03_02"
></A
>6.3.2. Suites and programs</H2
><P
>Current distributions usually come with all the necessary tools. Since these provide excellent guidelines and searchable indexes in the <SPAN
CLASS="guimenu"
>Help</SPAN
> menus, we won't discuss them in detail. For references, see you system documentation or the web sites of the projects, such as</P
><P
></P
><UL
><LI
><P
><A
HREF="http://www.openoffice.org"
TARGET="_top"
>http://www.openoffice.org</A
></P
></LI
><LI
><P
><A
HREF="http://www.koffice.org"
TARGET="_top"
>http://www.koffice.org</A
></P
></LI
><LI
><P
><A
HREF="http://freshmeat.net"
TARGET="_top"
>Freshmeat</A
> and <A
HREF="http://sourceforge.org"
TARGET="_top"
>SourceForge</A
> for various other projects.</P
></LI
></UL
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="sect_06_03_03"
></A
>6.3.3. Remarks</H2
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="sect_06_03_03_01"
></A
>6.3.3.1. General use of office documents</H3
><P
>Try to limit the use of office documents for the purposes they were meant for: the office.</P
><P
>An example: it drives most Linux users crazy if you send them a mail that says in the body something like: <SPAN
CLASS="QUOTE"
>"Hello, I want to tell you something, see attach"</SPAN
>, and then the attachement proves to be an MS Word compatible document like: <SPAN
CLASS="QUOTE"
>"Hello my friend, how is your new job going and will you have time to have lunch with me tomorrow?"</SPAN
> Also a bad idea is the attachment of your signature in such a file, for instance. If you want to sign messages or files, use GPG, the PGP-compatible <SPAN
CLASS="application"
>GNU Privacy Guard</SPAN
> or SSL (Secure Socket Layer) certificates.</P
><P
>These users are not annoyed because they are unable to read these documents, or because they are worried that these formats typically generate much larger files, but rather because of the implication that they are using MS Windows, and possibly because of the extra work of starting some additional programs.</P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="sect_06_03_03_02"
></A
>6.3.3.2. System and user configuration files</H3
><P
>In the next chapter, we start configuring our environment, and this might include editing all kinds of files that determine how a program behave.</P
><P
><EM
>Don't edit these files with any office component!</EM
></P
><P
>The default file format specification would make the program add several lines of code, defining the format of the file and the fonts used. These lines won't be interpreted in the correct way by the programs depending on them, resulting in errors or a crash of the program reading the file. In some cases, you can save the file as plain text, but you'll run into trouble when making this a habit.</P
></DIV
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="sect_06_03_03_03"
></A
>6.3.3.3. But I want a graphical text editor!</H3
><P
>If you really insist, try <B
CLASS="command"
>gedit</B
>, <B
CLASS="command"
>kedit</B
>, <B
CLASS="command"
>kwrite</B
> or <B
CLASS="command"
>xedit</B
>; these programs only do text files, which is what we will be needing. If you plan on doing anything serious, though, stick to a real text mode editor such as <B
CLASS="command"
>vim</B
> or <B
CLASS="command"
>emacs</B
>.</P
><P
>An acceptable alternative is <B
CLASS="command"
>gvim</B
>, the <SPAN
CLASS="application"
>Gnome</SPAN
> version of <B
CLASS="command"
>vim</B
>. You still need to use <B
CLASS="command"
>vi</B
> commands, but if you are stuck, you can look them up in the menus.</P
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="sect_06_02.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="sect_06_04.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Using the Vim editor</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="chap_06.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Summary</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
Reference in New Issue View Git Blame Copy Permalink