Added Markdown from jnovack.github.com/pear/Markdown

[jnovack]

Markdown was revamped by Filipe Dobreira (https://github.com/filp/Markdown) to be PHP 5.3.0 complaint with object-orientation goodness.

I had since:

• made the code more PEAR complaint (cosmetic changes only)
• added in HTML5 level elements from pull requests made to https://github.com/michelf/PHP-Markdown
• upgraded the underling base from 1.0.1n to 1.0.1o

I created my own github pear repository to host the PEAR repo, and installed it.

This now permits setup checking properly.

This branch is running at phorkie.ozmonet.com

[cweiske]

While this is a tempting idea, I'm also reluctant to not use the package from the official maintainer.

The main problem I have is that the future of your repository is uncertain, while I have higher hopes for the (current) maintainer - his code will always be up to date, at least until he decides to not maintain it anymore.

Please please try to get your changes merged. Discuss the issues with him and convince him that your version is better. Find a solution to keep BC.

Also run phpcs (PHP_CodeSniffer) on that code; your announced PEAR compliance still leaves 245 CS errors.

[jnovack]

To be fair, I said "more" PEAR compliance, I never said it was complete. ;)

I understand, I'm a nobody, but why not your repo then? You already have packages coming from there.

In this instance, I'm unsure of the official maintainer. The original maintainer michelf, is unwilling to update to Object-Orientated code because he wants to support PHP4 (doesn't make him a bad person). I have a pull request pending to filp which makes his repo a fork which may never be merged.

Don't make me run PHP_CodeSniffer on the phorkie classes. ;)

[cweiske]

Hello Justin,

I understand, I'm a nobody, but why not your repo then? You already have packages coming from there. Because I know about the burden of maintenance and won't do that. I rather have a small hack in my software and use a maintained package than forking it.

In this instance, I'm unsure of the official maintainer. The original maintainer michelf, is unwilling to update to Object-Orientated code because he wants to support PHP4 (doesn't make him a bad person). PHP 5.2 is EOL'd, and PHP4's EOL is long forgotten in the dawns of time. PHP4 compatiblity makes no sense anymore. But it's his decision.

Don't make me run PHP_CodeSniffer on the phorkie classes. ;) Do it. I did yesterday, and all that's left are "docblock missing" errors.

Regards/Mit freundlichen Grüßen Christian Weiske

-=≡ Geeking around in the name of science since 1982 ≡=-

[jnovack]

Should I close and delete this branch? No point in leaving this out there while I attempt to resolve it with the maintainers.

[cweiske]

throw it away.