Word-processing file formats

In most word processors, the appearance of the screen realistically represents what the printout on paper will look like (WYSIWYG). Word processing files actually contain large amounts of code relating to text format etc., but these clutter the screen if visible, as in non-WYSIWYG programs. Some word processors are menu driven, others require keyboard entry of codes menus are easier to start with and the more sophisticated programs allow you to choose between these options. 

Another area we can learn from is the exchange of text documents. How many of you have ever tried to exchange a word processing file from one program to another How many succeeded, while still maintaining intricate formatting details What happened if you tried to get it back from the other program ... 

The simplest of the formats used to transfer data into word processing applications is the ASCII (.ASC). ASCII is a standard set of 128 binary codes used by all computers to represent all the characters presented on the normal or shifted keyboard plus control codes, originally intended for use on teletypewriters. These code allow us to display lower case leters, capital letters, numbers, and punctuation marks, but formatting codes for underline, boldface, and italics are not included in ASCII, and are removed in converting formats. ASCII files have space-separated code and can be sent out over a modem or a serial cable to another computer and applications importing ASCII code. 

The author guidelines will indicate if there are word-processing templates available for authors to download and will specify if there are requirements about their use. Template files contain all the necessary formatting for a particular journal and are provided by the publisher from its Web site. Templates make it easier to format submissions to meet the publisher s specifications. 

The true business value of an EDMS is realized to the extent that it serves as more than just the terminus for document-related activities in an enterprise. To fully realize its goals, an enterprise paperless documentation system will perform functions across the entire document life-cycle. In addition to the storage of existing documents, users with appropriate system privileges must be able to create new electronic documents from within the electronic document management system. The system must explicitly support the file formats used by the business, which typically include word processing, spreadsheet, graphics, and database files. 

Integrate software using OLE including access to all formats provided by the sonrce application (e.g.. Molecule [MOL] files from ISIS/Draw, Rich Text Format (RTF) files from word processing applications, Comma Separated Valne (CSV) formats from worksheet applications). 

Any word processing program may be used, as long as the file is saved as text only. The Windows Notepad program is good for this task, as it saves its files in text-only format by default. Name the file first. pi. 

The standardisation process is broken. Standards need to be open source to facilitate easy updating in a highly volatile profession, and of unlimited free access. Proprietary file formats have caused enough misery without compounding it with proprietary standards. The current situation whereby standards are heavily protected, expensive and frequently outdated before they even appear is unhelpful to say the least and it is possible that Wikipedia and its like may play a substantial future role. NASA also has always been an excellent role model here, providing free access to lots of useful documents and data (e.g. Dvorak 2009). However, on a cautionary note, open source standards without measurement constraint will simply produce free words. 

In preparing an NBO input file, it is important to use an ordinary text editor (rather than Word or other word processor) in order to scrupulously avoid tabs or other control characters embedded in the plain-ASCII text file. Unseen control characters, corresponding to ASCII characters outside the printable range 32-126, cause unpredictable errors in processing the input file. Check also that text-file format is consistent between the platform on which the input file was prepared and that under which the... 

Figure 7.3-1 outlines steps in the scoping process. However, if this information is to be gathered, it should be in a convenient form such as collecting the data as a computer file in a notebook personal computer. The file may be a word processor, a spreadsheet, or a database. If the input is into a word processor such as WordPerfect or Word, it may be in table format. Very similar but Process Scoping Steps... 

---