Actually it is supported. <snip>It needs some fiddling to get the result you want.
At the risk of quibbling, or appearing ungrateful, I think the current behavior is not helpfully supportive of an important subset of the BBCode I was customarily using. I don't doubt it all makes sense in terms of underlying behavior, but for this user, it is a big step backward, especially as the use of BBCode is implicitly encouraged.
Shawn wrote:
In the meantime, you can go to the "Format" box and select "Preformatted".
Thank you, Shawn. My personal "eye filter" was skipping over that entire menu bar. I've never used it on any web site where I post. Now I must here.
As you suggest, I now realize I can get usefully aligned tables, such as this test case, but even when I have selected preformatted, it is adding an extra linefeed I don't want unless I use the shift+enter trick:
Header1 Header2
value1 value2 (when I use the keyboard "enter" key)
value1 value2 (when I depress the keyboard "shift" key, then enter)
I personally agree with you that the current setup is confusing. I am working on a way to clarify this for users.
Also, I forgot that you can click "Disable rich-text", which will send you to a plain text editor. There you can use [code] and other BBcode tags without the Rich-text filter interfering. Unfortunately you can't "Preview" your comment as it will switch back to the Rich-text editor and erase/change your BBcode text. Instead you should Post Comment without Previewing.
Also, I forgot that you can click "Disable rich-text", which will send you to a plain text editor. you should Post Comment without Previewing.
I'm having a try at that now:
[pre]
Header1 Header2
Value1 Value2
Value3 Value4[/pre]
An added bonus is that with rich text disabled the extremely annoying insertion of un-requested line-feeds seems to go away.
I'm pretty sure I tried rich-text disabled before, but used preview, so thanks a lot for your advice of the destructive effects of using that feature. As I am of an age and disability where reviewing anything I type is essential, I'll just have to try harder to review the input box, and perhaps catch some things by editing after posting--though I'll likely need to purge much "inherited" HTML to make that work (as I had to in quoting you for this post).
Obviously that did not work for me. I don't know what I did wrong. Perhaps the fact I started using the "quote" function, then changed to disable rich-text. But I thought I got rid of absolutely all the odd stuff inherited into the box that way, and I did hit "post comment" without ever having previewed so don't know why the pre tag seems not to function in this case.
So for the moment my path to getting done what I need to do seems largely to avoid BBCode explicit use, and learn to use the capabilities on the formatting bar, with suppressed mild cursing at the extra linefeeds inserted.
Obviously that did not work for me. I don't know what I did wrong. Perhaps the fact I started using the "quote" function, then changed to disable rich-text. But I thought I got rid of absolutely all the odd stuff inherited into the box that way, and I did hit "post comment" without ever having previewed so don't know why the pre tag seems not to function in this case.
I believe the pre tag is no longer supported. You should be able to get what you want with the "code" tag instead:
Example with fixed-width font, and it preserves
both spaces and
line breaks
When previewing a new post the subject is not displayed in the CURRENT STYLE OF BOLD CAPITALS - but displays a soft yellow box of silence (in lower case of course)
Interesting, what Browser are you using? The yellow background should be bigger and remind you that it only is a preview. The reply preview should also have this yellow background but it does not. So this is a bug. Here is how it should look like:
Edit: Nevermind. I just created a new thread and in the preview the title is indeed missing and the yellow box does not span the whole post. This looks like a minor CSS issue. I'll add it to our list of things to fix.
FYI: I can't reproduce that behavior using Safari. Both previews have the expected yellow background, so it's a browser-dependent CSS issue. The title isn't shown in the new topic preview, but again, it was probably never intended to.
Christian Beer wrote:Actually
)
At the risk of quibbling, or appearing ungrateful, I think the current behavior is not helpfully supportive of an important subset of the BBCode I was customarily using. I don't doubt it all makes sense in terms of underlying behavior, but for this user, it is a big step backward, especially as the use of BBCode is implicitly encouraged.
Thank you, Shawn. My personal "eye filter" was skipping over that entire menu bar. I've never used it on any web site where I post. Now I must here.
As you suggest, I now realize I can get usefully aligned tables, such as this test case, but even when I have selected preformatted, it is adding an extra linefeed I don't want unless I use the shift+enter trick:
Header1 Header2
value1 value2 (when I use the keyboard "enter" key) value1 value2 (when I depress the keyboard "shift" key, then enter)
@Archae86, I personally
)
@Archae86,
I personally agree with you that the current setup is confusing. I am working on a way to clarify this for users.
Also, I forgot that you can click "Disable rich-text", which will send you to a plain text editor. There you can use [code] and other BBcode tags without the Rich-text filter interfering. Unfortunately you can't "Preview" your comment as it will switch back to the Rich-text editor and erase/change your BBcode text. Instead you should Post Comment without Previewing.
Einstein@Home Project
Shawn Kwang wrote:Also, I
)
I'm having a try at that now:
[pre]
Header1 Header2
Value1 Value2
Value3 Value4[/pre]
An added bonus is that with rich text disabled the extremely annoying insertion of un-requested line-feeds seems to go away.
I'm pretty sure I tried rich-text disabled before, but used preview, so thanks a lot for your advice of the destructive effects of using that feature. As I am of an age and disability where reviewing anything I type is essential, I'll just have to try harder to review the input box, and perhaps catch some things by editing after posting--though I'll likely need to purge much "inherited" HTML to make that work (as I had to in quoting you for this post).
archae86 wrote:I'm having a
)
Obviously that did not work for me. I don't know what I did wrong. Perhaps the fact I started using the "quote" function, then changed to disable rich-text. But I thought I got rid of absolutely all the odd stuff inherited into the box that way, and I did hit "post comment" without ever having previewed so don't know why the pre tag seems not to function in this case.
So for the moment my path to getting done what I need to do seems largely to avoid BBCode explicit use, and learn to use the capabilities on the formatting bar, with suppressed mild cursing at the extra linefeeds inserted.
Thanks.
archae86 wrote:archae86
)
I believe the pre tag is no longer supported. You should be able to get what you want with the "code" tag instead:
Einstein@Home Project
When previewing a new post
)
When previewing a new post the subject is not displayed in the CURRENT STYLE OF BOLD CAPITALS - but displays a soft yellow box of silence (in lower case of course)
Silence? The preview just
)
Silence? The preview just shows the post, but yes, without the title since there's nothing to preview for the title as you can't style it anyway.
Best,
Oliver
Einstein@Home Project
(No subject)
)
Thanks for the reply Oliver, I should have included a screenshot.
If i compare a New Post Preview here
With a Reply Preview here
You will see an empty yellow header box, (and extra dotted line) i assumed that was intended for the Subject.
Interesting, what Browser are
)
Interesting, what Browser are you using? The yellow background should be bigger and remind you that it only is a preview. The reply preview should also have this yellow background but it does not. So this is a bug. Here is how it should look like:
Edit: Nevermind. I just created a new thread and in the preview the title is indeed missing and the yellow box does not span the whole post. This looks like a minor CSS issue. I'll add it to our list of things to fix.
FYI: I can't reproduce that
)
FYI: I can't reproduce that behavior using Safari. Both previews have the expected yellow background, so it's a browser-dependent CSS issue. The title isn't shown in the new topic preview, but again, it was probably never intended to.
Oliver
Einstein@Home Project