> Sometimes you have to use brackets anyway. Maybe the speaker or writer was using an acronym or a completely unfamiliar piece of jargon that the reader needs explained. Maybe they were referring to a person by their last name or nickname, when the reader has not yet been introduced to the person’s full name. But these changes should be both necessary and obvious.
Not quite explicitly, but it isn't a far leap from "referring to a person by their last name or nickname" to pronouns.
"It's an older code, sir, but it checks out", the officer said, referring to the stolen access code Han had just provided, stolen from god knows where, god knows how long ago.
See, now the original quote is undisturbed and the added context is less authoritative (on purpose), since it is not inserted into the quote. The provenance of all the information is clear.
Personally I think the only brackets we should use in quotes are [sic], indicating an error in the original. Otherwise we are on the slippery slope to, "oh, what they really meant to say is [phrase phrase phrase]".
The primary usage I see of this is to replace some second or third person pronoun with the actual name of the person, which is much simpler than appending a short biography of the person and trivially easy to verify.
Overwriting the quote makes the expression unclear, which does require readers seek original expressions or otherwise speculate.
I think back to the one period after sentence move we've seen play out for a while now.
When two spaces are used, end of sentence is a parsable thing, easily differentiated from other uses, such as abbreviations.
Without them, assistive technology gets capitalization wrong all the time.
This kind of thing makes problem spaces way larger and more complicated than they need to be.
In your second example, the quote is clear, verbatim as quotes are intended to be.
In the first example, what has been clear, precise syntax is not a matter of ambiguity.
In your example, it's somewhat clear, but inference is required to understand what was said.
The example given in the article actually does bring genuine ambiguity to what would otherwise be a precise, easily understood expression:
They may groan when Corky, denied the massive funding he’s asked for, tells the town council he’s going to “go home and bite [his] pillow,” the way I do now.
Did Corky say, "go home and bite pillow" broken English style?
Or, did Corky say something else?
Until this construct, we would know because "[his]" would be added into quote context. It would not be a modifier, essentially hiding or changing the quote.
Notably, what Corky did say isn't actually present in the expression, meaning we have to now trust the author interpreting things for us.
Breaking the line with how brackets are used is going to lead to significantly increased ambiguity, and that's going to happen because it will be employed to spin or otherwise manage far less trivial examples, and sorting it out will all take considerably more effort than it all would otherwise be, given brackets are never normally used to modify a quote itself.
And all for a bit of flow? I don't buy it. The whole affair diminishes how robust brackets are and introduced ambiguity into expression that does not add any real value.
Replacing a word breaks the syntax and brings ambiguity to some use cases involving brackets and quotes that did not have it before.
As I mentioned elsewhere, a similar thing happened with the one space vs. two spaces to end a sentence.
In that last sentence, there is now ambiguity after "vs. " where there was not before. Right now I am on desktop, but if I were to input that sentence on my Android, "two" would be auto-capitalized, even though I am mid sentence.
I see this headed a similar direction.
Cases where the actual verbatim expression may be made more clear with something added in brackets will now overlap with cases where someone wants to replace a word in a quote...
Sigh :(
Spitballing:
"It is not worth doing," she said, [it=foobar].
We do this all the time in programming languages. Without introducing too much syntax, this is doable.
If you're just going to use it once, or if all usages have `[it=foobar]`, I don't think you'd do it.
I could imagine doing something like what you mention if I had moved code from another context, and I wanted to have a commit that shows plainly that it was moved verbatim. But then I'd make subsequent commit where I do the necessary substitution.
If you never pulled out code into its own separate function just in order to name some lines of code, you should give it a try. You can avoid a lot of comments and/or confusion by just structuring your code in a way that allows you to name lines of code as concepts and abstractions. No need for it to happen more than once for you to do so.
But I don't understand your point in bringing it up here.
> "It is not worth doing," she said, [it=foobar]
baz(it) = "$it is not worth doing"
baz("foobar")
`it` is neither a descriptive identifier, nor did I see a suggestion for what the function `baz` could be called to make it descriptive.Slippery slope arguments tend to ignore that if a result is actually unconscionable then regardless of the apparent slope we'll still actually stop somewhere. Additionally, they often could be applied just as well in reverse, indicating some sort of flaw in the reasoning: "We can no longer even substitute proper nouns into our quotations: how long is it till we can't use 'sic', and from there it's a slippery slope to not being able to fully quote people at all for fear of misrepresentation."
In this case though, what would be so bad about the use of brackets changing over time? Changes don't happen in isolation, so presumably people would adapt, recognizing that the author's interpretation probably plays a key role (much as it already does because of the author choosing the context to omit and the new home for an unsuspecting snippet).
Using them this way breaks that and renders both past and future text less clear, and does not add real value otherwise.
Real ambiguity becomes codified into otherwise precise expression.
I disagree. The point of the slippery slope argument is that no one knows where we'll stop, or if at all. We should be cautious in ever starting sliding.
As Einstein put it, "[Grammar nazis] are [really the worst]."
So resolving the pronoun with square brackets can be less confusing, to say nothing of the benefits of brevity.
It depends on the native language. Spanish is flexible to a fault, so "a huge orange cat", "an orange huge cat", and even "a cat orange huge" are easy to understand... but correctly translating "un enorme gato naranja" to English is the hard part.
> The Elements of Eloquence: How to Turn the Perfect English Phrase by Mark Forsyth. "Adjectives absolutely have to be in this order: opinion-size-age-shape-colour-origin-material-purpose Noun. So you can have a lovely little old rectangular green French silver whittling knife. But if you mess with that order in the slightest you’ll sound like a maniac."
> He said he was going to "post this on HN [Hacker News] right away."
Of course, there are often other ways to do that:
> He said he was going to "post this on HN right away," referring to the website Hacker News.
As an additional device, [sic] is also helpful to indicate an original typo or improper usage not by the quoter.
How ever there is a question should you take more care in writing when some of your audience has English as a second language?
I disagree. I think interviews are critical tool of discourse!
(I'm kidding...to your point)
I think it's extra prevalent now when there is so much video media that users want to get summarized for them. It takes longer to watch a video than to read a summary from someone whose viewpoint I already align with to make a judgment about the video.
This discussion about citation/quoting/primary sources makes me recall university days when (as a student of history) I tried to cite a DVD as a source. But, the professor's required Style guide made no provisions for the media type. Thus, there was pressure to either quote from a book (either written by the person being quoted or from a secondary source quoting the person) rather than transcribing the quote from the visual source I was verifying myself: literally seeing the person I was quoting say the exact words.
Of course it's better to find a quote that can stand alone, but if you can't do that — say, because there's a pronoun that refers to something too far away from the phrase of interest to include — then use brackets, ellipses, and so on.
From TFA:
> Sometimes you have to use brackets anyway. Maybe the speaker or writer was using an acronym or a completely unfamiliar piece of jargon that the reader needs explained. Maybe they were referring to a person by their last name or nickname, when the reader has not yet been introduced to the person’s full name. But these changes should be both necessary and obvious.
Edit: All you lazy copy-paste writers downvoting all the comments here that propose paraphrasing instead of quoting: I see you.
Disagree; adding context or identifying of an unusual pattern as part of the quote is common practice
> Less reason...
> Let’s [sic] your reader see...
These two points are at odds with each other - and how would my reader understand the contrast between the source and my interpretation without knowing the source?
A larger quote would still be arbitrarily cut out of a larger context. If you're extending past the good part purely to get a subject I'd even say it ends up more arbitrary.
Unless you're taking a test, you don't need to prove you understood it, and if your reader lacks confidence in your understanding then paraphrasing makes the problem worse! Instead of merely worrying you missed important context, now they have to worry you completely altered the meaning.
Paraphrasing can mangle words so easily. I'm baffled why you would imply otherwise.
And your edit just makes you look stupid.
I was tempted to reply to this by throwing etiquette out of window, but that would get me downvoted to hell. Because there is an etiquette.
> Paraphrasing can mangle words so easily. I'm baffled why you would imply otherwise.
When I paraphrase someone, they're my words. Not the original author's. I take responsibility for them.
> And your edit just makes you look stupid.
You're right down there with me. Welcome.
There is. But "It's bad because it's bad etiquette", with no further elaboration or citation, is a pretty useless claim.
I think it’s more faithful to the original, at a slight cost of fluid readability, which is often a good trade-off of features.
Frankly, implying otherwise diminishes the language.
Edit: All of which is why the article was written. People changing quotes, wrapping it in brackets so it flows better, in their view.
That's a mess!
Others here, myself included, correctly maintain appropriate bracket use does not change a quote, which is true until this garbage.
So quoting the last clause in the above paragraph, I might write
> when the author refers to [the subject] only implicitly.
The obvious alternative is to quote a longer passage. Maybe this is one of those cases where conciseness fights with authenticity.
Another solution might be to substitute in the subject and just not indicate it with brackets. That certainly reads easier, but risks hiding a common type of misunderstanding.