CMSC 313 Spring 2011

Announcements | Exams | FAQ | Home | Projects | Resources | Schedule / Notes | Staff | Syllabus

Objective

Background

The Task

Since your program is doing both translations, in theory, the output from translating an English file into Morse code could follow whatever conventions you chose for separating characters, separating words and handling special characters such as punctutation. However, we require that you follow the translation rules below so that the Morse code produced by all students is the same (so they can be verified) and so that we can provide our own Morse Code files for your program to convert into the original English text.

English to Morse Code

1. Translate all alphabetic and numeric characters into the appropriate Morse code sequence of dashes and dots according to the table above.
2. Since a period is a dot, translate it into the pound ('#') character.
3. Since a hyphen is a dash, translate it into the caret ('^') character.
4. Separate Morse code sequences for each character within a word with a single space.
5. Use the pipe ('|') character to denote the last Morse code sequence of a word.
6. Other than period and hyphen, all other characters (punctuation, whitespace, etc) should written to the output file without translation.

Morse Code to English

1. Morse code sequences should be translated back into the appropriate alphabetic or numeric character.
   Note that Morse code does not distiguish between upper- and lower-case for alphabetic characters. Use upper-case.
2. The pound character ('#') should be translated into a period.
3. The caret character ('^') should be translated into a hyphen.
4. All other characters (other than the pipe ('|') which has special meaning) should be output without translation.

Requirements, Hints and Notes

Requirements

1. The order of user input is
   1. Input filename
   2. Output filename
   3. Translation -- use E2M for English to Morse code and M2E for Morse code to English.
2. If you are unable to open either file, print an appropriate message and exit your program.
3. You must make appropriate use of functions for this project. In particular, you must write separate functions to translate an alphanumeric character into Morse code and to translate Morse code back to an alphanumeric character. Since these functions can be used by any application that deals with Morse code, these two functions must be placed into their own .c file.
4. You must provide a makefile that will compile all .c files you submit and create an executable named Project2 when the graders type make.
5. You must make appropriate use of static for variables and functions.
6. You must make appropriate use of #define and const variables.

Hints

7. This project is harder than it seems. Start early.
8. Consider reading the input file one character at a time using fgetc( ).
9. To test your code, translate an English language file into Morse code. Your program should be able to reproduce the original English file from the Morse code produced.
10. Since one alphanumeric character may result in a Morse code sequence of up to 5 dots/dashes, start with small files and short lines when testing your code.

Notes

11. Since '#', '^', and '|' have special meaning in the Morse code file, they will not appear in any English text file you are asked to translate.

Sample Files

English text file:

Hello "bob!".
123 454 Hello?

??? Hello      "Johnny   "?

Resulting Morse code file

.... . .-.. .-.. ---| "-... --- -...|!"#
.---- ..--- ...--| ....- ..... ....-| .... . .-.. .-.. ---|?

??? .... . .-.. .-.. ---|      ".--- --- .... -. -. -.--|   "?

Project Grading

1. Functionality (45 points)
   Note that your functionality score will be zero if your code does not compile or create an executable.
   • Basic cases (15 points)
     1. Typing make creates an executable named Project2.
     2. An English file that contains only lower-case alphanumeric characters.
     3. A Morse code file that does not contain punctuation.
   • More complex cases (20 points)
     1. An English file that contains upper- and lower-case alphanumeric characters as well as punctuation (including periods and hyphens).
     2. A Morse code file that contains punctuation characters and whitespace.
   • Atypical cases (10 points)
     1. An empty input file or any file that cannot be opened
     2. An English or Morse code file that contains only punctuation and whitespace
2. Code (15 points)
   • Design (10 points) -- see requirements above regarding functions, static, separate compilation
   • Style (5 points) - we expect that your code adheres to the course coding standards, particularly with respect to comments, naming conventions, and readability.

Submitting the Program

You can submit your project using the submit command.

submit cs313 Proj2 makefile <list of .c and .h files>

See this page for a description of other project submission related commands. To verify that your project was submitted, you can execute the following command at the Unix prompt. It will show all files that you submitted in a format similar to the Unix 'ls' command.

submitls cs313 Proj2

Top of Page Last Modified: Saturday, 26-Feb-2011 09:54:51 EST