Displaying crosstables in the forum

[BobMessenger]

@Hal Terrie

P.S. I know there must be a way to turn the above into a nicely formatted chart with all the values centered under the headers but I can’t figure out how to do it. Can someone explain the method?

Use [ code ] and [ /code ] tags (without the spaces). See the BBCode guide.

[Smythe_Dakota]

@BobMessenger

… Use [ code ] and [ /code ] tags (without the spaces). See the BBCode guide.

That’ll work, but it’s tiny and difficult to read. I don’t like it.

The main problem is, that without the [code] tag, multiple consecutive spaces are automatically converted to single spaces. That messes up the intended column alignment. But if you use periods instead of spaces (at least when you want more than one space), you can get closer to what you want. Because of the variable character width, you’ll still have to switch back and forth into and out of Preview mode several times and experiment with how many periods you’ll need between each pair of entries in each row:

Name … wins … draws … losses
Susie … 9 … 15 … 12
Bob … 14 … 6 … 4

Finally, if you want to make the periods invisible, just surround each bunch of periods with the “Font colour” tag and choose color FFFFFF (white):

Name … wins … draws … losses
Susie … 9 … 15 … 12
Bob … 14 … 6 … 4

This is tedious, but if you really care about the quality of your work (blah blah blah) …

Bill Smythe

[BobMessenger]

@Smythe Dakota

@BobMessenger

… Use [ code ] and [ /code ] tags (without the spaces). See the BBCode guide.

That’ll work, but it’s tiny and difficult to read. I don’t like it.

You can increase the font size:

[ size=150 ][ code ]
Name wins draws losses
Susie 9 15 12
Bob 14 6 4
[ /code ][ /size ]

This displays as:

[size=150] Name wins draws losses Susie 9 15 12 Bob 14 6 4 [/size]

[Smythe_Dakota]

The larger size does indeed make a great difference. For some reason I had thought the [size] tag wouldn’t work with [code].

Now if only it were possible to change the color, and/or to use bolding, within a [code]. That light green color is atrocious for those of us with old eyes.

Bill Smythe

[BobMessenger]

@Smythe Dakota

The larger size does indeed make a great difference. For some reason I had thought the [size] tag wouldn’t work with [code].

Now if only it were possible to change the color, and/or to use bolding, within a [code]. That light green color is atrocious for those of us with old eyes.

Bill Smythe

You can change the color for the entire code block, but I don’t think you can make changes within the block.

[jwiewel]

@BobMessenger

@Smythe Dakota

The larger size does indeed make a great difference. For some reason I had thought the [ size] tag wouldn’t work with [ code].

Now if only it were possible to change the color, and/or to use bolding, within a [ code]. That light green color is atrocious for those of us with old eyes.

Bill Smythe

You can change the color for the entire code block, but I don’t think you can make changes within the block.

[size=150] Name wins draws losses Susie 9 15 12 Bob 14 6 4[/size]

[size=150] Name wins draws losses Susie 9 15 12 Bob 14 6 4 [/size]

[size=150] Name wins draws losses Susie 9 15 12 Bob 14 6 4 [/size]
Here are examples with color inside code, between size and code, and outside size. The color only affects the word CODE

[BobMessenger]

Oops, I should have tested it first. You can at least do this:
[size=150][code]

Name wins draws losses
Susie 9 15 12
Bob 14 6 4

[/code][/size]

[wintdoan]

I have a solution (not to the pairing issue, but to the display issue—probably need to split the topic). Define a new BB Code that maps to the HTML

. If one doesn’t want to be original with the name, this can be

[pre]{TEXT}[/pre]
as the usage
and
{TEXT}
as the HTML replacement. Unlike code (which is designed for verbatim rendering), pre takes HTML codes within it, so you can add color highlighting, or underline or bold face or put in a smilie. The only loss is that it doesn’t provide a scroll box—20 lines takes up 20 lines in the post.

[BobMessenger]

This topic is a spin-off from Pairing Issue.

[GKarRacer]

@wintdoan

I have a solution (not to the pairing issue, but to the display issue—probably need to split the topic). Define a new BB Code that maps to the HTML

. If one doesn’t want to be original with the name, this can be

[pre]{TEXT}[/pre]
as the usage
and
{TEXT}
as the HTML replacement. Unlike code (which is designed for verbatim rendering), pre takes HTML codes within it, so you can add color highlighting, or underline or bold face or put in a smilie. The only loss is that it doesn’t provide a scroll box—20 lines takes up 20 lines in the post.

What’s really needed is a BBCode for an HTML TABLE. Then all other formatting would still apply. Perhaps this is available in a newer version of BB? Don’t know…

[wintdoan]

@GKarRacer

@wintdoan

I have a solution (not to the pairing issue, but to the display issue—probably need to split the topic). Define a new BB Code that maps to the HTML

. If one doesn’t want to be original with the name, this can be

[pre]{TEXT}[/pre]
as the usage
and
{TEXT}
as the HTML replacement. Unlike code (which is designed for verbatim rendering), pre takes HTML codes within it, so you can add color highlighting, or underline or bold face or put in a smilie. The only loss is that it doesn’t provide a scroll box—20 lines takes up 20 lines in the post.

What’s really needed is a BBCode for an HTML TABLE. Then all other formatting would still apply. Perhaps this is available in a newer version of BB? Don’t know…

One can add table, tr and td relatively easily. I don’t think it’s built in.

[Akzidenz]

@BobMessenger

@Smythe Dakota

@BobMessenger

… Use [ code ] and [ /code ] tags (without the spaces). See the BBCode guide.

That’ll work, but it’s tiny and difficult to read. I don’t like it.

You can increase the font size:

[ size=150 ][ code ]
Name wins draws losses
Susie 9 15 12
Bob 14 6 4
[ /code ][ /size ]

This displays as:

[size=150] Name wins draws losses Susie 9 15 12 Bob 14 6 4 [/size]

Yes, the “code” and “pre” tags work the same way: both call a monospaced font, in this case, Courier New, which most users have on their computers. That comes in handy for quick display of WinTD output on a web page, or even in an HTML email, without having to table-tag it. For any other font, you would have to use table commands to line stuff up properly.

[wilecoyote]

@Akzidenz

@BobMessenger

@Smythe Dakota

@BobMessenger

… Use [ code ] and [ /code ] tags (without the spaces). See the BBCode guide.

That’ll work, but it’s tiny and difficult to read. I don’t like it.

You can increase the font size:

[ size=150 ][ code ]
Name wins draws losses
Susie 9 15 12
Bob 14 6 4
[ /code ][ /size ]

This displays as:

[size=150] Name wins draws losses Susie 9 15 12 Bob 14 6 4 [/size]

Yes, the “code” and “pre” tags work the same way: both call a monospaced font, in this case, Courier New, which most users have on their computers. That comes in handy for quick display of WinTD output on a web page, or even in an HTML email, without having to table-tag it. For any other font, you would have to use table commands to line stuff up properly.

But even with the “code” and “pre” tags, it is still a pain in the posterior to use spaces to line up columns.

[wintdoan]

@wilecoyote

But even with the “code” and “pre” tags, it is still a pain in the posterior to use spaces to line up columns.

True, since the forum editor uses a proportional font. You really have to run everything through a WYSIWYG editor set for a Courier font and paste the results into the forum from that. With WinTD, you can print a wall chart to a text window and copy and paste that in.

[code] Name Group/Team Rate Rnd 1 Rnd 2

1. A2189 |2189 | B 31 | W 18 |
   |nnnn | 1.0 | 2.0 |

---

2. A2120 |2120 | W 23 | B 17 |
   |nnnn | 1.0 | 2.0 |

---

3. A1960 |1960 | B 24 | W 19 |
   |nnnn | 1.0 | 2.0 |

---

4. A1825 |1825 | B 26 | W 20 |
   |nnnn | 1.0 | 2.0 |

---

5. B1813 |1813 | W 27 | B 21 |
   |nnnn | 1.0 | 2.0 |

---

6. A1813 |1813 | B 29 | W 22 |
   |nnnn | 1.0 | 2.0 |

---

7. A1754 |1754 | W 30 | B 28 |
   |nnnn | 1.0 | 2.0 |

---

8. A1895 |1895 | W 25 | B 12 |
   |nnnn | 1.0 | 1.5 |

---

9. A1718 |1718 | HALF | B 32 |
   |nnnn | 0.5 | 1.5 |

---

10. A1698 |1698 | B 37 | HALF |
    |nnnn | 1.0 | 1.5 |

---

11. A1641 |1641 | B 41 | HALF |
    |nnnn | 1.0 | 1.5 |

---

12. A1636 |1636 | B 39 | W 8 |
    |nnnn | 1.0 | 1.5 |

---

13. A1089 |1089 | HALF | B 34 |
    |nnnn | 0.5 | 1.5 |

---

14. A1052 |1052 | HALF | W 35 |
    |nnnn | 0.5 | 1.5 |

---

15. A1879 |1879 | HALF | HALF |
    |nnnn | 0.5 | 1.0 |

---

16. A1849 |1849 | HALF | HALF |
    |nnnn | 0.5 | 1.0 |

---

17. A1734 |1734 | B 36 | W 2 |
    |nnnn | 1.0 | 1.0 |

---

18. A1708 |1708 | W 33 | B 1 |
    |nnnn | 1.0 | 1.0 |

---

19. A1668 |1668 | W 38 | B 3 |
    |nnnn | 1.0 | 1.0 |

---

20. A1550 |1550 | W 40 | B 4 |
    |nnnn | 1.0 | 1.0 |

---

21. A1500 |1500 | B 42 | W 5 |
    |nnnn | 1.0 | 1.0 |

---

22. A1488 |1488 | W 44 | B 6 |
    |nnnn | 1.0 | 1.0 |

---

23. A1450 |1450 | B 2 | W 36 |
    |nnnn | 0.0 | 1.0 |

---

24. A1428 |1428 | W 3 | B 38 |
    |nnnn | 0.0 | 1.0 |

---

25. A1409 |1409 | B 8 | W 37 |
    |nnnn | 0.0 | 1.0 |

---

26. A1167 |1167 | W 4 | B 40 |
    |nnnn | 0.0 | 1.0 |

---

27. A1014 |1014 | B 5 | W 39 |
    |nnnn | 0.0 | 1.0 |

---

28. A940 | 940 | W 43 | W 7 |
    |nnnn | 1.0 | 1.0 |

---

29. A925 | 925 | W 6 | B 44 |
    |nnnn | 0.0 | 1.0 |

---

30. A878 | 878 | B 7 | W 42 |
    |nnnn | 0.0 | 1.0 |

---

31. A1485 |1485 | W 1 | B 33 |
    |nnnn | 0.0 | 0.5 |

---

32. A1049 |1049 | HALF | W 9 |
    |nnnn | 0.5 | 0.5 |

---

33. A747 | 747 | B 18 | W 31 |
    |nnnn | 0.0 | 0.5 |

---

34. A591 | 591 | HALF | W 13 |
    |nnnn | 0.5 | 0.5 |

---

35. A261 | 261 | HALF | B 14 |
    |nnnn | 0.5 | 0.5 |

---

36. A831 | 831 | W 17 | B 23 |
    |nnnn | 0.0 | 0.0 |

---

37. A742 | 742 | W 10 | B 25 |
    |nnnn | 0.0 | 0.0 |

---

38. A615 | 615 | B 19 | W 24 |
    |nnnn | 0.0 | 0.0 |

---

39. A523 | 523 | W 12 | B 27 |
    |nnnn | 0.0 | 0.0 |

---

40. A372 | 372 | B 20 | W 26 |
    |nnnn | 0.0 | 0.0 |

---

41. A294 | 294 | W 11 | ZERO |
    |nnnn | 0.0 | 0.0 |

---

42. A286 | 286 | W 21 | B 30 |
    |nnnn | 0.0 | 0.0 |

---

43. A256 | 256 | B 28 | ZERO |
    |nnnn | 0.0 | 0.0 |

---

44. A243 | 243 | B 22 | W 29 |
    |nnnn | 0.0 | 0.0 |

---

[/code]

[Smythe_Dakota]

@BobMessenger

Oops, I should have tested it first. You can at least do this:
[size=150][code]

Name wins draws losses
Susie 9 15 12
Bob 14 6 4

[/code][/size]

So [code=php] instead of just [code] displays in blue instead of green. That’s an improvement. Are there any other options, such as colors other than blue and green, or bolding, etc?

Bill Smythe

[Smythe_Dakota]

@Akzidenz

… Yes, the “code” and “pre” tags work the same way: both call a monospaced font, in this case, Courier New, which most users have on their computers. …

What’s this “pre” tag all about? It’s not listed on the PHP help screen, and it doesn’t seem to do anything, at least not on this forum.

Bill Smythe

[BobMessenger]

@Smythe Dakota

@BobMessenger

Oops, I should have tested it first. You can at least do this:
[size=150][code]

Name wins draws losses
Susie 9 15 12
Bob 14 6 4

[/code][/size]

So [code=php] instead of just [code] displays in blue instead of green. That’s an improvement. Are there any other options, such as colors other than blue and green, or bolding, etc?

Bill Smythe

Nothing useful, as far as I can tell.

[wintdoan]

@Smythe Dakota

@Akzidenz

… Yes, the “code” and “pre” tags work the same way: both call a monospaced font, in this case, Courier New, which most users have on their computers. …

What’s this “pre” tag all about? It’s not listed on the PHP help screen, and it doesn’t seem to do anything, at least not on this forum.

Bill Smythe

It’s an HTML tag, not part of the standard PhpBB:

w3schools.com/tags/tag_pre.asp

The main difference between “pre” and “code” is that anything inside code is included exactly (thus code can be used to demonstrate html), while pre allows embedded html tags.

[Smythe_Dakota]

@I

… Are there any other options … ?

@In response

… Nothing useful, as far as I can tell.

OK, well, at least you guys have demonstrated how to print in blue instead of green, and that [size] can be used with [code]. That takes care of the worst problems, I’d say. Thank you.

Bill Smythe

[BobMessenger]

I’ve moved a discussion about displaying crosstables on MSA in tiebreak order to the existing topic Allowing USCF crosstables to be shown in tiebreak order in the US Chess Issues forum.