Highlight Encoding Problems about docs HOT 6 CLOSED

I literally just replaced the markdown parser with the github flavored markdown parser. Next push should have a fix.

from docs.

Hrmm, so that didn't seem to help.

I would really appreciate it if you could hunt down this issue. It's been bugging me and I haven't had the time to track it down. :-(

from docs.

The problem is with code highlight. I commented the hl() call in article.js and the encoding problem is gone. I'll dig into the highlighting. Why not go with a browser highlighting? Are you avoiding js on the docs?

from docs.

Why not try this one?

http://search.npmjs.org/#/koala (from TJ Holowaychuk)

I would avoid going deep into the vendor folder.

from docs.

@dresende @Marak I just gave koala a shot:

https://github.com/nodejitsu/docs/blob/gh-28/lib/generators/article.js#L97-L117

Indeed, it seems that the results from using koala have much fewer encoding errors. However, even with screening out invalid javascript by testing uglify-js's ability to parse the code, I'm now getting a few jsdom "invalid html" warnings. The results look fine, but invalid html can't be good.

Is there a way to reasonably intercept such jsdom errors? Maybe @tmpvar knows.

from docs.

This issue has been "hackfixed". It's relatively brittle, but seems to suffice for the docs.

from docs.