Last modified: 2013-06-18 16:31:40 UTC
Created attachment 7713 [details] The parsed code with the splitted layout. Previously, I was using GeshiCodeTag.php and decided to switch to SyntaxHighlight_GeSHi due to the fact that it was supported widely. I heavily use listed descriptions in my wiki such as: ================ We'll assume we're continuing from [[Installing mediawiki]]. #Create the directory for the new wikis #:<code>cd /wikifarm/ sudo mkdir wiki1 </code> #Create the specific directories #:<code>cd wiki1 sudo mkdir images config sudo chmod a+w config </code> #Link the source files from the main wiki #:<code>sudo ln -s /wikifarm/wikimain/* . sudo ln -s /wikifarm/wikimain/config/index.php config/ </code> ================ but when I tried to adopt it by replacing the "<code>","</code>" tags with "<syntaxhighlight lang="bash">,</syntaxhighlight> it produced erratic results as captured in the attached file. If the block is a one-liner, the fontsize of the option links (i.e., page/discussion/edit/...) gets smaller and disoriented -- it the block is multi-lined it gets worse, with the layout becoming splitted. I repeated this error on the wikipedia (in the Sandbox page) to make sure that it wasn't my system configuration related. With my best regards, Sururi
Correction: In the sandbox, the layout doesn't get distorted but the multi-lines still aren't supported.
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
This is a bug again when using MediaWiki 1.20.2 with SyntaxHighlight 1.0.8.11
That's how wikitext lists work: each list item is only one line. There's no way to put a multi-line construct in a wikitext list. *** This bug has been marked as a duplicate of bug 1581 ***
Sorry, didn't see this reply until now.. It has definitely worked in the past, as my wiki completely changed shape upon an upgrade. I see you have pointed the finger at the MediaWiki parser and can now understand the background. Do you happen to know if the perser project is likely to fix this any time soon?