Change/clean biber citestyle and extend hyperref box
I have encountered two issues which might be related:
first of all I'm wondering if it is possible to have a better/clean solution to changing the intext cite style of biber. My required format is: (LAST_NAME YEAR)
or (LAST_NAME YEAR: PAGENUMBER)
. I have achieved that by the following commands (using parencite
):
DeclareFieldFormat{postnote}{#1} %remove p
DeclareFieldFormat{multipostnote}{#1} %remove pp
renewcommand*{nameyeardelim}{addspace} %just space between name and year
renewcommand*{postnotedelim}{addcolonspace} %colon after year
Is there a cleaner/better way to change the cite style in biber (probably my solution is bound to produce problems?)? In natbib there was setcitestyle{notesep={: }}
and setcitestyle{aysep={}}
but I need it in biber.
Secondly I would like to change the hyperref box to the WHOLE Cite, but currently it only extend to the year:
Is it possible (although probably not useful for multi-author-quotes) to extend the hyperref box to everything within the parenthesis?
Here the MWE:
documentclass{scrartcl}
usepackage[style=authoryear]{biblatex}
usepackage{hyperref}
DeclareFieldFormat{postnote}{#1} %remove p
DeclareFieldFormat{multipostnote}{#1} %remove pp
renewcommand*{nameyeardelim}{addspace} %just space between name and year
renewcommand*{postnotedelim}{addcolonspace} %colon after year
addbibresource{biblatex-examples.bib}
begin{document}
parencite[1--2]{aristotle:poetics}
parencite{aristotle:poetics}
newpage
printbibliography
end{document}
Cheers!
biblatex bibliographies hyperref citing biber
add a comment |
I have encountered two issues which might be related:
first of all I'm wondering if it is possible to have a better/clean solution to changing the intext cite style of biber. My required format is: (LAST_NAME YEAR)
or (LAST_NAME YEAR: PAGENUMBER)
. I have achieved that by the following commands (using parencite
):
DeclareFieldFormat{postnote}{#1} %remove p
DeclareFieldFormat{multipostnote}{#1} %remove pp
renewcommand*{nameyeardelim}{addspace} %just space between name and year
renewcommand*{postnotedelim}{addcolonspace} %colon after year
Is there a cleaner/better way to change the cite style in biber (probably my solution is bound to produce problems?)? In natbib there was setcitestyle{notesep={: }}
and setcitestyle{aysep={}}
but I need it in biber.
Secondly I would like to change the hyperref box to the WHOLE Cite, but currently it only extend to the year:
Is it possible (although probably not useful for multi-author-quotes) to extend the hyperref box to everything within the parenthesis?
Here the MWE:
documentclass{scrartcl}
usepackage[style=authoryear]{biblatex}
usepackage{hyperref}
DeclareFieldFormat{postnote}{#1} %remove p
DeclareFieldFormat{multipostnote}{#1} %remove pp
renewcommand*{nameyeardelim}{addspace} %just space between name and year
renewcommand*{postnotedelim}{addcolonspace} %colon after year
addbibresource{biblatex-examples.bib}
begin{document}
parencite[1--2]{aristotle:poetics}
parencite{aristotle:poetics}
newpage
printbibliography
end{document}
Cheers!
biblatex bibliographies hyperref citing biber
add a comment |
I have encountered two issues which might be related:
first of all I'm wondering if it is possible to have a better/clean solution to changing the intext cite style of biber. My required format is: (LAST_NAME YEAR)
or (LAST_NAME YEAR: PAGENUMBER)
. I have achieved that by the following commands (using parencite
):
DeclareFieldFormat{postnote}{#1} %remove p
DeclareFieldFormat{multipostnote}{#1} %remove pp
renewcommand*{nameyeardelim}{addspace} %just space between name and year
renewcommand*{postnotedelim}{addcolonspace} %colon after year
Is there a cleaner/better way to change the cite style in biber (probably my solution is bound to produce problems?)? In natbib there was setcitestyle{notesep={: }}
and setcitestyle{aysep={}}
but I need it in biber.
Secondly I would like to change the hyperref box to the WHOLE Cite, but currently it only extend to the year:
Is it possible (although probably not useful for multi-author-quotes) to extend the hyperref box to everything within the parenthesis?
Here the MWE:
documentclass{scrartcl}
usepackage[style=authoryear]{biblatex}
usepackage{hyperref}
DeclareFieldFormat{postnote}{#1} %remove p
DeclareFieldFormat{multipostnote}{#1} %remove pp
renewcommand*{nameyeardelim}{addspace} %just space between name and year
renewcommand*{postnotedelim}{addcolonspace} %colon after year
addbibresource{biblatex-examples.bib}
begin{document}
parencite[1--2]{aristotle:poetics}
parencite{aristotle:poetics}
newpage
printbibliography
end{document}
Cheers!
biblatex bibliographies hyperref citing biber
I have encountered two issues which might be related:
first of all I'm wondering if it is possible to have a better/clean solution to changing the intext cite style of biber. My required format is: (LAST_NAME YEAR)
or (LAST_NAME YEAR: PAGENUMBER)
. I have achieved that by the following commands (using parencite
):
DeclareFieldFormat{postnote}{#1} %remove p
DeclareFieldFormat{multipostnote}{#1} %remove pp
renewcommand*{nameyeardelim}{addspace} %just space between name and year
renewcommand*{postnotedelim}{addcolonspace} %colon after year
Is there a cleaner/better way to change the cite style in biber (probably my solution is bound to produce problems?)? In natbib there was setcitestyle{notesep={: }}
and setcitestyle{aysep={}}
but I need it in biber.
Secondly I would like to change the hyperref box to the WHOLE Cite, but currently it only extend to the year:
Is it possible (although probably not useful for multi-author-quotes) to extend the hyperref box to everything within the parenthesis?
Here the MWE:
documentclass{scrartcl}
usepackage[style=authoryear]{biblatex}
usepackage{hyperref}
DeclareFieldFormat{postnote}{#1} %remove p
DeclareFieldFormat{multipostnote}{#1} %remove pp
renewcommand*{nameyeardelim}{addspace} %just space between name and year
renewcommand*{postnotedelim}{addcolonspace} %colon after year
addbibresource{biblatex-examples.bib}
begin{document}
parencite[1--2]{aristotle:poetics}
parencite{aristotle:poetics}
newpage
printbibliography
end{document}
Cheers!
biblatex bibliographies hyperref citing biber
biblatex bibliographies hyperref citing biber
asked Jan 23 at 19:22
user180114user180114
111
111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
As you have there two questions, I'll give you different sorts of advice regarding each of them.
As to the first, the redefinition of delimiters. biblatex
has two "types" of delimiters, some are context sensitive, others are not. nameyeardelim
is one of those context sensitive ones. In biblatex.def
you'll find its definitions as:
DeclareDelimFormat{nameyeardelim}{addspace}
DeclareDelimFormat[textcite]{nameyeardelim}{addspace}
DeclareDelimFormat[bib,biblist]{nameyeardelim}{addspace}
You notice the definition is done for each of different types of context. Of course, the definition in this case, is the same. But the possibility of defining it separately is built-in. So, if you do:
renewcommand*{nameyeardelim}{addspace}
It will work, but this context sensitivity characteristic of the delimiter is gone, and you probably are getting more than what you asked for. So, you should use instead the proper interface for context sensitive delimiters of biblatex
. For example, if you want the change to apply to parencites:
DeclareDelimFormat[parencite]{nameyeardelim}{addspace}
supplying the contexts as the case may be.
postnotedelim
, on the contrary, is a "plain" delimiter, defined in biblatex.def
as:
newcommand*{postnotedelim}{addcommaspace}
So, here, clearly there is no harm in redefining it with renewcommand*
. It is actually the natural way to do it.
As to postnote
and multipostnote
, you are there in the right direction, DeclareFieldFormat
is the right tool for the job. But some improvement can be made. The original definition of those are (in a recent version of biblatex
):
DeclareFieldFormat{postnote}{mkpageprefix[pagination][mknormrange]{#1}}
DeclareFieldFormat{multipostnote}{mkpageprefix[pagination][mknormrange]{#1}}
mkpageprefix
, as the name suggests, is indeed responsible for adding "p."/"pp." or similar, as the case may be. So, removing it is what you want. But the above field formatting directives are also doing a second job, with mknormrange
, which parses the postnote argument for page ranges and normalises them. So, you would get better results with:
DeclareFieldFormat{postnote}{mknormrange{#1}}
DeclareFieldFormat{multipostnote}{mknormrange{#1}}
Regarding your second question, of hyperlinking the whole citation, and not just the year, there are plenty of questions and corresponding solutions here on the site. See, for example:
hyperlink name with biblatex authoryear (biblatex 1.4b)
hyperlink name with biblatex authoryear
Biblatex, authoryear-comp, and hyperlinks
Note, however, that the issue is less trivial than it looks. PLK left a comment in one of Audrey's answers saying "Hmm, I rather think it should be the default." But the issue was later discussed in biblatex's issue tracker (https://github.com/plk/biblatex/issues/428) and the conclusion there seems to be there was good reason in the choice to hyperlink only the year, and the issue was closed as "wontfix".
Of course, you certainly can still get good alternatives in one of the links above, if you'd like to do it.
1
There is good reason why You should ask only one question per question.
– gusbrs
Jan 23 at 20:15
For the record, a Johannes_B comment suggesting the hyperlinking of the year only was by design.
– gusbrs
Jan 23 at 20:16
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
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
},
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%2ftex.stackexchange.com%2fquestions%2f471553%2fchange-clean-biber-citestyle-and-extend-hyperref-box%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
As you have there two questions, I'll give you different sorts of advice regarding each of them.
As to the first, the redefinition of delimiters. biblatex
has two "types" of delimiters, some are context sensitive, others are not. nameyeardelim
is one of those context sensitive ones. In biblatex.def
you'll find its definitions as:
DeclareDelimFormat{nameyeardelim}{addspace}
DeclareDelimFormat[textcite]{nameyeardelim}{addspace}
DeclareDelimFormat[bib,biblist]{nameyeardelim}{addspace}
You notice the definition is done for each of different types of context. Of course, the definition in this case, is the same. But the possibility of defining it separately is built-in. So, if you do:
renewcommand*{nameyeardelim}{addspace}
It will work, but this context sensitivity characteristic of the delimiter is gone, and you probably are getting more than what you asked for. So, you should use instead the proper interface for context sensitive delimiters of biblatex
. For example, if you want the change to apply to parencites:
DeclareDelimFormat[parencite]{nameyeardelim}{addspace}
supplying the contexts as the case may be.
postnotedelim
, on the contrary, is a "plain" delimiter, defined in biblatex.def
as:
newcommand*{postnotedelim}{addcommaspace}
So, here, clearly there is no harm in redefining it with renewcommand*
. It is actually the natural way to do it.
As to postnote
and multipostnote
, you are there in the right direction, DeclareFieldFormat
is the right tool for the job. But some improvement can be made. The original definition of those are (in a recent version of biblatex
):
DeclareFieldFormat{postnote}{mkpageprefix[pagination][mknormrange]{#1}}
DeclareFieldFormat{multipostnote}{mkpageprefix[pagination][mknormrange]{#1}}
mkpageprefix
, as the name suggests, is indeed responsible for adding "p."/"pp." or similar, as the case may be. So, removing it is what you want. But the above field formatting directives are also doing a second job, with mknormrange
, which parses the postnote argument for page ranges and normalises them. So, you would get better results with:
DeclareFieldFormat{postnote}{mknormrange{#1}}
DeclareFieldFormat{multipostnote}{mknormrange{#1}}
Regarding your second question, of hyperlinking the whole citation, and not just the year, there are plenty of questions and corresponding solutions here on the site. See, for example:
hyperlink name with biblatex authoryear (biblatex 1.4b)
hyperlink name with biblatex authoryear
Biblatex, authoryear-comp, and hyperlinks
Note, however, that the issue is less trivial than it looks. PLK left a comment in one of Audrey's answers saying "Hmm, I rather think it should be the default." But the issue was later discussed in biblatex's issue tracker (https://github.com/plk/biblatex/issues/428) and the conclusion there seems to be there was good reason in the choice to hyperlink only the year, and the issue was closed as "wontfix".
Of course, you certainly can still get good alternatives in one of the links above, if you'd like to do it.
1
There is good reason why You should ask only one question per question.
– gusbrs
Jan 23 at 20:15
For the record, a Johannes_B comment suggesting the hyperlinking of the year only was by design.
– gusbrs
Jan 23 at 20:16
add a comment |
As you have there two questions, I'll give you different sorts of advice regarding each of them.
As to the first, the redefinition of delimiters. biblatex
has two "types" of delimiters, some are context sensitive, others are not. nameyeardelim
is one of those context sensitive ones. In biblatex.def
you'll find its definitions as:
DeclareDelimFormat{nameyeardelim}{addspace}
DeclareDelimFormat[textcite]{nameyeardelim}{addspace}
DeclareDelimFormat[bib,biblist]{nameyeardelim}{addspace}
You notice the definition is done for each of different types of context. Of course, the definition in this case, is the same. But the possibility of defining it separately is built-in. So, if you do:
renewcommand*{nameyeardelim}{addspace}
It will work, but this context sensitivity characteristic of the delimiter is gone, and you probably are getting more than what you asked for. So, you should use instead the proper interface for context sensitive delimiters of biblatex
. For example, if you want the change to apply to parencites:
DeclareDelimFormat[parencite]{nameyeardelim}{addspace}
supplying the contexts as the case may be.
postnotedelim
, on the contrary, is a "plain" delimiter, defined in biblatex.def
as:
newcommand*{postnotedelim}{addcommaspace}
So, here, clearly there is no harm in redefining it with renewcommand*
. It is actually the natural way to do it.
As to postnote
and multipostnote
, you are there in the right direction, DeclareFieldFormat
is the right tool for the job. But some improvement can be made. The original definition of those are (in a recent version of biblatex
):
DeclareFieldFormat{postnote}{mkpageprefix[pagination][mknormrange]{#1}}
DeclareFieldFormat{multipostnote}{mkpageprefix[pagination][mknormrange]{#1}}
mkpageprefix
, as the name suggests, is indeed responsible for adding "p."/"pp." or similar, as the case may be. So, removing it is what you want. But the above field formatting directives are also doing a second job, with mknormrange
, which parses the postnote argument for page ranges and normalises them. So, you would get better results with:
DeclareFieldFormat{postnote}{mknormrange{#1}}
DeclareFieldFormat{multipostnote}{mknormrange{#1}}
Regarding your second question, of hyperlinking the whole citation, and not just the year, there are plenty of questions and corresponding solutions here on the site. See, for example:
hyperlink name with biblatex authoryear (biblatex 1.4b)
hyperlink name with biblatex authoryear
Biblatex, authoryear-comp, and hyperlinks
Note, however, that the issue is less trivial than it looks. PLK left a comment in one of Audrey's answers saying "Hmm, I rather think it should be the default." But the issue was later discussed in biblatex's issue tracker (https://github.com/plk/biblatex/issues/428) and the conclusion there seems to be there was good reason in the choice to hyperlink only the year, and the issue was closed as "wontfix".
Of course, you certainly can still get good alternatives in one of the links above, if you'd like to do it.
1
There is good reason why You should ask only one question per question.
– gusbrs
Jan 23 at 20:15
For the record, a Johannes_B comment suggesting the hyperlinking of the year only was by design.
– gusbrs
Jan 23 at 20:16
add a comment |
As you have there two questions, I'll give you different sorts of advice regarding each of them.
As to the first, the redefinition of delimiters. biblatex
has two "types" of delimiters, some are context sensitive, others are not. nameyeardelim
is one of those context sensitive ones. In biblatex.def
you'll find its definitions as:
DeclareDelimFormat{nameyeardelim}{addspace}
DeclareDelimFormat[textcite]{nameyeardelim}{addspace}
DeclareDelimFormat[bib,biblist]{nameyeardelim}{addspace}
You notice the definition is done for each of different types of context. Of course, the definition in this case, is the same. But the possibility of defining it separately is built-in. So, if you do:
renewcommand*{nameyeardelim}{addspace}
It will work, but this context sensitivity characteristic of the delimiter is gone, and you probably are getting more than what you asked for. So, you should use instead the proper interface for context sensitive delimiters of biblatex
. For example, if you want the change to apply to parencites:
DeclareDelimFormat[parencite]{nameyeardelim}{addspace}
supplying the contexts as the case may be.
postnotedelim
, on the contrary, is a "plain" delimiter, defined in biblatex.def
as:
newcommand*{postnotedelim}{addcommaspace}
So, here, clearly there is no harm in redefining it with renewcommand*
. It is actually the natural way to do it.
As to postnote
and multipostnote
, you are there in the right direction, DeclareFieldFormat
is the right tool for the job. But some improvement can be made. The original definition of those are (in a recent version of biblatex
):
DeclareFieldFormat{postnote}{mkpageprefix[pagination][mknormrange]{#1}}
DeclareFieldFormat{multipostnote}{mkpageprefix[pagination][mknormrange]{#1}}
mkpageprefix
, as the name suggests, is indeed responsible for adding "p."/"pp." or similar, as the case may be. So, removing it is what you want. But the above field formatting directives are also doing a second job, with mknormrange
, which parses the postnote argument for page ranges and normalises them. So, you would get better results with:
DeclareFieldFormat{postnote}{mknormrange{#1}}
DeclareFieldFormat{multipostnote}{mknormrange{#1}}
Regarding your second question, of hyperlinking the whole citation, and not just the year, there are plenty of questions and corresponding solutions here on the site. See, for example:
hyperlink name with biblatex authoryear (biblatex 1.4b)
hyperlink name with biblatex authoryear
Biblatex, authoryear-comp, and hyperlinks
Note, however, that the issue is less trivial than it looks. PLK left a comment in one of Audrey's answers saying "Hmm, I rather think it should be the default." But the issue was later discussed in biblatex's issue tracker (https://github.com/plk/biblatex/issues/428) and the conclusion there seems to be there was good reason in the choice to hyperlink only the year, and the issue was closed as "wontfix".
Of course, you certainly can still get good alternatives in one of the links above, if you'd like to do it.
As you have there two questions, I'll give you different sorts of advice regarding each of them.
As to the first, the redefinition of delimiters. biblatex
has two "types" of delimiters, some are context sensitive, others are not. nameyeardelim
is one of those context sensitive ones. In biblatex.def
you'll find its definitions as:
DeclareDelimFormat{nameyeardelim}{addspace}
DeclareDelimFormat[textcite]{nameyeardelim}{addspace}
DeclareDelimFormat[bib,biblist]{nameyeardelim}{addspace}
You notice the definition is done for each of different types of context. Of course, the definition in this case, is the same. But the possibility of defining it separately is built-in. So, if you do:
renewcommand*{nameyeardelim}{addspace}
It will work, but this context sensitivity characteristic of the delimiter is gone, and you probably are getting more than what you asked for. So, you should use instead the proper interface for context sensitive delimiters of biblatex
. For example, if you want the change to apply to parencites:
DeclareDelimFormat[parencite]{nameyeardelim}{addspace}
supplying the contexts as the case may be.
postnotedelim
, on the contrary, is a "plain" delimiter, defined in biblatex.def
as:
newcommand*{postnotedelim}{addcommaspace}
So, here, clearly there is no harm in redefining it with renewcommand*
. It is actually the natural way to do it.
As to postnote
and multipostnote
, you are there in the right direction, DeclareFieldFormat
is the right tool for the job. But some improvement can be made. The original definition of those are (in a recent version of biblatex
):
DeclareFieldFormat{postnote}{mkpageprefix[pagination][mknormrange]{#1}}
DeclareFieldFormat{multipostnote}{mkpageprefix[pagination][mknormrange]{#1}}
mkpageprefix
, as the name suggests, is indeed responsible for adding "p."/"pp." or similar, as the case may be. So, removing it is what you want. But the above field formatting directives are also doing a second job, with mknormrange
, which parses the postnote argument for page ranges and normalises them. So, you would get better results with:
DeclareFieldFormat{postnote}{mknormrange{#1}}
DeclareFieldFormat{multipostnote}{mknormrange{#1}}
Regarding your second question, of hyperlinking the whole citation, and not just the year, there are plenty of questions and corresponding solutions here on the site. See, for example:
hyperlink name with biblatex authoryear (biblatex 1.4b)
hyperlink name with biblatex authoryear
Biblatex, authoryear-comp, and hyperlinks
Note, however, that the issue is less trivial than it looks. PLK left a comment in one of Audrey's answers saying "Hmm, I rather think it should be the default." But the issue was later discussed in biblatex's issue tracker (https://github.com/plk/biblatex/issues/428) and the conclusion there seems to be there was good reason in the choice to hyperlink only the year, and the issue was closed as "wontfix".
Of course, you certainly can still get good alternatives in one of the links above, if you'd like to do it.
edited Jan 23 at 23:39
answered Jan 23 at 20:02
gusbrsgusbrs
7,5512840
7,5512840
1
There is good reason why You should ask only one question per question.
– gusbrs
Jan 23 at 20:15
For the record, a Johannes_B comment suggesting the hyperlinking of the year only was by design.
– gusbrs
Jan 23 at 20:16
add a comment |
1
There is good reason why You should ask only one question per question.
– gusbrs
Jan 23 at 20:15
For the record, a Johannes_B comment suggesting the hyperlinking of the year only was by design.
– gusbrs
Jan 23 at 20:16
1
1
There is good reason why You should ask only one question per question.
– gusbrs
Jan 23 at 20:15
There is good reason why You should ask only one question per question.
– gusbrs
Jan 23 at 20:15
For the record, a Johannes_B comment suggesting the hyperlinking of the year only was by design.
– gusbrs
Jan 23 at 20:16
For the record, a Johannes_B comment suggesting the hyperlinking of the year only was by design.
– gusbrs
Jan 23 at 20:16
add a comment |
Thanks for contributing an answer to TeX - LaTeX 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%2ftex.stackexchange.com%2fquestions%2f471553%2fchange-clean-biber-citestyle-and-extend-hyperref-box%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