Conference iosg::all-in-1_v30

    Hi,
    
    Problem number 2 has been fixed in the PFR and it is was a case of
    removing a superfluous OA$FLD_DONE  from OAN$INDEX. The change was to
    the last few lines of the XOP ~~REGULAR_FIND~~. 
    
    Before it was 
    
     .IF (OA$SCROLL_DATA_SET NES "*NOTEIND") AND (#OAN_STATUS EQ 0)
      THEN
         CLOSE_PRIOR\\
         OA$FLD_DONE\\
         OA$FLD_EXIT
    
    Now it is
    
     .IF (OA$SCROLL_DATA_SET NES "*NOTEIND") AND (#OAN_STATUS EQ 0)
      THEN
         CLOSE_PRIOR\\
         OA$FLD_EXIT
    
    I tried to reproduce problem 1 and printed a wide note to TERMINAL and
    it worked OK. When you say you set the left margin, exactly what did
    you do (including keystrokes please)?
    
    For problem 3, which menu option did you use to get the print? This
    question shows the depth of my GPC knowledge!!
    
    Cheers
    
    Stuart

    Hi Stuart,
	
	nice to meet you again (better: to read your reply)! 

>    Problem number 2 has been fixed in the PFR and it is was a case of
>    removing a superfluous OA$FLD_DONE  from OAN$INDEX. The change was to
>    the last few lines of the XOP ~~REGULAR_FIND~~. 

	Thank you very much for this info. I've traced it and I'm sitting here 
	with the logfile. Ufffh, really fine!
    
>    I tried to reproduce problem 1 and printed a wide note to TERMINAL and
>    it worked OK. When you say you set the left margin, exactly what did
>    you do (including keystrokes please)?

	GPC SEL select a conference and a note-ID.
	Then P rint this on a Printer (e.g. a DECLASER with ANSI/PS Queue)
	<GOLD A> PG Left Margin e.g. 5.
	P rint again. (now foreground!)
	OR if you've stored this settings in #0 Print-Settings you can do
	P rint <RETURN> (background!)
	See your Printout, nasty.

>    For problem 3, which menu option did you use to get the print? This
>    question shows the depth of my GPC knowledge!!
 
	I think that they've written a script which does something like
	ICK (Index of Keywords). I'll try to get the script!

	I hope this will help you!

	Many many thanks for your response! 
	Best regards	
	Charly_from_CSC_Vienna

	

	Good morning Stuart,

>    For problem 3, which menu option did you use to get the print? This
>    question shows the depth of my GPC knowledge!!
 
>	I think that they've written a script which does something like
>	ICK (Index of Keywords). I'll try to get the script!

	Well, it's not a script it's GPC ICK GOLD M  R ead  "keyword" or
                                                     P rint "keyword"

	I think here's the problem with the limitation of a DSAB > 255 chars.

	Many many thanks for your response! 
	Best regards	
	Charly_from_CSC_Vienna
    

Hi Stuart,
	
	some more details for GPC ICK R (sorry that this is German LLV).


                  Verzeichnis der Stichw�rter einer Konferenz
 (Markiert: 0  )  Konferenz: TESTFORCHARLY              (Neue Nachrichten: 0  )

 Nr.     Stichwort              Beitr�ge mit Stichwort

   1     COV
 > 2     TEST                   1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0, 10

R ead

 
 Stichwort:  TEST                                                            
                                                                             
 In Beitrag: 1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0, 10.0, 11.0, 12.    
             0, 13.0, 14.0, 15.0, 16.0, 17.0, 18.0, 19.0, 20.0, 21.0, 22.    
             0, 23.0, 24.0, 25.0, 26.0, 27.0, 28.0, 29.0, 30.0, 31.0, 32.    
             0, 33.0, 34.0, 35.0, 36.0, 37.0, 38.0, 39.0, 40.0, 41.0, 42.    
             0, 43.0, 44.0,                                                  
                                                                             
Weiter mit [Return].

But keyboard TEST has topics 1.0 - 110.0 related. (I've created them by hand!)

And if you choose P rint you'll only see

TEST                                                            
            
Stichwort    Beitr�ge mit Stichwort
==============================================================================
TEST	               1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0, 10.0, 11.0,
                       12.0, 13.0, 14.0, 15.0, 16.0, 17.0, 18.0, 19.0, 20.0, 21
                       .0, 22.0, 23.0, 24.0, 25.0, 26.0, 27.0, 28.0, 29.0, 30.0
                       , 31.0, 32.0, 33.0, 34.0, 35.0, 36.0, 37.0, 38.0, 39.0, 
                       40.0

Should I SPR this now, because it's very urgent for CoV. I hope that a fix
will be available (:==:)

Best regards
Charly_from_CSC_Vienna

    

    Hi Charly,
    
    Re .3 and .4
    
    I've looked at the code and the 255 restriction is in a PASCAL source
    module that customers are not given. So an SPR is your only hope -
    sorry.
    
    Re .2
    
    I've also looked at the printing problem. GPC assumes that it has 80
    characters per line for its text, as do most other utilities. As an
    experiment could try temporarily going to set working conditions (US
    SWC) and setting your editor to EDT. Then try printing from GPC, and
    you will find it prints without the left margin, but without bolding on
    some types of printers.
    
    If this is acceptable then you can customise oan$print.scp to replace
    oa$default_extension by ".txt"
    
    Cheers
    
    Stuart

    Hi again,
    
    Here is an unofficial fix I've knocked up that you can try:
    
    Change the V2.4 OAN$INDEX as follows:
    
    a) Change the line 
    
    FORM OAN$INDEX$FIND\IFEXIT\CLOSE_PRIOR\OA$SCL_EXIT\BIND_BREAK *NOTEIND\
    
    to
    
    FORM OAN$INDEX$FIND\
    .IF OA$FORM_DISPOSE EQ 0
      THEN
        GET #STATUS = 0\\
        CLOSE_PRIOR\\
        OA$FLD_EXIT\
    IFEXIT\CLOSE_PRIOR\OA$SCL_EXIT\BIND_BREAK *NOTEIND\
    
    b) in the index option (OA$_MO_INDEX) change the line
    
    XOP ~~REGULAR_FIND~~\
    
    to
    
    XOP ~~REGULAR_FIND~~\OA$FLD_STAY\
    
    Cheers
    
    Stuart