Talk:LSL Portal

From Second Life Wiki
Jump to: navigation, search
Essay.png This is a talk page. Please sign comments you leave here by putting four tildes (~~~~) at the end of your comment. For more guidelines, see Talk Page Guidelines.

Please do not copy content from LSLwiki

From Rob Linden's post to the forum:

Hi folks, sorry for dropping into this conversation late. I haven't read through everything here, but I'd like to present an alternative.
There have been several requests that Linden Lab take on the hosting of the LSL wiki. There are several problems with us doing this work. The primary problem is the question of ownership of the material. Since, to the best of our knowledge, there was never an explicit, consistent notice of ownership of this material throughout its creation, nor a clear assignment/license associated with contributing more material, it would seem the only safe way to license this content would be to contact every single contributor throughout the life of the wiki and get an explicit license or copyright assignment from them. Note that I said "safe", not "practical".
We're not in a position to go down that road. However, we do have, which has had, since day one, a very clear notice about the license under which contributions are made and distributed. We would be very happy to see the community collaborate on newly created content on As long as you author the content (not cut and paste from sources you are not the sole author of), we welcome your contribution. -- Rob Linden 14:30, 24 January 2007 (PST)

OK, so let's talk about formatting rules for entries.

(Moved to LSL Portal Guidelines, so that this talk doesn't get too cluttered.) -- Talarus Luan 16:32, 24 January 2007 (PST)

Talarus Luan 14:28, 24 January 2007 (PST)

Other Discussion

LSL Guide lost linked from the page history says new residents downloading the client won't be getting a copy of the LSL_Guide.html any more ...

Q1. Where on the web do new residents go to get the LSL_Guide now? -- Ppaatt Lynagh 16:17, 3 January 2009 (UTC)

Q2. How should this LSL Portal page tell new residents to be sure to read the LSL_Guide first to correctly understand what else we say here? -- Ppaatt Lynagh 16:17, 3 January 2009 (UTC)

Untitled Chat

Should we make this the front page to the LSL reference, or put that one more level down? I kinda lean toward the former. Gigs Taggart 14:09, 24 January 2007 (PST)

Yeah i think so... (Unsigned by Dimentox Travanti}

Remember to sign your post with four tildes. Gigs Taggart 14:26, 24 January 2007 (PST)

I used a modified version of the GeSHiHighlight plugin for MediaWiki. With an LSL syntax file. The license for the plugin and for GeSHi is GPL, it also requires another plugin purgePage. --Thraxis Epsilon 15:00, 24 January 2007 (PST)

Regarding copying content from the existing Wiki

This isn't clear from Rob's post, but it should be made clear: we CAN copy our OWN content from the existing wiki. IE, I plan to copy/paste my XML-RPC notes from the existing one. Does that present an issue? If so, why? Talarus Luan 16:03, 24 January 2007 (PST)

If you are the sole author, it wouldn't. Just be careful and check the page history. Gigs Taggart 16:10, 24 January 2007 (PST)

Syntax Highlighting

Updated info on the syntax highlighting is available here [GeSHiHiLight] --Thraxis Epsilon 16:10, 24 January 2007 (PST)

Lets hope they include it soon ^^ Strife Onizuka 21:21, 24 January 2007 (PST)
Is there anyone we can ask? Dimentox Travanti 10:50, 25 January 2007 (PST)
any news or update on this? Blueman Steele 6:12, 10 February 2007 (PST)
We tried to use start using this on Thursday, but ran into some problems. Thraxis, it'll help if you can contact me privately to discuss some of the issues. -- Rob Linden 00:37, 11 February 2007 (PST)
What's the status of syntax highlighting? --Mokelembembe Mokeev 15:11, 24 April 2007 (PDT)
No one has made any efforts recently to get the highlighter included in the wiki. If you are going to post highlighted code, it would be good to have it output in such a way that keywords link to their appropriate pages. -- Strife Onizuka 16:53, 24 April 2007 (PDT)
Talked with Rob Liden - The concern with the script is about security and the possiblity of injecting PHP code into the script hilighting. Since its a possible security issue he would like somebody at Linden to look into and fix it. I'm going to look into the script and tell Rob what I found also. --Mokelembembe Mokeev 15:29, 4 May 2007 (PDT)

Let's refer to this simply as the "LSL portal"

Since there's already something out there called the "LSLwiki", let's refer to this as the LSL Portal to distinguish it. If there's no objection, I'll move the pages with "LSL Wiki" in the title to some other appropriate name -- Rob Linden 17:09, 24 January 2007 (PST)

No objections here. :) I just updated LSL Wiki To-do with some assignment tables. I went ahead and moved it to LSL Portal To-do Talarus Luan 18:12, 24 January 2007 (PST)
Simple, consistent messaging: I've gotten into the habit of using "LSL Portal" regularly myself.
--Torley Linden 10:40, 31 January 2007 (PST)

A way back...

Every page should have a header that goes back to the portal index not the wiki index. if we could even geta link in the left hand would be great.

Dimentox Travanti 10:47, 25 January 2007 (PST)

I second the idea of a link in the main Navigation list. It makes it a lot easier to access the LSL Portal.
Cron Stardust 11:25, 5 March 2007 (PST)


Encouraging to see this happening — and to see a second mirror for the LSL wiki too; hopefully I haven't come too late, because these developments look like they've transpired over the last few days.

Just wanted to let you know I've added a link to our LSL Portal from our blog's Notices; it'll be up for some time. I'm also going to add a simple article to the Knowledge Base directing to this LSL Portal, since it's important to get more contributors aware, interested, and involved.

I'd like to personally be more active in this wiki... great things are afoot. I've been spread across too many communication channels lately, so I've been rotating between focuses (foci?); hopefully next week I'll have more hands-on energy here.

Thanx to each and all of you building up this resource so far!

--Torley Linden 10:21, 26 January 2007 (PST)

LSL Header/Footer

Below is the header/footer template: {{LSL Header}}

Also, since <lsl></lsl> tags don't seem to work yet, I used <pre></pre>... hope that's alright, I know nothing about wikis except what I've taught myself tonight. --DoteDote Edison 20:45, 27 January 2007 (EST)

Actually, go ahead and use the <lsl></lsl> tags. Even though it may look like crap right this minute, as soon as the module is installed, it will instantly be perfect. :) Talarus Luan 14:59, 29 January 2007 (PST)

LSL wiki-namespace

All the LSL pages are prefixed with "LSL ", like "LSL Portal", "LSL LLRand", etc. It would seem more justly to use the wiki-namespace "LSL:". Change the names from "LSL LLRand" to "LSL:LLRand". My 2 lindens. Dzonatas Sol 00:28, 2 February 2007 (PST)

Just thought about this little more. We could use subpages instead of namespaces, then the talk pages will fully work. "LSL/LLRand" for example Dzonatas Sol 00:41, 2 February 2007 (PST)
I'm not going to make a big fuss about it, but I'd prefer if, per the Editing Guidelines, that the page just be called "LLRand". -- Rob Linden 01:06, 2 February 2007 (PST)
As this wiki has grown a great deal in other aspects the need for a namespace for LSL: has become even greater. This would allow the search functions to isolate LSL results from the more general content unrelated to LSL. This would also start a shift from many listings being sorted entirely under L. — kizmutT/C 12:02, 14 June 2012 (PDT)

LSL conformance test

Hi folks, we're planning to consolidate a lot of our scattered LSL conformance tests on this wiki. I created two rather crude templates: Template:LSL conformance test and Template:LSL conformance script, which were created for adding our conformance suite. See LSL llGetUnixTime test for an example. I'd like to get a sense from people if this is a sensible way to do this. The idea is to get these templates stabilized, and that will provide us a mechanism for those of us at LL to consolidate our tests. Of course, if the community wants to chip in, that's great too...having items in our standard LSL conformance suite makes it less likely that we'll break an LSL feature that's important to you. -- Rob Linden 22:53, 7 February 2007 (PST)

LSL Categories List

What about a vertical list of categories down the right side of the LSL Portal front page? The right-side list on the original wiki was my primary source of navigation, but maybe I'm odd. I could add it myself, but I'm not sure how to make it automatically update the list as new categories are added. --DoteDote Edison 20:20, 9 February 2007 (EST)

Oops... right after I posted this, I noticed that it's item #4 on the "To-Do" list. I went ahead and modified the front page to add a cetagories list. If you don't like it, feel free to revert. --DoteDote Edison 20:55, 9 February 2007 (EST)
The names all start with "LSL" and the names are not optimal for listing... The names could be changed though. I'll dig though the MediaWiki commands later and see if I can find any that would work well in this case. I don't have high hopes in this case. Strife Onizuka 18:59, 9 February 2007 (PST)

Is the 200 articles per category page a mediawiki limit, or can we change it to 400 per page in a configuration somewhere? DoteDote Edison 21:50, 22 February 2007 (EST)

If there's an issue with seeing all the pages, I can add the alphabetical navigation template later.
SignpostMarv Martin 06:16, 23 February 2007 (PST)


How do we want to go about internationalizing the LSL wiki. It should probably be tied into the global wiki effort. Strife Onizuka 07:20, 11 February 2007 (PST)

With modular templates (e.g. the way I do them) vs monolithic templates (e.g. the way you do them), the templates won't need to be changed, only the content going into them. Regarding Project:Internationalisation#multi-lingual articles, I have some freaky ideas to make maintenance of the LSL-specific multi-lingual articles a little easier to maintain.

p.s. I'm not sure whether Internationalisation of the LSL articles should be discussed here or there.
SignpostMarv Martin 08:05, 11 February 2007 (PST) Moved from Talk:LSL_Function_Style
But your idea on templates don't provide structure, it requires the user to provide the structure and if we want to change the layout of the pages we need to go through and change ever single page. I'm pretty sure I can put together template-templates that should make translating the templates easy as setting a few variables. We wouldn't be using the template-template directly for rendering but use substitution. Changing a dozen monolithic templates is better then changing a dozen * 328 pages. Also means that you get the same translation ever single time.
I've been thinking i could modify the LSLC, LSLG, LSLGC templates to support automated linking in language specific subpages. So if the page you are on is in Spanish, the links will lead to pages in Spanish if they exist. No special modifications to the links needed.Strife Onizuka 06:43, 13 February 2007 (PST)
But your idea on templates don't provide structure, it requires the user to provide the structure
  • That's kinda the point. Look at what information will need to be reused over and over again, and put it into a small template. Then those templates can be used directly, or as part of a wrapper template.
I'm pretty sure I can put together template-templates that should make translating the templates easy as setting a few variables.
  • The templates don't need translating, just the content.
I've been thinking i could modify the LSLC, LSLG, LSLGC templates to support automated linking in language specific subpages. So if the page you are on is in Spanish, the links will lead to pages in Spanish if they exist.
  • That would be bad.
  • Better idea to follow.
SignpostMarv Martin 13:13, 13 February 2007 (PST)
Template:Multi-lang I've given up fixing the bugs in that, but you get the idea behind it's intent. Include Help:Getting_started_in_Second_Life/langs in your test page and {{#vardefine:article-lang}} to either spa or eng'.
Please fork the code into your own userspace if you're going to work on it (unless you know of an instant fix) to prevent edit collisions.
I've also started work on Template:ISO_639-3/native to save a bit of time with entering languages that one browser might not be configured for (e.g. the higher-end UTF-8 characters)
SignpostMarv Martin 22:08, 19 February 2007 (PST)
Catherine Pfeffer Starting translation of the LSL Portal to French with the group "Constructeurs et scripteurs"
Please refer to a related discussion on Project:Languages. -- Alissa Sabre 07:58, 4 November 2007 (PST)

phasing out of Template:LSLG

Since the need to prefix almost everything with LSL_ is now being removed, all articles that are calling Template:LSLG should be edited to use a Wiki link, as the template is now rather redundant.

The list of articles calling LSLG can be viewed via Special:Whatlinkshere.
SignpostMarv Martin 22:08, 19 February 2007 (PST)

I think the pages in the FixMe category should be of a higher priority. Phasing out usage is reasonable, going through every page that uses it on the other hand just to remove it would be a waste of resources. I'm a bit nervous about stopping using it at present, the metaphoric paint hasn't even dried on the move yet. Considering it doesn't effect the rendering, phasing it's usage out is appropriate. Strife Onizuka 23:20, 20 February 2007 (PST)
Waste of resources ?
Isn't it a waste of resources to use a template that in most cases is entirely redundant ?
SignpostMarv Martin 02:23, 21 February 2007 (PST)
We haven't even finihed moving the function pages to the new names and template yet. You could help with that instead of worrying about templates, you know. Gigs Taggart 07:35, 21 February 2007 (PST)

The original LSL Wiki is back!

Catherine Omega's original LSL Wiki is back. She mentioned:

"This is DEFINITELY back. And it's definitely permanent. It's all editable. And it's the 'official', Catherine-Omega-approved one."

Further context can be found @ her blog. --Torley Linden 13:41, 28 February 2007 (PST)


I've been playing with the table (again). I've tried to get it so it looks decent in both IE and Firefox. I've been trying to get it to put all the extra space into the last section, which I managed in Firefox but haven't figured out the correct permutation of parameters for IE. I'm content at this moment to leave it be (I use Firefox). Strife Onizuka 08:49, 17 March 2007 (PDT)

Warning notice?

Might it be an idea to include a short warning on the top of this page that the LSL Portal is as yet incomplete?

I just spent a while trying to find a list function I knew existed, but couldn't remember the exact name of, which hasn't made it here yet before realising that not all functions are listed yet. --Nick Shatner, 02:56, 2 May 2007 (PDT)

The vast majority of functions have been catagorized so if you had started from the list category page you probably would have found it. There are a small handful of functions that haven't been catagorized beyond the Functions category. I'm not sure if a warning is warranted but I do recognize there are gaps in the LSL information. -- Strife Onizuka 13:31, 2 May 2007 (PDT)

llSetText page which is here is missing from page listing all the functions. Can't quite figure out how that page gets its info, so not going to touch it. -- (anonymous and undated) (because not signed with dash dash tilde tilde tilde tilde)
includes llSetText nowadays
maybe because "LSL Functions" appears in the Categories list at the end nowadays.
-- Ppaatt Lynagh 05:57, 2 December 2007 (PST)


I whould like to know if
a) this is a public wiki, where everybody can contribute so the LSL gets better known, or if it is a private viki with conspirativ charakter
b) why it is kept so spartanik with information
c) why no lindens who wrote LSL document their work
d) why some private persons are called administrators, what rights do they have, and if they have ever signed a paper that makes them not abuse theyr position
e) why linden lab employees never fisicaly work and only give "precios advises"
dont dare to delete this.
Anylyn Hax 04:09, 8 August 2007 (PDT)

I shall try to answer:
a) It is a public wiki but not everyone can contribute, you must have an SL account to contribute.
b) No one has added more information.
c) They did, it's in the LSL manual that ships with the client (it's common knowledge that it sucks).
d) I don't know of any non-linden administrators on the wiki.
e) The design of LSL is stable and there are very few LSL bugs that haven't been vetted; it would surprise me if there were any full time LSL devs. Just because we don't see them working doesn't mean they aren't working; the SL code base is huge.
-- Strife Onizuka 12:56, 8 August 2007 (PDT)

Vehicle Tutorial

Could we get the original vehicle tutorial added to this wiki. I realize it's not in the correct format, but it's a place to start. There was a wikified version too in the old wiki someone did, but they'd have to contribute it themselves I'd think. I can't find the original tutorial outside the old wiki.

The tutorial was part of the LSL manual that ships with the client. LL has given permission to post it on the wiki. -- Strife Onizuka 16:37, 8 September 2007 (PDT)
I found an old copy I had and wikified it. This is pretty much the original version, so it's probably a bit whacked, please fix any problems you're aware of Ralph Doctorow


It would be very helpful if I could use different colored text when writing my articles. Could buttons be added for black text, red text, green text, and one other color of text? Or could someone list the codes that can be used to change text color?

Just as an example of what I intend to use color for:

blackrotation redvariableblack=<red%,%,%,green#.#black>;

-- Anonymous, Undated

The LSL /LSL tags give colour to LSL code, e.g.:

<lsl>vector up = < 0, 0, 1 >;</lsl> -- Ppaatt Lynagh 16:20, 3 January 2009 (UTC)

LSL tags and automatic linking: some errors noticed

I'm not aware of a specific template to edit/update, but I've noticed some of auto-linked functions and constants from <lsl></lsl> tags point to incorrect or 'bad' (not found) pages. case in point, llSay points to Lsl_LLSay (which will redirect), and PUBLIC_CHANNEL points to a non-existant search page (there is an actual page available, but it doesn't go there). I'm sure there are other examples of this, but I'm not aware of a way to update it....

also curious to know if there is any hope of having localized pages (like french) redirect to their language equivalents through these tags at some point (I know it's not really feasible at the moment) -- Void Singer 13:42, 19 February 2008 (PST)


Could we please create a hacks page to be linked on the main LSL portal. Similiar to the old LSL wiki of compiling a growing list of well known tricks and tips for scripting.

For example a well known trick, which I use frequently is the use of (List!=[]) instead of llGetListLength. --Nexii Malthus 07:38, 19 May 2008 (PDT)

I've slapped a page together: LSL Hacks. I'd like comments on the style and layout. Please in the future don't stand on ceremony, if a niche needs filling, then please fill it with content. I have found that if you wait for people to weigh in before you start then nothing will get done. Better to do your best and make adjustments when there is a stink. -- Strife Onizuka 09:37, 19 May 2008 (PDT)

(moved from Template talk:LSL Function)

I had a discussion with Gally today and we came to the following conclusion:
Since we're not able to copy content from and vice versa - because of licensing problems - we might benefit from linking related articles of both wikis. So users can easily switch from one Wiki to the other and find the information most helpful for them. There shouldn't be a rivalry between these two documentation projects. They should benefit from each other. Therefor, we're adding a link to the related article to this template. I hope it's ok.
Something else on the same topic: It seems to be(come) quite popular in Wiki culture to double-license the own contributions, in order to make them easier to share. Wikis of interest for us:

Please consider to double-license your contributions to this (or other) Wikis in order to make them easier to share, by writing a statemanet about double licensing on your userpage. You can also use one of Marv's templates: Template:Re-license contributions as well as Template:License.
This is just a suggestion of course. Just do it, in case you want to do it.
Greetz, Zai signature.png Lynch (talk|contribs) 20:14, 9 September 2008 (PDT)

LSL Portal should have links to pages that are helpful and often used

  • The guidelines shown is for editing the LSL portal and not about LSL script it self. Instead it should link to say LSL Style Guide or just be removed.
  • The same thing with the to do link. I would just remove it.
  • I most often use Category:LSL Functions. When I first was looking for information on how to script in LSL this is what I wanted. I think it should be the first link. Looking at Special:Statistics it is the 5th most viewed page with 708,956 views.
  • Next I think LSL Tutorial should be added as it is a great place for people who have never scripted before and even for those who work in other languages. This is also the 8th most viewed page on the wiki.
  • The last link I would add Category:LSL_Library which is a list of scripts that show off how LSL works or does a common task.

Master Starship 17:34, 23 April 2010 (UTC)

  • I take it you haven't see the Header at the top of every article in the LSL Portal. It has all those links you call for. (Those articles didn't get popular because people used "Search").
  • The LSL Portal Guidelines contains not just the rules but the mission statement for the LSL Portal. It is fundamental to the this portals continued existence. Without it we would lack direction, and defined social guidelines. Without defined guidelines we would eventual descend into chaos (I've seen it happen; the writing of the guidelines has mostly been in reaction to specific incidents). It needs to be in a prominent position so that editors will find it and read it (or can't make excuses as to why they haven't read it).
  • Like the LSL Portal Guidelines, the LSL Portal To-do link is in a section dedicated to the LSL Portal as a whole, not to LSL scripting. The rest of the page is dedicated to scripting. It's a small section.

-- Strife (talk|contribs) 19:14, 23 April 2010 (UTC)

Proposal About "LSL Categories" Section

I find current view is too messing and difficult to find what I need. The users end up looking in huge list of Functions, clicking much. I am thinking about organizing the list to easily look up the LSL articles.

Here is the proposal of categorizing.

 - Animation
 - Attachment
 - Behavior
 - Camera
 - Properties
 - Parcel
 - Region
 - Detection
 - Existence
 - Face
 - Inventory
 - Link
 - Media
 - Physic
 - Properties
 - Text
 - Control
 - Convert
 - List
 - Math
 - Network
 - String
 - Time

I tried to sort all existing 339 functions (except God, not active one). Here is the list ---> User:Mako_Nozaki/Category_Function

My thought is, current categories will remain as is and will be used as "tags". Missing categories will be added and be linked from each functions. Adding these categories to LSL Header using Javascript (pulldown menu) might be cool. --Mako 12:56, 1 May 2010 (UTC)

User-Defined Functions

I'm personally adverse to linking to the template description rather than the category (which already back links to the template) in the "language reference" section, as per the [recent edit]. but since it's obvious someone else is not I thought I'd solicit thoughts before reverting it. I'm thinking it could be more clear on the category page though.
-- Void (talk|contribs) 22:49, 10 May 2012 (PDT)

I agree with you. In addition to that, I think the two articles should be merged. We gain nothing of value by having them separate. -- Strife (talk|contribs) 10:37, 11 May 2012 (PDT)
Pointed the link back at the category, folded the article into the category page, and marked the original article page for deletion.
-- Void (talk|contribs) 10:45, 1 June 2012 (PDT)


It's probably time to update the category list and tree again. It's been a while and I'm sure I've added more since the last time we update them. Also I should remember to update the LSL News box. -- Strife (talk|contribs) 10:42, 11 May 2012 (PDT)

There are extensions that can update the category list automagically like Extension:DynamicPageList. I am not sure one is installed here. Would we have to wait for a Linden to set something up like this? — kizmutT/C 12:18, 14 June 2012 (PDT)
It really has to be done manually, some categories are intentionally excluded and it's not a pure tree (I think there may even be loops). -- Strife (talk|contribs) 21:00, 14 June 2012 (PDT)
If the category list on LSL portal top page is shorter, I think it will be more navigable. I have once considered the new list few years ago (you can see it above). Both tag (as wiki category) and hierarchical access may be needed to easily find what they want to know. -- Mako 03:47, 15 June 2012 (PDT)

We've had several new categories in the last year. Wouldn't be a bad time to update. I wonder if there is some good way of indexing them. -- Strife (talk|contribs) 23:16, 7 July 2013 (PDT)

Recent Formatting Edits

prettying up the alphabetical Functions links as they were (formatted now for consistency as bulletted links) brought up a deficiency in the original manner in how the links Should work. towit A-L should find an Anchor ID in the target page's listed functions to scroll the browser to, same as L-V (i suppose at the L functions), T-Z (at the T). i can't edit the subsequent target page Category:LSL Functions so the actual listing shows more than what it actually performs. each alpha category jumps the browser to the top of the page. if anyone can access the Category:LSL Functions page could they put some Anchor ID tags at the demarked alphabetical links? -- EnCore Mayne 21:55, 7 September 2012 (PDT)

I added an anchor at the end of the content but it looks better to use the one supplied with Pages in category "LSL Functions". -- Strife (talk|contribs) 07:50, 8 September 2012 (PDT)

Articles in need of version number

I've gotten sick of seeing the Articles in need of version number/LSL category link, so I've modified Multi-lang to support disabling of versioning (which will require a wiki-god to approve the edit), and I've hidden the category for the mean time. Versioning is a underused feature and we don't use it. -- Strife (talk|contribs) 23:10, 7 July 2013 (PDT)

Tiny font in script samples

Since 22 January 2015, I've noticed the text of code snippets has shrank, reducing readability. Upon further inspection of recent changes, I learned that all instances were the result of the <lsl></lsl> tags being replaced with <source lang="lsl2"></source>. The Caveats list sections of several pages have also become vertically misaligned. Whatever benefits the change from <lsl> to <source> brings, I doubt they are worth having to squint at. Isn't readable text a must on a nearly pure text site? I can only imagine how it will appear for users with 1080p+ resolution monitors. Unless lsl2 brings critical features or is mandatory, I propose the change be reverted for easier reading. -- Sharpe Clowes (talk) 19:29, 30 January 2015 (PST)

Yep, the tag change was required by a move from an old extension to a current one. I'm not seeing big font changes or caveat misalignment here, what browser are you on? --Cerise Sorbet (talk) 21:54, 30 January 2015 (PST)
OK, going to guess that you're using Firefox? The current CSS yields to the user's browser preference for the monospace font, and Firefox defaults to a tiny 13 points for that. --Cerise Sorbet (talk) 00:14, 31 January 2015 (PST)
It's happening to me too in Iceweasel (Firefox). The culprit seems to be this line from the geshi stylesheet:
.lsl2.source-lsl2 .de1, .lsl2.source-lsl2 .de2 {font: normal normal 1em/1.2em monospace; margin:0; padding:0; background:none; vertical-align:top;font-family: monospace, monospace;}
specifically the 1em part. Removing it gets the font back to the <pre> font default height which is 12px and makes it work decently. --Pedro Oval (talk) 08:58, 31 January 2015 (PST)
We recently had a wiki software upgrade (it was done for security reasons, you may have noticed that we couldn't edit the wiki for several months...), as part of that upgrade we got a different version of Geshi. Geshi development forked long ago and I'm guessing we were using one of the dead forks. We upgraded to a live (one that is actively developed and supported) fork that unfortunately didn't work quite the same way as our old unsupported version. This required us to change all the syntax highlighting tags. There is no way to go back to the old highlighter. We can only try and get LL to make this one usable. -- Strife (talk|contribs) 09:09, 31 January 2015 (PST)
So anyway, in Firefox options, click Content from the left-hand bar, then the Advanced... button to the right of Fonts & Colors. You can change the Monospace font and size to something that works well for you there, The change will be reflected on open wiki tabs as soon as you hit OK on that panel. --Cerise Sorbet (talk) 02:19, 1 February 2015 (PST)
Unfortunately, that breaks other things for me. I solved it by editing my userContent.css to add this line:
pre.de1, pre.de2 { font-size: 12px !important; }
(12px is the value that it inherits from <pre>). --Sei Lisa (talk) 11:30, 2 February 2015 (PST)