-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathManual.html
3014 lines (3014 loc) · 92.7 KB
/
Manual.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!-- Created by Bracy 0.4 on Monday, January 1, 2018 at 7:48 PM CST -->
<html>
<head>
<title>
The Bracy Manual
</title>
<style>
a:active
{ color: purple;
font-weight: bold;
text-decoration: none }
a:link
{ color: blue;
font-weight: bold;
text-decoration: none }
a:visited
{ color: purple;
font-weight: bold;
text-decoration: none }
hr
{ background-color: black;
border: none;
color: black;
height: 1px }
table
{ border-collapse: collapse }
</style>
</head>
<body bgcolor="#FFFFFF">
<a name="top">
</a>
<p align="center">
<b>The Bracy Manual</b>
<br />
<br />
James B. Moen
<br />
June 30, 2017
</p>
<p align="justify">
Copyright © 2017 James B. Moen. Permission is granted to copy,
distribute, and/or modify this document under the terms of the
G<small>NU</small> Free Documentation License, Version 1.3 or any later
version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the
license may be obtained at
<a href="http://fsf.org/">
<tt><http://fsf.org/>.</tt>
</a>
<br>
This manual uses special characters. Without
proper rendering support, you may see question marks, boxes, or other
symbols in place of these characters.
</p>
<hr />
<p align="center">
<b>Contents</b>
</p>
<table cellpadding="0" cellspacing="0">
<tr valign="top">
<td>
<p>
<a href="#introduction">
1.
</a>
</p>
</td>
<td>
<p>
Introduction.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#running">
2.
</a>
</p>
</td>
<td>
<p>
Running Bracy.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#syntax">
3.
</a>
</p>
</td>
<td>
<p>
Syntax.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
</p>
</td>
<td>
<table cellpadding="0" cellspacing="0">
<tr valign="top">
<td>
<p>
<a href="#styles">
3.1.
</a>
</p>
</td>
<td>
<p>
Styles.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#bbb">
3.2.
</a>
</p>
</td>
<td>
<p>
Braces, backslashes, and blanks.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#scopes">
3.3.
</a>
</p>
</td>
<td>
<p>
Scopes.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
</p>
</td>
<td>
<table cellpadding="0" cellspacing="0">
<tr valign="top">
<td>
<p>
<a href="#left">
3.3.1.
</a>
</p>
</td>
<td>
<p>
Left.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#right">
3.3.2.
</a>
</p>
</td>
<td>
<p>
Right.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#justify">
3.3.3.
</a>
</p>
</td>
<td>
<p>
Justify.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#center">
3.3.4.
</a>
</p>
</td>
<td>
<p>
Center.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#bullet">
3.3.5.
</a>
</p>
</td>
<td>
<p>
Bullet.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#column">
3.3.6.
</a>
</p>
</td>
<td>
<p>
Column.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#number">
3.3.7.
</a>
</p>
</td>
<td>
<p>
Number.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#itemize">
3.3.8.
</a>
</p>
</td>
<td>
<p>
Itemize.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#display">
3.3.9.
</a>
</p>
</td>
<td>
<p>
Display.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#indent">
3.3.10.
</a>
</p>
</td>
<td>
<p>
Indent.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#orson">
3.3.11.
</a>
</p>
</td>
<td>
<p>
Orson.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#over">
3.3.12.
</a>
</p>
</td>
<td>
<p>
Over.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#narrow">
3.3.13.
</a>
</p>
</td>
<td>
<p>
Narrow.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#comment">
3.3.14.
</a>
</p>
</td>
<td>
<p>
Comment.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#title">
3.3.15.
</a>
</p>
</td>
<td>
<p>
Title.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#goto">
3.3.16.
</a>
</p>
</td>
<td>
<p>
Goto.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#label">
3.3.17.
</a>
</p>
</td>
<td>
<p>
Label.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#image">
3.3.18.
</a>
</p>
</td>
<td>
<p>
Image.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#insert">
3.3.19.
</a>
</p>
</td>
<td>
<p>
Insert.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#table">
3.3.20.
</a>
</p>
</td>
<td>
<p>
Table.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#layout">
3.3.21.
</a>
</p>
</td>
<td>
<p>
Layout.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#rule">
3.3.22.
</a>
</p>
</td>
<td>
<p>
Rule.
</p>
</td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
<tr valign="top">
<td>
<p>
<a href="#references">
4.
</a>
</p>
</td>
<td>
<p>
References.
</p>
</td>
</tr>
<tr valign="top">
<td>
<p>
</p>
</td>
<td>
<p>
</p>
</td>
</tr>
</table>
<hr />
<a name="introduction">
</a>
<p>
<b>1. Introduction.</b>
</p>
<blockquote>
<p align="justify">
‘‘I never intended <small>HTML</small> source code (the
stuff with the angle brackets) to be seen by users...’’
</p>
<p align="right">
<a href="#ber2001">
[<small>BER</small> 2001]
</a>
</p>
</blockquote>
<p align="justify">
<i>Bracy</i> (pronounced <i>bray-see</i>) is a minimalist document
compiler. It makes <small>HTML</small>
<a href="#pow2001">
[<small>POW</small> 2001]
</a>
files that are supposed to look like printed pages when displayed by a web
browser. (The page you’re reading now was made by Bracy.) Most
browsers aren’t very good at rendering text, but Bracy tries as hard
as it can anyway. Bracy also tries to produce <small>HTML</small>
that’s nicely indented, so it’s readable by Humans (not just
programs). This is useful if you want to edit an <small>HTML</small>
file made by Bracy, but you don’t have Bracy, or you don’t have
the Bracy source that produced the <small>HTML</small> file, or both.
<br>
H<small>TML</small>’s syntax is
incredibly verbose and inconsistent: some features are implemented as tags,
others as attributes of tags, and still others as styles associated with
tags, all without apparent design principles. And despite claims to the
contrary, there is no standard <small>HTML</small>, since no two
browsers seem to agree on what <small>HTML</small>’s constructs
mean, or what subset of them should be implemented. As a result,
<small>HTML</small> is nearly useless to the programmer who wants his
or her code to work the same way on any computer. (Please
<i>don’t</i> write to say that <small>HTML</small> was
created by the gods and it’s a sin for me to criticize it, or any
similar nonsense.)
<br>
The important word in the previous paragraph
was <i>nearly.</i> H<small>TML</small> does seem to have a few
constructs that work almost the same way in all browsers. Bracy tries to use
these few constructs exclusively. It hides them behind a simpler notation so
you don’t have to see them, or even think about them. The good news,
then, is that Bracy is easier to use than <small>HTML</small>. The bad
news is that Bracy can’t do everything <small>HTML</small> can.
<br>
Bracy is written in the experimental
programming language <i>Orson</i>
<a href="#moe2017">
[<small>MOE</small> 2017],
</a>
which I designed and implemented. One reason I wrote Bracy is to find bugs
in my Orson compiler. I found lots of them. I also wanted a relatively
painless way to write Orson documentation in <small>HTML</small>. There
are mechanisms in Bracy to facilitate this, but you can still use Bracy even
if you don’t care about Orson.
</p>
<a name="running">
</a>
<p>
<b>2. Running Bracy.</b>
</p>
<p align="justify">
Bracy works under Unix-like operating systems, such as
G<small>NU</small>/Linux. This section assumes that Bracy is already
installed on your system.
<br>
To run Bracy, you must first make a file
containing Bracy source code, using your favorite text editor. (Bracy source
code will be described in the remainder of this manual.) The name of the
Bracy source file must end with the suffix ‘<tt>.by</tt>’.
<br>
Bracy source files use 31-bit characters,
encoded using <small>UTF</small>-8. This includes the familiar 21-bit
Unicode characters
<a href="#uni2006">
[<small>UNI</small> 2006]
</a>
and the 7-bit <small>ASCII</small> characters
<a href="#ans1986">
[<small>ANS</small> 1986]
</a>
as subsets. If you write source files on a Unix-like system in Unicode or in
<small>ASCII</small>, then you don’t need to care about this:
everything should work fine.
<br>
Suppose you have a Bracy source file called
<tt>Manual.by.</tt> You can translate it to <small>HTML</small> by
typing the command <tt>bracy</tt> <tt>Manual.by</tt> to the
Unix shell. Bracy then makes an object file called <tt>Manual.html</tt>
that contains <small>HTML</small> code. This file can be viewed with a
web browser. If your source file has syntax errors, then Bracy will also
print messages that tell you where the errors appear.
<br>
Bracy makes <small>HTML</small> object
files using <small>ASCII</small> characters exclusively. A character
not in <small>ASCII</small> is rendered as
‘<tt>&#</tt><i>d</i><tt>;</tt>’ where
<i>d</i> is a series of one or more digits, the character’s
decimal numeric code. For example, Bracy renders the character α (Greek
lower-case <i>alpha</i>) as ‘<tt>&#945;</tt>’.
Some browsers can’t display characters like these.
<br>
The <tt>bracy</tt> command has options
that are not discussed here. Type <tt>man</tt> <tt>bracy</tt>
to see what they are, and how to use them. You can also type
<tt>man</tt> <tt>ascii</tt> to find out more about the
<small>ASCII</small> character set. On many systems you can type
<tt>man</tt> <tt>unicode</tt> and
<tt>man</tt> <tt>utf-8</tt> to find out about Bracy’s
character encoding.
</p>
<a name="syntax">
</a>
<p>
<b>3. Syntax.</b>
</p>
<p align="justify">
Bracy’s syntax was inspired by that of the document compiler
S<small>CRIBE</small>
<a href="#rei1980">
[<small>REI</small> 1980].
</a>
The syntax has two parts. The first deals with <i>styles,</i> which
describe how characters will appear. The second deals with
<i>scopes,</i> most of which describe how text is rendered into
<small>HTML</small>.
</p>
<a name="styles">
</a>
<p>
<b>3.1. Styles.</b>
</p>
<p align="justify">
Bracy has ten character styles. They were chosen partly for their potential
usefulness, and partly because they are likely to be supported by all web
browsers
<a href="#pow2001">
[<small>POW</small> 2001].
</a>
Each style is written as
<tt>{</tt><i>style</i> <i>text</i><tt>}</tt>, where
<i>style</i> is a series of one or more characters that tells what
style you want, and <i>text</i> is the text that you want to appear in
that style.
</p>
<ul>
<li>
<p align="justify">
<tt>{b Abc}</tt> gives you <b>Abc</b> in boldface.
</p>
<li>
<p align="justify">
<tt>{c Abc}</tt> gives you A<small>BC</small> in small capitals.
</p>
<li>
<p align="justify">
<tt>{i Abc}</tt> gives you <i>Abc</i> in italics.
</p>
<li>
<p align="justify">
<tt>{g Abc}</tt> gives you <font color="#A9A9A9">Abc</font> in
gray.
</p>
<li>
<p align="justify">
<tt>{s Abc}</tt> gives you <strike>Abc</strike> struck through.
</p>
<li>
<p align="justify">
<tt>{t Abc}</tt> gives you <tt>Abc</tt> in typescript.
</p>
<li>
<p align="justify">
<tt>{u Abc}</tt> gives you <u>Abc</u> underlined.
</p>
<li>
<p align="justify">
<tt>{+ Abc}</tt> gives you <sup>Abc</sup> in superscript.
</p>
<li>
<p align="justify">
<tt>{- Abc}</tt> gives you <sub>Abc</sub> in subscript.
</p>
<li>
<p align="justify">
<tt>{- Abc {= Ez}}</tt> gives you <sub>Abc
<sub>Ez</sub></sub> in subscript and sub-subscript.
</p>
</ul>
<p align="justify">
Bracy simulates the small capitals style by using upper case letters in a
reduced size. Also, underlined words displayed with
‘<tt>u</tt>’ are not links, and must not be confused with
them.
<br>
Character styles can be nested, so that
<tt>{b</tt> <tt>{i</tt> <tt>Abc}}</tt> gives you
<b><i>Abc</i></b> in boldface italic. Similarly,
<tt>{i</tt> <tt>{c</tt> <tt>{t</tt> <tt>Abc}}}</tt>
gives you <i><tt>A<small>BC</small></tt></i> in italic small
capital typescript. In principle, you should be able to get any combination
of styles, but in practice, some combinations may not look good with your
browser. For example, using ‘<tt>+</tt>’ and
‘<tt>-</tt>’ together may give results different from what
you expect.
<br>
Bracy doesn’t care about the order of
nested styles, so
<tt>{i</tt> <tt>{b</tt> <tt>Abc}}</tt> gives you
the same results as
<tt>{b</tt> <tt>{i</tt> <tt>Abc}}.</tt> Duplication
of styles has no effect, so if you write
<tt>{b</tt> <tt>{b</tt> <tt>Abc}},</tt> then
you’ll get the same results as
<tt>{b</tt> <tt>Abc}</tt>; you won’t get boldface
that’s twice as bold. You can abbreviate a nested style like
<tt>{b</tt> <tt>{i</tt> <tt>Abc}}</tt> by writing
<tt>{bi</tt> <tt>Abc}</tt> or
<tt>{ib</tt> <tt>Abc},</tt> since order doesn’t matter.
You could even write <tt>{bibi</tt> <tt>Abc},</tt> since
duplication doesn’t matter either, but that would be silly. You can
abbreviate any number of nested styles in this way.
</p>
<a name="bbb">
</a>
<p>
<b>3.2. Braces, backslashes, and blanks.</b>
</p>
<p align="justify">
As the previous examples suggest, Bracy gets its name because it uses the
open brace ‘<tt>{</tt>’ and the closing brace
‘<tt>}</tt>’ as grouping symbols. Some people call these
characters ‘‘curly brackets.’’
<br>
If you want to show braces in your text, then
you must prefix them with backslashes, as in ‘<tt>\{</tt>’
and ‘<tt>\}</tt>’. Braces prefixed in this way will be
treated as ordinary characters, not as grouping symbols. If you want to show
a backslash in your text, then you must also prefix it with a backslash, as
in ‘<tt>\\</tt>’. For example, if you write
‘<tt>\{\\\}</tt>’, then the browser will display it as
‘<tt>{\}</tt>’.
<br>
When a web browser is displaying your text,
it might break a line where a blank appears. Sometimes you don’t want
that to happen. You can avoid this problem by writing a blank prefixed by a
backslash: ‘<tt>\ </tt>’. This is called a
<i>nonbreaking blank.</i> For example, if you write
‘<tt>a\ b\ c</tt>’ then Bracy will make sure
<tt>a</tt>, <tt>b</tt>, and <tt>c</tt> all stay on the same
line.
</p>
<a name="scopes">
</a>
<p>
<b>3.3. Scopes.</b>
</p>
<p align="justify">
Bracy uses <i>scopes</i> to determine how your text should be organized
into lines and paragraphs, and how those lines and paragraphs should be
displayed. A scope is written as
<tt>{</tt><i>scope</i> <i>text</i><tt>},</tt> where
<i>scope</i> is the name of the scope. Depending on which scope is
being used, the <i>text</i> may be a series of words, a series of
lines, a series of paragraphs, a series of scopes, or a series of both words
and scopes. These are defined in the following way.
</p>
<ul>
<li>
<p align="justify">
A <i>newline</i> is the invisible character that you get when you
press the <small>RETURN</small> key or the <small>ENTER</small>
key.
</p>
<li>
<p align="justify">
A <i>word</i> is a series of one or more characters, terminated by a
blank, a newline, or a brace.
</p>
<li>
<p align="justify">
A <i>line</i> is a series of zero or more words, separated by one or
more blanks, and terminated by a newline or a closing brace.
</p>
<li>
<p align="justify">
An <i>empty line</i> is a line with zero words: all it has is a
newline or a closing brace at the end.
</p>
<li>
<p align="justify">
A <i>paragraph</i> is a series of one or more non-empty lines,
terminated by an empty line or by a closing brace.
</p>
</ul>
<p align="justify">
A Bracy source file is a series of zero or more scopes. These scopes are
described in the rest of this manual.
</p>
<a name="left">
</a>
<p>
<b>3.3.1. Left.</b>
</p>
<p align="justify">
The <i>left</i> scope is simplest. It displays a series of paragraphs
whose lines are flush left and filled. The first paragraph is not indented,
but the second and later paragraphs are. The text in most web pages appears
this way. For example, if your source file contains this:
</p>
<blockquote>
<p>
<tt>{left </tt>
<br />
<tt> {b Thelma Suzette Bracy} (January 2, 1919 – </tt>
<br />
<tt> October 9, 1967) was an American science fiction writer. </tt>
<br />
<tt> Along with Isaac Asimov, L. Sprague de Camp, Robert </tt>
<br />
<tt> Heinlein, and A. E. van Vogt, she was one of many new </tt>
<br />
<tt> writers discovered in the late 1930’s by John W. Campbell, </tt>
<br />
<tt> editor of {i Astounding Science Fiction} magazine. </tt>
<br />
<tt> </tt>
<br />
<tt> Bracy is well known for her short stories that eerily </tt>
<br />
<tt> predicted many aspects of modern computer technology, </tt>
<br />
<tt> including cell phones, programming languages, and the </tt>
<br />
<tt> Internet. </tt>
<br />
<tt> Some claim that the name of the Internet language {c html} </tt>
<br />
<tt> was obtained by permuting the consonants of Bracy’s first </tt>
<br />
<tt> name, but there is no evidence for this. </tt>
<br />
<tt> </tt>
<br />
<tt> In many of Bracy’s stories, the protagonist is Dr. Jules </tt>
<br />
<tt> Webster, a private detective with a doctorate in </tt>
<br />
<tt> ‘‘electrolinguistics.’’ </tt>
<br />
<tt> The ‘‘electronic brain’’ owned by a large organization </tt>
<br />
<tt> mysteriously fails, and the reclusive Webster is hired to </tt>
<br />
<tt> repair it. </tt>
<br />
<tt> He does so by typing a cleverly written ‘‘logigram’’ into </tt>
<br />
<tt> the brain, using a ‘‘keypunch.’’}</tt>
</p>
</blockquote>
<p align="justify">
then the browser will display these three paragraphs:
</p>
<blockquote>
<p>
<b>Thelma Suzette Bracy</b> (January 2, 1919 – October 9, 1967)
was an American science fiction writer. Along with Isaac Asimov, L. Sprague
de Camp, Robert Heinlein, and A. E. van Vogt, she was one of many new
writers discovered in the late 1930’s by John W. Campbell, editor of
<i>Astounding Science Fiction</i> magazine.
<br>
Bracy is well known for her short stories
that eerily predicted many aspects of modern computer technology, including
cell phones, programming languages, and the Internet. Some claim that the
name of the Internet language <small>HTML</small> was obtained by
permuting the consonants of Bracy’s first name, but there is no
evidence for this.
<br>
In many of Bracy’s stories, the
protagonist is Dr. Jules Webster, a private detective with a doctorate in
‘‘electrolinguistics.’’ The
‘‘electronic brain’’ owned by a large organization
mysteriously fails, and the reclusive Webster is hired to repair it. He
does so by typing a cleverly written ‘‘logigram’’
into the brain, using a ‘‘keypunch.’’
</p>
</blockquote>
<p align="justify">
Biographical information about Thelma Bracy is from the introduction to
<i>Beyond Computation: The Complete Short Fiction of Thelma Bracy</i>
<a href="#cha2004">
[<small>CHA</small> 2004].
</a>
</p>
<a name="right">
</a>
<p>
<b>3.3.2. Right.</b>
</p>
<p align="justify">
The <i>right</i> scope displays a series of paragraphs whose lines are
flush right and filled. Paragraphs are not indented. This usually works well
only for short texts, such as quotations. For example, this:
</p>
<blockquote>
<p>
<tt>{right </tt>
<br />
<tt> Computers don’t really work. </tt>
<br />
<tt> I just knew that before you did. </tt>
<br />
<tt> </tt>
<br />
<tt> — Thelma Bracy (1966)}</tt>
</p>
</blockquote>
<p align="justify">
will appear like this:
</p>
<blockquote>
<p align="right">
Computers don’t really work. I just knew that before you did.
<br />
— Thelma Bracy (1966)
</p>
</blockquote>
<a name="justify">
</a>
<p>
<b>3.3.3. Justify.</b>
</p>
<p align="justify">
The <i>justify</i> scope displays a series of paragraphs whose lines
are justified and filled. The first paragraph is not indented, but the
second and later paragraphs are. Text in books and papers is typically
justified, although text in most web pages is not (this page isn’t
typical). For example, the source text:
</p>
<blockquote>
<p>
<tt>{justify </tt>
<br />
<tt> Bracy’s first published story, ‘‘Fruit Counter,’’ </tt>
<br />
<tt> appeared in the March 1938 issue of {i Astounding.} </tt>
<br />
<tt> The electronic brain that runs the assembly line of the </tt>
<br />
<tt> National Canned Produce Company is inexplicably putting </tt>
<br />
<tt> pears into peach cans. </tt>
<br />
<tt> Baffled company engineers call Jules Webster in to </tt>
<br />
<tt> investigate. </tt>
<br />
<tt> </tt>
<br />
<tt> When Webster arrives, he thinks for a few moments, </tt>
<br />
<tt> then asks to see a can of peas. </tt>