state of the project?

[geshi]

state of the project?

[cweiske]

A namespace will no be introduced since it will break backwards compatibility. Use geshi-1.1 for that.

What I would really miss is unit tests that tell me if a patch breaks things :/

[splitbrain]

Yeah. Unit tests would be awesome, but I don't know enough about the GeSHi internals to do that. However I thought about two things that would be relatively easy:

1. dogfood the geshi source through geshi and simply check that a few keywords are in the resulting output -- this would ensure at least the PHP compatibility and catch possible syntax errors.
2. use the checklang.php mechanism in a unit test

When both are in place it could be set up at travis and you could at least see if new PRs violate those basic things already. Eg. I had to fix most of the language additions becasue checklang found some issues

[cweiske]

unit tests would be too much,yes. I thought about having a set of source test files and their expected output, which gets compared by phpunit.

But having checklang in travis would also help, yes.

[splitbrain]

@cweiske I started working on unit testing as outlined above. Can you have a look at my questions here: splitbrain-forks#1

[splitbrain]

I converted the geshi-doc.html document to markdown, manually fixed stuff and added the contents (mostly) to the wiki. I left out stuff that very obviously needs rewriting. A new table of contents linking to the various documents should be created on the Home page. And of course all the pages need some work, but now the community could step in.

[splitbrain]

I'm closing this in favor of #79 #81 and #82