Last time I observed that neutrality doesn't work. Even if Initial Neutrality does work by leveling the field, it does so by making the learning task too hard in general, which isn't good. (I've seen projects that were deliberately made unnecessarily hard for the sake of neutrality.) Outcome Neutrality is good in theory, but people vary, so what works for some doesn't work for others.
This leads us to the Eterna Komencanto or Eternal Beginner. Though most noticeable among Esperantists (simply because there are more of them), such people can be found in all auxlangs large enough to be subject to the laws of probability. And even a little reflection shows that the phenomenon is even more common among natlang learners.
Think about it: we've all seen (even perhaps been) the one who just doesn't get some language. I think I first personally witnessed it in high-school French, though there were indicative incidents in Spanish class as well. The intensity of the condition ranges from lack of confidence for active use to total inability to learn, though passive ability is generally good enough to understand at least the gist of a text.
Someone will no doubt object that anyone can learn any language, if it's properly taught. That's technically true. But there's a difference between technicality and practicality: the only reason some people know even their native language is from years of uninterrupted immersion as children--an extreme measure impractical for most adults, especially if the language has relatively few speakers. In theory, any auxlang could be forced on everyone. In practice, people will only willingly learn an auxlang whose difficulty does not exceed their interest, so an auxlang must be incredibly easy or incredibly interesting. And since interest requires either practicality (and thus a large user base that will not appear out of nowhere overnight) or a personal appeal that will be present for some people but not for others, it's a shaky rationale anyway.
Given all this, we may ask where the global user base for any given auxlang will come from. Most projects I've seen simply assume that users will appear; the projects are often ill-suited to attracting users strongly enough to invest the time and effort to master the auxlang. "Hey, that's clever" isn't enough.
And consider that many people, though strongly motivated to learn some natlang, barely achieve intelligibility. English has plenty of Eternaj Komencantoj, probably more than there are Esperantists of any kind.
The conclusion? Some people will always be left out of any given auxlang, but it won't be quite the same group for all auxlangs taken as a whole. This will normally be considered unacceptable, but I'll argue next that it's completely acceptable once we drop the Onelang idea of a single auxlang for everyone.
Tuesday, January 18, 2011
Why I Reject the Onelang View: 1-Neutrality
I've tried to explain this idea several times, with little or no success. But I think I've found a better explanation, so I'll try again.
To begin with, "neutrality" is variously defined these days. It's becoming common to define it in terms of what I call "initial neutrality," not the classical "outcome neutrality." So let's look at those two views:
Initial Neutrality. Everyone starts out relatively even in terms of how familiar the auxlang seems to them or how it represents their language compared to other languages.
Outcome Neutrality. Regardless of the auxlang's sources and structure, learners are likely to attain near-native fluency in roughly the same time, and more quickly and easily than they could achieve such fluency in a natlang.
I tend toward Outcome Neutrality: I don't care about an auxlang's sources, just about how quickly and easily I can achieve near-native fluency. I've encountered stories of people who couldn't communicate confidently in any but their native language--and some auxlang. Struggling with a non-native language made them seem inarticulate, but in their own language and auxlang they were eloquent.
The problem is that neutrality (by any definition) varies by individual, and unlike the Initial Neutrality people, I see no way of avoiding this problem: some people will never achieve near-native fluency in certain languages. In Esperanto, such people are called "Eternaj Komencantoj," and they form the next part of the argument.
To begin with, "neutrality" is variously defined these days. It's becoming common to define it in terms of what I call "initial neutrality," not the classical "outcome neutrality." So let's look at those two views:
Initial Neutrality. Everyone starts out relatively even in terms of how familiar the auxlang seems to them or how it represents their language compared to other languages.
Outcome Neutrality. Regardless of the auxlang's sources and structure, learners are likely to attain near-native fluency in roughly the same time, and more quickly and easily than they could achieve such fluency in a natlang.
I tend toward Outcome Neutrality: I don't care about an auxlang's sources, just about how quickly and easily I can achieve near-native fluency. I've encountered stories of people who couldn't communicate confidently in any but their native language--and some auxlang. Struggling with a non-native language made them seem inarticulate, but in their own language and auxlang they were eloquent.
The problem is that neutrality (by any definition) varies by individual, and unlike the Initial Neutrality people, I see no way of avoiding this problem: some people will never achieve near-native fluency in certain languages. In Esperanto, such people are called "Eternaj Komencantoj," and they form the next part of the argument.
Sunday, January 16, 2011
The Curse of Datuval
Not coming soon, I hope, to a theater near any of us. As this is the Auxlang Lab, I'll be exploring design issues and offering advice to designers and learners. (I've already done a bit of this.) This post is about a common and usually fatal temptation designers face.
I'll probably go into the issues involved in Volapük's demise later, but part of the problem was Schleyer's insistence on "owning" the language. He was the "Datuval"--the Creator, and he began to confuse himself, I think, with the other Creator mentioned in Genesis. You'd think a priest would know better.
Anyway, one of the warning signs of Datuval Disease is doing your level best to restrict access to your project. Serious designers post info in hypertext, plain text, or other easily-accessible format. The control freaks lock it in secured PDFs so that no one can defile their creation.
This is a bad idea on several levels. For one thing, you shouldn't make it hard for potential learners to access your material, and they may find it useful to tweak your presentation. You may find it useful, too. Never turn down free assistance, especially when there's a good chance it will be competent--and modern early adopters often are competent in some relevant area.
Here's how you can set up your auxlang on a Datuval-free basis: start a group on Yahoo! and store your basic files (grammar, vocabulary, and sample texts) there in some user-friendly format--probably hypertext, Word, RTF, or plain text. I'll explain in a later post where to go from there.
Anyway, today's Amazing Free Clue: once you've released your auxlang, it's no longer yours; it belongs to the users. It's free to evolve independently of your wishes. It may even diverge so sharply that, in effect, your project dies or becomes dormant and something else rises from the ashes. Them's the breaks, as the saying goes. Horrible as that thought may seem, you have to release your auxlang if it is to truly be an auxlang. Otherwise you should call it an artlang and keep it to yourself. It will be a relief to all of us.
I'll probably go into the issues involved in Volapük's demise later, but part of the problem was Schleyer's insistence on "owning" the language. He was the "Datuval"--the Creator, and he began to confuse himself, I think, with the other Creator mentioned in Genesis. You'd think a priest would know better.
Anyway, one of the warning signs of Datuval Disease is doing your level best to restrict access to your project. Serious designers post info in hypertext, plain text, or other easily-accessible format. The control freaks lock it in secured PDFs so that no one can defile their creation.
This is a bad idea on several levels. For one thing, you shouldn't make it hard for potential learners to access your material, and they may find it useful to tweak your presentation. You may find it useful, too. Never turn down free assistance, especially when there's a good chance it will be competent--and modern early adopters often are competent in some relevant area.
Here's how you can set up your auxlang on a Datuval-free basis: start a group on Yahoo! and store your basic files (grammar, vocabulary, and sample texts) there in some user-friendly format--probably hypertext, Word, RTF, or plain text. I'll explain in a later post where to go from there.
Anyway, today's Amazing Free Clue: once you've released your auxlang, it's no longer yours; it belongs to the users. It's free to evolve independently of your wishes. It may even diverge so sharply that, in effect, your project dies or becomes dormant and something else rises from the ashes. Them's the breaks, as the saying goes. Horrible as that thought may seem, you have to release your auxlang if it is to truly be an auxlang. Otherwise you should call it an artlang and keep it to yourself. It will be a relief to all of us.
Friday, January 14, 2011
Levels of maturity
I'm talking about linguistic maturity, here. Auxlang users may sit around all day wearing pajamas and picking their nose for all I care. I'm trying to gauge reasonable literary projects for the better-known auxlangs and their learners. Essentially, the breakdown will be something like this:
New user/auxlang: anecdotes, proverbs, etc. (a paragraph or so)
Stable beginner (basic grammar/vocabulary, nothing fancy): flash fiction (a page or two)
Intermediate (moving beyond basics into optional gimmicks): short stories and novellas (about 10-100 pages; may include abbreviated novels)
Mature (advanced gimmicks generally well established: odd word order, etc.): novels without major linguistic complications (not Tom Sawyer, for example)
Advanced (can handle most anything)
Now let's get controversial:
Esperanto: Mature to advanced. Active users (verkistoj) are often "mature."
Ido: Intermediate to mature. Primary problem is slow lexical growth--not a linguistic failing but a flaw in Idist culture. Theoretically resolvable.
Occidental: Intermediate. This is a user-base problem; Occ is capable of advanced usage, but it lacks coherency and user base.
Interlingua: Mature to advanced. The Latin/Romance schism is a problem, but it can also be harnessed for literary purposes.
Lingua Franca Nova: Intermediate at best. Syntactic issues and user-base problems.
Lingwa de Planeta: Stable beginner (more or less) working toward intermediate status.
Sambahsa: Anomalous; the language itself is probably advanced, but the user base (apart from Dr. Olivier Simon himself) is both small and ill-equipped. This puts it on a par with some revival projects, such as Idiom Neutral, but with a better corpus.
So if you're interested in producing novels (original or translated), your best bets are Esperanto and Interlingua, though Ido and perhaps Occidental are also worth considering. If you'd rather pioneer with shorter works, try one of the less mature auxlangs.
New user/auxlang: anecdotes, proverbs, etc. (a paragraph or so)
Stable beginner (basic grammar/vocabulary, nothing fancy): flash fiction (a page or two)
Intermediate (moving beyond basics into optional gimmicks): short stories and novellas (about 10-100 pages; may include abbreviated novels)
Mature (advanced gimmicks generally well established: odd word order, etc.): novels without major linguistic complications (not Tom Sawyer, for example)
Advanced (can handle most anything)
Now let's get controversial:
Esperanto: Mature to advanced. Active users (verkistoj) are often "mature."
Ido: Intermediate to mature. Primary problem is slow lexical growth--not a linguistic failing but a flaw in Idist culture. Theoretically resolvable.
Occidental: Intermediate. This is a user-base problem; Occ is capable of advanced usage, but it lacks coherency and user base.
Interlingua: Mature to advanced. The Latin/Romance schism is a problem, but it can also be harnessed for literary purposes.
Lingua Franca Nova: Intermediate at best. Syntactic issues and user-base problems.
Lingwa de Planeta: Stable beginner (more or less) working toward intermediate status.
Sambahsa: Anomalous; the language itself is probably advanced, but the user base (apart from Dr. Olivier Simon himself) is both small and ill-equipped. This puts it on a par with some revival projects, such as Idiom Neutral, but with a better corpus.
So if you're interested in producing novels (original or translated), your best bets are Esperanto and Interlingua, though Ido and perhaps Occidental are also worth considering. If you'd rather pioneer with shorter works, try one of the less mature auxlangs.
Thursday, January 13, 2011
Dracula Lite
Not sunlight, of course. No, the solution is to abridge and simplify the sucker.
Holy water, Batman! Wouldn't that adulterate him? It sounds indecent!
No need to cast aspersions; the Count has been (mal)adapted countless times in English alone. Once more--even once per major auxlang--should do no harm. And much of the story could be left intact, including most of the main characters' dialog. This isn't Tom Sawyer, which I believe has been translated into Esperanto, and whose dialect is a major part of the story. Most of the difficult bits of Dracula could be summarized easily enough.
There would even be a useful long-term effect: when the auxlang and its user base have matured enough for the complete novel, the abridgement could be used as a basis, so only the summarized bits would need to be translated. The rest could just be tweaked a bit.
In any case, this sort of thing has already been done. One of the first long Interlingua texts I encountered online was an abridgement of Pilgrim's Progress (translated by Paolo Castellina), and there's a short version of Robinson Crusoe on the Mondlango site.
Even so, this is at least an intermediate-level project--the sort of thing suitable to Ido and Occ, for example. (As already noted, Eo and Interlingua could manage an actual translation.) Other auxlangs could technically manage it--I suspect Sambahsa could, for example--but they don't have the user base to justify it.
Next time I'll try to explain the levels of development for various auxlangs.
Holy water, Batman! Wouldn't that adulterate him? It sounds indecent!
No need to cast aspersions; the Count has been (mal)adapted countless times in English alone. Once more--even once per major auxlang--should do no harm. And much of the story could be left intact, including most of the main characters' dialog. This isn't Tom Sawyer, which I believe has been translated into Esperanto, and whose dialect is a major part of the story. Most of the difficult bits of Dracula could be summarized easily enough.
There would even be a useful long-term effect: when the auxlang and its user base have matured enough for the complete novel, the abridgement could be used as a basis, so only the summarized bits would need to be translated. The rest could just be tweaked a bit.
In any case, this sort of thing has already been done. One of the first long Interlingua texts I encountered online was an abridgement of Pilgrim's Progress (translated by Paolo Castellina), and there's a short version of Robinson Crusoe on the Mondlango site.
Even so, this is at least an intermediate-level project--the sort of thing suitable to Ido and Occ, for example. (As already noted, Eo and Interlingua could manage an actual translation.) Other auxlangs could technically manage it--I suspect Sambahsa could, for example--but they don't have the user base to justify it.
Next time I'll try to explain the levels of development for various auxlangs.
Not Bloody Likely: Translating Dracula
One of the blogs I follow is Dave MacLeod's Page F30, which is mostly about languages (including auxlangs) and astronomy. He also shows up on Auxlang a lot and isn't locked in to just one auxlang. At various points he has advocated Dracula as a translation project.
No. Let's stake this idea here and now.
* Length. Seriously, even in an at-sight auxlang, Dracula is a bit long. Serializing would help somewhat, but it's an actual novel (and nineteenth century, too), which means it has pacing appropriate for fluent readers. If you're familiar with the story, there's building tension in the first chapter that works really well, especially if you somehow don't know what Dracula is. But it would be tedious for a learner.
* Vocabulary. This, as they say on Monty Python, is the cruncher--or one of them, anyway. The terminological traps are legion: geographical fine points to begin with, but also architectural, medical, and nautical jargon. There are also a lot of letters, including period business correspondence. Ouch. Right off hand, I'd say that the only auxlangs I'd have any chance of translating Dracula into would be Esperanto and Interlingua, with a slight possibility of Occidental. In Eo I could work around the lexical problems by compounding, which is also a possibility for Occ. For Interlingua, I could use some existing translations into Romance languages as guides. (I couldn't translate Dracula into Spanish or French very well, either: I haven't the specialized vocabulary and the result would sound stilted.)
* Basilect/dialect issues. This is almost Vocabulary II: The Sequel, but there's more to it. Once Drac comes to Britain, we begin running into some amusing bits of dialect and basilect:
"I'm afraid, my deary, that I must have shocked you by all the wicked things I've been sayin' about the dead, and such like, for weeks past, but I didn't mean them, and I want ye to remember that when I'm gone. We aud folks that be daffled, and with one foot abaft the krok-hooal, don't altogether like to think of it, and we don't want to feel scart of it, and that's why I've took to makin' light of it, so that I'd cheer up my own heart a bit. ..."
Translate that (preserving the feel!) if you can.
But the other problem is that this would be dangerous for anything but a mature auxlang. How do you render "I've took to makin' light of it"? Perhaps (in Eo) "Mi 'as ade ma'gravigi tion"? This is nonstandard usage, friends, and that should be reflected in the translation. I might even drop the accusative. But beginners, especially in a young auxlang, should not be confronted with nonstandard usage: they're trying to get a grip on the standard language. (For this reason, I wouldn't use the English original with people learning English, either.)
This leaves an obvious alternative, however. I'll turn to that next.
No. Let's stake this idea here and now.
* Length. Seriously, even in an at-sight auxlang, Dracula is a bit long. Serializing would help somewhat, but it's an actual novel (and nineteenth century, too), which means it has pacing appropriate for fluent readers. If you're familiar with the story, there's building tension in the first chapter that works really well, especially if you somehow don't know what Dracula is. But it would be tedious for a learner.
* Vocabulary. This, as they say on Monty Python, is the cruncher--or one of them, anyway. The terminological traps are legion: geographical fine points to begin with, but also architectural, medical, and nautical jargon. There are also a lot of letters, including period business correspondence. Ouch. Right off hand, I'd say that the only auxlangs I'd have any chance of translating Dracula into would be Esperanto and Interlingua, with a slight possibility of Occidental. In Eo I could work around the lexical problems by compounding, which is also a possibility for Occ. For Interlingua, I could use some existing translations into Romance languages as guides. (I couldn't translate Dracula into Spanish or French very well, either: I haven't the specialized vocabulary and the result would sound stilted.)
* Basilect/dialect issues. This is almost Vocabulary II: The Sequel, but there's more to it. Once Drac comes to Britain, we begin running into some amusing bits of dialect and basilect:
"I'm afraid, my deary, that I must have shocked you by all the wicked things I've been sayin' about the dead, and such like, for weeks past, but I didn't mean them, and I want ye to remember that when I'm gone. We aud folks that be daffled, and with one foot abaft the krok-hooal, don't altogether like to think of it, and we don't want to feel scart of it, and that's why I've took to makin' light of it, so that I'd cheer up my own heart a bit. ..."
Translate that (preserving the feel!) if you can.
But the other problem is that this would be dangerous for anything but a mature auxlang. How do you render "I've took to makin' light of it"? Perhaps (in Eo) "Mi 'as ade ma'gravigi tion"? This is nonstandard usage, friends, and that should be reflected in the translation. I might even drop the accusative. But beginners, especially in a young auxlang, should not be confronted with nonstandard usage: they're trying to get a grip on the standard language. (For this reason, I wouldn't use the English original with people learning English, either.)
This leaves an obvious alternative, however. I'll turn to that next.
Wednesday, January 12, 2011
Auxlang maturity and literature
Part of the reason I've been so long in posting is my typical obsessive-compulsive problem with wanting to structure my posts. This is, however, a blog, so a "stream of consciousness" approach is eminently defensible.
As a writer and amateur literateur, I can understand the temptation to dabble in Great Projects of composition or translation in an auxlang. It's a bad idea, though. And curiously, the linguistic maturity of both auxlang and user have the same effect: younger means smaller.
The upshot is that new users and auxlangs should stick with short projects--probably just a paragraph or so. An auxlang designer may want to try something longer as a proof the auxlang works, but basically only a more advanced learner will bother reading anything over a page or so. A new auxlang has no such learners except the designer, so it's pointless to work on anything long at first.
At-sight projects skew this slightly: the less at-sight readable your project, the shorter the early texts should be. On the other hand, an at-sight project can have longer texts: Gode's Dece Contos in Interlingua are fairly reasonable both as writing and reading exercises.
Now, all this goes against the grain for newbies. "It's so easy, I bet I could do a novel!" No. Novels have all kinds of problems, even if you're just translating. Stick with short stories--the shorter the better. Otherwise you'll get a few chapters in, run into more and more difficulties, and give up.
(For readers, short chapters or sections can make even a novel seem less daunting; I've seen this sort of thing done with longer short stories and novellas on certain blogs. But the auxlang has generally been "at sight.")
What are the advantages of shorter pieces?
* Easier for writer and reader.
* Allows more variety. A novel will generally stick with a genre and setting (place and time); short pieces can cover a wider range, giving examples of numerous types of texts. How do you say, "Once upon a time"? Cliché phrases are actually useful for learners, and they only become a problem through overuse, which won't be an issue at first.
* Less likely to contain needless difficulties. I'll explain this next with a critique of Dracula as a translation project.
As a writer and amateur literateur, I can understand the temptation to dabble in Great Projects of composition or translation in an auxlang. It's a bad idea, though. And curiously, the linguistic maturity of both auxlang and user have the same effect: younger means smaller.
The upshot is that new users and auxlangs should stick with short projects--probably just a paragraph or so. An auxlang designer may want to try something longer as a proof the auxlang works, but basically only a more advanced learner will bother reading anything over a page or so. A new auxlang has no such learners except the designer, so it's pointless to work on anything long at first.
At-sight projects skew this slightly: the less at-sight readable your project, the shorter the early texts should be. On the other hand, an at-sight project can have longer texts: Gode's Dece Contos in Interlingua are fairly reasonable both as writing and reading exercises.
Now, all this goes against the grain for newbies. "It's so easy, I bet I could do a novel!" No. Novels have all kinds of problems, even if you're just translating. Stick with short stories--the shorter the better. Otherwise you'll get a few chapters in, run into more and more difficulties, and give up.
(For readers, short chapters or sections can make even a novel seem less daunting; I've seen this sort of thing done with longer short stories and novellas on certain blogs. But the auxlang has generally been "at sight.")
What are the advantages of shorter pieces?
* Easier for writer and reader.
* Allows more variety. A novel will generally stick with a genre and setting (place and time); short pieces can cover a wider range, giving examples of numerous types of texts. How do you say, "Once upon a time"? Cliché phrases are actually useful for learners, and they only become a problem through overuse, which won't be an issue at first.
* Less likely to contain needless difficulties. I'll explain this next with a critique of Dracula as a translation project.
Subscribe to:
Posts (Atom)