|
Post by dreamingfifi on Dec 22, 2014 0:17:46 GMT
I think we need to make a fairly intuitive way to input the grammatical rules for other languages, so that teachers and linguists can build libraries in other languages.
So, the core of the function of the program is ___ equals ___ with _these_notations_.
You'd be able to make, edit, and organize notations so that the ones you make often can be done quickly.
This basic set of principles could be implemented in these ways:
Say you want to teach how to write in Tengwar. Instead of equating words, you'd be equating individual letters.
Say you want to teach how to read Ancient Egyptian texts. Instead of text, you could use pictures.
Say you wanted to annotate a Shakespearean play - you don't need both columns, but you'd use the annotating feature.
What do you think?
|
|
|
Post by Auburn on Dec 22, 2014 2:11:50 GMT
So here is a try at an admin panel.... Things that would be interactive web elements are placed in [brackets like this]. ***
Admin Panel Options
#1- Select Visible Columns: Primary Text Column [check on/off] Phonetic/Latin Equivalent Column [check on/off] Alphabet/Symbols Column [check on/off] Add New Symbol: [letter/characters] = [browse image file] [add new field]
#2 - Database Import: [browse for file]
#3 - Add a root to database: [word field] [translation] [meaning] [part of speech] [submit button]
#4 - Language Morphology Notations [browse file] Add Morphology:
This is what I managed to envision so far. I had to make an image for the last one, cuz it's a bit complicated. Click to see full details. Making the morphology menus for the language is hard either way, but it can be done easier using a sort of tree like this. I think that, considering how dramatically different languages can be, an approach for data entry like this one is most universal, although it takes a little learning. I think if there was a "How to" link next to this box, we'd be okay. You basically just have to replace the text for the options. And use [if "____"] in case you want a menu to popup only if the word is designated to have a certain attribute. What do you think..?
|
|
|
Post by Auburn on Dec 22, 2014 19:40:37 GMT
After rethinking it yesterday, if the point's gonna be to make this an easy interface for anyone, then maybe a less technical approach would be needed. Something like: So basically this would act more like a file folders directory. It's dynamic. So if you click one menu, the sub-menu box populates the sub-items that are in that one menu. If you designate an item as not having sub-menus, then that lets the software know it's the "final" one, and it will let you add a description in the "Descriptions" box, describing the item. Otherwise the Descriptions box would be grayed-out. I think this approach is more intuitive, though it would take more coding hours. Still we might be able to manage it.
|
|
|
Post by dreamingfifi on Dec 23, 2014 0:57:39 GMT
Oh, I like this a lot better for making the menus.
So, when inputting the translation, there'd be a lot fewer options to muddle through. It'd look something like this: (rough text-only approximation)
[#][____][insert picture instead] = [#] [_____] [select part of speech] annotation: [________________]
Then, as I'm filling it out, this would happen:
[1][Gur] = [2][ heart ] [Noun] [nominative] annotation: [Root form: gûr <br>The reduced vowel is because of the possessive suffix attached to it.]
[2][en ] = [1][My ] [pronoun] [1st person singular] [genitive] [suffix] annotation: [Root form: -n. <[/i]br>There is discussion about where the -e- comes from, whether it is a relic from the word's ancient form, or if it is inserted between the two consonants to prevent a consonant cluster.]
[3][ bêd ] = [3][ speaks ] [verb] [soft mutation] [present tense] [3rd person singular] annotation: [Root form: ped-. <[/i]br>Why it is mutated, no one is exactly sure. The leading theories are that because it's part of an idiom, the words have been worn down a little, causing gûr to completely shorten its long vowel and annin to be shortened into enni. The other theory is that verbs are mutated when directly following their subject.]
[4][ enni.] = [4][ to me.] [pronoun] [1st person singular] [dative] [independent pronoun] annotation [One would expect this pronoun to take the form annin as they are formed by taking the oblique pronoun and prefixing the preposition an onto it. It appears that Tolkien took annin and wore it down - making the I cause I-affection and cutting the N off. We're not sure why though. One theory is that this is just how the 1st person singular dative pronoun is, and the other is that it's only this way in this idiom because it's been repeated so often that the whole phrase became worn down, like how in English "How do you do?" became "Howdy!"]
What do you think? (Is my post intelligable at all?)
|
|
|
Post by Auburn on Dec 23, 2014 3:46:38 GMT
It makes sense to me now, yep. =) So we'll add annotations each step of the way. And have the capacity for more sub-menus than this. So, I think now we've refined it to something like.. I've included an "abbreviation" field in the description. The bigger box description is for a laymen's explanation. This will allow the admin to toggle between the two display styles, depending on the level of the audience. i.e. Professors using this for their undergrad students will likely prefer the annotated option, and so forth.
|
|
|
Post by Auburn on Dec 30, 2014 1:11:01 GMT
|
|