Character names: Unpronounceables, Apostrophes and Foreign Accents are neck tattoos.
edmcdonaldwriting.com/2016/11/19/unpronouncea...Posted Nov 23, 2016, 7:37 AM UTC
Posted Nov 23, 2016, 7:37 AM UTC
The author makes a good point, but I think there is an argument to be made against such an anglocentric view.
First and foremost if you are writing something you want to read, then someone else will want to read it to (big number statistics...).this doesn't mean that it'll sell a million copies, but writing isn't about that.
Second, embracing other cultures and mindsets is so important. Especially if your protagonist is a human (an English speaker) and they encounter an ancient and powerful race (perhaps with Hindu names and culture), then it becomes important that the difference exists. And the story can serve as a metaphor for real cultures, thereby educating someone on a more worldly perspective from the comfort of their own home.
Finally, a concession: If you are trying to appeal to the largest audience from a US/UK publisher, stick with simple English. If you are going to stray away from that, then do what I mentioned in the second point: Introduce a strong sense of normal English before going into the deeper complexities of another culture and language. This feels real to life no matter what your background because everyone things their language/culture is normal and that another language/culture is foreign.
Don't not do something because someone on the internet told you not to. Or even because a famous author told you not to. Break the mould, just accept that doing so will not always result in success.
I'd stay away from 'representing' Hindu and Indian culture with another race. That could get messy.
Fantasy nowadays does draw on other cultures (increasingly so), but it does so mostly through diversity in human characters rather than assigning other cultures to races. I quite enjoyed what I read of Kate Elliott's fantasy setting with a gradient between a traditional European culture and a West/South/East Asian influence interacting.
I also think that if we continue to bend to the idea that our work should be Anglocentric, nothing will change. There's an awful lot more diversity in fantasy than this post suggests - Mark Lawrence wrote Jalan Kendeth as half-Italian, half-Indian; he and Kate Elliott are both trade-published - and reducing other cultures to 'races' is a bit reductive.
I think the point of the article stands (don't overdo the apostrophes - unless you're writing in Ukrainian!) - but I think this is neglecting a lot of the burgeoning diversity in fantasy.
100% agreed here.
I get where the writer is coming from - weird-looking names can be difficult and are often red flags to agents - but I wouldn't go so far as to say that "Amélie" is an unpronounceable. Counterpoints:
What’s important is that you give the reader an excellent experience.
An excellent experience, to me, doesn't mean replacing every slightly unusual name with Chad and Jessica.
Well said.
Also, a lot of non-English speakers read in English.
This is drivel. How can this person claim to be a writing professor? Not only is their blog ugly to read, irritatingly informal but also extremely anglocentric. Seriously, you don't even know what to do with umlauts?! There is an entire world out there, it doesn't need to be fantasy to use sounds outside of the proscriptive English phonetic dictionary.
You can disagree and slam the author all you want, but he makes a very good and real point.
I didn't find the informality irritating or the website "ugly to read". Maybe you were just in a bad mood when you read it?
I think the anglocentric angle comes from his intention to give advice to writers of English: "If you are writing in English, then that means English punctuation." That seems fair to me. He's manifestly not talking about limiting yourself to anglocentric content, he's just asking that you render that content in a manner that is appropriate for English reading audiences. That seems fair to me.
I agree with the general point he is making.
Yeah. Even with foreign names, I don't use other diacritics than an English language speaker would expect to encounter. The only one I do use is the acute accent, and then only when necessary.
I think this article refers to a specific subset of names. If you're writing international historical fiction you can probably push the boat out a bit to make names fit the setting. I'm reading Ayse Kulin's Last Train to Istanbul and the names are fine by me.
I know it's just a placeholder - I'd expect a fantasy name to be a bit more exotic than Dylan. Strikes me as a bit ordinary. In practice, as most published fantasy proves, you can have more artful names and not go too wrong. To have an exotic, mysterious setting but characters named Bill and Ted would break suspension of disbelief as much as an ott fantasy name.
But I completely understand the sentiment. Too much exoticism for not enough benefit gets confusing.
Just keep in mind: Ano != Año.
?
Well yes I was definitely in a bad mood when I read it so I have to concede that one. I could have taken more time to argue my point rather than attack. I stand by my point that it's anglocentric though.
Names like Kx'ñmglàr may be a bit 'try-hard' but at the same time I find the author's point to be a step too far and even patronising . I've never put down a book due to a character's name being foreign to me nor have I heard of someone else doing so.
To rule out all sounds and structures outside of the English language is at best needlessly limiting and at worst overtly anglocentric. English is a living, global language used by millions as a second or third language. It has also eaten the dictionaries of multiple cultures along the way. This is one of its strengths, not something to be policed.
You've never had "that professor"?
pingüino
maïs
coöperate
schön
Häagen-Dazs
Onödowá'ga:'
If you didn't know anything about the languages the above words came from, would you know what you were supposed to do with those umlauts?
Haagen-Dazs is made up, but I understand your point. However, there's a long way between that and 'Dylan'.
I'm not sure I understand your point.
Basically - excluded middle. There's enough space for Jalan, Kvothe and even Agnieszka (Uprooted) before we get to unpronounceable.
A fantasy hero called Dylan isn't going to be the thing that makes me pick up the book (mainly because I'm gonna think 'portal fantasy', but also because it's so ...boring).
Not really getting at you, though. More talking about the article in general and how it completely ignores the big gulf between Dylan and Dyy'Laene.
Well I could take inspiration and endeavour to find out. Google perhaps? Then I could continue reading with added investment as the author had exposed me to something new.
Or I'm one of the millions of people who speak English but who do not come from the UK,US or Commonwealth and I don't even notice in the first place...
Well I could take inspiration and endeavour to find out. Google perhaps?
But, if you're reading a made up language, you won't have the luxury of Google. Unless the author includes a pronunciation key in the back, you will never know how you're supposed to pronounce them. In case you didn't realize it, the umlauts/diareses above do not do the same thing in each case.
I nearly always use real world names, even in fantasy settings. Trying anything else nearly always ends up sounding incredibly silly.
And that's without going into all the stuff this article writes about.
In fantasy settings, I just use older names. I can't be arsed making up new names.
You can use a tool like this to declare a bunch of rules for how syllables in your fantasy-language are constructed, and then generate a list of words. If the consonants and vowels you choose are all pronounceable by English speakers, then you can have words that “sound foreign” (and even sound like they come from the same foreign language) without giving your reader a headache.