![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Entry tags:
grepping and groping (i got overly excited about words again oops)
So in the Viz translation of the Wolf's Rain manga, they did an odd thing with chapter titles—instead of labeling things "chapter 1," chapter 2," etc, each section was titled "grope 1," grope 2," etc.
There was a translator's note that explained this odd naming convention. Evidently, the original Japanese also used a non-standard word to label the chapters; it used a word that meant something to the effect of "to reach a point at the end of a long struggle." The translator chose to render this as "grope," I imagine, as a closest approximation to the original Japanese while remaining concise. One problem, though: your first thought upon seeing the word "grope" all by its lonesome was probably "ew is there some molester person in this manga." Alas, connotations.
It's unfortunate that "grope" has such ugly connotations, because I adore the lovely and shadowy connotations of "grope" when put in a context like "groping through the darkness for the key"—it implies blindness, struggle, indeterminateness, a question and a quiet fear. It implies grasping with hands, implies physicality, moreso than say, "struggle," which is just generalized striving. I liked how it fit with the travel/quest plotline of Wolf's Rain—with the translator's context in mind, seeing it after every chapter gave me this small sense of relief, a small outbreath. It went a long way toward implying that some big, exhausting struggle had just happened, and a big exhausting journey was still ahead.
I was thinking about this today because there's a Unix function—"grep"—which also means something like "to search," and sounds a bit like "grope." In technical use, grep is a terminal command that lets you search for a particular word or words within a bunch of files. If I type, say, "grep -r ponies ./ponypalace" into a terminal, it searches the ponypalace folder for all instances of the word "ponies." It's super-useful when you're programming, to figure out where a particular function or class was first defined, all of the files that use a particular object, changing variable names, and so on.
But, if you hang out around programmers who only ever talk with other programmers and should really go outside sometimes (aka, me), they'll sometimes use grep in slangy ways, or in non-technical contexts. "I was grepping around my homedir," is a perfectly acceptable technical use of the term, but then they'll be like "ugh I need to grep my bookshelf for that Knuth book," which is obviously non-technical. It's not really done self-consciously or ironically, either, unlike "lol I'd fork your repo"-style jokes. It's just a part of the vocabulary—you spend so much time grepping at the terminal that you start grepping in real life, too.
Me? I like "grep" as a word a lot. I like that it sounds a bit like "grope," and it makes me think of some of those lovely connotations I mentioned before. I like that it has the same vowel as the word "trek," that it's nearly a slant-rhyme for "trek," as it implies something a bit grander in scope. Trekking. It's fitting—grepping through a really huge file tree does feel pretty grand.
Grep isn't quite grope, obviously. When I think about the two side-by-side, I think grep sounds a bit more focused, a bit more purposeful. But not in the sense of say, find or strive. Striving has an end goal, a plan, and exertion as its primary characteristic. In Unix, you're generally grepping to find all instances of something, or to figure out where to look more closely—it's a purposeful but scattershot search, broad in scope and often experimental.
But grep is a weird word, by conventional standards, and though hearing someone use "grep" as a verb scarcely makes me blink anymore, I imagine for most other people, it sounds cyberpunky and unnatural. Like a word you'd see on one of those standardized tests with the fake words and fake definitions you have to memorize. Lep and bloy and plam and grep.
Two takeaways from this: first, I think this kind of, in a roundabout way, speaks to the difficulty that science fiction writers face when they try to spin up a jargon or set of science-y words for their universe. Like, they have to do that to an extent, right—if people are still talking about space shuttles and the internet and headphones in the year 3030, I'm not gonna totally believe you. But to my ear, 99% of the time the made-up terms ends up sounding like unnatural gobbledegook.
But dude, for a long time I thought my mathsci colleagues were speaking unnatural gobbledegook, too, and that was a real, actually extant jargon. I remember making fun of an especially math-y, cs-y friend for using "orthogonal to" and "increasing monotonically" and "ping" and so on in casual speech, when we first started hanging out freshman year of college; after about a year of hanging around him and doing All The Maths and All The Computer Science, I sounded a whole hell of a lot like him.
In theory, fantasy writers have this problem too, but rather than face it head-on, they tend to reserve the weird made-up words for magic incantations that are meant to be nonsensical anyway, and just resort to pseudo-Early-Modern-English for the rest. Sometimes they substitute "by the goddess" or "hellfires" in place of actual swearywords, but those never feel quite natural, either, which just goes back to proving how hard this inventing-a-jargon thing is.
But the other takeaway, which is really the point of this whole ramble, is: I want to fast-forward fifty years so I can use "grep" in standard prose without sounding like a fucking blockhead, because I'm totally writing a story right now where grep would be a rather interesting and lovely word in this one sentence if it were actually in common colloquial use and had the connotations I imagine it to have, and clearly fifty years from now everyone will be using Unix and contributing to Viva La Revolution Open Source so it will totally be a colloquial term by then, am I right or what.
There was a translator's note that explained this odd naming convention. Evidently, the original Japanese also used a non-standard word to label the chapters; it used a word that meant something to the effect of "to reach a point at the end of a long struggle." The translator chose to render this as "grope," I imagine, as a closest approximation to the original Japanese while remaining concise. One problem, though: your first thought upon seeing the word "grope" all by its lonesome was probably "ew is there some molester person in this manga." Alas, connotations.
It's unfortunate that "grope" has such ugly connotations, because I adore the lovely and shadowy connotations of "grope" when put in a context like "groping through the darkness for the key"—it implies blindness, struggle, indeterminateness, a question and a quiet fear. It implies grasping with hands, implies physicality, moreso than say, "struggle," which is just generalized striving. I liked how it fit with the travel/quest plotline of Wolf's Rain—with the translator's context in mind, seeing it after every chapter gave me this small sense of relief, a small outbreath. It went a long way toward implying that some big, exhausting struggle had just happened, and a big exhausting journey was still ahead.
I was thinking about this today because there's a Unix function—"grep"—which also means something like "to search," and sounds a bit like "grope." In technical use, grep is a terminal command that lets you search for a particular word or words within a bunch of files. If I type, say, "grep -r ponies ./ponypalace" into a terminal, it searches the ponypalace folder for all instances of the word "ponies." It's super-useful when you're programming, to figure out where a particular function or class was first defined, all of the files that use a particular object, changing variable names, and so on.
But, if you hang out around programmers who only ever talk with other programmers and should really go outside sometimes (aka, me), they'll sometimes use grep in slangy ways, or in non-technical contexts. "I was grepping around my homedir," is a perfectly acceptable technical use of the term, but then they'll be like "ugh I need to grep my bookshelf for that Knuth book," which is obviously non-technical. It's not really done self-consciously or ironically, either, unlike "lol I'd fork your repo"-style jokes. It's just a part of the vocabulary—you spend so much time grepping at the terminal that you start grepping in real life, too.
Me? I like "grep" as a word a lot. I like that it sounds a bit like "grope," and it makes me think of some of those lovely connotations I mentioned before. I like that it has the same vowel as the word "trek," that it's nearly a slant-rhyme for "trek," as it implies something a bit grander in scope. Trekking. It's fitting—grepping through a really huge file tree does feel pretty grand.
Grep isn't quite grope, obviously. When I think about the two side-by-side, I think grep sounds a bit more focused, a bit more purposeful. But not in the sense of say, find or strive. Striving has an end goal, a plan, and exertion as its primary characteristic. In Unix, you're generally grepping to find all instances of something, or to figure out where to look more closely—it's a purposeful but scattershot search, broad in scope and often experimental.
But grep is a weird word, by conventional standards, and though hearing someone use "grep" as a verb scarcely makes me blink anymore, I imagine for most other people, it sounds cyberpunky and unnatural. Like a word you'd see on one of those standardized tests with the fake words and fake definitions you have to memorize. Lep and bloy and plam and grep.
Two takeaways from this: first, I think this kind of, in a roundabout way, speaks to the difficulty that science fiction writers face when they try to spin up a jargon or set of science-y words for their universe. Like, they have to do that to an extent, right—if people are still talking about space shuttles and the internet and headphones in the year 3030, I'm not gonna totally believe you. But to my ear, 99% of the time the made-up terms ends up sounding like unnatural gobbledegook.
But dude, for a long time I thought my mathsci colleagues were speaking unnatural gobbledegook, too, and that was a real, actually extant jargon. I remember making fun of an especially math-y, cs-y friend for using "orthogonal to" and "increasing monotonically" and "ping" and so on in casual speech, when we first started hanging out freshman year of college; after about a year of hanging around him and doing All The Maths and All The Computer Science, I sounded a whole hell of a lot like him.
In theory, fantasy writers have this problem too, but rather than face it head-on, they tend to reserve the weird made-up words for magic incantations that are meant to be nonsensical anyway, and just resort to pseudo-Early-Modern-English for the rest. Sometimes they substitute "by the goddess" or "hellfires" in place of actual swearywords, but those never feel quite natural, either, which just goes back to proving how hard this inventing-a-jargon thing is.
But the other takeaway, which is really the point of this whole ramble, is: I want to fast-forward fifty years so I can use "grep" in standard prose without sounding like a fucking blockhead, because I'm totally writing a story right now where grep would be a rather interesting and lovely word in this one sentence if it were actually in common colloquial use and had the connotations I imagine it to have, and clearly fifty years from now everyone will be using Unix and contributing to Viva La Revolution Open Source so it will totally be a colloquial term by then, am I right or what.
no subject
But WORDS, yay! The problem with any terminology that relies so heavily on context is that it's so dependent on the author knows their audience enough to know that they'll be able to infer whatever subtle connotations the author's carefully chosen words imply. That probably goes without saying, but I consider it more elegant to evoke a strong mental image or visceral reaction with a few common, short words than one single more esoteric term.
(I used to think "emeraldine" was a perfectly valid term for a deep, lustrous shade of green, I mean god wtf, me?)Even before semantic drift kicks in, there's a connotation drift kicking in. I still clearly remember a time when "queer" was an acceptable synonym for "strange" and not completely supplanted by the modern definition of "LGBT issues." So I guess the point I'm trying to make is, by the time "grep" becomes common parlance, the rest of the sentence that word fits perfectly in will all be antiquated. ;P
...first, I think this kind of, in a roundabout way, speaks to the difficulty that science fiction writers face when they try to spin up a jargon or set of science-y words for their universe
I think I remember Anthony Burgess (the guy who wrote Clockwork Orange) saying he invented such an out-there slanguage in order to keep it timeless and unfamiliar. To avoid the linguistic equivalent of zeerust I guess.
On a side note, not knowing any of the context, I probably would have translated those chap. titles as something a little less esoteric: "Ordeal #" or "Catharsis #", maybe? Trade some of the connotation of literal movement/grasping towards a goal for a more clearly metaphorical movement forward. Plus "grope" is just a terrible chapter title, I mean really.
no subject
I think the proper use of these kinds of words ought to understand why the participants talk that way and how the new word differs from old ones. Like, a mathy person giving directions to some random person on the elevator probably isn't going to be like, "Go straight down this hall until you come to an orthogonal intersection and make a half-pi rotation." One, they *know* the other person isn't going to catch that, and two, the use of technical terminology honestly doesn't give any benefit here. "Go down the hall and take the first left" is not only simpler, but more accurate. In contrast, grepping a bookshelf, as you say, describes a particular activity that's not quite *finding* the book (because it might not be there) and isn't quite *scanning* the bookshelf (because you do more book plucking and checking), so when you're looking at the bookshelf for a book of a particular size and plucking them out to check if they're the right ones, here "grepping" is genuinely more accurate.
So tl;dr I think there's a certain level of playfulness, but calling on technical concepts is useful in the presence of others who understand them when other descriptors seem more cumbersome. ("Then slice the tomato orthogonally...")
no subject
I think I've seen the word Lua's talking about, though I can't seem to find Wolf's Rain raws. The word specifically refers to not the movement, but the point at which the journey is finally over. "Arrival" is far more mundane but probably closer than any of the above. Of the evocative ones I like "Catharsis" best though it's not quite accurate.
I'm with you both in that "grope" is a terrible choice. The "groping around in the darkness" meaning is way, way less mentally prominent than the molestation.
no subject
Math words are so handy, yo.
no subject
Note: I have never actually read or watched A Clockwork Orange.
But! That actually reminds me a bit of what Yuki Kajiura does with a lot of her music; she writes a lot of stuff in this "Kajiuraese" language she made up, aiming to sound pleasing to the ear. I do think it's a more amusing idea than always relying on Latin to be the incomprehensible music-y language :P