-------------------------------------------------------------------------------
FTETX  - TeX-Package for FTE                                       version 0.04
-------------------------------------------------------------------------------

Notes and Hints:
----------------


DOS:

  o  Don't think the DOS-version of Alladin Ghostscript will work
     with fte/txlaunch. This is due to the DOS4GW 32bit DOS extender
     (used by Alladin Ghostscript) versus go32 or emx. You might encounter
     problems from running out of files upto system crashes.
       
     Note:
       Is this still true with go32 (djgpp) version 2 ?

  o  Memory gets low when running external programs. (At least
     conventional memory below 640K.) If you get in trouble:
       a) Try to replace the batchfile calls. Call the program
          directly without a batchfile.
       b) Try to get an new version of that program, compiled with
          djgpp. Or try to get an old version with less features
          and maybe less need for memory ;)
       c) If you want to run an emx-program, try the emx-version of
          txlaunch. Maybe you need a mixed installation (both txlaunch
          DOS versions in use, renamed to unique names; modified
          files in /contrib/tex_v004/menu/run.)

     Note:
       I've seen XMS getting low, too. I'm running Novell DOS 7,
       Novell DPMI host disabled, CWSDPMI in use, 8MB RAM.
       XMS memory used by fte and txlaunch appears not to be swapped out
       when running emTeX-previewers.
       

DOS,OS/2:

  o  If you run both systems on one machine (e.g. with OS/2 BootManager
     installed), you can have two different configuration files for
     txlaunch:
       Give them different names (e.g. `txlaunch.dos' and `txlaunch.os2', 
       that's default now).
       Put the statements `SET TXLAUNCHC=D:\EMTEX\DATA\TXLAUNCH.DOS' into
       your AUTOEXEC.BAT and `SET TXLAUNCHC=D:\EMTEX\DATA\TXLAUNCH.OS2'
       into your CONFIG.SYS for OS/2, if you do not have emTeX installed
       on drive C. If you have, this can be ommitted.
     This should work for mix of other OS too.  

       
OS/2, PM version:

  o  When running spellcheckers (ispell) currently you MUST do a MANUAL
     RELOAD (Files menu) after the spell check is complete. Currently FTE
     does not wait for the spellchecker's termination and reloads the file
     immedieatly while ispell is starting up.

     
OS/2, DOS:

  o  If you modify the prog-menus:
     Note the backward quotes around the section names when calling txlaunch
     (e.g. `LaTeX2e`). This is for the djppp (DOS) version of fte.
     The C-library coming with djgpp has the `nice' feature, that it strips
     quotes from commandlines when calling child programs. But it doesn't
     strip the `-quotes :). This is why I have implemented the backward quotes
     in txlaunch too... Otherwise we would have to write:
     "txlaunch.exe \"'section'\" ...".
     ...what is a mess to read and write.




TODO / Lists of wishes / Lists of questions
-------------------------------------------


Macro-menu:
-----------

  Some things are a 'little' bit mixed up and non-consistent:

    o  Which macros should end up with an 'backslash-space' sequence, 
       which shouldn't ?
    o  Which macros should automatically grab the following character ? 
       (currently these are some accents)
    o  When inserting, the cursor is automatically placed inside the pair 
       of curley braces (of the macro-argument) for *some* macros.
       For other macros this isn't done. 
    o  Some macros are inserted with default values for the arguments
       others are not.
    o  There are some accents I don't know the name for - do you ?
    o  The handling of a prevously selected area is not well.
    o  Still macros absent (surprise? ;) ) Which are really needed,
       which macros could be removed ? 
    o  ...




TeX-Prog-menu / txlaunch:
-------------------------

  First note:
    All of my code is initially for emTeX (by Eberhard Mattes) running
    on IBM OS/2 Warp. It's tested with DOS in a next step. I've compiled
    txlaunch for linux, too, but I cannot really check FTETX with linux
    (due to lack of time, linux expierence...)

  Things todo:

    o  maybe porting txlaunch to NT, Win95. The DOS-versions should run
       in a DOS-box. But a real Windows box might give better speed or
       memory performance.
       This can't be done by me (OS, compiler, time missing).
    o  Additional configuration files for NT, Win95, UNIX/Linux.
    o  Configuration files for other TeX implementations.
    o  Find out a source for an emx-compiled DOS version of Ghostscript
       -- if there is any --; and place the URL somewhere in the
       documentation ;)
       See above.

  Things that might be done but will become a hack:
       
    o  Viewing the logfiles with fte would be nice. But unfortunately
       most of them - and their names - are implementation specific :( 
    o  Parsing the TeX-logfile and prev-/next-error would be nice...
       I have to think if I can do this.
    o  Piping TeXs input/output from TXLAUNCH with re-re-directing
       TeXs stdin back to console (if this is possible). (Goal: running TeX
       via Compile from FTE, in a message buffer).
    o  Maybe support of TeX's interactive editor-call. 
    


Documentation:
--------------

  Writing better english - and german, too :-)))

  Documentation is unfortunately a bit mixed up. But I didn't spent too
  much time for it. And it's better to have this one than no one. Right?

  Last note:
    That's no longer true! I spent *too* much time in the documentation.
    Therefore it's a little bit mixed up... ;)

  The english translation of doc-files has been done very quickly
  (about ten times faster than writing the original german files).
  Mercy!
  

Misc.
-----

    o Online LaTeX help. (LaTeX2e.info / LaTex2e.inf / LaTeX2e.hlp)
      But I'm waiting to see what happens to FTE.
      Currently calling help files is possible, context help for
      Keyword is not.


-------------------------------------------------------------------------------
