I'm developing a Flash MX 2004 CD/ROM or web-based tutorial that teaches Hebrew (or potentially Spanish and other languages). I want to create a teaching "engine" where language specialists can create XML files that drive the engine.
I will bid this out as a series of prototypes, one bid for each teaching module, exercise, or game. If I find someone I like working with, they will probably get preference on future projects.
I need someone with these skills:
1) game development
2) Computer-Based-Training development
3) Strong XML knowledge with knowledge of how to process XML in Action Script
4) If you are Israeli or fluent in Hebrew - that's a plus, but not required.
I'm not interested in fancy graphics/backgrounds etc...
in these first prototypes.
You will need to download Hebrew font and keyboard from this page:
[url removed, login to view]
(You will need XP or Win 2000+ to be able to use keyboard/font.)
1) Program should read [url removed, login to view] and display a list of dialogs that the student can choose from (the information on the screen must be driven by the XML file). I will provide 4 XML files for testing (see below).
2) Each dialog has its own XML file associated with it. When the
student clicks on a dialog, the menu "program" should transfer to the "dialog" program, which should read the corresponding dialog XML file, and display the Hebrew dialog on the screen in Hebrew letters only. The dialog xml file will have numbers that refer to the words in another dictionary xml file.
NOTE: the exericise will have a direction attribute indicating "LTR" (left to right - for Hebrew) or "RTL" (right to left for Spanish or other languages) and a FONT attribute.
3) Each foreign (Hebrew) word should have two capabilities:
a) on mouseover - the English transliteration and translation should display in the same tool-tip style box to the upper right of the Hebrew word (tranliteration is for example "Shalom" - spelling Hebrew letters in English letters, translation would be "peace or wellbeing").
b) on mouseclick - the Hebrew word should be spoken.
name of sound file is provided in dictionary xml file.
c) Hopefully this could be done with a movieclip or some object-oriented reusable tool.
4) Each "row" should have an arrow-icon to click to hear the row spoken. The names of the sound files are in the dialog xml file on the row element. On the mouse-over of the arrow, a tool-tip style box should appear with the translation of the entire row (this comes from the dialog xml file row element).
5) If the dialog is longer than one screen, a scrolling mechanism
should be provided. A big plus would be if the user could change the font size himself. The default font size should be 24. The text should not wrap! The xml file will determine how many words are displayed on each row.
6) One more trick - the dictionary will not have common prefixes to words.
For example: "mishpacha" means "family" but "hamishpacha" means "the family".
So rather than recording to words in the dictionary, the dialog xml files will specify any prefix letter(s) that need to be added to a word. To keep the dialog files in all English letters, the prefix will be specified for example as "h" but needs to converted to the hebrew keyboard equivalent of "h". There are only five prefixes but sometimes they are used together, for example:
single prefixes: h,b,l,k,v combined: vb, vl, vk, vhb, vhl, vhk.
(Just so you know, the Hebrew to English meanings are:
b=in l=to/for k=like/as, h=the, v=and).
7) Summary/Examples of the three XML files:
a) [url removed, login to view]
b) Dialogs: for example: [url removed, login to view], and also [url removed, login to view]
c) Dictionary file:
The Hebrew words will show up in this post as ????. But after installing the Font library above, you should be able to see them.
Note: the mp3 file names can either be coded in this file,
or the names could be assigned by taking the lookup attribute and
just attaching ".mp3" on the end of it.
1) Do all sound files have to be loaded in the flash program?
What if I have a dictionary of 5000 words, each having its own soundfile.
To help you win the bid, please address the issues above and any others that I may not have considered. I have no idea if the bid should be under $300 or over $300, so I chose the under $300 category. Bids over $300 will still be considered if competitive.
This bid is just for the "dialog module". Future projects will include other types of exercises that will use much of the same technology, but different XML files for each exercise. I will provide 4 XML files and all sound files to winner of bid.