How to use 2 footnotes in the same word?
I have this Paragraph and I was wondering if it's possible to do what is underlined in the figure (RED), or if you know how to do this in another way, let me know. Basically the "DOM.Element" is a child of WEB API. So there are 2 things there. The "DOM" & "Element".
How to use multiple footnotes in this case? Is that a good way of doing it? TBH I haven't seen anything like it before.
For the LaTex folks:
As mentioned above, the design is created due to the reference of Cascade Style Sheets (CSS3) in a HyperText Markup Language (HTML5). This will assign different design commands for every
textit{
DOMfootnote{ Document Object Model (DOM) - url{https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model}}
.Elementfootnote{ Element - url{https://developer.mozilla.org/en-US/docs/Web/API/Element}}
}
individually, or in a form of a group using textit{Element.id} and/or textit{Element.className}.The benefit of using CSS at this stage is that it loads the styles of the elements before the page loads on the user's screen.
footnotes
migrated from english.stackexchange.com 5 hours ago
This question came from our site for linguists, etymologists, and serious English language enthusiasts.
add a comment |
I have this Paragraph and I was wondering if it's possible to do what is underlined in the figure (RED), or if you know how to do this in another way, let me know. Basically the "DOM.Element" is a child of WEB API. So there are 2 things there. The "DOM" & "Element".
How to use multiple footnotes in this case? Is that a good way of doing it? TBH I haven't seen anything like it before.
For the LaTex folks:
As mentioned above, the design is created due to the reference of Cascade Style Sheets (CSS3) in a HyperText Markup Language (HTML5). This will assign different design commands for every
textit{
DOMfootnote{ Document Object Model (DOM) - url{https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model}}
.Elementfootnote{ Element - url{https://developer.mozilla.org/en-US/docs/Web/API/Element}}
}
individually, or in a form of a group using textit{Element.id} and/or textit{Element.className}.The benefit of using CSS at this stage is that it loads the styles of the elements before the page loads on the user's screen.
footnotes
migrated from english.stackexchange.com 5 hours ago
This question came from our site for linguists, etymologists, and serious English language enthusiasts.
add a comment |
I have this Paragraph and I was wondering if it's possible to do what is underlined in the figure (RED), or if you know how to do this in another way, let me know. Basically the "DOM.Element" is a child of WEB API. So there are 2 things there. The "DOM" & "Element".
How to use multiple footnotes in this case? Is that a good way of doing it? TBH I haven't seen anything like it before.
For the LaTex folks:
As mentioned above, the design is created due to the reference of Cascade Style Sheets (CSS3) in a HyperText Markup Language (HTML5). This will assign different design commands for every
textit{
DOMfootnote{ Document Object Model (DOM) - url{https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model}}
.Elementfootnote{ Element - url{https://developer.mozilla.org/en-US/docs/Web/API/Element}}
}
individually, or in a form of a group using textit{Element.id} and/or textit{Element.className}.The benefit of using CSS at this stage is that it loads the styles of the elements before the page loads on the user's screen.
footnotes
I have this Paragraph and I was wondering if it's possible to do what is underlined in the figure (RED), or if you know how to do this in another way, let me know. Basically the "DOM.Element" is a child of WEB API. So there are 2 things there. The "DOM" & "Element".
How to use multiple footnotes in this case? Is that a good way of doing it? TBH I haven't seen anything like it before.
For the LaTex folks:
As mentioned above, the design is created due to the reference of Cascade Style Sheets (CSS3) in a HyperText Markup Language (HTML5). This will assign different design commands for every
textit{
DOMfootnote{ Document Object Model (DOM) - url{https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model}}
.Elementfootnote{ Element - url{https://developer.mozilla.org/en-US/docs/Web/API/Element}}
}
individually, or in a form of a group using textit{Element.id} and/or textit{Element.className}.The benefit of using CSS at this stage is that it loads the styles of the elements before the page loads on the user's screen.
footnotes
footnotes
asked 5 hours ago
Loizos Vasileiou
migrated from english.stackexchange.com 5 hours ago
This question came from our site for linguists, etymologists, and serious English language enthusiasts.
migrated from english.stackexchange.com 5 hours ago
This question came from our site for linguists, etymologists, and serious English language enthusiasts.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Just use "DOM element" instead.
"DOM.Element" is not actually a word. It is way used to represent a DOM element in a programming context. In that context it would indeed behave like word and your usage might be correct.
However the sentence or the text is not in that kind of context. If it was you'd have no need to footnote either "DOM" or "Element". This is a general explanation using normal English so you should use normal words and expressions.
Same is true of element id and class. I understand what you are trying here but the text is talking about the general concepts on a very general level not about the specific types in a programming context.
I am guessing that later in the text it gets more technical and that is where the usage comes from?
CSS is from "Cascading StyleSheets". Not "Cascade".
Also the entire first sentence makes no sense at all, and it’s impossible to tell what the antecedent of this in the second sentence is supposed to be (the design, perhaps?). The whole thing is in dire need of editing and proofreading.
– Janus Bahs Jacquet
2 hours ago
@JanusBahsJacquet "This" refers to the browser reading the referenced CSS and applying it to the document. More or less the entire first sentence. Which refers to "as was explained before" But you are right it is pretty much incomprehensible. I just happened to know what he was trying to explain, so I did not notice. LOL.
– Ville Niemi
2 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "166"
};
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%2fwriting.stackexchange.com%2fquestions%2f43247%2fhow-to-use-2-footnotes-in-the-same-word%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Just use "DOM element" instead.
"DOM.Element" is not actually a word. It is way used to represent a DOM element in a programming context. In that context it would indeed behave like word and your usage might be correct.
However the sentence or the text is not in that kind of context. If it was you'd have no need to footnote either "DOM" or "Element". This is a general explanation using normal English so you should use normal words and expressions.
Same is true of element id and class. I understand what you are trying here but the text is talking about the general concepts on a very general level not about the specific types in a programming context.
I am guessing that later in the text it gets more technical and that is where the usage comes from?
CSS is from "Cascading StyleSheets". Not "Cascade".
Also the entire first sentence makes no sense at all, and it’s impossible to tell what the antecedent of this in the second sentence is supposed to be (the design, perhaps?). The whole thing is in dire need of editing and proofreading.
– Janus Bahs Jacquet
2 hours ago
@JanusBahsJacquet "This" refers to the browser reading the referenced CSS and applying it to the document. More or less the entire first sentence. Which refers to "as was explained before" But you are right it is pretty much incomprehensible. I just happened to know what he was trying to explain, so I did not notice. LOL.
– Ville Niemi
2 hours ago
add a comment |
Just use "DOM element" instead.
"DOM.Element" is not actually a word. It is way used to represent a DOM element in a programming context. In that context it would indeed behave like word and your usage might be correct.
However the sentence or the text is not in that kind of context. If it was you'd have no need to footnote either "DOM" or "Element". This is a general explanation using normal English so you should use normal words and expressions.
Same is true of element id and class. I understand what you are trying here but the text is talking about the general concepts on a very general level not about the specific types in a programming context.
I am guessing that later in the text it gets more technical and that is where the usage comes from?
CSS is from "Cascading StyleSheets". Not "Cascade".
Also the entire first sentence makes no sense at all, and it’s impossible to tell what the antecedent of this in the second sentence is supposed to be (the design, perhaps?). The whole thing is in dire need of editing and proofreading.
– Janus Bahs Jacquet
2 hours ago
@JanusBahsJacquet "This" refers to the browser reading the referenced CSS and applying it to the document. More or less the entire first sentence. Which refers to "as was explained before" But you are right it is pretty much incomprehensible. I just happened to know what he was trying to explain, so I did not notice. LOL.
– Ville Niemi
2 hours ago
add a comment |
Just use "DOM element" instead.
"DOM.Element" is not actually a word. It is way used to represent a DOM element in a programming context. In that context it would indeed behave like word and your usage might be correct.
However the sentence or the text is not in that kind of context. If it was you'd have no need to footnote either "DOM" or "Element". This is a general explanation using normal English so you should use normal words and expressions.
Same is true of element id and class. I understand what you are trying here but the text is talking about the general concepts on a very general level not about the specific types in a programming context.
I am guessing that later in the text it gets more technical and that is where the usage comes from?
CSS is from "Cascading StyleSheets". Not "Cascade".
Just use "DOM element" instead.
"DOM.Element" is not actually a word. It is way used to represent a DOM element in a programming context. In that context it would indeed behave like word and your usage might be correct.
However the sentence or the text is not in that kind of context. If it was you'd have no need to footnote either "DOM" or "Element". This is a general explanation using normal English so you should use normal words and expressions.
Same is true of element id and class. I understand what you are trying here but the text is talking about the general concepts on a very general level not about the specific types in a programming context.
I am guessing that later in the text it gets more technical and that is where the usage comes from?
CSS is from "Cascading StyleSheets". Not "Cascade".
answered 3 hours ago
Ville NiemiVille Niemi
1,05244
1,05244
Also the entire first sentence makes no sense at all, and it’s impossible to tell what the antecedent of this in the second sentence is supposed to be (the design, perhaps?). The whole thing is in dire need of editing and proofreading.
– Janus Bahs Jacquet
2 hours ago
@JanusBahsJacquet "This" refers to the browser reading the referenced CSS and applying it to the document. More or less the entire first sentence. Which refers to "as was explained before" But you are right it is pretty much incomprehensible. I just happened to know what he was trying to explain, so I did not notice. LOL.
– Ville Niemi
2 hours ago
add a comment |
Also the entire first sentence makes no sense at all, and it’s impossible to tell what the antecedent of this in the second sentence is supposed to be (the design, perhaps?). The whole thing is in dire need of editing and proofreading.
– Janus Bahs Jacquet
2 hours ago
@JanusBahsJacquet "This" refers to the browser reading the referenced CSS and applying it to the document. More or less the entire first sentence. Which refers to "as was explained before" But you are right it is pretty much incomprehensible. I just happened to know what he was trying to explain, so I did not notice. LOL.
– Ville Niemi
2 hours ago
Also the entire first sentence makes no sense at all, and it’s impossible to tell what the antecedent of this in the second sentence is supposed to be (the design, perhaps?). The whole thing is in dire need of editing and proofreading.
– Janus Bahs Jacquet
2 hours ago
Also the entire first sentence makes no sense at all, and it’s impossible to tell what the antecedent of this in the second sentence is supposed to be (the design, perhaps?). The whole thing is in dire need of editing and proofreading.
– Janus Bahs Jacquet
2 hours ago
@JanusBahsJacquet "This" refers to the browser reading the referenced CSS and applying it to the document. More or less the entire first sentence. Which refers to "as was explained before" But you are right it is pretty much incomprehensible. I just happened to know what he was trying to explain, so I did not notice. LOL.
– Ville Niemi
2 hours ago
@JanusBahsJacquet "This" refers to the browser reading the referenced CSS and applying it to the document. More or less the entire first sentence. Which refers to "as was explained before" But you are right it is pretty much incomprehensible. I just happened to know what he was trying to explain, so I did not notice. LOL.
– Ville Niemi
2 hours ago
add a comment |
Thanks for contributing an answer to Writing 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%2fwriting.stackexchange.com%2fquestions%2f43247%2fhow-to-use-2-footnotes-in-the-same-word%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