Re: if meaning "married" works against it ...
in reply to a message by noel
For me, sound is more important than meaning. You can tell me a name means "hideous witch demon who eats children", but if I love the way it sounds, I'll put it on my PNL and even consider it for a child. I might even like it MORE than a name with a vanilla meaning, like "beautiful meadow" or "born by the riverside", or whatever. At least it's a little different, you know?
* The Poster Formerly Known As Billina *
* The Poster Formerly Known As Billina *
This message was edited 11/26/2015, 10:12 AM
Replies
Yeah, a nice meaning might be a plus, but what really counts is the sound.
A name would need to have a truly appalling meaning for me to rule it out if I liked it otherwise. On the other hand, there are plenty of names that have lovely meanings but that I really don't like the look and sound of, so I'd never use them.
A name would need to have a truly appalling meaning for me to rule it out if I liked it otherwise. On the other hand, there are plenty of names that have lovely meanings but that I really don't like the look and sound of, so I'd never use them.
I agree?
Sort of. I wouldn't want to use a name that meant "disease" or "trash", even if I loved the sound.
Sort of. I wouldn't want to use a name that meant "disease" or "trash", even if I loved the sound.
TRUTH
I was pretty upset to see that Cormac's meaning on the site has changed from "son of defilement" to "raven/wheel?? + son". Oh Cormac, you were so metal. So metal.
I was pretty upset to see that Cormac's meaning on the site has changed from "son of defilement" to "raven/wheel?? + son". Oh Cormac, you were so metal. So metal.