CSCI 241 - Lab 5 :
C Strings

Due by 11:59.59pm Wednesday, April 20

Introduction

For this assignment create a program pig that will read in English text and translate it into Pig Latin. In particular you'll be working with strings in C.

Programming Details

Pig Latin is used by both adults and children to obfuscate what they are saying from the other. Some of you might have toyed around with the language yourself as a child.

Translating Pig Latin

For this assignment, you'll be creating a programs pig. pig will read in English text and convert it into pig latin.

Pig Latin Translation Rules

There are a couple of varying rules to Pig Latin. For this assignment, we'll be using the following:

1. Rule 1:

   If the string begins with a vowel (that is begins with 'a', 'e', 'i', 'o', or 'u') add "yay" to the end of the string.

2. Rule 2:

   Otherwise, find the first occurance of a vowel, then move all the letters before the vowel to the end of the word and add "ay".

   Note:

   "y" should be considered a vowel in this context.

You can consider a word to be a consecutive sequence of letters (A-Z, a-z). "y" should be treated as a consonant if it is the first letter of the word but as a vowel otherwise.

Punctuation & Grammar

In addition to modifying the words as specified above, your program should also respect the following rules:

• Puntuation in sentences should be preserved (periods, commas whitespace, tabs, etc.)
• Capitalization should be preserved. The original capital letter should be lowercased and the new initial letter should be capitalized. So, Linux would become Inuxlay.
• The letter pair "qu" together should be treated as a consonant, rather than a single character.
• Hypenated words should be treated as two words.

Some dialects of pig latin say that you should move "silent" letters to the end as well (such as in the word knife). You can ignore contraction words (don't).

Examples

In general, the words will be translated as follows:
Linux -> Inuxlay

yes -> esyay
example -> exampleyay

Programming Notes

Some guidelines you should follow when working on your solution:

• No word we use in our testing will be longer than 100 characters.
• strcpy, strcat, strdup are useful functions for this assignment.

You'll want to think about how to breaks this program into its component parts.

Command line arguments

Additionally, I'd like you to implement a -h and -? flag that prints out a brief usage message and exits the program with a non-zero value. You should do the same if an unknown flag is passed to the program.

You should have your program's main function return 0 upon successful completion of the assigned task.

Extra Credit

Handin

README

Create a file called README that contains

1. Your name and a description of the program
2. A listing of the files with a short one line description of the contents
3. Any known bugs or incomplete functions
4. Your estimated time from the start and the actual time taken
5. Your affirmation as to the honor code if you followed it

Now you should make clean to get rid of your executables and handin your folder containing your source files, Makefile, and README through GitHub

    % git add
    % git commit
    % git push

Remember, if you have issues with commits due to odd merges, it is easier to start over, clone into a new directory, and copy the files over before commiting and pushing.

In addition, if you are working with a partner, you should do git pull periodically to pull their changes into your direction to avoid having to do a merge

Grading

Here is what I am looking for in this assignment:

• A working Makefile with your program, all, and clean as targets
• Appropriately modular code
• Good comments
• Programs which run under valgrind without errors
• A statement about any valgrind errors which occur and that you could not fix
• A README with the information above. The listing of known bugs is important.