Conference vaxuum::document_ft

RE: .0

The DSR converter is almost completed. We have not begun work on a WPS 
converter, but welcome any requirements for such a converter. How would
you be using it? Do you use the DECpage keying conventions? Do you use
*any* keying conventions? Would your users continue to use WPS to enter
text, or would they enter SDML tags once a document had been converted?

Information about issues such as the above will be a great help to us
in identifying what a WPS to DOCUMENT converter really means.

Thanks,
Brian

	 A WPS+ converter would be great to use in ALL-IN-1

         (If DOCUMENT can be intergrated with ALL-IN-1)
	 
	 ALL-IN-1 users could use DOCUMENT without having to
	 know LSE etc. to create high quality documents.

	 <Eric>
	 
	 

	Another vote for a DOCUMENT/ALL-IN-1 interface!!!!!!

	I would lobby vigorously for my Area DIS manager to put such a thing 
on the Area ALL-IN-1 cluster.  Then I can FORGET about RUNOFF and DECpage!

  I think (what I understand All-in-1 users do with WPS+ - two packages
  I have sofar managed to stay clear off) that the converter should 
  be able to take a WPS+ file, with all its hidden formatting commands
  for lists, headers, rulers etc, to be converted in a normal ASCII 
  text file including the proper Document commands.

  I have no clue to give how to do this though...

  
Theo


P.S.
Unrelated, but we seem to have sold Document to Philips for their internal
documentation... and others are interested too. Document may live and prosper
in Holland. Any converter can only add in its significance
  

	If I may, I would like to make a couple of suggestions:


	1. Forget trying to convert DECpage/WPSPLUS to DOCUMENT.  As someone 
in Topic 53 so elequently said, "So little time, so many ratholes".  Trying 
to turn WYSIWYG documents into SDML is like trying to read someone's mind
AFTER they had the thought!  Let the authors go back and do that.

	2. Concentrate on getting DOCUMENT interfaced to ALL-IN-1. WPSPLUS, 
the stand-alone product, uses ALL-IN-1's core as an application engine, thus 
uses its file cabinet, file naming convention (bizarre!), and script 
meta-language, so an ALL-IN-1 interface should meld nicely with WPSPLUS 
product.  The application would look similar to DECpage's, I think.

	I can't begin to fathom the amount of value ALL-IN-1 would add to 
DOCUMENT, and vice-versa.  Think of the EXPOSURE to customers!

    The converter sounds like a good idea to me.  Some of our departments
    have gone to WPS/DECpage so they can have the secretaries type their
    documents.  The secretaries know WPS and don't know LSE/OUTLINE/SDML.
    So now we have separate departments using incompatible tools.  Delivery
    units use OUTLINE/LSE/DOCUMENT and Sales/SS use WPS/DECPAGE.  
             
    The converter would be best to convert both types of WPS stuff,
    both with and without the DECPAGE conventions.  Perhaps a switch?
    
    Integration with All-in-1 is OK, BUT PLEASE BE SURE NOT TO FORCE
    INTEGRATION!!!  There are many of us out in the field that don't
    use machines with All-in-1 any more than we ABSOLUTELY have to.
    Please make sure that the functionality of DOCUMENT isn't compromised
    in any way just for integration purposes.
    
    D

    It depends upon your resources.
    
    You can only do so much with the people you have.
    
    It would seem that the following should be concentrated on and in
    this order.
    
    1.  V2 with all of its new features for designing page layouts and
        other...
    
    2.  WYSIWYG front-end editor.
    
    	I see document as great, but I am a techie by heart anyway. The real
	problem in getting it accepted (even by DEC) is the problem with its'
	interface.  I mean runoff style input, tags etc... most of the sales
	updates favor WPS+/DECpage for 'Electronic Publishing' unless
        you have major stuff to do with many users.
    
        If we had a 'Interleaf' style front-end editor we could simply
        let the WPS people do a DX into an ascii file and import into
        the front-end WYSIWYG editor and go to it.  Thereafter they
        could just use it to create more.

    
    These are my thoughts.
    
    Jerry

    Somebody already tried it out.......



              <<< OAXTRA::DUA1:[NOTES$LIBRARY]ALLIN1_V2.NOTE;2 >>>
                                ALL-IN-1 V2 Notes
Created: 28-FEB-1986 15:49         2073 topics        Updated:  8-SEP-1987 17:10
       -< ALL-IN-1 is a valuable trademark.  Please spell it correctly. >-

================================================================================
Note 2064.3          Alternating heading in WPSPLUS document              3 of 3
SNO78C::WAITES "Ahh winter in Sydney.."              20 lines   7-SEP-1987 19:25
--------------------------------------------------------------------------------
                           -< DOCUMENT Integration >-

    Ian Smith and I interfaced DOCUMENT to ALL-IN-1 at DECUS to demo
    integrated publishing.
    
    The steps were:
    
        - new DT option to transfer/convert from WPSPLUS to SDML
        - new DOCUMENT format (similar to RUNOFF)
    
    It was pretty rough and ready but took only a few hours.
    
    Final result did seem incredibly similar to DECpage but it used
    DOCUMENT so I understood it better and with a little more time we
    could have played with different formats, etc.
    
    Note: the WPSPLUS to SDML conversion was pretty primitive (going
    through DX format on the way but maintaining bold and underline
    characteristics)
    
    wifdi (...fun..)
    Andrew

     

    To clarify:
    
    	Some of the early replies are clearly talking about a very advanced
    level of conversion from WPSPLUS. What Ian's program did was VERY
    simple. No lists, tables, TDE. It took a DX format file with bold
    and underlining and converted it to SDML with <P> and <EMPHASIS>
    markers.
    
    	I did most of the "integration" stuff. This was very simple
    but effectively integrated DOCUMENT to the same level that RUNOFF
    has been integrated. I strongly suggest that this IS easy and DOCUMENT
    product management should have a word with ALL-IN-1 pm about this.
    
    	When I get the stuff off backup I may be able to add more info
    if required.
    
    Andrew