<TeXmacs|1.0.2.5>

<style|tmdoc>

<\body>
  <tmdoc-title|Frequently asked questions>

  <section*|Overview>

  <\itemize>
    <item>General

    <\itemize-minus>
      <item>What is <TeXmacs>?

      <item>For what typical purposes do people use \ <TeXmacs>?

      <item>What Operation Systems are supported?

      <item>What are the system requirements?

      <item>I have a question, where should I ask it?

      <item>Is it free Software?
    </itemize-minus>

    <item>System Appearance and Behavior

    <\itemize-minus>
      <item><TeXmacs> hangs when opening a document for a whle and my disk is
      being filled with files?

      <item>How can I see the <LaTeX> or <TeX> code corresponding to what I
      see on the screen?

      <item>Why don't you use a common graphical user interface like GTK for
      your scrollbars, menus, and so on?

      <item>Trying to start <TeXmacs> remotely over a ssh connection, I get
      an error, while <abbr|e.g.> xclock works without a problem?
    </itemize-minus>

    <item>Usage

    <\itemize-minus>
      <item>How to mark/select a whole paragraph?

      <item>Spell checking always starts at the beginning of the document?
    </itemize-minus>

    <item>Microtypography

    <\itemize-minus>
      <item>There is too much space after an abbreviation like <abbr|wrt.> or
      <abbr|etc.>?

      <item>How to add unbreakable space?
    </itemize-minus>

    <item>Legacy Questions
  </itemize>

  <value|hrule>

  <section*|General>

  <\question>
    What is <TeXmacs>?
  </question>

  <\answer>
    GNU <TeXmacs>

    <\itemize-dot>
      <item>is a free scientific text editor, which was both inspired by
      <TeX> and GNU Emacs.

      <item>allows you to write structured documents via a wysiwyg
      (what-you-see-is-what-you-get) and user friendly interface.

      <item>lets you create new styles.

      <item>implements high-quality typesetting algorithms and <TeX> fonts,
      which helps you to produce professionally looking documents.

      <item>is suitable as an interface for computer algebra systems, as the
      high typesetting quality goes through for automatically generated
      formulas.

      <item>can be highly customized as it supports the Guile/Scheme
      extension language.

      <item>lets you export your documents to PS and PDF and offers both
      import and export to HTML, <LaTeX>, Scheme, Verbatim and Xml. We would
      very much appreciate your <hlink|help|http://www.texmacs.org/Web/Contribute.html>
      for writing and improving converters for <TeXmacs> documents.
    </itemize-dot>
  </answer>

  <\question>
    For what typical purposes do people use \ <TeXmacs>?
  </question>

  <\answer>
    \ <TeXmacs> can be used for

    <\itemize>
      <item>Books and Articles. They can be written fully within <TeXmacs>.
      If your publisher requires a certain <LaTeX> style for an article, then
      as a last step you can export your document to <LaTeX> and make the
      final modifications there.

      <item>Presentations.

      <item>Interface to Computer Algebra Systems.

      <item>Webpages. For example the <TeXmacs> webpage is maintained as
      <TeXmacs> documents, which are exported to <name|HTML>.\ 
    </itemize>
  </answer>

  <\question>
    What Operation Systems are supported?
  </question>

  <\answer>
    <TeXmacs> can be easily installed on all major systems. There are
    <name|rpm> and Debian packages as well as binaries available for
    <name|Linux>. For Mac <name|OS X> there is a <name|Fink> package. For
    <name|MS Windows>, a <name|Cygwin> package is in preparation, but so far
    you have to compile <TeXmacs> yourself, as it is the case for more exotic
    systems.\ 

    Work is in progress to rewrite the graphical user interface of <TeXmacs>,
    so that it becomes more portable. Your
    <hlink|help|http://www.texmacs.org/Web/Contribute.html> might actually be
    very useful here.
  </answer>

  <\question>
    What are the system requirements?
  </question>

  <answer|A reasonably fast machine is recommended. Having said this, I
  (Andreas) am typing this on a Pentium III 450Mhz under Cygwin, and
  <TeXmacs> is still useable here, although not overly reactive. >

  <\question>
    I have already learned <TeX>/<LaTeX> and <name|Emacs>, do I have to learn
    all over again?
  </question>

  <answer|You will find out, that much <LaTeX>-knowledge can be reused. For
  example, you can start a section by typing <key|\\section[return]> or you
  get <with|mode|math|\<alpha\><rsub|1>> by typing <key|$\\alpha_1$>. Note
  that there are even shorter ways provided, for example <key|$a[tab]$> gives
  you an alpha as well, so you might want to migrage after a while. Styles
  like article, book or seminar, as known from <LaTeX>, are provided as well.
  Furthermore, many <name|Emacs> shortcuts like <key|C-x C-s> for saving a
  file, or <key|C-_> for undo will work. >

  <\question>
    I have a question, where should I ask it?
  </question>

  <answer|The best place is the <TeXmacs> user mailing list. Search this list
  and the FAQ beforehand, to ensure your question was not asked before.>

  <\question>
    Is it free Software?
  </question>

  <answer|<TeXmacs> falls under the GNU public licence. >

  <section*|System Appearance and Behavior>

  <\question>
    <TeXmacs> hangs when opening a document for a whle and my disk is being
    filled with files?
  </question>

  <answer|This behaviour is normal. <TeXmacs> calls <name|Metafont> in order
  to generate fonts which are not yet present. The first time you launch
  <TeXmacs>, many fonts may therefore have to be generated. In order to avoid
  this, you may download some <hlink|pregenerated
  fonts|http://www.texmacs.org/Download/Fonts.html>.>

  <\question>
    How can I see the <LaTeX> or <TeX> code corresponding to what I see on
    the screen?
  </question>

  <answer|This question is due to a fundamental misunderstanding about
  <TeXmacs>. Indeed, <TeXmacs> is not <em|based> on <TeX>/<LaTeX>, although
  it does support (not yet perfect) <em|conversion> to and from <LaTeX>.
  Furthermore, in theory at least, there is actually no need anymore to look
  at something like the <TeX> source, since <TeXmacs> is guaranteed to be
  fully WYSIWYG. Conversion to <LaTeX> may only be useful, when transmitting
  an accepted paper to the publisher of a journal.>

  <\question>
    Why don't you use a common graphical user interface like GTK for your
    scrollbars, menus, and so on?
  </question>

  <\answer>
    When I (Joris) started to develop <TeXmacs> about four years ago, the
    common graphical user interfaces were not as good as nowadays. Moreover,
    I wanted the GUI to support some special features, like <TeX> fonts in
    the menus. Nevertheless, now that graphical user interfaces did become
    much better, I plan to switch to guile-gtk as soon as possible. Using
    Guile-gtk in combination with <TeXmacs> has three main advantages:

    <\enumerate>
      <item>One has full access to the GTK widget set, which includes menus,
      scrollable windows, file choosers, iconbars, etc.

      <item>Guile-gtk provides you with a very flexible and customizable way
      to use these widgets.

      <item>The incorporation of Guile-gtk in <TeXmacs> should be natural,
      since <TeXmacs> already supports the <name|Guile>/<name|Scheme>
      extension language.
    </enumerate>
  </answer>

  <\question>
    Trying to start <TeXmacs> remotely over a ssh connection, I get an error,
    while <abbr|e.g.> xclock works without a problem?
  </question>

  <\answer>
    If you get an error message including the following:

    <verbatim|Fatal error: I failed to connect to Xserver in
    'x_display_rep::x_display_rep>

    then execute <verbatim|export DISPLAY=127.0.0.1:10.0> on the remote
    machine and make sure your /etc/hosts file is sound, <abbr|i.e.> it
    contains the line <verbatim|127.0.0.1 localhost> and the IP information
    about the local and remote machine.
  </answer>

  <section*|Usage>

  <\question>
    How to mark/select a whole paragraph?
  </question>

  <answer|Clicking once on a word will place the cursor there, clicking twice
  marks this word, clicking thrice will mark the paragraph and so on;
  eventually, the whole document will be selected.>

  <\question>
    Spell checking always starts at the beginning of the document?
  </question>

  <answer|Mark a region, and spell checking will be restricted to this
  selection.>

  <section*|Microtypography>

  <\question>
    There is too much space after an abbreviation like <abbr|wrt.> or
    <abbr|etc.>?
  </question>

  <answer|This is because <TeXmacs> thinks, that the sentence ends after the
  dot in the abbreviation. To resolve this <em|a posteriori>, mark the
  abbreviation and press <key|A-a>. To care for this while writing: <key|A-a>
  <key|etc.> <key|[right]>.>

  <\question>
    How to add unbreakable space?
  </question>

  <answer|>

  <value|hrule>

  Remaining legacy questions:

  <\question>
    A publisher sent me a giant <LaTeX> preamble I'm supposed to put in in
    order to prepare a book for them. What is the best way of putting it in
    and figuring if it will work?
  </question>

  <\answer>
    I recommand to convert the preamble to <TeXmacs> and to put the result in
    a <TeXmacs> style file. However, the result will probably be
    disappointing, because conversion between <TeX>/<LaTeX> and <TeXmacs> is
    not yet perfect and style files are particularly problematic. What you
    can also do is write a <TeXmacs> style file by your own which supports
    the major extra constructs you want to use from the editors style file.
    When you convert your book to <LaTeX>, you next use the editors style.
    Some layout will probably need to be redone at that stage, but this
    should actually be the work of the editor... Please look in the <TeXmacs>
    help for more information about convertions between <TeXmacs> and
    <LaTeX>.
  </answer>

  <apply|tmdoc-copyright|1998--2002|Joris van der Hoeven>

  <tmdoc-license|Permission is granted to copy, distribute and/or modify this
  document under the terms of the GNU Free Documentation License, Version 1.1
  or any later version published by the Free Software Foundation; with no
  Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
  Texts. A copy of the license is included in the section entitled "GNU Free
  Documentation License".>
</body>

<\initial>
  <\collection>
    <associate|preamble|false>
    <associate|info flag|short>
    <associate|paragraph width|150mm>
    <associate|odd page margin|30mm>
    <associate|page right margin|30mm>
    <associate|page top margin|30mm>
    <associate|reduction page right margin|25mm>
    <associate|page type|a4>
    <associate|reduction page bottom margin|15mm>
    <associate|even page margin|30mm>
    <associate|reduction page left margin|25mm>
    <associate|page bottom margin|30mm>
    <associate|reduction page top margin|15mm>
    <associate|language|english>
  </collection>
</initial>

<\references>
  <\collection>
    <associate|toc-10|<tuple|2.2|?>>
    <associate|toc-11|<tuple|3.2|?>>
    <associate|toc-12|<tuple|3.2|?>>
    <associate|toc-13|<tuple|3.2|?>>
    <associate|toc-14|<tuple|3.2|?>>
    <associate|toc-15|<tuple|3.2|?>>
    <associate|toc-16|<tuple|3.2|?>>
    <associate|toc-17|<tuple|3.2|?>>
    <associate|toc-18|<tuple|3.2|?>>
    <associate|toc-19|<tuple|4.2|?>>
    <associate|toc-1|<tuple|1|?>>
    <associate|toc-2|<tuple|1.1|?>>
    <associate|toc-3|<tuple|1.2|?>>
    <associate|toc-4|<tuple|1.2|?>>
    <associate|toc-5|<tuple|1.2|?>>
    <associate|toc-6|<tuple|2.2|?>>
    <associate|toc-7|<tuple|2.2|?>>
    <associate|toc-8|<tuple|2.2|?>>
    <associate|toc-9|<tuple|2.2|?>>
  </collection>
</references>
