ࡱ > r t q c F jbjbSS L 1 1 4 $ ] $ P * $ N | +
L h
h
h
* * * * * * * , - / $ * 0 * h
h
S
v V h
h
* ^ | ^ * r w ) t * < sV a * MIT-ITS WEB SITE STANDARDS
Look and Feel Standards
Overview
The "look and feel" of a web site is very important to the success of a web site. The "look", meaning the page colors and graphics considered as a whole, should give the user a sense of professionalism and continuity. The "feel", which we will define as the specific location of common elements such as navigation elements, should give the user an easy means by which to move about the web site. Together, the look and feel should reflect the purpose with which the site was designed.
As much as possible, MIT-ITS web pages should conform to the general MIT web site standards. They must also conform to the established accessibility guidelines. See the related MIT URLs for more information:
"Guidelines for Web Pages at MIT" - http://web.mit.edu/guidelines.html "Universal Design and Web Accessibility" - http://web.mit.edu/ada/waccess.html
Consistency of look and feel in all areas of a web site allows users to develop an intuitive model for using the site. Users can then rely on that intuitive model when they need to use a part of the site new to them. The intuitive model helps users learn new functions and transactions more quickly and easily. For this reason, all pages on the MIT-ITS web site are required to conform to a standard look and feel
In simplest terms, that standard is defined as having a light blue background with a standard header and footer. Other specific standards apply.
General Specifications
Download Time
An important aspect of development is making certain that the end-user will be able to use the site in a reasonable amount of time. This download time includes the total time it will take to download the web page itself, plus all of the graphics included on that page. All pages intended for community viewing should take less than 40 seconds to download.
Comment Tags
Include comment tags around every element that is a functional piece of html.
Colors, Fonts, Layout, Formatting
As much as possible all color, font, layout and formatting will be controlled by an external style sheet. This improves download time, improves accessibility and makes maintenance easier. The style sheet has been written with the understanding that Netscape is the required browser for using ITS. Screens may display the pages differently depending on their support of css. With styles turned off these pages are still usable, i.e., they degrade gracefully.
The link to the style sheet is included within the block of each page:
OR
Style Sheet Contents
Home Page
The home page, index.html, must contain:
Hours of operation, and business support.
Email address and phone number for business and technical support.
Reference to the Americans with Disabilities Act of 1990.
Links to all MIT-ITS functions.
Links to help, getting started (certificates, kerberos id, etc.)
System status message (UP or DOWN).
Link to MIT home page.
Link to SAP for MIT home page.
MIT copyright at bottom of screen.
Other Pages
All content on the MIT-ITS site must be pertinent to MIT interests. Content should also be reviewed by process-owners for approval and suggestions. All MIT-ITS pages other than the home page must contain the standard MIT-ITS header, navigation area, and footer. Both the header and the footer must be inserted through the use of server-side includes.
The standard MIT-ITS header is currently the title bar placed in the top of the web page. It includes the MIT-ITS logo, the title of the transaction accessed, and the date.
Below the header, right-justified, is the navigation area with navigation links for the function type (e.g., Journal Vouchers) plus links to the MIT-ITS home page and to help documentation. All pages must have a navigation area, even if it only includes links to the home page and to help. Exceptions will be transaction detail pages that require a specific exit or form submission.
The footer on all pages must contain the copyright below a horizontal rule.
Common Page Elements
Elements Governed by Styles
(See style sheet contents above.)
Headings Within a Page class=heading
On-screen Instruction class=note
R/3 Message Table Cell class=message
Field Section Table Cell class=section
Field Label Table Cell class=fieldlabel
Field Data Table Cell class=data
Column Heading Table Cell class=column
Body Tags
Include margin height and width specifications in the body tag.
Background
The background on any MIT-ITS page should be: bgcolor="#B8CCD9" (light blue). Even in the case of a different color, the background must be very light so that text will be easily seen on top of it. This value is governed by the external style sheet.
Header (server-side include)
Navigation Area
The navigation area appears just below the header and is right justified. Some pages will have a right justified row of navigation links, e.g. Help | SAPweb | Purchasing.
Other pages may not have this right justified row of navigation links because using a link on these pages will lock the transaction.
On Screen Instructions and Notes
Any instructions appearing as a part of an MIT-ITS screen must be specific and concise. On screen instructions must appear inside a light blue table:
R/3 Messages
When the R/3 system detects an error within field contents, or has a message to display regarding the current session, the R/3 message is placed into the ~messageline parameter. If a message exists, it is displayed to the user in a highlighted block through the use of a single-cell table, formatted as shown below. If no message exists, the table is not displayed.
Images
Images cause longer download times. Whenever possible, use text rather than images. All images included on MIT-ITS pages are subject to review. Removal will only occur in extreme cases, such as graphics with large file sizes (>100K).
Buttons
All buttons will be standard HTML form buttons, not graphical buttons. On long forms for which users may need to scroll to the bottom, all functional and navigational buttons will be made available at the top of the form as well as at the bottom
Tables
Tables should have a border of 0 or 1, depending on the use of the table. Cell spacing should be 1 or 2, and Cell padding should be no more than 4. For example:
Footer
Elements Not Allowed / Subject to Approval
Except where otherwise noted, all elements which have not been specifically allowed on the MIT-ITS site should be considered barred. This ban includes, but is not limited to, the following:
Frames
In every instance when you would use frames, tables can be used to display information in a similar layout. File management becomes much easier, and the audience for the information is increased. An exception will be made for SAP delivered transactions.
Company or Software Logos
MIT-ITS should not be viewed as endorsing or promoting any software vendor, product or company. Logos are allowed for organizations with which departments have created a partnership, but those logos are only allowed in the context of those partnerships.
JavaScript
JavaScript must be approved for their technical content to make certain that they (1) do not take too long to download, (2) do not pose a security risk to the end-user computer or the enterprise network, and (3) conform to MIT-ITS look and feel standards.
Sounds
Sounds should be avoided. While sounds may grab a user's attention the first visit to the site, they can quickly become an annoyance upon further visits, especially if the sound file requires significant download time.
Video and Streaming Media
Until a standard has been developed for this technology, video and streaming media are not allowed on the MIT-ITS site.
Author Information
Individual elements of the MIT-ITS web site should not be presented as authored or maintained by individuals.
Summary
The "look and feel" of a site is very important to the usability of a site. Radical differences between various sections of a site lead to confusion and significantly reduce usability. The more consistency there is, the easier it is for users to perform their work and learn new functions.
The current standards used for the MIT-ITS web site are designed by a subcommittee of the MIT-ABAP Committee. Members of the subcommittee are accepted on a volunteer basis.
Development and Maintenance
Service Naming Conventions
There are two kinds of objects that are relevant to ITS:
The R3 transactions SAP delivered or custom (created and maintained in transaction se80).
The web objects. (Services, Theme, Templates, Mimes):
Created/maintained in Web Application Builder (se80) & Web Object Administration (siac1).
Published on the MIT-ITS server.
Briefly, the procedures for deploying these MIT-ITS transactions are:
If a standard service XXXX already exists
Copy service XXXX to ZYY_XXXX in transaction SIAC1in SF2 (where YY is the 2-Character Abbr. of the Application Name Appendix B of MIT SAP development standards http://web.mit.edu/sapr3/dev/standards4.html). This will copy the service/theme/mimes and templates.
In Web Application Builder:
Strip down service ZYY_XXXX from username/password/language, and change references of 'XXXX' into 'ZYY_XXXX'.
Delete the SAP GUI for HTML templates.
Generate the templates (generation style: classic) one for every screen.
Publish entire service ZYY_XXXX into SF2ITS.
Release transport (transaction se10) and send email to r3-chmgt requesting transport and publishing of ZYY_XXXX into SF5ITS.
If a service DOES NOT already exist
Develop new transaction ZXXXX in transaction se80.
In Web Application Builder:
Create service ZYYXXXX to point to transaction 'ZXXXX'. . (Where YY is the 2-Character Abbr. of the Application Name Appendix B of MIT SAP development standards http://web.mit.edu/sapr3/dev/standards4.html)
Generate the templates (generation style: classic) one for every screen.
Publish ZYYXXXX into SF2ITS
Release transport and send email to r3-chmgt requesting transport and publishing of ZYYXXXX into SF5ITS.
Note: According to the above scenarios the service naming convention is the following:
- XXXX: a SAP service file that calls SAP transaction XXXX.
- ZYY_XXXX: a modified service file that still calls SAP transaction XXXX.
- ZYYXXXX: an MIT service file that calls MIT transaction ZXXXX
(ZXXXX is a modified version of SAP transaction XXXX, or a native MIT transaction)
Images
All images after being created in Photoshop or any other software have to be uploaded to SAP to the Internet Service ZGLOABL using transaction se80. Then images can be published to the MIT-ITS servers and transported to other SAP instances.
Version control
If Web Application Builder (transaction: se80) and Web Object Administration (transaction siac1) totally replace WebStudio then all objects are transportable via the SAP transport system. The existing emailing lists r3-chmgt and fss-chg can be used for transport requests. Version generation and management can be accomplished under the menu option Utilities. Publishing logs can also be displayed under the menu option Utilities.
In order for publishing to work IACOR needs to be running on the ITS-server.
If IACOR is not running we will need to use floppies to transport the Web objects from one environment to the other. All floppies should be dated and kept for reference. The R3 transactions (SAP delivered or custom) are still transportable via the SAP transport system.
The contact person at the MIT-ITS server site is:
name: Hart, Daniel R
email: dhart@MIT.EDU
phone: (617) 253-4107
Dan Hart has agreed to copy files to the MIT-ITS servers at 7:30am, 11:00am and 1:30pm. The floppies are to be delivered at his mailbox at the first floor of W91.
In order to move Web Objects to SF2-ITS, SF5-ITS and SF8-ITS the developer needs to send an email to HYPERLINK "mailto:dhart@MIT.EDU" dhart@mit.edu and provide him with floppy or file names.
In order to move Web Objects to PS1 the developer needs to send an email to fss-chg. The members of fss-chg after verifying the transport with the process owner and the change request form will forward the email to dhart@mit.edu.
The list of developers authorized to request movement of Web Objects to SF2, SF5 and SF8 are:
AEKING
KATERINA
MSPRAGUE
SROACH
ZAVOLEAS
The list of developers authorized to request the movement of Web Objects to PS1 are:
DWILEY
PPAGE
WTURNER
MDAMIAN
The subject of the email should contain MIT-ITS Web Object move.
In the body of the email the developer needs to specify source and target system and the file names:
For example:
Subject: MIT-ITS Web Object move from SF5 to PS1
From : SF5-ITS To: PS1-ITS
Files to be copied:
Service files:
c:\program files\SAP\ITS\2.0\SF5\services\zfi_inbx.srvc
c:\program files\SAP\ITS\2.0\SF5\services\zfi_veri.srvc
Template folders:
c:\program files\SAP\ITS\2.0\SF5\templates\zfi_inbx\
c:\program files\SAP\ITS\2.0\SF5\templates\zfi_veri\
Mimes:
c:\program files\ServersandDaemons\Apache Group\Apache\htdocs\SAP\ITS\mimes\global\
c:\program files\ ServersandDaemons\Apache Group\Apache\htdocs\SAP\ITS\mimes\zinbx\
Files:
c:\program files\Apache Group\Apache\htdocs\SAP\ITS\zjvrpt.html
---------------end of email----------------------------------------------
Note: Running Web Studio is another way to maintain Web Objects. Because of our security concerns this is not a viable solution.
MIT-ITS Web Site Standards * DRAFT * DRAFT * DRAFT * DRAFT * DRAFT * Look and Feel Standards
DATE \@ "M/d/yy" 6/20/01 TIME \@ "h:mm AM/PM" 11:35 AM * DRAFT * DRAFT * DRAFT * DRAFT * DRAFT * Page PAGE 9 of NUMPAGES 9
MIT-ITS Web Site Standards Development and Maintenance
Note: Some text with instructions or info to note here.
BODY {font-family: verdana, arial, helvetica, sans-serif;
font-style: normal;
color: #000000;
margin: 0em;
background: #B8CCD9; /*light blue*/
background-image: none; }
A:link {color: #003B66; /*royal blue*/
text-decoration: none;
text-transform: none;
font-weight: normal }
P, TD {font-family: verdana, arial, helvetica, sans-serif;
font-size: small;}
TD {valign="top"}
H1 {font-family: verdana, arial, helvetica, sans-serif;
font-size: medium;}
P.heading {font-family: verdana, arial, helvetica, sans-serif;
color: #0039aa; /*bright blue*/
font-size: medium;
font-weight: bold;}
.note {background: #DCE7ED; /*pale blue*/
text-align: left;}
TD.pagehead { background: #405580; /*navy blue*/
color: #FFFFFF; /*white*/
font-size: small;
font-weight: bold;}
TD.date { background: #405580; /*navy blue*/
color: #B8CCD9; /*slate blue*/
text-align: right;
font-weight: bold;}
TD.message { background: #ffff98; /*yellow*/
font-size: small;
font-weight: bold;
text-align: middle;}
TD.section { background: #405580; /*navy blue*/
color: #FFFFFF; /*white*/
font-weight: bold;
vertical-align: text-top;}
TD.fieldlabel { background: #98b0c7; /*slate blue*/
text-align: right;}
TD.data { background: #DFDFD7} /*putty*/
TD.column { background: #405580; /*navy blue*/
color: #FFFFFF; /*white*/
font-weight: bold;
text-align: center;
vertical-align: bottom;}
5 6 7 @ R `
W ] * u { * v w z
߸ ߍ ߀ j 5OJ QJ UmH B*
CJ OJ QJ j 56CJ OJ QJ UmH j CJ UmH CJ OJ QJ PJ j 56OJ QJ UmH CJ OJ QJ j CJ OJ QJ UmH j U56CJ OJ QJ 5OJ QJ 55CJ OJ QJ CJ OJ QJ 2 6 7 @ ( 3 S `
x x x x x -D
H$ 6 7 @ ( 3 S `
% O y X | {skc
$
_
A
/}
# :;n $ % O y X | B q 9 ^ x x x
& F
h x x
! B q 9 ^ + 5 v x z c
½~{xurn
?@ACt
#Mu
- ] ^*9EFi
* + 5 v x z c x x x
x x
! x x x
!
& ( ) * + , - . / 0 1 2 3 4 5 < + 3 * x x H$ 7$ 8$ hx x x & ( ) * + , - . / 0 1 2 3 4 5 < + 3 * 1 }zwto O VWBC
D
E
F
G
H
I
J
K
M
TUW u
+ & ' 1 5 < + 3 * 1 !
! ! " " " # # $ $ % & & ' ' {) ) ) ) + + - - -
.
. $. J1 1 2 2 2 2 j U j U CJ OJ QJ 5CJ 5CJ 6CJ OJ QJ 5CJ OJ QJ 6 j 56CJ OJ QJ UmH
j UmH 56CJ OJ QJ 5OJ QJ B*
CJ OJ QJ j 5OJ QJ UmH :* 1 x H$ 7$ 8$
h8p @ x x ! !
! ! ! " ~" " " # # # # /$ $ $ $ $ $ % R% % % <& ]& ^& & & & ' ' _( ( ( |tl
:
V\
I
./KL M '()&AB &'(345PQ ' ! !
! ! ! " ~" " " # # # # /$ $ $ $ $ $ % R% % % <& ]&
& F 8
h
& F
& F < x x x ]& ^& & & & ' ' _( ( ( ( {) ) ) ) * + #+ + + , j, , - - -
& F <
& F
< x x x h
( ( {) ) ) ) * + #+ + + , j, , - - - -
. /
0 1 J1 _1 t1 1 1 .2 2 3 74 >4 G4 P4 W4 `4 a4 4 4 4 4 ¿}zwtqnk hnuR8!n!12#* H
%
n
= Y-
[
(- -
. /
0 1 J1 _1 t1 1 1 .2 2 3 74 >4 G4 P4 W4 `4 a4 4 4 4 4 4 4 4 5 x x x 2 2 2 2 5 -8 .8 38 <8 F8 8 8 8 8 8 8 8 8 8 8 8 9 9 9 "9 #9 *9 +9 ,9 -9 C9 D9 L9 M9 P9 W9 X9 ^9 `9 f9 h9 n9 p9 w9 }9 ~9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 ; ; ; ; 弳 B*
CJ OJ QJ 0J CJ OJ QJ mH 0J CJ OJ QJ j 0J CJ OJ QJ UCJ OJ QJ mH j CJ OJ QJ U5CJ OJ QJ CJ OJ QJ CJ 5CJ CJ OJ QJ j U ?4 4 4 4 5 ~5 5 5 5 5 5 5 5 46 l6 m6 6 6 6 6 6 F7 7 7 7 7 -8 .8 8 8 9 9 9 9 9 9 9 9 : : \: e: : : : : : : : : : : ; ; ; ; ; h; i; {; ; ; ; ; ; ; H:ABw/>RSnoVWX` A5 ~5 5 5 5 5 5 5 5 46 l6 m6 6 6 6 6 6 F7 7 7 7 7 -8 .8 8 8 9 9
!H$ H$ 7$ 8$ x 9 9 9 9 9 9 9 : : \: e: : : : : : : : : : : ; ; ; ; ;
!$
!H$ ; h; i; {; ; ; ; ; ; ; ; >< ?< O< X< \< ]< < < < < < < < -= .= M= Q= H$ 7$ 8$
h8p @ ; ; >< ?< O< X< \< ]< < < < < < < < -= .= M= Q= = = = = = = = = = = = = = +> ,> _> d> ~> > > > > > > /? 0? ? ? ? @ @ D@ i@ @ @ @ @ @ A NA uA A A A A
B DB ]B B B B B "C =C >C qC C C C C D 6D ND }D D D D E $E FE jE E E E F 8F TF qF F F F F
d; < < < < = = > 0? ? ? @ @ A A F F F F CJ CJ OJ QJ CJ OJ PJ QJ B*
CJ OJ QJ Q= = = = = = = = = = = = = = +> ,> _> d> ~> > > > > > > H$ 7$ 8$
h8p @ > /? 0? ? ? ? @ @ D@ i@ @ @ @ @ @ A NA uA A A A A
B DB ]B . H$ 7$ 8$
M h8p @ xHP X !(# ]B B B B B "C =C >C qC C C C C D 6D ND }D D D D E $E FE jE E E E F 8F TF TF qF F F F F H$ 7$ 8$ ( &P 1h / =!"#$% | ,, c yg( ,, ( d ' ` ( &P 1h / =!"#$% | ,, c yg( ,, ( d ' ` D y K d h a r t @ M I T . E D U y K * m a i l t o : d h a r t @ M I T . E D U
[ 8 @ 8 N o r m a l CJ _HaJ mH sH tH : : H e a d i n g 1 $`@& ]` 5\F F H e a d i n g 2 $
!# @&] 5\2 @ 2 H e a d i n g 3 $@& 5\ H e a d i n g 4 f $
S h 8p @ xHP X !(# h@&^h 5CJ OJ QJ H e a d i n g 5 f $
S h 8p @ xHP X !(# h@&^h 5CJ OJ QJ H e a d i n g 6 $@&
ƪ 8 h 8Tp$
@ \
xHPl < X !!t"(##D%%`'((|)0**+L, - 5CJ OJ QJ H @ H H e a d i n g 7 $@& 56CJ OJ QJ \]^J < A@ < D e f a u l t P a r a g r a p h F o n t . B . B o d y T e x t
`]` . U@ . H y p e r l i n k >*B*ph 8 T 8
B l o c k T e x t ` ]`^ > V@ !> F o l l o w e d H y p e r l i n k >*B* ph > P 2> B o d y T e x t 2
!# |]| P BP H T M L B o d y 7$ 8$ H$ CJ OJ QJ _HaJ mH sH tH 0 Q@ R0 B o d y T e x t 3 6], @ b, H e a d e r
! , @ r, F o o t e r
! & )@ & P a g e N u m b e r < Z@ <
P l a i n T e x t CJ OJ QJ ^J aJ G H # [ 0 B " ! G H # [ 0
B ~ *~ ~ ~ ! ! ! ! ! ! ! ! !
z ) 0 B V
+ D ^ ^ # # # # # & 2 ; F % - 4 : * ]& - 5 9 ; Q= > ]B TF F & ( * + . 0 1 3 6 7 8 ; < = > ( 4 ; F ' ) , / 2 5 9 . . . B X^ q y { & ! D ! # @ " (
n
c $
" `
c $
n
c $
" n
c $
"
H ? ?
" `
c $
`
c $
`
c $
`
!
c $ !
`
"
c $ "
B
S ?
v
& B P# O t ( 0 d# t d# * t <# { t H& $ t % t &
t ! & t ( f $'
t " 8'
t A D E M N T P \ ?/ B/ 2 3 3 D3 X3 p3 q3 3 4 4 4 5 5 +5 ,5 M5 N5 w5 }5 5 5 5 5 5 5 a6 c6 m6 |6 ~6 6 6 6 6 6 6 6 6 6 6 6
7 7 m7 w7 49 @9 9 9 9 9 9 9 9 9 9 9 `: b: h: s: u: {: : : 6; E; G; U; V; g; j; k; ; ; ; ; ; ; ; ; ; ; ; < < $< &< +< -< 6< < < < < < < = = = = = = = > > #> %> *> ,> 5> ^> g> v> }> > > > > ?? J? ? ? O@ Y@ @ @ kA xA A A A A B B 8 : L ~ D K b
7 A h l w J- N- ^- _- d- s- t- y- - a0 0 0 0 1 1 1 1 1 32 42 52 k2 2 2 2 2 2 2 2 2 E3 F3 G3 3 3 3 3 3 3 3 ,4 4 4 4 5 5 +5 ,5 M5 N5 w5 }5 5 5 5 5 5 5 5 5 6 "6 a6 c6 j6 l6 6 6 6 6 6 6 6 6
7 7 7 7 }7 ~7 7 7 7 7 7 7 @8 B8 P8 V8 Y8 Z8 8 8 8 8 /9 19 N9 O9 R9 W9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 -: 2: `: b: e: g: : : : : 1; 5; j; k; ; ; U< _< p< u< < < < < < < < < < < < < .= == _= m= = = = = I> R> > > > > > > > > *? 4? K? W? y? ~? ? ? ? ? ? ? ? @ "@ ,@ :@ E@ Z@ f@ @ @ @ @ @ @ @ @ A A 2A =A OA ]A yA A A A A A A A B "B @B KB \B fB yB B B B n g i f t J \ \ R - C R E W S E R V E R \ R - T r n D e v l \ W o r k F o l d e r s \ N a n c y \ I T S L o o k & F e e l S t a n d a r d s _ N G . d o c n g i f t J \ \ R - C R E W S E R V E R \ R - T r n D e v l \ W o r k F o l d e r s \ N a n c y \ I T S L o o k & F e e l S t a n d a r d s _ N G . d o c n g i f t J \ \ R - C R E W S E R V E R \ R - T r n D e v l \ W o r k F o l d e r s \ N a n c y \ I T S L o o k & F e e l S t a n d a r d s _ N G . d o c n g i f t i C : \ W I N N T \ P r o f i l e s \ n g i f t \ A p p l i c a t i o n D a t a \ M i c r o s o f t \ W o r d \ A u t o R e c o v e r y s a v e o f I T S L o o k & F e e l S t a n d a r d s _ N G . a s d P L C : R - t r n D e v l : W o r k F o l d e r s : N a n c y : I T S L o o k & F e e l S t a n d a r d s _ N G . d o c P L C 9 M a c i n t o s h : T e m p o r a r y I t e m s : A u t o R e c o v e r y s a v e o f I T S L o o k & F e P L C / M a c i n t o s h : T e m p o r a r y I t e m s : W o r d W o r k F i l e A 2 1 1 8 P L C 1 R - t r n D e v l : S i t e s : s a p i t s : I T S L o o k & F e e l S t a n d a r d s . d o c P L C 1 R - t r n D e v l : S i t e s : s a p i t s : I T S L o o k & F e e l S t a n d a r d s . d o c P L C 1 R - t r n D e v l : S i t e s : s a p i t s : I T S L o o k & F e e l S t a n d a r d s . d o c k (rt /.3 wT> :qhE h h^h` . h h^h` ) h h^h` ) h h^h`OJ QJ o( h h^h`OJ QJ o( ^`o( . ^` . pL p^p`L . @ @ ^@ ` . ^` . L ^`L . ^` . ^` . PL P^P`L . h ^` . h ^` . h pL p^p`L . h @ @ ^@ ` . h ^` . h L ^`L . h ^` . h ^` . h PL P^P`L . ^` . ^` . pL p^p`L . @ @ ^@ ` . ^` . L ^`L . ^` . ^` . PL P^P`L . h ^` . h ^` . h pL p^p`L . h @ @ ^@ ` . h ^` . h L ^`L . h ^` . h ^` . h PL P^P`L . :q k ( /. wT @ @W B @ @
G T i m e s N e w R o m a n 5 S y m b o l 3 A r i a l ; H e l v e t i c a G
M S M i n c h o T i m e s q5 A r i a l m o n o s p a c e d f o r S A P A n d a l e M o n o ? C o u r i e r N e w 7 V e r d a n a ?& r H e l l a s A r i a l ; W i n g d i n g s " 1 h VFVfV& L P/ d ! 0 d : ]" , J C : \ W I N N T \ P r o f i l e s \ k a t e r i n a \ A p p l i c a t i o n D a t a \ M i c r o s o f t \ T e m p l a t e s \ N o r m a l . d o t ( I n d y G o v W e b P a g e L o o k a n d F e e l S t a n d a r d s k a t e r i n a P L C
Oh +'0 ` l x
' ) IndyGov Web Page Look and Feel Standards ord ndy katerina eb ate ate I \WINNT\Profiles\katerina\Application Data\Microsoft\Templates\Normal.dot a \ PLC 4 C Microsoft Word 8.0 e@
@ X*"@ @ v؞ L P/
՜. +,D ՜. +,T h p |
' MIT d : : ) IndyGov Web Page Look and Feel Standards Title ( R Z
_PID_GUID _PID_HLINKS ' A N { 9 8 2 F 9 B 8 3 - 6 3 C D - 1 1 D 5 - 8 7 A 7 - 0 0 5 0 E 4 5 6 5 9 6 0 } A d 3 m a i l t o : d h a r t @ M I T . E D U x
! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? A B C D E F G I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` b c d e f g h j k l m n o p s R o o t E n t r y F j}u D a t a
@ 1 T a b l e H 0 W o r d D o c u m e n t L S u m m a r y I n f o r m a t i o n ( a D o c u m e n t S u m m a r y I n f o r m a t i o n 8 i C o m p O b j X F Microsoft Word Document NB6W Word.Document.8