|
Okay, I'm a little more clear on that. My mistake was in thinking that you expected the user to do his or her own parsing. Of course, if it's a language designed strictly for use on the internet, there's no reason that's necessary, which as you note allows the user interface to be adapted or altered as necessary; so long as the parser is there to act as an intermediate layer, the type of interface is almost wholly irrelevant.
However, I do still see an issue, which is in deciding how to render certain concepts so that they're universally agreed upon. You claim English as your native language, but seem familiar with Eastern languages as well. Do you speak anything other than English?
I myself am bi-lingual and speak French as well as English. As such, I'm all too aware that some concepts that are easy to verbalize and/or differentiate in one language can be much harder to distinguish in another. Even if you do only speak English, you only have to watch one poorly dubbed Japanese film to realize exactly how true this is. But perhaps a more concrete example.
French actually does have a fair amount in common grammatically with English, although they're by no means identical. However, there are some words in English that can translate into multiple different words in French, depending on context and the same goes the other way. The French verb faire, for example, can mean either to do or to make, contextually, which are two related concepts that are nonetheless distinct in English. Essentially, in English one does not say that one does a sweater (at least, it's not grammatically proper to do so), whereas in French it would be perfectly correct to say exactly that (je fais une chemise). This is a grade school level example, but it serves to illustrate I think.
With human interpretation of the language, this is hardly an insurmountable issue; one simply translates the word contextually to it's correct analogue. Machine parsers, however, are somewhat poor at reading context, which in turns leads to mistranslations; at worst, this can render an output that says something markedly different from the input. While hardly an insurmountable problem, I'd imagine one may have difficulty creating a parser and interface that is robust enough to allow for this without it becoming unwieldy.
__________________
I wake up in the morning more tired than before I slept
I get through cryin' and I'm sadder than before I wept
I get through thinkin' now, and the thoughts have left my head
I get through speakin' and I can't remember, not a word that I said
- Ben Harper, Show Me A Little Shame
|