Table Tag

[TosaInu]

therother, seems that each cell is using = from a worksheet? I'm pretty sure that shouldn't be there (possibly only visible in the WYSIWYG editor).


It's not perfect (adds a space between bl and a near end) but it should do in some cases.

It's adding extra " with the smiley, I guess the textparser can be fixed for this.

[Mouzafphaerre]

-
Thank you very much Tosa. I believe I can hack the autobreaking lines with my own tricks for now.
-

[therother]

These are some entries that aren't formatted quite right -

The 1st, 3rd and 4th have the "=" displayed instead of aligning the text in the centre. The 2nd one is different - under the CufForm Column, 10 is displayed as 1 0 for some reason.

As a say above, removing any character on the left hand side of the aberation removes the problem.

Hmm, now this is curious: this is the code for the table, pasted into the standard editor from notepad:

3^=Name|=Dist|=Dist-10|=Game %|=WithRules|=Diff|=CurForm|=Diff2|=Dist|=Dist-10
2^=Thermon|=19.6977156|=9.697715604|=10|=10|=0|=5|=-5|=19.6977156|=9.697715604
2^=Larissa|=22.36067977|=12.36067977|=10|=10|=0|=10|=0|=22.36067977|=12.36067977
2^=Thessalonica|=24.51530134|=14.51530134|=15|=15|=0|=10|=-5|=24.
2^=Segestica|=28.46049894|=18.46049894|=15|=20|=5|=15|=0|=28.46049894|=18.46049894

Notice the spaces, and crucially the position of them. I wonder why this is?

[TosaInu]

Hello therother,

It's an odd thing, but try skipping the = signs in the input, they are not required.

[therother]

It's an odd thing, but try skipping the = signs in the input, they are not required.

I don't think that it's the = sign that is causing the problem - the board seems to add a space into "words" over 60 characters in length:

For example:

1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890 123456789012345678901234567890

There are no spaces in that number, yet one is added after the 60th character, and again after the 120th.

This explains the mysterious =, as the table was entered without spaces, as well as the odd spaces that appear in the table.

A "=" appears when the 60th character is after the division marker |, so something entered as "|=60" becomes "| =60", resulting in the = being displayed instead of centring the text.

A workaround would be to insert spaces before the |, and try not to use 60 digit numbers or 60 character words!

And so the hack itself is exonerated.

[TosaInu]

Yes, there's adding of spaces. That's something that showed up with the linebreak 'test'. Typing '=' signs in cells is redundant here as they are not required. It may not cause the problem, but the specific problem in above example can be avoided by deleting =.

3^Name|Dist|Dist-10|Game %|WithRules|Diff|CurForm|Diff2|Dist|Dist-10
7^Thermon|19.6977156|9.697715604|10|10|0|5|-5|19.6977156|9.697715604
7^Larissa|22.36067977|12.36067977|10|10|0|10|0|22.36067977|12.36067977
7^Thessalonica|24.51530134|14.51530134|15|15|0|10|-5|24.
7^Segestica|28.46049894|18.46049894|15|20|5|15|0|28.46049894|18.46049894

[therother]

What you say is true. However, the ability to align text is useful, especially if there is a wide range of column widths.
e.g.
[table 1 2 2]=This is a wide column|=Narrow
=Narrow|=narrow[/table]
To me, the 2nd version just looks nicer, and is easier to read.

I still think the best solution, in terms of data fidelity, is to ensure that no entry is more than 60 characters in length, as this will eliminate both the extra spaces and any erroneously displayed alignment characters (i.e. = and/or ~).

For example, in the table without the = signs above, we have entries of

22. 36067977
2 8.46049894

Your eye can certainly compensate for these errors when reading, but if the table is presenting data to be copied and pasted by members, then 2 8.46049894 is not the same as 28.46049894, and you may not notice the spaces when you've just copied a 100x6 table!

Edit: This is a centred version of the table above, with a space inserted after the Game % entry. As the Column is 6 characters wide in any case, it makes no difference to the appearance of the table, as the extra space seems to be chopped off, i.e. it doesn't appear when you copy the table and paste it into a local application (e.g. a spreadsheet).