Errors in the code should be recorded as gemini issues, that way the development team can see them and fix them (IMHO wiki's are for product documentation, not errors - that's what error issuetrackers are for, as you need to record version information etc. - though I suspect any wiki will end up with a page linking to gemini to aggregate common issues and known workarounds). BTW I looked into this a few times before and was not able to recreate it, though I did not consider case-sensitivity, so I'll reexamine it again. However, it may not be directly code related i.e. it might be to do with your version of the .net framework or your PC localisation settings or even the version of vs.net youre using, hence why you noticed the problem and others didnt (I haven't validated this yet, but would have expected more people to have this issue than have reported it)
Regarding a wiki, we're still working hard on this, and have identified the software to use (but are waiting on an update for a particular feature), as well as planning out the security structure etc. It will be a public wiki, not one limited to PE customers.
Regarding the PE knowledgebase, it contains a multitude of items including tutorials, how-to's,useful info, installation & configuration guidelines which were written for PE customers - just in the same way that ISP's/hosting providers/independant developers write documentation for their customers. There is also a list detailing some of the more common errors encountered with both the core and 3rd party modules, but this comes from posts in gemini/forums - we just tidy it up and aggregate it for PE customers. I don't think any of this is devisive or against OSS principles - if you look at any popular project you'll see the same i.e. the information is readily available, but can take time to gather, whereas a Pro version saves you this time - this is one of the reasons for subscribing i.e. time=money is important for many people.
Another point about the Pro offering - if you'd been a pro customer and raised this as an issue , the support team would have worked through it until they worked out a solution and then resolved it (as per the terms of the support agreement) - the ability to not have to rely on volunteer/oss efforts is important to many people, and hence why they take our a pro version.
I'll flag this post with the team and hopefully it can get fixed for 5.2.
Cathal