1. Two Common Formatting Mistakes on the Forum
- Posted by jeremy (admin) Nov 06, 2010
- 2490 views
- Last edited Nov 07, 2010
I see some repeating patterns in some of the quotes I include in my forum replies. The biggest one is the improper use of a forced line break, \\. The second is not using no-wiki tags {{{ }}} around console type pastes, such as the output of a command line program.
Forced Line Break
\\
This should not be needed hardly ever in the forum. This is a forced line break. The forum is created in such a manner that it word wraps properly. If you want to make a new paragraph, you should put a blank line between your two paragraphs. For example:
Hello, World\\ \\ This is a message to the Euphoria Community.\\ \\ Goodbye!
That is way too much work! It need not be that complicated. Here is the output of the above text:
Hello, World
This is a message to the Euphoria Community.
Goodbye!
Looks fine, however this accomplishes the exact same result:
Hello, World This is a message to the Euphoria Community. Goodbye!
Here is the output of the above text:
Hello, World
This is a message to the Euphoria Community.
Goodbye!
No-Wiki {{{
{{{ }}}
This causes two things to happen:
- If the tag begins and ends on their own lines, it enters a pre-formatted mode <pre>...</pre>
- Disables all creole formatting so ** stays ** and doesn't trigger the bold attribute
Say you have the output of a dir command. You could enter it as:
C:\projects> dir CoolProject1 CoolProject2 CoolProject3
However, that's not right. It turns out like:
C:\projects> dir CoolProject1 CoolProject2 CoolProject3
You could use forced line breaks at the end of each line (\\) but again, that's too much work. Simply wrap the whole thing in {{{ }}} and it'll all just work. For example, it should be (minus the ~ on the ending tag, I had to add that for Creole to not end the no-wiki at that point):
{{{
C:\projects> dir
CoolProject1
CoolProject2
CoolProject3
~}}}
That outputs as:
C:\projects> dir CoolProject1 CoolProject2 CoolProject3
I hope this has helped some spend less time on writing messages and more time using Euphoria!
Jeremy
2. Re: Two Common Formatting Mistakes on the Forum
- Posted by DerekParnell (admin) Nov 06, 2010
- 2459 views
There is also a little known alternate way to create forced line breaks. This is for people who like to control the maximum length of lines and/or don't like spaces between paragraphs. (IMHO both are bad stylistic approaches, but hey, who am I to say).
You have see Jeremy point out that using {{{ }}} around a block of text keeps the line formatting exactly how you typed it, but also prevents any wiki tags being used in that text. Well there is a way to keep the lines ending where you typed and having wiki tags expanded - enclose the text inside [[[ ]]] tags.
For example...
This text has short
lines and wiki tags
rendered correctly.
3. Re: Two Common Formatting Mistakes on the Forum
- Posted by DanM Nov 07, 2010
- 2379 views
I think a better way to help people format their posts here more easily would be to have a set of BUTTONS somewhere on the post editing window, which, when clicked, would auto-paste the appropriate formatting commands into a post at the position of the cursor.
Could include smiley faces, too (ie, click on single button with a generic smiley face, opens up a block of various smiley faces on their own buttons, click on one of them, get that smiley face at the position of cursor in post).
Dan
4. Re: Two Common Formatting Mistakes on the Forum
- Posted by ne1uno Nov 07, 2010
- 2361 views
I think a better way to help people format their posts here more easily would be to have a set of BUTTONS somewhere on the post editing window, which, when clicked, would auto-paste the appropriate formatting commands into a post at the position of the cursor.
the old wiki had that for page edit, but it only worked in firefox.
5. Re: Two Common Formatting Mistakes on the Forum
- Posted by DanM Nov 07, 2010
- 2401 views
I see some repeating patterns in some of the quotes I include in my forum replies. The biggest one is the improper use of a forced line break, \\. The second is not using verbatim tags {} around console type pastes, such as the output of a command line program.
Forced Line Break
\\
This should not be needed hardly ever in the forum. This is a forced line break. The forum is created in such a manner that it word wraps properly. If you want to make a new paragraph, you should put a blank line between your two paragraphs. For example:
Hello, World\\ \\ This is a message to the Euphoria Community.\\ \\ Goodbye!
That is way too much work! It need not be that complicated. Here is the output of the above text:
Hello, World
This is a message to the Euphoria Community.
Goodbye!
Looks fine, however this accomplishes the exact same result:
Hello, World This is a message to the Euphoria Community. Goodbye!
Here is the output of the above text:
Hello, World
This is a message to the Euphoria Community.
Goodbye!
Verbatim {{{
{{{ }}}
This causes two things to happen:
- Enter a pre-formatted mode <pre>...</pre>
- Disables all creole formatting so ** stays ** and doesn't trigger the bold attribute
Say you have the output of a dir command. You could enter it as:
C:\projects> dir CoolProject1 CoolProject2 CoolProject3
However, that's not right. It turns out like:
C:\projects> dir CoolProject1 CoolProject2 CoolProject3
You could use forced line breaks at the end of each line (\\) but again, that's too much work. Simply wrap the whole thing in {{{ }}} and it'll all just work. For example, it should be (minus the ~ on the ending tag, I had to add that for Creole to not end the verbatim at that point):
{{{
C:\projects> dir
CoolProject1
CoolProject2
CoolProject3
~}}}
That outputs as:
C:\projects> dir CoolProject1 CoolProject2 CoolProject3
I hope this has helped some spend less time on writing messages and more time using Euphoria!
Jeremy
ok, interesting and useful to know, but:
1. Sections of your post, when included in a reply, show up DIFFERENTLY than originally, with CROSSED OUT WORDS displayed instead of the original words NOT crossed out, which can be confusing to a person reading a reply, eg.:
Hello, World
This is a message to the Euphoria Community.
Goodbye!
I sorta understand why it happens, but I still suggest that it SHOULDN'T, because the QUOTED reply isn't actually QUOTED, ie, same as original.
[edit: well, when I PREVIEW this section, I see CROSSED OUT words, but when I see it POSTED, they're NOT crossed out, so maybe I DON'T "sorta" understand what's going on!]
2. And one of your examples of "similarity", ISN'T similar, eg.:
Here is the output of the above text:
Hello, World
This is a message to the Euphoria Community.
Goodbye!
Which ISN'T the same as:
Hello, World
This is a message to the Euphoria Community.
Goodbye!
And again, I sorta realize why this happens, but having an example of similarity NOT be similar sorta defeats the purpose of the example, therefore it shouldn't happen.
3. And putting a blank line doesn't always work as it should, I had to put the \\ for line break after the above "line boxed" example, to separate that example and my next text with a blank line, after 3 blank lines were ignored. (I presume that's because they were "naked" ENTER/RETURN keypresses, with no other text in the same line, but still, it's counter intuitive, making a "blank" line by hitting ENTER should YIELD a blank line, in the resulting post, I think.)
All in all, though, I have to say that the functionality of the forum is getting much better, good job!
Dan
6. Re: Two Common Formatting Mistakes on the Forum
- Posted by jeremy (admin) Nov 07, 2010
- 2315 views
ok, interesting and useful to know, but:
1. Sections of your post, when included in a reply, show up DIFFERENTLY than originally, with CROSSED OUT WORDS displayed instead of the original words NOT crossed out, which can be confusing to a person reading a reply, eg.:
I don't see anything crossed out?
Jeremy
7. Re: Two Common Formatting Mistakes on the Forum
- Posted by DanM Nov 07, 2010
- 2259 views
ok, interesting and useful to know, but:
1. Sections of your post, when included in a reply, show up DIFFERENTLY than originally, with CROSSED OUT WORDS displayed instead of the original words NOT crossed out, which can be confusing to a person reading a reply, eg.:
I don't see anything crossed out?
Jeremy
Sorry, I probably should have put my edited comment about this in bold so it would have been more clear WHEN it was happening and when it was NOT: I see text crossed out WHEN I PREVIEW my comment to your original post with your post QUOTED in my reply. But you're right, it DOESN'T happen in the post itself, just in the PREVIEW of a reply to your original post.
Does it show like that for you if you read and PREVIEW your original post?
Dan
8. Re: Two Common Formatting Mistakes on the Forum
- Posted by useless Nov 07, 2010
- 2284 views
I see some repeating patterns in some of the quotes I include in my forum replies. The biggest one is the improper use of a forced line break, \\. The second is not using verbatim tags {{{ }}} around console type pastes, such as the output of a command line program.
Forced Line Break
\\
This should not be needed hardly ever in the forum. This is a forced line break. The forum is created in such a manner that it word wraps properly. If you want to make a new paragraph, you should put a blank line between your two paragraphs. For example:
Jeremy
Maybe it was a bug in previous editions of the host or creole or Euphoria, but i'll bet no one is wasting time by adding forced newline slashes if they haven't been needed. Or, perhaps if they were needed, someone rtfm to figure out how to get their postings properly formatted. Either way, why would anyone find their post looks like what they typed, and then rtfm, and went back and added creole newline slashes?
useless
9. Re: Two Common Formatting Mistakes on the Forum
- Posted by jaygade Nov 07, 2010
- 2271 views
Blech. Just give me bbcode tags.
10. Re: Two Common Formatting Mistakes on the Forum
- Posted by jimcbrown (admin) Nov 07, 2010
- 2242 views
Blech. Just give me bbcode tags.
+1 !
11. Re: Two Common Formatting Mistakes on the Forum
- Posted by jeremy (admin) Nov 07, 2010
- 2266 views
BBCodes will not solve any problems we've had with formatting. You still have to remember to use [code]..[/code] around blocks of code, otherwise it comes out in paragraph format, just like Creole. Further, you do not need to force line breaks in BBCode or in Creole, which is one of the main points of this thread.
| BBCode | Creole |
|---|---|
| [b]Bold[/b] | **Bold** |
| [i]Italic[/i] | //Italic// |
| [code]...[/code] | {{{...}}} |
That's about it for basic BBCode. Creole is much easier and pleasant to the eye reading directly. Oh, and don't try to create a table like the above in BBCode, what a mess!
Jeremy
12. Re: Two Common Formatting Mistakes on the Forum
- Posted by jeremy (admin) Nov 07, 2010
- 2270 views
One more comment. Creole is used in the forums, news, wiki, ticket system, all of euphoria's source documentation and manual. eudoc is an extensive tool that will be shipped with 4.0 and it directly deals with Creole format and a very powerful creolehtml tool was created by Derek in Euphoria for conversion of all of our docs to HTML and there to PDF and Text.
So, as a Euphoria programmer, Creole is going to be all around you. These things couldn't have been done with BBCode.
Jeremy
13. Re: Two Common Formatting Mistakes on the Forum
- Posted by jimcbrown (admin) Nov 07, 2010
- 2253 views
One more comment. Creole is used in the forums, news, wiki, ticket system, all of euphoria's source documentation and manual. eudoc is an extensive tool that will be shipped with 4.0 and it directly deals with Creole format and a very powerful creolehtml tool was created by Derek in Euphoria for conversion of all of our docs to HTML and there to PDF and Text.
So, as a Euphoria programmer, Creole is going to be all around you. These things couldn't have been done with BBCode.
Jeremy
Agreed. Derek has done great work with EuCreole. It's value can not be easily replaced.
14. Re: Two Common Formatting Mistakes on the Forum
- Posted by jaygade Nov 07, 2010
- 2206 views
I agree that it's consistent among the different Euphoria pages - although each page has its own purpose - but I disagree that it's easier.
I find BBCode to be far easier because it is consistent among hundreds of forums and not some thing which seems to me to be unique to the Euphoria websites.
In 20+ years of BBSes and Internet forums, this is the only place I've ever seen "creole".
I can see using creole for the wiki or for documentation for which layout and structure are far more important than in a forum. But forum posts rarely need that kind of structure and layout to them. They need code, emphasis, and strong. And maybe sometimes a table. And people who only spend a little bit of time on any one forum don't necessarily want to learn a wholly different means of expressing that.
Not that I'm a hater. Creole is what it is. It's like preferring Mac when everyone else does PC. Don't mean nothin'. Just expressing my opinion.
Edit: See, I can't use double dash without it interpreting it as strikeout. What's up with THAT???
15. Re: Two Common Formatting Mistakes on the Forum
- Posted by DanM Nov 08, 2010
- 2215 views
Edit: See, I can't use double dash without it interpreting it as strikeout. What's up with THAT???
Yes, I think people would sometimes like to put (double dashes) in a sentence, without the (double dashes) yielding strikeouts, as they did in this example.
So, I would think that something like *- (or * followed by two dashes) might be better for indicating strikeout, though I suspect there's some reason it can't be used?
And to see the same problem of unintended strikeouts in Jeremy's original post:
1. Click to read the top post in this thread;
2. Click "Reply with quote";
3. Click "Preview"
(And I had to use "\\" above in order to get a bold list, because I couldn't figure out how to do it with a properly formatted enumerated list. Plus the properly formatted enumerated list insists on putting a blank line between the line of text before it and the list. Just "nits", I know, but the forum and it's utilization is one of the faces of Euphoria.)
Dan
16. Re: Two Common Formatting Mistakes on the Forum
- Posted by ne1uno Nov 08, 2010
- 2185 views
Yes, I think people would sometimes like to put (double dashes) in a sentence, without the (double dashes) yielding strikeouts, as they did in this example.
So, I would think that something like *- (or * followed by two dashes) might be better for indicating strikeout, though I suspect there's some reason it can't be used?
And to see the same problem of unintended strikeouts in Jeremy's original post:
1. Click to read the top post in this thread;
2. Click "Reply with quote";
3. Click "Preview"
(And I had to use "\\" above in order to get a bold list
~-- no strikeout
-- no strikeout
the ~ tilde is used to escape creole and should be more prominent in the help.
there is no bold list, but you can bold each list item.
**And to see the same problem of unintended strikeouts in Jeremy's original post:** # **Click to read the top post in this thread;** # **Click "Reply with quote** # **Click "Preview**
And to see the same problem of unintended strikeouts in Jeremy's original post:
- Click to read the top post in this thread;
- Click "Reply with quote
- Click "Preview
any time creole is detected in a message preview could be the default action before post is enabled. but, that would also be confusing.
17. Re: Two Common Formatting Mistakes on the Forum
- Posted by ne1uno Nov 08, 2010
- 2196 views
And to see the same problem of unintended strikeouts in Jeremy's original post:
1. Click to read the top post in this thread;
2. Click "Reply with quote";
3. Click "Preview"
---- Hello, World\\ \\ This is a message to the Euphoria Community.\\ \\ Goodbye! ---- ---- Hello, World\\ \\ This is a message to the Euphoria Community.\\ \\ Goodbye! ----
Hello, World
This is a message to the Euphoria Community.
Goodbye!
that strikeout in preview looks like a preview bug. adding a space before the HR (----) doesn't help.
workaround, you need an extra blank line after the HR.
is more a bug in creole than an indictment of the whole creole application and usage. debugging by observation is a slow process.
18. Re: Two Common Formatting Mistakes on the Forum
- Posted by DanM Nov 08, 2010
- 2167 views
Yes, I think people would sometimes like to put (double dashes) in a sentence, without the (double dashes) yielding strikeouts, as they did in this example.
So, I would think that something like *- (or * followed by two dashes) might be better for indicating strikeout, though I suspect there's some reason it can't be used?
And to see the same problem of unintended strikeouts in Jeremy's original post:
1. Click to read the top post in this thread;
2. Click "Reply with quote";
3. Click "Preview"
(And I had to use "\\" above in order to get a bold list
~-- no strikeout
-- no strikeout
the ~ tilde is used to escape creole and should be more prominent in the help.
there is no bold list, but you can bold each list item.
**And to see the same problem of unintended strikeouts in Jeremy's original post:** # **Click to read the top post in this thread;** # **Click "Reply with quote** # **Click "Preview**
And to see the same problem of unintended strikeouts in Jeremy's original post:
- Click to read the top post in this thread;
- Click "Reply with quote
- Click "Preview
any time creole is detected in a message preview could be the default action before post is enabled. but, that would also be confusing.
Thanks, agree that ~ tilde to escape creole should be prominent in help, and dunno why I didn't try bold each item in enumerated list!
But not sure what you mean about Preview: I would think Post and Preview should look the same, that's why one Previews, to see what the post will look like.
Dan
19. Re: Two Common Formatting Mistakes on the Forum
- Posted by jeremy (admin) Nov 08, 2010
- 2188 views
I have 100% control over what formatting is applied where. Maybe on the forum I should disable some of them such as --? Then, if all people need is Bold, Italic and Code, all they need to know is **bold**, //italic//, {{{~code}}} or <eucode>...</eucode>
Jeremy
20. Re: Two Common Formatting Mistakes on the Forum
- Posted by DanM Nov 08, 2010
- 2183 views
I have 100% control over what formatting is applied where. Maybe on the forum I should disable some of them such as --? Then, if all people need is Bold, Italic and Code, all they need to know is **bold**, //italic//, {{{~code}}} or <eucode>...</eucode>
Jeremy
Dunno, I think strikeout could be useful in some instances, like if someone wanted to show what they'd edited, just include info about ~ tilde to escape/defeat creole in forum help below edit box; and if possible make Preview and Post show the same thing.
Dan
21. Re: Two Common Formatting Mistakes on the Forum
- Posted by DerekParnell (admin) Nov 08, 2010
- 2205 views
that strikeout in preview looks like a preview bug. adding a space before the HR (----) doesn't help.
workaround, you need an extra blank line after the HR.
is more a bug in creole than an indictment of the whole creole application and usage. debugging by observation is a slow process.
What "strikeout in preview". I'm not seeing any strikeout being shown in preview mode?
22. Re: Two Common Formatting Mistakes on the Forum
- Posted by ne1uno Nov 08, 2010
- 2196 views
that strikeout in preview looks like a preview bug. adding a space before the HR (----) doesn't help.
workaround, you need an extra blank line after the HR.
is more a bug in creole than an indictment of the whole creole application and usage. debugging by observation is a slow process.
What "strikeout in preview". I'm not seeing any strikeout being shown in preview mode?
Jeremy's first post in this thread hit preview and there is a section that shows strikeout in preview only. I copied the markup in my message which also has strikeout in preview.
23. Re: Two Common Formatting Mistakes on the Forum
- Posted by jimcbrown (admin) Nov 08, 2010
- 2174 views
I agree that it's consistent among the different Euphoria pages - although each page has its own purpose - but I disagree that it's easier.
I find BBCode to be far easier because it is consistent among hundreds of forums and not some thing which seems to me to be unique to the Euphoria websites.
In 20+ years of BBSes and Internet forums, this is the only place I've ever seen "creole".
I can see using creole for the wiki or for documentation for which layout and structure are far more important than in a forum. But forum posts rarely need that kind of structure and layout to them. They need code, emphasis, and strong. And maybe sometimes a table. And people who only spend a little bit of time on any one forum don't necessarily want to learn a wholly different means of expressing that.
Not that I'm a hater. Creole is what it is. It's like preferring Mac when everyone else does PC. Don't mean nothin'. Just expressing my opinion.
Edit: See, I can't use double dash without it interpreting it as strikeout. What's up with THAT???
+5 !
I fully agree with everything you say here. However, adding BBCode support means writing a parser for it. (The easiest way to do this would be to write a BBCode-to-Creole converter that also knew how to escape text properly in Creole. Otherwise, there's the additional headaches of writing a converter-to-html for it, and dealing with different post formats in the database, and dealing with someone quoting a Creole post from BBCode or vice versa.)
We used Creole because it was already available and worked very well on euwiki (IIRC it predates not only euweb but even forum.ex). No BBCode parser existed back then, and none exists now. Until someone writes one, this is not remotely possible.
24. Re: Two Common Formatting Mistakes on the Forum
- Posted by DerekParnell (admin) Nov 08, 2010
- 2180 views
What "strikeout in preview". I'm not seeing any strikeout being shown in preview mode?
Jeremy's first post in this thread hit preview and there is a section that shows strikeout in preview only. I copied the markup in my message which also has strikeout in preview.
Sorry, but my browser (Opera) does not show any strikeout text when previewing Jeremy's first post in this thread. Can you tell me exactly which text is being rendered as struck-out by your browser?
25. Re: Two Common Formatting Mistakes on the Forum
- Posted by ne1uno Nov 08, 2010
- 2166 views
What "strikeout in preview". I'm not seeing any strikeout being shown in preview mode?
Jeremy's first post in this thread hit preview and there is a section that shows strikeout in preview only. I copied the markup in my message which also has strikeout in preview.
Sorry, but my browser (Opera) does not show any strikeout text when previewing Jeremy's first post in this thread. Can you tell me exactly which text is being rendered as struck-out by your browser?
this will look ok when posted and is strikeout in preview. using firefox2.
---- Hello, World\\ \\ This is a message to the Euphoria Community.\\ \\ Goodbye! ----
Hello, World
This is a message to the Euphoria Community.
Goodbye!
26. Re: Two Common Formatting Mistakes on the Forum
- Posted by DerekParnell (admin) Nov 08, 2010
- 2164 views
... However, adding BBCode support means writing a parser for it ...
It would not be a big issue to have our creole parser support a subset of the (oldfashioned) BBCodes.
We used Creole because it was already available ...
Actually, we selected creole because it already existed and looked easy to write a parser for it. See WikiCreole
27. Re: Two Common Formatting Mistakes on the Forum
- Posted by DerekParnell (admin) Nov 08, 2010
- 2156 views
this will look ok when posted and is strikeout in preview. using firefox2.
---- Hello, World\\ \\ This is a message to the Euphoria Community.\\ \\ Goodbye! ----
Hello, World
This is a message to the Euphoria Community.
Goodbye!
Looks like a firefox issue then. Opera does not render ANY strikout text. Please, WHAT EXACTLY IS THE TEXT BEING STRUCK OUT ?
28. Re: Two Common Formatting Mistakes on the Forum
- Posted by DerekParnell (admin) Nov 08, 2010
- 2153 views
We could add a rule to the creole parser that if it sees -- (but not ----) and does not see a matching -- on the same line, then it will not cause the text to be struck out. In other words, strikeout will only occur on text that is enclosed by -- on the same line.
How does that idea sound?
29. Re: Two Common Formatting Mistakes on the Forum
- Posted by jimcbrown (admin) Nov 08, 2010
- 2160 views
We used Creole because it was already available ...
Actually, we selected creole because it already existed and looked easy to write a parser for it. See WikiCreole
Yeah, the choice of WikiCreole for euwiki would have been a no-brainer.
... However, adding BBCode support means writing a parser for it ...
It would not be a big issue to have our creole parser support a subset of the (oldfashioned) BBCodes.
If I understand this correctly, you are saying that it would be very easy from a technical standpoint to add support for this into the forum?
30. Re: Two Common Formatting Mistakes on the Forum
- Posted by jeremy (admin) Nov 08, 2010
- 2138 views
If I understand this correctly, you are saying that it would be very easy from a technical standpoint to add support for this into the forum?
Might be technically easy but not worth mixing the standards. Again, BBCode will not solve any of the problems we have. People will still forget to use [code]...[/code]. Whatever format you use that will happen. The only way to solve this is for education, with the possible exception of providing some fancy javascript. There are actually a few nice creole toolbars that I have seen which would provide this functionality, but even that will not solve the problem, I've participated in many BBCode enabled forums that suffer the same fate as we do, even w/toolbars.
Jeremy
31. Re: Two Common Formatting Mistakes on the Forum
- Posted by jeremy (admin) Nov 08, 2010
- 2120 views
We could add a rule to the creole parser that if it sees -- (but not ----) and does not see a matching -- on the same line, then it will not cause the text to be struck out. In other words, strikeout will only occur on text that is enclosed by -- on the same line.
How does that idea sound?
The downfall would be marked a paragraph removed. Not sure which is more of a downfall though.
Jeremy
32. Re: Two Common Formatting Mistakes on the Forum
- Posted by jeremy (admin) Nov 08, 2010
- 2104 views
And to see the same problem of unintended strikeouts in Jeremy's original post:
- Click to read the top post in this thread;
- Click "Reply with quote
- Click "Preview
This has been fixed. It turns out to be a unix/windows line ending issue. That's why some people were seeing it and others not. Appears that Opera and IE send the same type of line endings while Chrome and Firefox send another.
Derek made a rush fix to creole.e and it should now work on all browsers.
Jeremy
33. Re: Two Common Formatting Mistakes on the Forum
- Posted by DerekParnell (admin) Nov 08, 2010
- 2121 views
We could add a rule to the creole parser that if it sees -- (but not ----) and does not see a matching -- on the same line, then it will not cause the text to be struck out. In other words, strikeout will only occur on text that is enclosed by -- on the same line.
How does that idea sound?
The downfall would be marked a paragraph removed. Not sure which is more of a downfall though.
Jeremy
Huh? I don't understand what you said.
34. Re: Two Common Formatting Mistakes on the Forum
- Posted by DanM Nov 08, 2010
- 2135 views
We could add a rule to the creole parser that if it sees -- (but not ----) and does not see a matching -- on the same line, then it will not cause the text to be struck out. In other words, strikeout will only occur on text that is enclosed by -- on the same line.
How does that idea sound?
I'm using Firefox 3, saw the original unintended strikeouts in Preview of quoted replies, BUT I DON'T SEE THE STRIKEOUTS THERE NOW, LOOKS LIKE IT'S FIXED?
[EDITED] Didn't see Jeremy's post when I wrote the above, so thanks Derek!
35. Re: Two Common Formatting Mistakes on the Forum
- Posted by jeremy (admin) Nov 08, 2010
- 2102 views
The downfall would be marked a paragraph removed. Not sure which is more of a downfall though.
Huh? I don't understand what you said.
Sorry, I'm having problems with my left hand and am having to do editing, that sentence didn't come out right.
The down fall to making strikeout work only per line is if you have a paragraph of lines you want to strikeout. You would have to do it on each line, is that correct? i.e.
--Line number one-- --Line number two-- --Line number three-- New paragraph
What if it were done on a block basis? What I mean by block is anything that creates a logical block in HTML, for example a paragraph, a list item, a table column. So, all of these would be simple double dashes:
* John Doe -- Name * 22 -- Age | John Doe | -- Name | | 22 | -- Age | Hello, world. How are you doing? -- Greeting
Jeremy
36. Re: Two Common Formatting Mistakes on the Forum
- Posted by jeremy (admin) Nov 08, 2010
- 2132 views
I'm using Firefox 3, saw the original unintended strikeouts in Preview of quoted replies, BUT I DON'T SEE THE STRIKEOUTS THERE NOW, LOOKS LIKE IT'S FIXED?
See message 32 in this thread.
Jeremy
37. Re: Two Common Formatting Mistakes on the Forum
- Posted by DanM Nov 08, 2010
- 2139 views
I'm using Firefox 3, saw the original unintended strikeouts in Preview of quoted replies, BUT I DON'T SEE THE STRIKEOUTS THERE NOW, LOOKS LIKE IT'S FIXED?
See message 32 in this thread.
Jeremy
Sorry, I was replying to message 28, didn't see #32 at that time.
