A simple question really: how strict is this community (or how strict does it want to be) about newlines when it comes to quines?
For example, is the Python quine
_='_=%r;print _%%_';print _%_
29 bytes, or is it 30 (including the trailing newline, since that's printed in its output)?
A lot of languages have multiple functions for printing, some of them will include a newline and some of them won't. It's the programmer's choice what function they use, if they choose to print a trailing newline it must be included in the source code because it's part of the output.
Questions like for example KC challenges state whether it's fine to include newlines or not. So if a quine challenge does not specify whether that's ok, it should be required by default. The tag-wiki defines a quine as:
A quine is a program which produces its source as output.
It doesn't say "which produces its source plus additional characters as output", newlines are not really different from other characters.
I'm guessing this question targets the Golf you a quine for great good! challenge which has an even less ambiguous definition (emphasis mine):
A quine is a non-empty computer program which takes no input and produces a copy of its own source code as its only output.
This means no trailing spaces, non-printable chars, unicode characters or newlines. If we would ask whether it's fine to print an additional a character, nobody would say that this is fine (unless the rules explicitly say so). Newlines should be treated the same as other characters.
Furthermore (and most importantly) most answers that currently include a newline as part of their output can be easily fixed[citation needed] and we won't lose valuable content by enforcing the rules.
