“The author means”, “The author writes”, “The author points out”, etc
I am currently writing a technical report. While writing the "Related work" section, I often need to write expressions as shown in the title:
"The author means that this algorithm is not suitable in all cases.",
"The author writes that..." or
"The author points out", etc.
As I am not a native English speaker, I find it hard to vary my language. I know I saw a list of many possible ways of refering to something other people has said or written, but it was not in English and it would probably not be directly translateble.
I am so sorry if there exist another question about this. Please let me know in that case, but I don't know what keywords to search for in this case. What other ways are there of refering to something someone has written or found out in their work, and what is this way of referring called (what can I search for)?
articles reference
add a comment |
I am currently writing a technical report. While writing the "Related work" section, I often need to write expressions as shown in the title:
"The author means that this algorithm is not suitable in all cases.",
"The author writes that..." or
"The author points out", etc.
As I am not a native English speaker, I find it hard to vary my language. I know I saw a list of many possible ways of refering to something other people has said or written, but it was not in English and it would probably not be directly translateble.
I am so sorry if there exist another question about this. Please let me know in that case, but I don't know what keywords to search for in this case. What other ways are there of refering to something someone has written or found out in their work, and what is this way of referring called (what can I search for)?
articles reference
I suggest taking a few of the words, in addition to those you already have, and looking up synonyms--e.g., for describes, expounds, covers, notes that, explains, takes the viewpoint, etc.
– Xanne
Apr 9 '17 at 1:54
@Xanne thank you alot, I can't believe I didn't think of that!
– Stephen Johnson
Apr 10 '17 at 8:44
1
I would avoid "the author means". It's fine to quote what the author says. Do that with "the author writes", "the author states", etc. If you employ minor paraphrasing, then "the author points out". But interpreting what the author meant is injecting your own opinion. You can do that in a discussion but not where you are simply citing the author.
– fixer1234
May 16 '17 at 18:33
add a comment |
I am currently writing a technical report. While writing the "Related work" section, I often need to write expressions as shown in the title:
"The author means that this algorithm is not suitable in all cases.",
"The author writes that..." or
"The author points out", etc.
As I am not a native English speaker, I find it hard to vary my language. I know I saw a list of many possible ways of refering to something other people has said or written, but it was not in English and it would probably not be directly translateble.
I am so sorry if there exist another question about this. Please let me know in that case, but I don't know what keywords to search for in this case. What other ways are there of refering to something someone has written or found out in their work, and what is this way of referring called (what can I search for)?
articles reference
I am currently writing a technical report. While writing the "Related work" section, I often need to write expressions as shown in the title:
"The author means that this algorithm is not suitable in all cases.",
"The author writes that..." or
"The author points out", etc.
As I am not a native English speaker, I find it hard to vary my language. I know I saw a list of many possible ways of refering to something other people has said or written, but it was not in English and it would probably not be directly translateble.
I am so sorry if there exist another question about this. Please let me know in that case, but I don't know what keywords to search for in this case. What other ways are there of refering to something someone has written or found out in their work, and what is this way of referring called (what can I search for)?
articles reference
articles reference
asked Apr 7 '17 at 14:19
Stephen JohnsonStephen Johnson
254
254
I suggest taking a few of the words, in addition to those you already have, and looking up synonyms--e.g., for describes, expounds, covers, notes that, explains, takes the viewpoint, etc.
– Xanne
Apr 9 '17 at 1:54
@Xanne thank you alot, I can't believe I didn't think of that!
– Stephen Johnson
Apr 10 '17 at 8:44
1
I would avoid "the author means". It's fine to quote what the author says. Do that with "the author writes", "the author states", etc. If you employ minor paraphrasing, then "the author points out". But interpreting what the author meant is injecting your own opinion. You can do that in a discussion but not where you are simply citing the author.
– fixer1234
May 16 '17 at 18:33
add a comment |
I suggest taking a few of the words, in addition to those you already have, and looking up synonyms--e.g., for describes, expounds, covers, notes that, explains, takes the viewpoint, etc.
– Xanne
Apr 9 '17 at 1:54
@Xanne thank you alot, I can't believe I didn't think of that!
– Stephen Johnson
Apr 10 '17 at 8:44
1
I would avoid "the author means". It's fine to quote what the author says. Do that with "the author writes", "the author states", etc. If you employ minor paraphrasing, then "the author points out". But interpreting what the author meant is injecting your own opinion. You can do that in a discussion but not where you are simply citing the author.
– fixer1234
May 16 '17 at 18:33
I suggest taking a few of the words, in addition to those you already have, and looking up synonyms--e.g., for describes, expounds, covers, notes that, explains, takes the viewpoint, etc.
– Xanne
Apr 9 '17 at 1:54
I suggest taking a few of the words, in addition to those you already have, and looking up synonyms--e.g., for describes, expounds, covers, notes that, explains, takes the viewpoint, etc.
– Xanne
Apr 9 '17 at 1:54
@Xanne thank you alot, I can't believe I didn't think of that!
– Stephen Johnson
Apr 10 '17 at 8:44
@Xanne thank you alot, I can't believe I didn't think of that!
– Stephen Johnson
Apr 10 '17 at 8:44
1
1
I would avoid "the author means". It's fine to quote what the author says. Do that with "the author writes", "the author states", etc. If you employ minor paraphrasing, then "the author points out". But interpreting what the author meant is injecting your own opinion. You can do that in a discussion but not where you are simply citing the author.
– fixer1234
May 16 '17 at 18:33
I would avoid "the author means". It's fine to quote what the author says. Do that with "the author writes", "the author states", etc. If you employ minor paraphrasing, then "the author points out". But interpreting what the author meant is injecting your own opinion. You can do that in a discussion but not where you are simply citing the author.
– fixer1234
May 16 '17 at 18:33
add a comment |
2 Answers
2
active
oldest
votes
Sorry to point this out and you’ve got that completely the wrong way round. In that context, the last thing you should be doing is varying your language. As a reader, above all I want the editor or producer to be clear and consistent, not creative.
In the very unlikely event that you ever needed to write expressions as shown in the title, such as The author means or writes or points out, why would it not be obvious that variety, style, flair and the like belong to the author in the main text and not to the editors in any ‘related work’ section… by which, d’you mean bibliography, or what, please?
If that algorithm is not suitable in all cases and that’s what the author meant, fine and when making the same kind of reference to anything else in the same reference index, appendix or ‘related work’ section, why on Earth would you change the wording?
Changing the wording in those sections won't add interest but it will often cause confusion; all the readers knew it was an appendix or index whose only purpose was to impart detailed information as clearly as possible. They all expected it to be as dull as ditch water. No-one who had the stamina to be looking in an appendix or index in the first place would be put off by repetitive wording in consecutive entries… squarely so since it’s prolly true that a majority of readers won’t be looking at every entry so for them, it matters less.
The "related work" section in many computer science technical reports is not an appendix. It's not a bibliography. It is an important part of the main text, that explains how the technical results presented in the text compare with previous results; how they build on previous results; and how they are novel. It should not deliberately be written in a deadly dull style. While you should not sacrifice clarity in order to vary your language, there is lots of room for variation that doesn't sacrifice clarity.
– Peter Shor
May 16 '17 at 18:29
add a comment |
hey y'all don't fuss and tuss imma get a bus so we can take a trip down writers work shop lane. I'm just messing with y'all if you Digg
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "97"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fenglish.stackexchange.com%2fquestions%2f382312%2fthe-author-means-the-author-writes-the-author-points-out-etc%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sorry to point this out and you’ve got that completely the wrong way round. In that context, the last thing you should be doing is varying your language. As a reader, above all I want the editor or producer to be clear and consistent, not creative.
In the very unlikely event that you ever needed to write expressions as shown in the title, such as The author means or writes or points out, why would it not be obvious that variety, style, flair and the like belong to the author in the main text and not to the editors in any ‘related work’ section… by which, d’you mean bibliography, or what, please?
If that algorithm is not suitable in all cases and that’s what the author meant, fine and when making the same kind of reference to anything else in the same reference index, appendix or ‘related work’ section, why on Earth would you change the wording?
Changing the wording in those sections won't add interest but it will often cause confusion; all the readers knew it was an appendix or index whose only purpose was to impart detailed information as clearly as possible. They all expected it to be as dull as ditch water. No-one who had the stamina to be looking in an appendix or index in the first place would be put off by repetitive wording in consecutive entries… squarely so since it’s prolly true that a majority of readers won’t be looking at every entry so for them, it matters less.
The "related work" section in many computer science technical reports is not an appendix. It's not a bibliography. It is an important part of the main text, that explains how the technical results presented in the text compare with previous results; how they build on previous results; and how they are novel. It should not deliberately be written in a deadly dull style. While you should not sacrifice clarity in order to vary your language, there is lots of room for variation that doesn't sacrifice clarity.
– Peter Shor
May 16 '17 at 18:29
add a comment |
Sorry to point this out and you’ve got that completely the wrong way round. In that context, the last thing you should be doing is varying your language. As a reader, above all I want the editor or producer to be clear and consistent, not creative.
In the very unlikely event that you ever needed to write expressions as shown in the title, such as The author means or writes or points out, why would it not be obvious that variety, style, flair and the like belong to the author in the main text and not to the editors in any ‘related work’ section… by which, d’you mean bibliography, or what, please?
If that algorithm is not suitable in all cases and that’s what the author meant, fine and when making the same kind of reference to anything else in the same reference index, appendix or ‘related work’ section, why on Earth would you change the wording?
Changing the wording in those sections won't add interest but it will often cause confusion; all the readers knew it was an appendix or index whose only purpose was to impart detailed information as clearly as possible. They all expected it to be as dull as ditch water. No-one who had the stamina to be looking in an appendix or index in the first place would be put off by repetitive wording in consecutive entries… squarely so since it’s prolly true that a majority of readers won’t be looking at every entry so for them, it matters less.
The "related work" section in many computer science technical reports is not an appendix. It's not a bibliography. It is an important part of the main text, that explains how the technical results presented in the text compare with previous results; how they build on previous results; and how they are novel. It should not deliberately be written in a deadly dull style. While you should not sacrifice clarity in order to vary your language, there is lots of room for variation that doesn't sacrifice clarity.
– Peter Shor
May 16 '17 at 18:29
add a comment |
Sorry to point this out and you’ve got that completely the wrong way round. In that context, the last thing you should be doing is varying your language. As a reader, above all I want the editor or producer to be clear and consistent, not creative.
In the very unlikely event that you ever needed to write expressions as shown in the title, such as The author means or writes or points out, why would it not be obvious that variety, style, flair and the like belong to the author in the main text and not to the editors in any ‘related work’ section… by which, d’you mean bibliography, or what, please?
If that algorithm is not suitable in all cases and that’s what the author meant, fine and when making the same kind of reference to anything else in the same reference index, appendix or ‘related work’ section, why on Earth would you change the wording?
Changing the wording in those sections won't add interest but it will often cause confusion; all the readers knew it was an appendix or index whose only purpose was to impart detailed information as clearly as possible. They all expected it to be as dull as ditch water. No-one who had the stamina to be looking in an appendix or index in the first place would be put off by repetitive wording in consecutive entries… squarely so since it’s prolly true that a majority of readers won’t be looking at every entry so for them, it matters less.
Sorry to point this out and you’ve got that completely the wrong way round. In that context, the last thing you should be doing is varying your language. As a reader, above all I want the editor or producer to be clear and consistent, not creative.
In the very unlikely event that you ever needed to write expressions as shown in the title, such as The author means or writes or points out, why would it not be obvious that variety, style, flair and the like belong to the author in the main text and not to the editors in any ‘related work’ section… by which, d’you mean bibliography, or what, please?
If that algorithm is not suitable in all cases and that’s what the author meant, fine and when making the same kind of reference to anything else in the same reference index, appendix or ‘related work’ section, why on Earth would you change the wording?
Changing the wording in those sections won't add interest but it will often cause confusion; all the readers knew it was an appendix or index whose only purpose was to impart detailed information as clearly as possible. They all expected it to be as dull as ditch water. No-one who had the stamina to be looking in an appendix or index in the first place would be put off by repetitive wording in consecutive entries… squarely so since it’s prolly true that a majority of readers won’t be looking at every entry so for them, it matters less.
edited May 16 '17 at 18:08
answered Apr 20 '17 at 22:24
Robbie GoodwinRobbie Goodwin
1
1
The "related work" section in many computer science technical reports is not an appendix. It's not a bibliography. It is an important part of the main text, that explains how the technical results presented in the text compare with previous results; how they build on previous results; and how they are novel. It should not deliberately be written in a deadly dull style. While you should not sacrifice clarity in order to vary your language, there is lots of room for variation that doesn't sacrifice clarity.
– Peter Shor
May 16 '17 at 18:29
add a comment |
The "related work" section in many computer science technical reports is not an appendix. It's not a bibliography. It is an important part of the main text, that explains how the technical results presented in the text compare with previous results; how they build on previous results; and how they are novel. It should not deliberately be written in a deadly dull style. While you should not sacrifice clarity in order to vary your language, there is lots of room for variation that doesn't sacrifice clarity.
– Peter Shor
May 16 '17 at 18:29
The "related work" section in many computer science technical reports is not an appendix. It's not a bibliography. It is an important part of the main text, that explains how the technical results presented in the text compare with previous results; how they build on previous results; and how they are novel. It should not deliberately be written in a deadly dull style. While you should not sacrifice clarity in order to vary your language, there is lots of room for variation that doesn't sacrifice clarity.
– Peter Shor
May 16 '17 at 18:29
The "related work" section in many computer science technical reports is not an appendix. It's not a bibliography. It is an important part of the main text, that explains how the technical results presented in the text compare with previous results; how they build on previous results; and how they are novel. It should not deliberately be written in a deadly dull style. While you should not sacrifice clarity in order to vary your language, there is lots of room for variation that doesn't sacrifice clarity.
– Peter Shor
May 16 '17 at 18:29
add a comment |
hey y'all don't fuss and tuss imma get a bus so we can take a trip down writers work shop lane. I'm just messing with y'all if you Digg
New contributor
add a comment |
hey y'all don't fuss and tuss imma get a bus so we can take a trip down writers work shop lane. I'm just messing with y'all if you Digg
New contributor
add a comment |
hey y'all don't fuss and tuss imma get a bus so we can take a trip down writers work shop lane. I'm just messing with y'all if you Digg
New contributor
hey y'all don't fuss and tuss imma get a bus so we can take a trip down writers work shop lane. I'm just messing with y'all if you Digg
New contributor
New contributor
answered 3 hours ago
Johnson BilldagerJohnson Billdager
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to English Language & Usage Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fenglish.stackexchange.com%2fquestions%2f382312%2fthe-author-means-the-author-writes-the-author-points-out-etc%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I suggest taking a few of the words, in addition to those you already have, and looking up synonyms--e.g., for describes, expounds, covers, notes that, explains, takes the viewpoint, etc.
– Xanne
Apr 9 '17 at 1:54
@Xanne thank you alot, I can't believe I didn't think of that!
– Stephen Johnson
Apr 10 '17 at 8:44
1
I would avoid "the author means". It's fine to quote what the author says. Do that with "the author writes", "the author states", etc. If you employ minor paraphrasing, then "the author points out". But interpreting what the author meant is injecting your own opinion. You can do that in a discussion but not where you are simply citing the author.
– fixer1234
May 16 '17 at 18:33