| At line 16 changed one line |
| A human user might do this, but rarely because it is wrong even in handwriting. But I don't know Texteditor-programms that do that automatically (putting hard line breaks in it, don't confuse it with wordwrap!!!). Such editors might exist, though I don't know a single relevant example. Then this editor would also mess up other display on other markup, because it might do hard line breaks where it should not put it... |
| A human user might do this, but rarely because it is wrong even in handwriting. But I don't know text editor-programs that do that automatically (putting hard line breaks in it, don't confuse it with wordwrap!!!). Such editors might exist, though I don't know a single relevant example. Then this editor would also mess up other display on other markup, because it might do hard line breaks where it should not put it... |
| At line 20 changed one line |
| *, damn it, this strange editor broke the line befor the ending bold |
| *, damn it, this strange editor broke the line before the ending bold |
| At line 24 changed one line |
| *, damn it, this strange editor broke the line befor the ending asterisk |
| *, damn it, this strange editor broke the line before the ending asterisk |
| At line 27 changed one line |
| Your example is hypothetical like mine unless you name me a Texteditor that has such a option that does hard line breaks that way relevant to practice. We already can exclude the most important Texteditors relevant to us: The TextArea field in Browsers(!). |
| Your example is hypothetical like mine unless you name me a text editor that has such a option that does hard line breaks that way relevant to practice. We already can exclude the most important text editors relevant to us: The TextArea field in Browsers(!). |
| At line 31 changed 2 lines |
| But mentionning negative numbers and manually typing return (we have |
| decided to ignore, i.e. permit, single hard line breaks in paragraphs), such as |
| But mentioning negative numbers and manually typing return (we have |
| decided to ignore, i.e. permit, single hard line breaks in paragraphs), such as "minus-one" |
| At line 38 changed one line |
| ==1, could be common as well. I understand your point, pleas understand mine. |
| ==1, could be common as well. I understand your point, please understand mine. |
| At line 53 added 34 lines |
| ---- |
|
| The examples I have in mind are: |
| {{{ |
| **START** I think these are realistic examples |
| - either using simple hyphens as here - or the |
| -- much nicer -- n/m-dash way of writing. |
| Note that the line-breaking may come from line- |
| wrapping software, so it is not a question where |
| you would put the dash. And the minus sign (like |
| -1) even must be placed there. Finally, whereas |
| in English only trailing hyphen-constructs like |
| sub- and superclass are common, in German also |
| leading hyphen-constructs occur, e.g. subclass and |
| -attribute. **END** |
| }}} |
|
| **START** I think these are realistic examples |
| - either using simple hyphens as here - or the |
| -- much nicer -- n/m-dash way of writing. |
| Note that the line-breaking may come from line- |
| wrapping software, so it is not a question where |
| you would put the dash. And the minus sign (like |
| -1) even must be placed there. Finally, whereas |
| in English only trailing hyphen-constructs like |
| sub- and superclass are common, in German also |
| leading hyphen-constructs occur, e.g. subclass and |
| -attribute. **END** |
|
| * Note that probably all humans and any software I known will only break at whitespace plus after a hyphen, so Christoph's bold-asterisk example does not occur. |
| * Also this seems to be all about bullet versus hyphen, not about requiring a blank after the lead markup. Essentially, requiring a blank makes a minimum of two characters for bullets (bullet symbol plus blank). Note that this whitespace that is visible when rendered, and would remain unchanged under all html/xml whitespace normalization rules... |
| * I would not mind being a bit more restrictive about the equal sign either, either by starting with double equal as minimal markup for heading, or requiring before and after in this case. Clearly, both solutions have disadvantages... |
| -- [Gregor Hagedorn] (I would prefer this to be NOT a bulleted list, but a signature...) |
| ---- |
.