<commit_before>---
layout : post
title : Version 0.3.0 Released
category : Version 0.3.0
tags :
  - new feaures
---

I recently received a quesiton about how to get source code to render correctly on a blog post. After doing some research, I found the available code rendering less than desirable with the current version of gh-pages-blog, mainly because syntax highlighting wasn't available. So I added some features to better support source code rendering and syntax highlighting.

The first thing you'll notice is the inclusion of a syntax.css file now. Thanks to [<NAME>](https://github.com/mojombo/jekyll) for making this file available under the MIT License.

If you don't like how the syntax highlight works, you can either edit the syntax.css or you can create a new file. If you create a new file, you'll want to update the syntax-hightling settings in the \_config.yml file to reference the new file. If you don't want to use syntax highlighting at all, you can also disable the loading of the css via the \_config.yml.

In order to get the soure code to render correctly on your blog post and pages, you'll need to wrap the code in the highlight tags supported by [Jekyll](http://jekyllrb.com).

{% raw %}
{% highlight text %}
code goes here
{% endhighlight %}"
{% endraw %}

It's very important to include `text` in the tag, otherwise the GitHub page won't build. Jekyll will render the line breaks and spacing correctly between the highlight tags, so it shouldn't be necessary to do any other formatting. It's not necessary to wrap your code in `<pre><code></code></pre>` when using the highlight tag.

Adding the highlight tags around some sample code would result in the following output:

{% highlight text %}
function code_example() {
  console.log("Showing the plain text rendering of code using gh-pages-blog.");
}
{% endhighlight %}

{% highlight javascript %}
function code_example_with_javascript_syntax_highlights() {
  console.log("Showing the syntax highlighting rendering of code using gh-pages-blog.");
}
{% endhighlight %}

{% highlight javascript linenos=table %}
function code_example_with_line_numbers() {
  console.log("Showing the line number rendering of code using gh-pages-blog.");
}
{% endhighlight %}


<commit_msg>Update 2013-08-29-version-0-3-0.md<commit_after>---
layout : post
title : Version 0.3.0 Released
category : Version 0.3.0
tags :
  - new feaures
---

I recently received a quesiton about how to get source code to render correctly on a blog post. After doing some research, I found the available code rendering less than desirable with the current version of gh-pages-blog, mainly because syntax highlighting wasn't available. So I added some features to better support source code rendering and syntax highlighting.

The first thing you'll notice is the inclusion of a syntax.css file now. Thanks to [<NAME>](https://github.com/mojombo/jekyll) for making this file available under the MIT License.

If you don't like how the syntax highlight works, you can either edit the syntax.css or you can create a new file. If you create a new file, you'll want to update the syntax-hightling settings in the \_config.yml file to reference the new file. If you don't want to use syntax highlighting at all, you can also disable the loading of the css via the \_config.yml.

In order to get the soure code to render correctly on your blog post and pages, you'll need to wrap the code in the highlight tags supported by [Jekyll](http://jekyllrb.com).

<pre>
{% raw %}
{% highlight text %}
code goes here
{% endhighlight %}
{% endraw %}
</pre>

It's very important to include `text` in the tag, otherwise the GitHub page won't build. Jekyll will render the line breaks and spacing correctly between the highlight tags, so it shouldn't be necessary to do any other formatting. It's not necessary to wrap your code in `<pre><code></code></pre>` when using the highlight tag.

Adding the highlight tags around some sample code would result in the following output:

{% highlight text %}
function code_example() {
  console.log("Showing the plain text rendering of code using gh-pages-blog.");
}
{% endhighlight %}

{% highlight javascript %}
function code_example_with_javascript_syntax_highlights() {
  console.log("Showing the syntax highlighting rendering of code using gh-pages-blog.");
}
{% endhighlight %}

{% highlight javascript linenos=table %}
function code_example_with_line_numbers() {
  console.log("Showing the line number rendering of code using gh-pages-blog.");
}
{% endhighlight %}



{'fraction_non_alphanumeric': 0.07865168539325842, 'fraction_numerical': 0.00506719541749284, 'mean_word_length': 4.4176610978520285, 'pattern_counts': {'":': 0, '<': 15, '<?xml version=': 0, '>': 15, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2956758', 'n_tokens_mistral': 1280, 'n_tokens_neox': 1145, 'n_words': 617}