You can also use BBcode [nobsp] for a non-breaking space to avoid text in columns being broken up in multiple lines.
Sure, Unicode U+2800 likely works too but it's kind of a hack as this is the Braille Space character. Pedantic users should probably opt for the correct Unicode character for a non-breaking space which is U+00A0, but I haven't tried it and so far can't confirm it's rendered properly by SMF code used for this forum.
Topic: Some suggestions if you want to use tables on Bitcointalk (Read 1260 times)
If possible, maybe you can still edit your post here to remove your pyramid quote.
And maybe the topic about pyramid quotes is also an interesting one for translation to your local board.
Thanks for the correction, sir. I have already corrected my mistake and am quite sure that many other members of my local board don’t understand anything concerning pyramid quotes. I will like to use your suggestion to request the translation of the topic about pyramid quotes to my local board.
| Language | translated by | Title |
| ___________________________ | _____________________ | _______________________________________________________________________ |
| Nigeria (Naija) | Egii Nna | reserved |
I want to use this medium to inform you that translation is ready at my local board. The links will be shared below.
https://bitcointalksearch.org/topic/m.63430897
Your translation got approved, I've added it to my list:
| Language | translated by | Title |
| ___________________________ | _____________________ | _______________________________________________________________________ |
| Nigeria (Naija) | Egii Nna | Another suggestion if you wan use table for bitcointalk |
Many thanks for providing a translation about my topic.
Tables are always tricky to understand but formatted correcly, tables are very helpful to present content and data.
If possible, maybe you can still edit your post here to remove your pyramid quote.
And maybe the topic about pyramid quotes is also an interesting one for translation to your local board.
| Language | translated by | Title |
| ___________________________ | _____________________ | _______________________________________________________________________ |
| Nigeria (Naija) | Egii Nna | reserved |
I want to use this medium to inform you that translation is ready at my local board. The links will be shared below.
https://bitcointalksearch.org/topic/m.63430897
~~ snip~~
Hi @1miau I will like to translate this awesome topic to my local board (Naija local board), pidgin, if permitted, I will be extremely happy.
Sorry for bumping this.
I translate it here https://bitcointalk.org/index.php?topic=5252374.new#new and want to notify 1miau
Thanks for your translation and sorry for my late reply, I didn't saw it until now. I translate it here https://bitcointalk.org/index.php?topic=5252374.new#new and want to notify 1miau
I've added a very detailed tutorial about the basics how to create tables written by so98nn:
And if you want to read more about tables (basics explained in detail) , you can have a look here: Tutorial - How to create Table in the BitcoinTalk Forum.
In general, it helps to understand the BBCode how tables are working, good read.
Sorry for bumping this.
I translate it here https://bitcointalk.org/index.php?topic=5252374.new#new and want to notify 1miau
I translate it here https://bitcointalk.org/index.php?topic=5252374.new#new and want to notify 1miau
I'm not sure but it could be this https://bitcointalksearch.org/topic/m.17876458
It's also a good solution and similar to our ___ version. In our version we are using ____ like he's using transparent fffff: Funny there is no mention of the display rendering bug in the first column of a table. I think this is a problem with either SMF, Bitcointalk, or the particular version of SMF used in bitcointalk (or some modding done by the admin).
Thing is the first column will be too thin. And, this doesn't show in the preview, only when you post.
Using ___ is a clever way to force the width. Another is to simply bypass the first column entirely by having an empty one.
vs
Good point! I've added this to my OP. Thing is the first column will be too thin. And, this doesn't show in the preview, only when you post.
Using ___ is a clever way to force the width. Another is to simply bypass the first column entirely by having an empty one.
| many words many words many words many words many words many words many words many words many words | many words many words many words many words many words many words many words many words many words | many words many words many words many words many words many words many words many words many words |
vs
| many words many words many words many words many words many words many words many words many words | many words many words many words many words many words many words many words many words many words | many words many words many words many words many words many words many words many words many words |
Almost forgotten about it and I remember o_e_l_e_o had a good solution (here).
Sums up perfectly our problem.
Some people don't want the use of underscore ("_") char because it's not needed, of course, it can be made transparent by color code.
But ___ is a nice way to divide the header from the rest of the table. 
("_")
| 1 | 2 | 3 | 4 | 5 | 6 |
| _________________ | _________________ | _________________ | _________________ | _________________ | _________________ |
| Is | it | working | properly | ? | I think so. |
Thank you for sharing the code. I'm sure it'll improve the quality of my posts.
Funny there is no mention of the display rendering bug in the first column of a table. I think this is a problem with either SMF, Bitcointalk, or the particular version of SMF used in bitcointalk (or some modding done by the admin).
Thing is the first column will be too thin. And, this doesn't show in the preview, only when you post.
Using ___ is a clever way to force the width. Another is to simply bypass the first column entirely by having an empty one.
~snip
Thing is the first column will be too thin. And, this doesn't show in the preview, only when you post.
Using ___ is a clever way to force the width. Another is to simply bypass the first column entirely by having an empty one.
~snip
Some people don't want the use of underscore ("_") char because it's not needed, of course, it can be made transparent by color code. Another way that can be applied to make the code more efficient is to use transparent char ("⠀"= U+2800) instead of space char in the longest text/sentence in the first column.
This char will be also very helpful for signature designers, where they must use the minimum number of chars possible.
Funny there is no mention of the display rendering bug in the first column of a table. I think this is a problem with either SMF, Bitcointalk, or the particular version of SMF used in bitcointalk (or some modding done by the admin).
Thing is the first column will be too thin. And, this doesn't show in the preview, only when you post.
Using ___ is a clever way to force the width. Another is to simply bypass the first column entirely by having an empty one.
vs
Thing is the first column will be too thin. And, this doesn't show in the preview, only when you post.
Using ___ is a clever way to force the width. Another is to simply bypass the first column entirely by having an empty one.
| many words many words many words many words many words many words many words many words many words | many words many words many words many words many words many words many words many words many words | many words many words many words many words many words many words many words many words many words |
vs
| many words many words many words many words many words many words many words many words many words | many words many words many words many words many words many words many words many words many words | many words many words many words many words many words many words many words many words many words |
I like playing with Unicode when I have time to spare.
Here's a template that might be useful to someone:
Here's a template that might be useful to someone:
| ╔ | ══════════ | ╦ | ══════════ | ╦ | ══════════ | ╦ | ══════════ | ╗ |
| ║ | col 1 | ║ | col 2 | ║ | col 3 | ║ | col 4 | ║ |
| ╠ | ══════════ | ╬ | ══════════ | ╬ | ══════════ | ╬ | ══════════ | ╣ |
| ║ | xxx | ║ | xxx | ║ | xxx | ║ | xxx | ║ |
| ╚ | ══════════ | ╩ | ══════════ | ╩ | ══════════ | ╩ | ══════════ | ╝ |
Code:
[table]
[tr]
[td]╔[/td] [td]══════════[/td] [td]╦[/td]
[td]══════════[/td] [td]╦[/td]
[td]══════════[/td] [td]╦[/td]
[td]══════════[/td] [td]╗[/td]
[/tr]
[tr]
[td]║[/td] [td][b]col 1[/b][/td] [td]║[/td]
[td][b]col 2[/b][/td] [td]║[/td]
[td][b]col 3[/b][/td] [td]║[/td]
[td][b]col 4[/b][/td] [td]║[/td]
[/tr]
[tr]
[td]╠[/td] [td]══════════[/td] [td]╬[/td]
[td]══════════[/td] [td]╬[/td]
[td]══════════[/td] [td]╬[/td]
[td]══════════[/td] [td]╣[/td]
[/tr]
[tr]
[td]║[/td] [td]xxx[/td] [td]║[/td]
[td]xxx[/td] [td]║[/td]
[td]xxx[/td] [td]║[/td]
[td]xxx[/td] [td]║[/td]
[/tr]
[tr]
[td]╚[/td] [td]══════════[/td] [td]╩[/td]
[td]══════════[/td] [td]╩[/td]
[td]══════════[/td] [td]╩[/td]
[td]══════════[/td] [td]╝[/td]
[/tr]
[/table]
I hope I understand you correctly, like that:
Thank you for the given format, that is what I would like to use if I want to add small notes beside images. This time, I saved your format and link to that post into my notebook, for later reference and for use.Code:
[table]
[tr]
[td]Picture[/td]
[td]Words[/td]
[/tr]
[tr]
[td]________________________________________[/td]
[td]______________________________[/td]
[/tr]
[tr]
[td][img height=350]https://i.imgur.com/Fs9qcge.png[/img][/td][td]thermos is keeping your tea safe and warm
thermos is keeping your tea safe and warm
thermos is keeping your tea safe and warm
thermos is keeping your tea safe and warm
thermos is keeping your tea safe and warm
thermos is keeping your tea safe and warm[/td]
[/tr]
[/table]
I'm not sure but it could be this https://bitcointalksearch.org/topic/m.17876458
It is not the post I mentioned but the given format results in same display. Thank you. 
For a long time ago, I read a post of one user whom guided to split table into two columns, one for image (on the left, for example), and another one for notes of that image (on the right). Unfortunately, I forgot to save that format.
I'm also searching sometimes, maybe you still know the topic and some key words posted in that topic to use the search button.
I'm not sure but it could be this https://bitcointalksearch.org/topic/m.17876458
I made a template to make a point and list for any post, anyone can edit with some table decoration by OP such as using |, *, + or ____,
Preview.
Here the code:
Preview.
| Your Point | ___ | List of point content |
| __________________ | ___ | __________________ |
| Poit A This is short summary | ___ |
|
| Point B This is short summary | ___ |
|
| Point C This is short summary | ___ |
|
| Poin D This is short summary | ___ |
|
Here the code:
Code:
[table]
[tr]
[td][b]Your Point[/b][/td]
[td][color=transparent]___[/color][/td]
[td][b]List of point content[/b][/td]
[/tr]
[tr]
[td][b]__________________[/b][/td]
[td][color=transparent]___[/color][/td]
[td][b]__________________[/b][/td]
[/tr]
[tr]
[td][b]Poit A[/b]
This is short summary [/td]
[td][color=transparent]___[/color][/td]
[td][list][li]Lorem ipsum[/li]
[li]Lorem ipsum dolor[/li]
[li]Lorem ipsum dolor sit amet[/li]
[/list][/td]
[/tr]
[tr]
[td][b]Point B[/b]
This is short summary [/td]
[td][color=transparent]___[/color][/td]
[td][list][li]Lorem ipsum[/li]
[li]Lorem ipsum dolor[/li]
[li]Lorem ipsum dolor sit amet[/li]
[/list][/td]
[/tr]
[tr]
[td][b]Point C[/b]
This is short summary [/td]
[td][color=transparent]___[/color][/td]
[td][list][li]Lorem ipsum[/li]
[li]Lorem ipsum dolor[/li]
[li]Lorem ipsum dolor sit amet[/li]
[/list][/td]
[/tr]
[tr]
[td][b]Poin D[/b]
This is short summary [/td]
[td][color=transparent]___[/color][/td]
[td][list][li]Lorem ipsum[/li]
[li]Lorem ipsum dolor[/li]
[li]Lorem ipsum dolor sit amet[/li]
[/list][/td]
[/tr]
[/table]
I'm not sure about BBCode but in Markdown you can make tables like:
And that fills in the table with a dark grey background for the headers and a light grey background for everything else. You could add more dashes to it but that is optional. I'm not a big fan of typing a bunch of underscores either, so I just play it safe and use the tr td notation here.
I don't know if it's possible for BBCode. You can do such kind of formatting and try to change the numbers ( I don't know what they mean Code:
Column A|Column B
---|---
Row A|Row A
Row B|Row B
And that fills in the table with a dark grey background for the headers and a light grey background for everything else. You could add more dashes to it but that is optional. I'm not a big fan of typing a bunch of underscores either, so I just play it safe and use the tr td notation here.
) Code:
[glow=#c6c6c6,2,300]such kind of formatting[/glow]
but it isn't really a satisfactory solution.
Maybe you can ask roslinpl, he did some great tutorials about BBCode: https://bitcointalksearch.org/topic/learn-bbcode-lessons-tutorials-tutorial-videos-1727100
Edit: there seems to be a solution (https://help.forumotion.com/t71690-background-for-bbcode-tables) but I tried and it didn't work. Maybe some BBCode designers can help out.
For a long time ago, I read a post of one user whom guided to split table into two columns, one for image (on the left, for example), and another one for notes of that image (on the right). Unfortunately, I forgot to save that format. I think that one is cool because it saves more space in post and in page of topic. Sometimes, we don't need a long paraphrase to describe one image, so that format makes sense.
If you can, please help me to do that, 1miau.
If you can, please help me to do that, 1miau.
I hope I understand you correctly, like that:
| Picture | Words |
| ________________________________________ | ________________________________________ |
 | thermos is keeping your tea safe and warm thermos is keeping your tea safe and warm thermos is keeping your tea safe and warm thermos is keeping your tea safe and warm thermos is keeping your tea safe and warm thermos is keeping your tea safe and warm |
Code:
[table]
[tr]
[td]Picture[/td]
[td]Words[/td]
[/tr]
[tr]
[td]________________________________________[/td]
[td]______________________________[/td]
[/tr]
[tr]
[td][img height=350]https://i.imgur.com/Fs9qcge.png[/img][/td][td]thermos is keeping your tea safe and warm
thermos is keeping your tea safe and warm
thermos is keeping your tea safe and warm
thermos is keeping your tea safe and warm
thermos is keeping your tea safe and warm
thermos is keeping your tea safe and warm[/td]
[/tr]
[/table]
?
Don't know if that's what you need.
I'm also searching sometimes, maybe you still know the topic and some key words posted in that topic to use the search button.
For a long time ago, I read a post of one user whom guided to split table into two columns, one for image (on the left, for example), and another one for notes of that image (on the right). Unfortunately, I forgot to save that format. I think that one is cool because it saves more space in post and in page of topic. Sometimes, we don't need a long paraphrase to describe one image, so that format makes sense.
If you can, please help me to do that, 1miau.
If you can, please help me to do that, 1miau.
I'm not sure about BBCode but in Markdown you can make tables like:
And that fills in the table with a dark grey background for the headers and a light grey background for everything else. You could add more dashes to it but that is optional. I'm not a big fan of typing a bunch of underscores either, so I just play it safe and use the tr td notation here.
Code:
Column A|Column B
---|---
Row A|Row A
Row B|Row B
And that fills in the table with a dark grey background for the headers and a light grey background for everything else. You could add more dashes to it but that is optional. I'm not a big fan of typing a bunch of underscores either, so I just play it safe and use the tr td notation here.
bump
I tried your given formats, and personally I like the first table template, rather than the second one with
Same here, the second one has also the disadvantage that several words per line will be splitted into two lines (if more than 2 words are used in the content and the line is longer than the headline): | xxxxx xxxxxxxx | | | xxx xxxxxxxx | | | xxxxxxxx xxxx | | |
| xxxxxxxxxxxx xxxxxxxxx | | | xxxxxx xxxxxxxxxxx | | | xxxxx xxxxxxxxxxx | | |
This layout is used here, for example: https://bitcointalksearch.org/topic/overview-of-bitcointalk-signature-ad-campaigns-last-update-01-jan-23-615953
So, it's still possible that the layout is looking good, but it's important which content should be posted there. After all, I prefer the first solution, too
Jump to: