Template:Eyecatch/Test Code

Tests 1111

test n1
test n2
test n3
test n4
test n5
test n6
test n7
test n8
test n9

Tests 2222

test
0
test
1
test
2
test
3


test
3
test
3


Real-world Examples

Real-world test of the code, issue empty line before eycatch:

Test 0 - Old code, if "info" = 2, it would indent by 2

No longer an issue!

2 Special case {{eyecatch|2|blah}} - Not all groups provide CRC checksums for their files. This means that this status has no meaning and will have the value "not checked against official CRC".


Test 1 - Empty line before and after eyecatch

Spacing below and above box is OK, space above box shows one "empty line" too much. VERY UGLY! FIXED!
Indicates whether the file entry in AniDB represents a perfect copy of the original file or not. You may request a change of the CRC Status if its not checked yet.

Note {{eyecatch|Note|blah}} - Not all groups provide CRC checksums for their files. This means that this status has no meaning and will have the value "not checked against official CRC".

Read more about file verification if you are unfamiliar with this subject.


Test 2 - Empty line before and after eyecatch, indent 1

Spacing below box is OK, space above box shows one "empty line" too much. VERY UGLY!
Indicates whether the file entry in AniDB represents a perfect copy of the original file or not. You may request a change of the CRC Status if its not checked yet.


Note {{eyecatch|1|Note|blah}} - Not all groups provide CRC checksums for their files. This means that this status has no meaning and will have the value "not checked against official CRC".

Read more about file verification if you are unfamiliar with this subject.


Note {{eyecatch|4|Note|blah}} - Not all groups provide CRC checksums for their files. This means that this status has no meaning and will have the value "not checked against official CRC".

Text text and even more text to test the code. Text text and even more text to test the code. Text text and even more text to test the code.


Test 3 - NO Empty line before and after eyecatch

Spacing above and below the box looks OK.
Indicates whether the file entry in AniDB represents a perfect copy of the original file or not. You may request a change of the CRC Status if its not checked yet.

Note {{eyecatch|Note|blah}} - Not all groups provide CRC checksums for their files. This means that this status has no meaning and will have the value "not checked against official CRC".

Read more about file verification if you are unfamiliar with this subject.


Test 4 - NO Empty line before and after eyecatch, indent 1

Spacing above and below the box looks OK.
Indicates whether the file entry in AniDB represents a perfect copy of the original file or not. You may request a change of the CRC Status if its not checked yet.

Note {{eyecatch|1|Note|blah}} - Not all groups provide CRC checksums for their files. This means that this status has no meaning and will have the value "not checked against official CRC".

Read more about file verification if you are unfamiliar with this subject.


Test 5 - Two eyecatch blocks, no empty lines

Spacing above and below the boxes looks OK. IMO it would be better to have a slight space between the two eyecatch boxes for the normal un-indented eyecatch usage.
AniDB stores the name and short name of the group/person that produced and released a file. The short name is usually found as tags in file names, for example "[AonE]".

Note {{eyecatch|Note|blah}} - If a file is a joint release, like a file by e.g. ANBU-AonE, that joint group has its own group entry. The file should not be registered under either ANBU or AonE, but to the group that combines them both.
Note {{eyecatch|Note|blah}} - Not all RAW groups are credited. See which RAW groups to credit.

Please note that not all groups registered in AniDB are listed with the tag they actually use, as AniDB can only have one distinctive tag for each group.


Test 6 - Two eyecatch blocks, indent 1, no empty lines

The slight space above, below and between the two eyecatch boxes looks fine, when NOT using extra empty lines in-text. But only for the indented eyecatch!
AniDB stores the name and short name of the group/person that produced and released a file. The short name is usually found as tags in file names, for example "[AonE]".

Note {{eyecatch|1|Note|blah}} - If a file is a joint release, like a file by e.g. ANBU-AonE, that joint group has its own group entry. The file should not be registered under either ANBU or AonE, but to the group that combines them both.
Note {{eyecatch|1|Note|blah}} - Not all RAW groups are credited. See which RAW groups to credit.

Please note that not all groups registered in AniDB are listed with the tag they actually use, as AniDB can only have one distinctive tag for each group.


Results

  • {{eyecatch|0|Note|blah}} works exactly the same as {{eyecatch|Note|blah}}
  • Empty or wrong entries (e.g. xyz) in # field, yields default eyecatch without an indent.
    e.g. {{eyecatch|Note|blah}} or {{eyecatch|xyz|Note|blah}}
    -> seems to be fool proof.


Solution

Basically the code works better than the original old version, i.e. the spacing above and below the the eyecatch boxes *now* looks really nice.

So, *never* add an empty line above the eyecatch box!

A empty line below the eyecatch box is ignored!

--foo2 14:38, 28 April 2009 (UTC)

MediaWiki spam blocked by CleanTalk.
MediaWiki spam blocked by CleanTalk.