THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net


S U M M A R Y


DIARY: March 20, 2002 07:23 PM Wednesday; Rod Welch

Improved addressability SDS on Internet so easier to link.

1...Summary/Objective
2...Explicit Links Enable Copy Link Address on Internet
3...Explicit Links Required for Microsoft Programs Intelligence Support
.........Onmouseover, Onmouseclick Possible Application
4...000008 Macro 142 Save Function
5...Save F2 Add Anchors to Para and Headings Automatically
6...0702051 Save Function Add Anchors to All Para and Headings
7...Underlined Headings within 6 Lines
8...Follow Up Blank Line Below Uniform Format
9...Highlighted Headlines - J Within 10 Lines
10...Lists with Multiple Dots Put Anchors Above List and Jump to Bottom
11...Paragraphs Get Anchors within 15 Lines Only on Capital Letters
.....Anchors on Paragraphs Within 30 Columns Avoid Labels
.....Left Margin Located with Macro 541 Anchors Only within 30 Columns
.....Control Fields Excluded from Anchor Process
.....Anchors Every 15 Lines
.....Indented Headings in Line Numbers
.....Justify Para with Anchors
12...Headlines Without Underlines Get Anchors

ACTION ITEMS.................. Click here to comment!

1... ......................................................... 2... 3... 4... 5...6...are Unique

.................ÄÄÄÄÄÄÄÄÄÄÄ
- ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ>160401 - Line 1220, ref OF 3 OX5K, -label ancRe in 0702051
......................................................... ....Develop code to verify every anchor in the record is unique. Use

....code developed for documents in 0122 on 000810. ref SDS 4 K4E1
......................................................... 7... ....We need this mostly when some lines are copied or repeated to
....another location, and the User forgets to change the anchors.
......................................................... 8... ....The code starts at the top and looks for anchors. It gets the
....anchor string and looks for any other strings in the file.
......................................................... 9... ....Setup F2 to re-start 0702051 to complete processing after the user
....modifies the anchor.
......................................................... 10... ....F1 is assigned to give another error message telling the user to
....change the anchor. Almost anything will work, so it is not a big
....deal. There may be a tendency for the user to want to press F1 F1
....F3 to create a whole new anchor, but this is not necessary.
....Changing just one or at most two characters to anything will make
....an anchor unique in the record under the current scheme. So, this
....is a simple solution to an important requirement for anchors to be
....unique within record.
......................................................... 11... ......................................................... 12... ......................................................... 13... ......................................................... 14... ......................................................... 15... ......................................................... 16... 17... 18...Time Milg Emply T Bill Function Special Subject/File

- K101 00.0 0000 00012 0 00040 11010100 00000000 03 00050 10 30 08 KCCK
19...0000 00012 0 00040 11010100 00000000 03 00050 10 30 08 KGR CG5JGC
20...0000 00012 0 00040 11010100 00000000 03 00050 10 30 CKHGC
21...NAME="L19>Anchors Addressibility Anchors in Doc Every Para, 0122, 000810
22...to Anchors so People Can Copy to Internet Address
23... 24... 25... ......................................................... 26...070405 Links Added Above Anchors to Aid Copying Internet Address

27...ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
28...On 980314 developed code to link summaries to headings. ref SDS 2
29...3549
......................................................... 30... 31...The improvements above that ensure anchors on all para and headings
32...enable improving display by browsers of SDS records a bit by....
......................................................... .....1...Making links in Summary to anchors above headings, so they

.........display better.
......................................................... 33... .........Currently the link in the summary goes to the heading line,
.........but this sometimes displays with a portion of the target line
.........not visible, which is distracting. Putting the anchor above
.........the heading line, using the above code, will solve the
.........problem.
......................................................... 34... .....2...Multiple headlines can now use the same anchor, because there
.........will always be an anchor at the top of the stack. This
.........requires a new design for selecting only the anchor above all
.........headlines, rather than the original design that provided a
.........link in the Summary to every line in a multi-headline list.
.........This was very redundant, but was required until explicit links
.........were added today, per above. ref SDS 0 VP6F
......................................................... 35... .........Action items will retain the original design in order to
.........maintain clarity. An example is an action item identified in
.........the middle of a paragraph. The anchor is above the para in
.........this case, so to ensure clarity will retain original feature
.........of constructing an anchor at the action item line for display
.........in a web browser. Actually, this condition does not occur
.........often, and so it might be ignored in conforming action item
.........anchors to the new system for headlines, which is adequate for
.........the majority of action items, since now every para gets an
.........anchor. Generally, action items begin a para, so most of them
.........will have an anchor on the line above. Will work with this
.........for awhile to gain more experience on utility.
......................................................... .040212 Gary Johnson asked about the format for linking

.............action items to the summary. ref SDS 31 6G5L
......................................................... 36... .....3...Add link with a dot above all headings that enable people to
.........easily copy the link.
......................................................... 37... .........Would like to use onmouseover or something similar, but for
.........now the dot may be adequate.
......................................................... 38... ......................................................... 39...Line 220, ref OF 4 NF3O, -label nPrg

......................................................... ....Testing debug here.

......................................................... 40... 41...Line 280, ref OF 4 5G9O, -label nPrg
......................................................... ....Today, remove code that checks for Summary/Objective and creates

....this if it is missing and deletes extraneous Summary/Objective
....headings. This is no longer needed because Save now puts this on
....every record, per above. ref SDS 0 0800
......................................................... 42... 43...Line 300, ref OF 4 XN5L, -label nPrg about 90 lines below
......................................................... ....Added code that transfers 0001 default anchor from Follow up line

....to above Summary/Objective, and create a blank line above default
....anchor line, so the code that enters the formatting will have space
....for entering HTML code for the font. per below. ref SDS 0 AU7R
......................................................... 44... ......................................................... 45...Line 360, ref OF 4 1407, -label cOMMn

......................................................... ....This is code that grabs up the headlines.

......................................................... 46... 47...Line 450, ref OF 4 JX6H, -label hdLC
......................................................... ....Here the code is getting the anchor above Summary/Objective and is

....deleting the Summary/Objective line. Changed this so we include
....Summary/Objective in the list of headlines.
......................................................... ....Actually, want to transfer 0001 anchor from 01 line where Follow

....up is, and put it above Summary/Objective, so it displays a little
....better.
......................................................... 48... ......................................................... 49...Line 1035, ref OF 4 1653, -label lp1, this is the loop that links the

50...Summary to the headings in the record.
......................................................... 51... 52...Line 1270, ref OF 4 ZN8I, -label lp1
......................................................... ....Add flag 117 0 to establish when an anchor is used other than the

....line number.
......................................................... ....If an anchor is found 117 = 1 and we substitute the actual anchor.

......................................................... 53... 54...Line 1650, ref OF 4 QX6K, -label bslist
......................................................... ....This is where formatting is entered above Summary/Objective. We

....need a line for the default anchor, and a line above that for the
....HTML font command, per above. ref SDS 0 AY3L
......................................................... 55... ......................................................... 56...Line 1840, ref OF 4 4411, -label lpcn1

......................................................... ....This is where references are converted to HTML.

......................................................... 57... ......................................................... 58...Line 2300, ref OF 4 NS5O, -label lnk1

......................................................... ....Begin link routine for summaries.

......................................................... ....At this point the code has captured all heading lines and put them

....at the top of the record and is preparing to link each line in the
....summary to the corresponding heading line.
......................................................... ........Today, we are going to change this by making multiple

........headings for the same body of stuff refer to a common anchor
........above the group rather than to each individual heading line,
........per explanation above. ref SDS 0 0800 and ref SDS 0 JY4M
......................................................... 59... ....Notice that the first summary heading is blank, so this indicates
....the code is capturing the line above the Summary/Objective line,
....which needs to be changed. Did this above. ref SDS 0 FX7K
......................................................... 60... ......................................................... 61... ....Macro 1182 captures the line number which is used to find the
....corresponding heading below.
......................................................... 62... ......................................................... 63...Line 2230, ref OF 4 T15F, -label nAI11

......................................................... ....We then build a link using the line number as the anchor

....description.
......................................................... 64... 65...Line 2420, ref OF 4 P53M, -label eol3 about 30 lines below
......................................................... ....Open 070405 and use the line number captured for the heading in

....the summary line as a parameter to find the corresponding heading
....line in the record in order to create a link.
......................................................... 66... 67...Line 2440, ref OF 4 1E5N,
......................................................... ....Find the line and build the link.

......................................................... 68... 69...Line 2580, ref OF 4 LD5K, -label fAnC
......................................................... ....Added code to look for an anchor above a headline, and if it is

....found within 6 lines of the heading, then use that anchor for the
....Summary link, and if not then build a link using the line number.
......................................................... 70... ......................................................... 71...Line 2640, ref OF 4 1E5N, -label AIanc

......................................................... ....Revised code for 11=1 and 117 0 to create an anchor for the link

....using the line number, which is the original design.
......................................................... ....When 11=1 and 117=1 then the code uses the string for the anchor

....assigned by the user.
......................................................... ....When 11=2 the action items are being processed. Since these

....are transitory, the code will use line numbers to construct an
....anchor from the Summary to the details.
......................................................... 72... ......................................................... 73... 74...2 Dots Addressability Anchors with Visibility of Redundant Links
75...Anchors Converted and Links Added with 2 Dots for Addressability
76...ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
77...Line 2440, ref OF 4 ZN9M, -label lpcar
......................................................... ....Think this is where anchors are identified.

......................................................... 78... 79...Line 2520, ref OF 4 WS3O, -label carot
......................................................... ....Add code to capture the anchor with macro 1182.

......................................................... 80... 81...Line 2580, ref OF 4 648M, -label carot about 50 lines below
......................................................... ....Add code to enter a link above the anchor and use a .. as the

....symbol to let folks know there is an anchor that can be captured.
......................................................... 82... 83...Line 2600, ref OF 4 AT5K, -label enLnk in 070405
......................................................... ....setcnt 86 2

....macro 1181
......................................................... .......Start entering the anchor string a 2, becasue we are reading it

.......with macro 1361 that starts at 1 with the HTML symbol <, and we
.......don't want this is the anchor ID.
......................................................... 84... 85...Line 2620, ref OF 4 AT5K, -label enLnk
......................................................... ....setcnt 86 2

......................................................... .......Start at 2, because 1 is the symbol.

......................................................... 86... ....macro 1181
....rel_cur 0 -1
......................................................... .......Enter the anchor string, and then backup one position to put

.......the cursor at the end, so the HTML code will occur without a
.......space between the end of the anchor.
......................................................... 87... ....ins_text
......................................................... .......End HTML and identify 2 dots so User can see the location

.......of the anchor.
......................................................... 88... ......................................................... 89... 90...Line 2640, ref OF 4 F84O, -label end
......................................................... ....For some reason we are getting Distribution at bottom of the

....file entered twice.
......................................................... 91... ......................................................... 92... 93...Format Headings on Indented Lines
94...ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
95...Line 1670, ref OF 4 5076, -label Hdgx
......................................................... 96... ......................................................... 97...Citations Format Links

98...ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
99...Line 1800, ref OF 4 4411, -label cites
......................................................... 100... ......................................................... 101... 102... 103...P Commands
104...Para Received Docs with HTML, 000812
105...HTML Add Anchors on Para P Commands, 000812
106...Dots Links Above Every Anchor to Aid People Copying Link Address Us
107... 108...Within Editor Files, 0704081
......................................................... 109... 110...Milg Emply T Bill Function Special Subject/File
111...0000 00012 0 00040 01070300 00000000 03 00050 10 30 08 CGKG KCHFC
112...0000 00012 0 00040 01070300 00000000 03 00050 10 30 08 CGKG KCHJ5HD
113...0000 00012 0 00040 01070300 00000000 03 00050 10 30 08 CGKG KCHJ5HJ
114...0000 00012 0 00040 01070300 00000000 03 00050 10 30 08 CGKG KCHJD
115...0000 00012 0 00040 01070300 00000000 03 00050 10 30 08 CGKG KCHJE
116...0000 00012 0 00040 01070300 00000000 03 00050 10 30 08 CGKG KKGFC
117...0000 00012 0 00040 01070300 00000000 03 00050 10 30 EFC
118...0000 00012 0 00040 01070300 00000000 03 00050 10 30 GPKHG 020320a
119...0000 00012 0 00040 01070300 00000000 03 00050 10 EC 020320a
120...NAME="L28>Anchors Cause Line Spacing Problem Used with Outline and DIR Commands
121...Dots Vertical Spacing Problem Correction Remove P Commands and BR C
122... 123... 124... ......................................................... 125...0122 Links from Anchors in Correspondence and Other Documents

126...ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
127...Follow up ref SDS 4 QS3E
......................................................... 128...Line 250, ref OF 2 R95O, -label anLP0

......................................................... 129... 130...Line 230, ref OF 2 RQ5I, -label npcL
......................................................... .....Move para commands in publications that occurs in new articles to

.....column 1 and on their own separate line.
......................................................... .....Publications typically have para commands in lower case, and in

.....the middle of lines because they are created with a wordprocessor
.....that simply slips in the para command to substitute for whatever
.....code is used for creating a para. We need to put this stuff on
.....col 1, so we can add anchors.
......................................................... 131... ......................................................... 132...Line 470, ref OF 2 JS9K, -label anLP1 about 70 lines below.

......................................................... .....We need code to jump a number of lines to avoid putting in

.....anchors.
......................................................... .....Created special flag to do this...

......................................................... ..........jf jump from

..........jt jump to
......................................................... 133... .....Created error message if someone enters one, but not the other.
......................................................... 134... ......................................................... 135...Line 1320, ref OF 2 K48I, -label LstsR

......................................................... ....Outline code formatting begins here.

......................................................... 136... 137...Line 1430, ref OF 2 Q44N, -label ulok
......................................................... ....This is where code is entered for ordered and unordered lists, OL

....and UL.
......................................................... ....We have been adding a line so there is a blank above the OL and UL

....commands, however, this tends to compound the vertical spacing when
....the double dot code is added, so at this location today, we are
....eliminating this add line command, hoping it avoids the compound
....vertical spacing problem.
......................................................... 138... 139...Line 1590, ref OF 2 8X6I, -label nmblt1
......................................................... ....Outline code ends here so also avoid entering an extra space, and

....use the outline code ol ul to create a space for the next para,
....i.e., eliminate a blank space where a para command might be
....entered.
......................................................... 140... ......................................................... 141...Address Add BR Commands, Remove the Last BR So Explicit Links Work

142...ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
143...Line 1780, ref OF 2 EV9G, -label adrslp in 0122 about 30 lines below.
......................................................... ......This is where subroutine ends for adding BR commands to the end

......of each address line. At this point, the last BR command is
......removed, so that BR command added for explicit links will place
......the link on the line between the bottom of the address block and
......the Subject line.
......................................................... 144... 145...Line 3340, ref OF 2 LS6F, -label breol in 0122 this is the subroutine
146...that adds BR commands at end of each address line, so the lines will
147...stack up, and add savescr 8 to identify the last BR location, so it
148...can be removed.
......................................................... 149... ......................................................... 150... 151...Explicit Links 2 Dots Above Every Anchor
152...ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
153...Line 2210, ref OF 2 1363, -label nfC this code converts SDS anchor
154...formats into HTML, per work on 990507.
......................................................... 155... 156...Line 2620, ref OF 2 2Q4F, -label caanc
......................................................... ....Added code to enter links using two dots above every anchor.

......................................................... 157... ....In order to get the anchor to appear above the link, you have to
....use BR commands, and this adds an extra line, unless the P command
....is removed above.
......................................................... 158... ....As a result, the code in 0122 now enters P commands, and then
....removes them for every anchor, which now is every paragraph.
......................................................... 159... ......................................................... ....Vertical Line Spacing Compounded by 2 Dots Convention

....ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
....There are several conditions that need special treatment....
......................................................... .............a...Lists...... ol

.............b...Indent..... dir
.............c...Center..... center
......................................................... 160... ....There is no evident solution for starting a list that will put the
....double dots in the space between the start of the list and the line
....above. If we use P or BR we get extra lines that we don't want, and
....if leave them out, then doubld dots occur at the end of the para
....above.
......................................................... 161... ....Therefore the only solution for rendering double dots that start a
....list is put them at the beginning of the last sentence in a
....paragraph above these alignment commants. This uses the anchor
....above the 1st item in a list by reference based on proximity.
......................................................... 162... ....Once the list command is underway, then the thing seems to work
....normally, until the alignment command ends.
......................................................... 163... ......................................................... 164...Line 2670, ref OF 2 WL7O, -label lafaa

......................................................... ....To manage this vertical line spacing problem caused by adding

....double dots to alignment commands created following conventions....
......................................................... 165... ....This is where the code evaluates if an anchor occurs.
......................................................... ........We create a new flag here if an OL or UL command occurs, so

........when code for explicit double dots is entered, it can omit the
........first BR command.
......................................................... 166... 167...Line 2760, ref OF 2 US6O, -label caanc about 70 lines below.
......................................................... ....This is where code for double dots explicit links is entered, and

....if counter 55 = 47, then omit the first BR to avoid compound
....vertical spacing on outline code.
......................................................... 168... ........Need code for suppressing adding anchors every 6 lines because
........the new code today messes up formatting for indented material
........surrounding ol and dir commands.
......................................................... 169... ........If we put anchors where there is no formatting problem that is
........good enough.
......................................................... 170... ........Decided to use...
......................................................... ...............{! n. or {! no anchor

......................................................... 171... ........They mean the same, since the code only reads to the "n"
......................................................... 172... ......................................................... 173... ......................................................... 174... ......................................................... 175... ......................................................... 176... ......................................................... 177... ......................................................... 178... 179...
CONTACTS 

SUBJECTS
Explicit Links Created During Conversion by 070405
Addressability Copy Location on Internet for Linking
Links References Connections Citations Traceability to Original Sourc
Development SDS Link Copy Anchor Feature Using Code for Purple Number
Purple Numbers Addressability Copy Location on Internet for Linking
Links to Anchors to Aid Adderssability for Copying that Aids Linking
Concept Objectives

1209 -
1209 -    ..
1210 - Summary/Objective
1211 -
121101 - Follow up ref SDS 17 0000, ref SDS 16 0000.
121102 -
121103 - Improved SDS to make it a little easier for people to cite the record
121104 - by copying an explicit link address from within SDS records.  Decided
121105 - to place explicit links on the line above anchors and use two dots for
121106 - showing where anchors are located. ref SDS 0 543J  People can copy the
121107 - link, or click the link and copy the address from the location bar to
121108 - create links that apply granualar addressability.  This has another
121109 - big advantage of making anchors for headings stable, since anchors in
121110 - the record are constant. ref SDS 0 XT6H  There is a slight improvement
121111 - in appearance of the record by better positioning of headings as a
121112 - result of the anchor being on the line above the heading. ref SDS 0
121113 - F24O  Creating this feature to aid others in using SDS addressability
121114 - required changing the SDS save function to add anchors automatically
121115 - to all headings and to every para within 15 lines. ref SDS 0 QP4G and
121116 - at ref SDS 0 K33N  So, now we add anchors when and where we need them
121117 - for analysis and alignment, and anchors are added automatically to
121118 - help others with their work, so it is a little faster and easier for
121119 - people to use "intelligence" on the Internet for growing a culture of
121120 - knowledge.
121122 -      ..
121123 -     [...in another record notified Gary of this solution. ref SDS 21
121124 -     0001
121126 -      ..
121127 -     [On 020325 Gary comments favorably on SDS explicit links.
121128 -     ref SDS 22 XQ4M
121130 -      ..
121131 -     [On 020530 Eric Armstrong feels people will use SDS to benefit
121132 -     from organizational memory. ref SDS 23 Y89F
121134 -      ..
121135 -     [On 020726 using addressability by clicking on explicit links, and
121136 -     by communicating with explicit links saves a lot of time and money
121137 -     and only takes a second. ref SDS 24 U26H
121139 -      ..
121140 -     [On 030102 eliminated feature created today because addressability
121141 -     was integrated into Alt F9 justify op in macro 49 ref SDS 28 NY4O
121143 -      ..
121144 -     [On 030121 added feature the "save" function to add explicit links
121145 -     on every paragraph in an SDS record, similar to the way editor
121146 -     files are processed by 0122. ref SDS 29 0001
121148 -      ..
121149 -     [On 030528 Mark demonstrates people can learn to use explicit
121150 -     links when sufficiently motivated. ref SDS 30 0001
121151 -
121152 -
121153 -
121155 -  ..
1212 -
1213 -
1214 - Evaluation
1215 -
121501 - Code created today for adding anchors automatically to SDS records
121502 - saves keystrokes in the approximate amount reported for developing the
121503 - same feature for documents using 0122, a few years ago on 000810.
121504 - ref SDS 4 4I6K
121506 -  ..
121507 - In fact there are typically 10 times number of anchors and links in a
121508 - typical SDS record than in a document, so the estimate for reducing
121509 - keystrokes and saving time can be conservatively adjusted as
121510 - follows...
121511 -
121512 -            2  x   800    =   1,600 keystrokes
121514 -             ..
121515 -            2  x  1600    =   3,200 seconds     say  50 minutes.
121516 -
121517 -
121518 -
121520 -  ..
1216 -
1217 -
1218 - Planning
1219 -
121901 - Explicit Links Enable Copy Link Address on Internet
121902 -
121903 - On 000824 consolidating commands to reduce keystrokes by integrating
121904 - functions saves time and money. ref SDS 6 0001
121905 -
121906 - On 020106 Gary explained difficulty preparing correspondence and
121907 - analysis linked to SDS records and to Welch publications...
121909 -          ..
121910 -         POIMS................................. ref OF 8 6221
121911 -         Typical Day Scenario.................. ref OF 9 0001
121912 -         NWO................................... ref OF 10 0001
121913 -
121914 - ...because these materials do not have explicit links to internal
121915 - anchors that can be copied with a browser feature that copies a link
121916 - address at the location of the pointer. ref SDS 18 W69L  At that time,
121917 - procedures were explained for capturing a link address in about 10
121918 - seconds. ref SDS 18 YO5J
121919 -
121920 -     [On 020726 using addressability by clicking on explicit links, and
121921 -     by communicating with explicit links saves a lot of time and money
121922 -     and only takes a second. ref SDS 24 U26H
121924 -      ..
121925 -     [On 030101 Moore's law saving time and money is doubled by
121926 -     integrating commands to combine tasks that reduce keystrokes.
121927 -     ref SDS 27 PM53
121929 -      ..
121930 -     [On 030121 made addressability faster and easier to create by
121931 -     integrating with F2 save in 0702051. ref SDS 29 AO4M
121933 -  ..
121934 - On 020213 Gary submitted correspondence linked to the SDS record and
121935 - to POIMS, showing progress and determination to contribute in building
121936 - a culture of knowledge, as shown by the history listed in the record
121937 - on 020213. ref SDS 19 DW9I
121939 -  ..
121940 - On 020313 Gary submitted examples of SDS records where he used a
121941 - feature developed by Eugene Kim for implementing Doug Engelbart's
121942 - process of putting redundant links at the end of a paragraph to the
121943 - beginning of a paragraph.  Eugene calls this purple numbers.  Gary
121944 - created an implementation of purple numbers for SDS. ref SDS 20 6F8N
121945 - Generally this makes it easier for people to link records in
121946 - correspondence because a feature of Netscape and IE web browsers for
121947 - copying a link address can be used to avoid having to type out the
121948 - address.
121949 -
121950 -
121952 -  ..
121953 - Explicit Links Required for Microsoft Programs Intelligence Support
121954 -
121955 - SDS enables people to use anchors for linking without redundancy of an
121956 - explicit link, and if Microsoft and Netscape added a copy link feature
121957 - that reads anchors, instead of only links, that would eliminate the
121958 - need for adding a lot of explicit links to the record that will mostly
121959 - go unused, as related in analysis on 020313. ref SDS 20 HX7N  However,
121960 - there does not seem to be a great ground swell of support to guide
121961 - Microsoft through focus groups and lawsuits toward better product
121962 - design.
121964 -  ..
121965 - Explicit links present two issues...
121966 -
121967 -     1.  Correspondence and other documents.
121968 -
121969 -         These files already have anchors added to every para when
121970 -         converted to HTML, created a few years ago on 000810.
121971 -         ref SDS 4 RD05
121973 -          ..
121974 -         Add feature that puts anchors on the blank line that separates
121975 -         paragraphs when a record is converted to HTML format using
121976 -         0122. ref SDS 0 OS7J
121978 -          ..
121979 -     2.  SDS Records
121980 -
121981 -         Anchors are currently created automatically for headings and
121982 -         can be created as needed to build connections for Knowledge
121983 -         Space.
121985 -          ..
121986 -         The issue now is to facilitate other people capturing a link
121987 -         for granular addressability, as demonstrated by the records
121988 -         Gary Johnson submitted on 020313 that apply functionality
121989 -         developed by Eugene Kim for adding links to email, called
121990 -         Purple Numbers. ref SDS 20 6F8N
121992 -          ..
121993 -         This entails adding a feature to put anchors everywhere
121994 -         somebody might want to address, similar to what was done for
121995 -         correspondence a few years ago on 000810. ref SDS 4 RD05
121996 -
121998 -  ..
121999 - There are two processes....
122000 -
122001 -     1.  Add anchors during save for SDS records.
122002 -
122003 -         Use code in 0122, ref OF 2 RQ5I, with some modifications and
122004 -         insert in 0702051 that archives pointers, rather than use
122005 -         macro 142 so that impact on compiler is minimized.
122007 -          ..
122008 -         Actually the code in 0122 doesn't work very well for SDS
122009 -         records, because there is a lot more structure in SDS records
122010 -         that needs special handling.
122012 -          ..
122013 -         With each save every underlined heading needs to be tested and
122014 -         every highlighted heading will be tested for anchors, and if
122015 -         there is no anchor, an anchor will be added above the heading.
122016 -         Additionally, if there is not an anchor within 15 lines, then
122017 -         one will be added to every para to increase addressability,
122018 -         explained further below. ref SDS 0 XP5L  This will result in
122019 -         anchors occurring in some inconvenient places, but it is very
122020 -         simple to fine tune appearance by re-positioning anchors.
122022 -          ..
122023 -         Explicit links have three advantages....
122024 -
122025 -           1.  Anchors will be stable.
122026 -
122027 -               This is a fairly big deal.  Up until now we have been
122028 -               creating sumary linked to specific headings in the
122029 -               record on the Internet by constructing an anchor based
122030 -               on the line number.  It turns out that line numbers
122031 -               change fairly frequently because we add or delete
122032 -               subjects and do other editing that changes line numbers.
122033 -               Practice has evolved for using email to reference people
122034 -               to SDS records.  If we later edit the record, these
122035 -               references can be incorrect, which happens quite often.
122036 -               Typically, we get a record partially done, and need to
122037 -               reference it in correspondence that requires or which
122038 -               there is a desire to make a response in order to capture
122039 -               current perspective.  As the record is subsequently
122040 -               edited, the link addresses used in the email are
122041 -               changed, with the result that when people use the link
122042 -               they are taken to the bottom of the record with an error
122043 -               message saying the link address is not present.  This
122044 -               can be avoided by using SDS to look up the anchor and
122045 -               use that in the email instead of the link in the Summary
122046 -               on the Internet, but this takes time and when time is
122047 -               short we either forget or there is not enough time with
122048 -               the result that readers are frustrated.
122050 -                ..
122051 -               The fix today that adds anchors above all headings and
122052 -               headlines enables changing the way that summaries are
122053 -               created for the Internet record.  Now the permenant
122054 -               anchor can be used, and this will be stable regardless
122055 -               of subsequent editing.
122057 -                ..
122058 -           2.  A single anchor will be used for a group of headings
122059 -               rather than separate anchors created for every heading
122060 -               in a group.  This will give people more context when
122061 -               using the Executive Summary on the Internet.  Up until
122062 -               now if there were 3 or 4 headings and someone clicked on
122063 -               description 3 or 4, then the stuff jumped to that line
122064 -               and hid the other lines, so this is a big improvement.
122066 -                ..
122067 -           3.  Headlines will occur below the anchor so they will
122068 -               display consistently.  Up until now, sometimes the
122069 -               target line which is a larger font is only partially
122070 -               displayed and so there is a distraction that requires
122071 -               scrolling the screen up to see the full description.
122073 -          ..
122074 -         This op will change the size of the file, but not much each
122075 -         pass, because save is used routinely and so each pass will add
122076 -         only a few anchors, and once a file is mature, save will
122077 -         rarely add anchors, because they will already be there.
122079 -          ..
122080 -         Existing files will be changed a lot during the first pass.
122082 -          ..
122083 -         Will add anchors every 15 lines, as explained further below.
122084 -         ref SDS 0 K33N
122086 -          ..
122087 -         Another idea is to make this a separate op and only run it
122088 -         when needed, say from the Diary menu, since we never put
122089 -         Schedule tasks on the Internet.
122091 -          ..
122092 -         The advantage of this is that Medit is beginning to get tired
122093 -         with all of the stuff we are doing now, and so this could
122094 -         cause memory to get fragmented causing program crash. Since we
122095 -         are doing this in a separate session, that helps. Will start
122096 -         by putting the anchor feature in 0702051 and see how that
122097 -         works on some large records.
122099 -          ..
122100 -         For now, decided to add this and see how well things hold up,
122101 -         and whether it induces a greater support for using connections
122102 -         that Doug requested in his letter on 001025. ref SDS 7 00VU
122104 -          ..
122105 -         The work is shown below in 0702051. ref SDS 0 0800
122107 -          ..
122108 -     2.  Add code in 070405 and in 0122 that convert SDS records and
122109 -         other files into HTML for publication, to add a redundant,
122110 -         explicit link to every anchor so it is faster and easier for
122111 -         people to create a connected web of traceability to original
122112 -         sources required by professional standards for good
122113 -         management, reviewed on 950721. ref SDS 1 1740  Internet to
122114 -         capture the link, even though so far hardly nobody has done
122115 -         this, because it takes about 10 seconds.  If we can reduce
122116 -         this to about 1 second, maybe we can encourage people to begin
122117 -         creating a connected record that saves time and money for
122118 -         everybody.
122120 -          ..
122121 -         It is a simple matter to create a link to an anchor and not
122122 -         put the anchor as a parameter of the command.  Then the link
122123 -         does not show up.  However, the anchor is not active either.
122125 -          ..
122126 -         We want to alert people about the existance of an anchor and
122127 -         make capturing the address fast and easy for creating a
122128 -         connected record, because lowering the level of effort for
122129 -         good management increases the number of people willing to make
122130 -         the effort.  At the same time, we want to avoid awkward steps
122131 -         and appearance that distract from the experience using the
122132 -         record day-to-day, i.e., we need a new feature that is useful
122133 -         but not burdensome.
122135 -          ..
122136 -         Will use two (2) dots above an anchor that fits between
122137 -         paragraphs.  This is unobtrusive, will not modify the existing
122138 -         structure, and provides a clear, obvious alert and easy
122139 -         technique for capturing an anchor to link back to original
122140 -         sources.  Below, this is created in 070405, ref SDS 0 I75L,
122141 -         and further in 0122. ref SDS 0 P69F
122142 -
122143 -             [On 081007 Morris proposes downward left arrowhead to
122144 -             replace double dots that identify explicit links.
122145 -             ref SDS 32 2U85
122146 -
122147 -
122148 -
122149 -
1222 -

SUBJECTS
Default Null Subject Account for Blank Record

1303 -
130401 -          ..
130402 -         Onmouseover, Onmouseclick Possible Application
130403 -
130404 -         Onmouseover is an HTML feature to avoid having the link show
130405 -         up, per the letter to W3C on 020313. ref SDS 20 R14J
130406 -
130407 -             The record on 991231 has some links to W3C showing HTML
130408 -             coding. ref SDS 3 2166
130410 -              ..
130411 -             Received ref DRT 1 0001 from Dave Ragget responding to my
130412 -             letter on 020313, ref SDS 20 R14J, explaining that
130413 -             onmouseover cannot be used with p command but could be
130414 -             used with css. ref DRT 1 FQ6O
130416 -          ..
130417 -         There is a resource showing how onmouseover is used with
130418 -         anchor command at....
130419 -
130420 -            http://www.geocities.com/ResearchTriangle/1500/mouseovr.html
130422 -          ..
130423 -         Onmouseover is an attribute of HTML shown in W3C
130424 -
130425 -
130426 -            http://www.w3.org/TR/1999/REC-html401-19991224/index/attributes.html
130427 -
130428 -         ....about 67% down the page listed alphabetically in a table.
130430 -              ..
130431 -             It seems to work only with a script that must be first
130432 -             defined then applied.
130434 -              ..
130435 -             Another source is....
130436 -
130437 -              http://builder.cnet.com/webbuilding/pages/Programming/Kahn/012898/
130439 -          ..
130440 -         Looks like onmouseover is used a lot with images, but in this
130441 -         case, we want to use it for a link, so that the link does not
130442 -         appear on the screen; and we want to execute the link or at
130443 -         least be able to copy the link address, per planning on
130444 -         020313. ref SDS 20 HX7N
130445 -
130446 -             [On 020325 Gary Johnson indicates onmouseover application
130447 -             is not a direct solution. ref SDS 22 1J8H
130449 -          ..
130450 -         Another thing to try is to up a dot or two dots above an
130451 -         anchor, and use that to copy the link address.
130453 -          ..
130454 -         This is an interim solution that avoids the clutter of an
130455 -         extraneous anchor.
130456 -
130457 -             [On 020325 Gary Johnson indicates 2 dots scheme is
130458 -             effective. ref SDS 22 3E4L and ref SDS 22 WM9I
130459 -
130460 -
130461 -
130462 -
130463 -
1305 -

SUBJECTS
Save, Primary, F2, macro 142, 0702051
Save Anchors Add to All Para in SDS record During Save, F2 macro 142,

1504 -
150501 -  ..
150502 - 000008  Macro 142 Save Function
150503 -
150504 - Line 2390, ref OF 6 4240, -entry 142 saves SDS records.
150506 -  ..
150507 - Line 2450, ref OF 6 1937, -entry 142 about 100 lines below.
150508 -
150509 -      Calls 0702051 to archive pointers and updated references.
150510 -
150512 -  ..
150513 - Save F2 Add Anchors to Para and Headings Automatically
150514 - 0702051  Save Function Add Anchors to All Para and Headings
150515 -
150516 - Follow up ref SDS 17 0800, ref SDS 10 0800.
150517 -
150518 - Line 440, ref OF 3 3504, -label bRArc about 30 lines below.
150520 -      ..
150521 -     Decided to put the default anchor 0001 above Summary/Objective and
150522 -     will use this for the summary created by 070402 so that
150523 -     Summary/Objective is displayed consistently to identify the
150524 -     narrative.  Previously, we have linked to the 0001 anchor on the
150525 -     Follow up line that is below Summary Objective.  This will
150526 -     improve appearance slightly.
150528 -  ..
150529 - Line 490, ref OF 3 V84N, -label 1spc
150530 -
150531 -     Actually, changed the design.  Will leave default anchor 0001 on
150532 -     the 01 Follow up line, because this has utilty for quickly linking
150533 -     stuff.  Instead, will use 0702051 to transfer anchor from Follow
150534 -     up line to above Summary/Objective to improve display during
150535 -     conversion to HTML, per below. ref SDS 0 596O
150537 -      ..
150538 -     Added code that makes 0001 default on Follow up line, and makes
150539 -     first indented description Summary/Objective.
150541 -      ..
150542 -     On 000811 code for creating anchors was developed. ref SDS 5 2120
150544 -      ..
150545 -     The basic operation is to put the cursor on column 9 which is the
150546 -     blank beyond the - in the line number and look for a line that is
150547 -     not blank based on the length being longer than 9 positions. Then
150548 -     test line to see if it already has an anchor, and if not then if
150549 -     it has a capital letter and is more than 15 lines below another
150550 -     line with an anchor, then put an anchor on the line.
150551 -
150553 -  ..
150554 - Underlined Headings within 6 Lines
150555 -
150556 - Line 510, ref OF 3 QH6J, -label hdgLp1
150557 -
150558 -     Decided to add anchors to all underlined headings.  This code will
150559 -     check and make sure every group of underlined headings has an
150560 -     anchor at the top.
150562 -  ..
150563 - Line 540, ref OF 3 2L5K, -label ancHe
150564 -
150565 -     Add anchors to all heading lines, but allow anchors to be within
150566 -     6 lines of top description line, so that anchors can be above
150567 -     indented headings for context.
150568 -
150570 -  ..
150571 - Follow Up Blank Line Below Uniform Format
150572 -
150573 - Line 690, ref OF 3 R44K, -label blbfu
150574 -
150575 -     Put a blank line below all Follow up r..  SDS... lines.  We need a
150576 -     blank line because the 004 routine that makes a new record and
150577 -     creates links back to the original source, expects a blank line,
150578 -     and because a blank line gives a good visual appearance to
150579 -     distinguish Follow up lines as a control and access element.
150581 -          ..
150582 -         [On 021012 this came up with a new user. ref SDS 25 HH52
150584 -      ..
150585 -     One problem with forcing this blank line is that a user who does
150586 -     not expect this, will be startled, may try to restore it, then get
150587 -     frustrated when a desired format is not accomplished.  Out of
150588 -     millions of potential users, some will want to avoid the blank
150589 -     line to conserve space or something.  That was the original
150590 -     design of SDS, but experience eventually showed that blank lines
150591 -     are a useful visual aid.
150593 -      ..
150594 -     This seems to work and does not add any appreciable time to the
150595 -     save operation.
150596 -
150598 -  ..
150599 - Highlighted Headlines - J Within 10 Lines
150600 -
150601 - Line 620, ref OF 3 AE3I, -label ancjH
150602 -
150603 -     Put anchors within 10 lines of highlighted headlines marked with
150604 -     the j flag.
150605 -
150607 -  ..
150608 - Lists with Multiple Dots Put Anchors Above List and Jump to Bottom
150609 -
150610 - Line 590, ref OF 3 R24N, -label dots
150611 -
150612 -     Add anchors above lists of stuff identified by
150613 -
150614 -            This is a list................. 904034,
150616 -      ..
150617 -     Need this so para command does not justify a list.
150618 -
150619 -         [On 030102 eliminated this feature because added
150620 -         addressability to Alt F9 justify op in macro 49 ref SDS 28
150621 -         5H6M
150623 -      ..
150624 -     To avoid this we add an anchor above the list, if there is not an
150625 -     anchor within 10 lines of the top of the list. ref OF 3 C37O
150627 -      ..
150628 -     Have to distinguish between a list string and place holders in
150629 -     ordinary text.
150630 -     ..
150631 -     Want the anchor to be on the blank line above the para above
150632 -     the list, and in column 10, so we simplify the thing, and leave it
150633 -     to the User to move the anchor if this is desirable.
150635 -  ..
150636 - Line 710, ref OF 3 416M, -label tolea
150637 -
150638 -     Call macro 987 in 000007 to enter and anchor and do not justify,
150639 -     because it is too complicated to account for all conditions when
150640 -     justify might mess things up.
150641 -
150642 -     Call macro 21 to return to the top of the list, and then jump to
150643 -     the bottom of the list to continue processing.
150644 -
150645 -
150647 -  ..
150648 - Paragraphs Get Anchors within 15 Lines Only on Capital Letters
150649 -
150650 - Line 740, ref OF 3 SD5G, -label ancHg
150651 -
150652 -     Begin process of entering anchors on (most) all para.
150654 -  ..
150655 - Line 810, ref OF 3 9G5N, -label ancT
150656 -
150657 -     Put anchors only on capital letters.
150659 -          ..
150660 -         [On 030102 eliminated this feature because added
150661 -         addressability to Alt F9 justify op in macro 49 ref SDS 28
150662 -         NY4O
150663 -
150665 -      ..
150666 -     Anchors on Paragraphs Within 30 Columns Avoid Labels
150667 -     Left Margin Located with Macro 541 Anchors Only within 30 Columns
150668 -
150670 -  ..
150671 - Line 890, ref OF 3 K27O, -label flM
150672 -
150673 -     Use macro 541 to find the left margin, which is in 000002 about
150674 -     line 820. ref OF 5 VT4I,
150675 -
150676 -         [On 030102 eliminated this feature because added
150677 -         addressability to Alt F9 justify op in macro 49 ref SDS 28
150678 -         NY4O
150680 -      ..
150681 -     Need new flag setcnt 28 937 for macro 541 in 000002 below -label
150682 -     jAW which is called to find the left margin for entering an
150683 -     anchor.  Want this function to exit without setting the margins,
150684 -     since it gives an error message when the left margin is less than
150685 -     20 positions of right margin, and this occurs in SDS records when
150686 -     underlined text and similar elements occur.  The code in 0702051
150687 -     is wired to omit anchors beyond col 5, but the code in macro 541
150688 -     returns an error message for before this occurs that stops
150689 -     processing, so this new flag exits before the error message is
150690 -     processed in macro 541.
150692 -  ..
150693 - Line 890, ref OF 3 0H4O, -label flM
150694 -
150695 -     Put anchors only within first 30 columns.
150696 -
150697 -          Counter 4 captures left margin in macro 541 in 000002 about
150698 -          line 2000, ref OF 5 GG5M, below -label jAW
150699 -
150701 -      ..
150702 -     Control Fields Excluded from Anchor Process
150703 -
150705 -  ..
150706 - Line 860, ref OF 3 NN3G, -label ancE
150707 -
150708 -     Jump control fields to speed things up.
150709 -
150710 -         [On 030102 eliminated this feature because added
150711 -         addressability to Alt F9 justify op in macro 49 ref SDS 28
150712 -         NY4O
150713 -
150715 -      ..
150716 -     Anchors Every 15 Lines
150717 -
150719 -  ..
150720 - Line 920, ref OF 3 XX3J, -label ancA
150721 -
150722 -     Enter anchors every 15 lines.
150723 -
150724 -         [On 030102 eliminated this feature because added
150725 -         addressability to Alt F9 justify op in macro 49 ref SDS 28
150726 -         NY4O
150727 -
150729 -      ..
150730 -     Indented Headings in Line Numbers
150731 -
150733 -  ..
150734 - Line 940, ref OF 3 RW5I, -label lpinD
150735 -
150736 -     Put anchors on line above an indented label, like "Progress"
150737 -
150738 -         [On 030102 eliminated this feature because added
150739 -         addressability to Alt F9 justify op in macro 49 ref SDS 28
150740 -         NY4O
150741 -
150743 -      ..
150744 -     Justify Para with Anchors
150745 -
150747 -  ..
150748 - Line 970, ref OF 3 1H4L, -label ancA
150749 -
150750 -     Call macro 49 to justify para after entering an anchor.
150752 -  ..
150753 - Line 990, ref OF 3 0W8H, -label ancA
150754 -
150755 -     Use split then macro 987 in 000006 to enter the anchor, then use
150756 -     join and macro 49 to assemble the para with the anchor justified
150757 -     within margins.
150758 -
150759 -         [On 030102 eliminated this feature because added
150760 -         addressability to Alt F9 justify op in macro 49 ref SDS 28
150761 -         NY4O
150762 -
150763 -
150765 -  ..
150766 - Headlines Without Underlines Get Anchors
150767 -
1508 - =============================
150801 - Line 670, ref OF 3 FN4M, -label ancJ
150802 -
150803 -     Want to add anchors above all j line headings that do not have
150804 -     underlines.
150805 -     ..
150806 -     These anchors should be a few lines above the j line
150807 -     heading, so that links will make the heading line clearly visible.
150809 -      ..
150810 -     This op is done last so that the prior two will typically have
150811 -     created anchors which are adequate for j lines.
150813 -      ..
150814 -     All anchors will be on column 10 on a blank line two lines above
150815 -     the target j line. In many cases this will be a mess, but it will
150816 -     be easy to fix visually.
150817 -
150819 -  ..
1509 -
1510 - Save, Primary, F2, macro 142, 0702051
1511 - Verify Anchors are Unique
151101 -
1512 -

SUBJECTS

===================================
-
-
                              ..
- /U>

- Verify Anchors are Unique
-

160401 - Line 1220, ref OF 3 OX5K, -label ancRe in 0702051
160402 -
Develop code to verify every anchor in the record is unique.  Use
160404 -    ref SDS 4 K4E1
160406 -     ..
160407 -    We need this mostly when some lines are copied or repeated to
160408 -     ..
160411 -    The code starts at the top and looks for anchors.  It gets the
160412 -     ..
160415 -    Setup F2 to re-start 0702051 to complete processing after the user
160416 -     ..
160419 -    F1 is assigned to give another error message telling the user to
160420 -    deal.  There may be a tendency for the user to want to press F1 F1
160422 -    Changing just one or at most two characters to anything will make
160424 -    is a simple solution to an important requirement for anchors to be
160426 -    160428 -
160429 -
160432 -
160433 -
160435 -  ..
L085P>1605 - Numbered Items
030601 -
SUBJECTS
Link to Anchors so People Can Copy to Internet Address
 ..
                                      to Ai  Copying Internet Address
190503 -
ref SDS 2
190505 -  ..
190508 - The improvements above that ensure anchors on all para and headings
190509 - 190511 -     1.  Making links in Summary to anchors above headings, so they
190512 -          ..
190515 -         Currently the link in the summary goes to the heading line,
190516 -         not visible, which is distracting.  Putting the anchor above
190518 -         problem.
190521 -          ..
190522 -     Multiple headlines can now use the same anchor, because there
190523 -         requires a new design for selecting only the anchor above all
190525 -         link in the Summary to every line in a multi-headline list.
190527 -         were added today, per above. ref SDS 0 VP6F
190530 -          ..
190531 -         Action items will retain the original design in order to
190532 -         the middle of a paragraph.  The anchor is above the para in
190534 -         of constructing an anchor at the action item line for display
190536 -         often, and so it might be ignored in conforming action item
190538 -         the majority of action items, since now every para gets an
190540 -         will have an anchor on the line above.  Will work with this
190542 -         190544h-             [On 040212 Gary Johnson asked about the format for linking
190545 -             ref SDS 31 6G5L
190547 -          ..
190548 -     Add link with a dot above all headings that enable people to
190549 -          ..
190552 -         Would like to use onmouseover or something similar, but for
190553 -          ..
LRX67>190557 - Line 220, ref OF 4 NF3O, -label nPrg
190558 -
 ..
190562 - Line 280, ref OF 4 5G9O, -label nPrg
190563 -
this if it is missing and deletes extraneous Summary/Objective
190566 -    every record, per above. ref SDS 0 0800
190569 -  ..
190570 - Line 300, ref OF 4 XN5L, -label nPrg about 90 lines below
190571 -
to above Summary/Objective, and create a blank line above default
190574 -    for entering HTML code for the font. per below. ref SDS 0 AU7R
190576 -
190578 -  ..
LFX7K>190579 - Line 360, ref OF 4 1407, -label cOMMn
190580 -
 ..
190584 - Line 450, ref OF 4 JX6H, -label hdLC
190585 -
deleting the Summary/Objective line.  Changed this so we include
190588 -    190590 -    Actually, want to transfer 0001 anchor from 01 line where Follow
190591 -    better.
190593 -
190595 -  ..
L6I7L>190596 - Line 1035, ref OF 4 1653, -label lp1, this is the loop that links the
190597 -  ..
190600 - Line 1270, ref OF 4 ZN8I, -label lp1
190601 -
line number.
190604 -
 ..
190608 - Line 1650, ref OF 4 QX6K, -label bslist
190609 -
need a line for the default anchor, and a line above that for the
190612 -    ref SDS 0 AY3L
190613 -
190615 -  ..
LRY86>190616 - Line 1840, ref OF 4 4411, -label lpcn1
190617 -
 ..
LKX8F>190622 - Line 2300, ref OF 4 NS5O, -label lnk1
190623 -
190626 -    At this point the code has captured all heading lines and put them
190627 -    summary to the corresponding heading line.
190629 -        ..
190630 -        Today, we are going to change this by making multiple
90631 -        headings for the same body of stuff refer to a common anchor
190632 -        per explanation above. ref SDS 0 0800 and ref SDS 0 JY4M
190635 -     ..
190636 -    Notice that the first summary heading is blank, so this indicates
190637 -    which needs to be changed.  Did this above. ref SDS 0 FX7K
190640 -     ..
190642 -     ..
190643 -    Macro 1182 captures the line number which is used to find the
190644 -     ..
LD29J>190648 - Line 2230, ref OF 4 T15F, -label nAI11
190649 -
description.
190653 -  ..
190654 - Line 2420, ref OF 4 P53M, -label eol3 about 30 lines below
190655 -
the summary line as a parameter to find the corresponding heading
190658 -     ..
190661 - Line 2440, ref OF 4 1E5N,
190662 -
 ..
190666 - Line 2580, ref OF 4 LD5K, -label fAnC
190667 -
found within 6 lines of the heading, then use that anchor for the
190670 -     ..
LRZ44>190674 - Line 2640, ref OF 4 1E5N, -label AIanc
190675 -
using the line number, which is the original design.
190678 -
assigned by the user.
190681 -    ..
190682 -    When 11=2 the action items are being processed.  Since these
7F>190683 -    are transitory, the code will use line numbers to construct an
190684 -    190686 -
190688 -  ..
190689 - 2 Dots Addressability Anchors with Visibility of Redundant Links
190690 - 190692 - Line 2440, ref OF 4 ZN9M, -label lpcar
190693 -
 ..
190697 - Line 2520, ref OF 4 WS3O, -label carot
190698 -
 ..
190702 - Line 2580, ref OF 4 648M, -label carot about 50 lines below
190703 -
symbol to let folks know there is an anchor that can be captured.
190707 -  ..
190708 - Line 2600, ref OF 4 AT5K, -label enLnk in 070405
190709 -
macro 1181
190712 -
with macro 1361 that starts at 1 with the HTML symbol <, and we
190715 -        ..
190718 - Line 2620, ref OF 4 AT5K, -label enLnk
190719 -
190722 -       Start at 2, because 1 is the < symbol.
190724 -     ..
190725 -    macro 1181
190726 -    190728 -       Enter the anchor string, and then backup one position to put
190729 -       space between the end of the anchor.
190732 -     ..
190733 -    ins_text !">..</A>!
190734 -       ..
190735 -       End HTML and identify 2 dots so User can see the location
190736 -       of the anchor.
190737 -
 ..
190741 - Line 2640, ref OF 4 F84O, -label end
190742 -
file entered twice.
190745 -
 ..
190749 - Format Headings on Indented Lines
190750 -
ref OF 4 5076, -label Hdgx
190752 -
190754 -  ..
LR34N>190755 - Citations Format Links
190756 -
ref OF 4 4411, -label cites
190758 -
 ..
1908 -   
1909 - Anchor Para Received Docs with HTML, 000812
1911 - 2 Dots Links Above Every Anchor to Aid People Copying Link Address Us
1913 - Links Within Editor Files, 0704081
030601 -
0306 -

SUBJECTS
2 Dots Vertical Spacing Problem Correction Remove P Comm  ds and BR C
 ..
                                     sponde  e and Other Documents
280503 -
ref SDS 4 QS3E
280505 -
ref OF 2 R95O, -label anLP0
280508 -  ..
280509 - Line 230, ref OF 2 RQ5I, -label npcL
280510 -
column 1 and on their own separate line.
280513 -
the middle of lines because they are created with a wordprocessor
280516 -     code is used for creating a para.  We need to put this stuff on
280518 -      ..
LHI4M>280522 - Line 470, ref OF 2 JS9K, -label anLP1 about 70 lines below.
280523 -
anchors.
280526 -
280529 -          <! jf     jump from
280530 -           ..
280533 -     Created error message if someone enters one, but not the other.
280534 -
280536 -  ..
LPA94>280537 - Line 1320, ref OF 2 K48I, -label LstsR
280538 -
 ..
280542 - Line 1430, ref OF 2 Q44N, -label ulok
280543 -
and UL.
280546 -
commands, however, this tends to compound the vertical spacing when
280549 -    eliminating this add line command, hoping it avoids the compound
280551 -     ..
280554 - Line 1590, ref OF 2 8X6I, -label nmblt1
280555 -
use the outline code ol ul to create a space for the next para,
280558 -    entered.
280560 -
280562 -  ..
LLW9N>280563 - Address Add BR Commands, Remove the Last BR So Explicit Links Work
280564 -
ref OF 2 EV9G, -label adrslp in 0122 about 30 lines below.
280566 -
of each address line.  At this point, the last BR command is
280569 -      the link on the line between the bottom of the address block and
280571 -       ..
280574 - Line 3340, ref OF 2 LS6F, -label breol in 0122 this is the subroutine
280575 - stack up, and add savescr 8 to identify the last BR location, so it
280577 - 280579 -
280581 -  ..
280582 - Explicit Links 2 Dots Above Every Anchor
280583 -
ref OF 2 1363, -label nfC this code converts SDS anchor
280585 -  ..
280588 - Line 2620, ref OF 2 2Q4F, -label caanc
280589 -
 ..
280593 -    In order to get the anchor to appear above the link, you have to
280594 -    is removed above.
280597 -     ..
280598 -    As a result, the code in 0122 now enters P commands, and then
280599 -     ..
6O>280603 -    Vertical Line Spacing Compounded by 2 Dots Convention
280604 -
280607 -             a.  Lists...... ol
280608 -             c.  Center..... center
280611 -     ..
280612 -    There is no evident solution for starting a list that will put the
280613 -    above. If we use P or BR we get extra lines that we don't want, and
280615 -    above.
280618 -     ..
280619 -    Therefore the only solution for rendering double dots that start a
280620 -    paragraph above these alignment commants.  This uses the anchor
280622 -     ..
280625 -    Once the list command is underway, then the thing seems to work
280626 -     ..
LQ885>280630 - Line 2670, ref OF 2 WL7O, -label lafaa
280631 -
double dots to alignment commands created following conventions....
280635 -     ..
280636 -    This is where the code evaluates if an anchor occurs.
280637 -
when code for explicit double dots is entered, it can omit the
280640 -         ..
280643 - Line 2760, ref OF 2 US6O, -label caanc about 70 lines below.
280644 -
if counter 55 = 47, then omit the first BR to avoid compound
280647 -     ..
280650 -        Need code for suppressing adding anchors every 6 lines because
280651 -        surrounding ol and dir commands.
280654 -         ..
280655 -        If we put anchors where there is no formatting problem that is
280656 -         ..
280659 -        Decided to use...
280660 -
 ..
280664 -        They mean the same, since the code only reads to the "n"
280665 -
280668 -
280669 -
280672 -
280673 -
280676 -
280677 -