Locking Rubby Gems versions for use in a variety of environments.

[carlosdelfino]

What/why?

In my development environment I have several projects each one works with a different version of gems which sometimes leaves me in doubt if it is the version that is causing a certain bug, to avoid this, I fixed the versions of the gems where I identified that it would be important In rich versions environments.

I recreate the pull-request, because I renamed the branch the pull-request #25 was close by github automatically,

How was it tested?

bundle update bundle exec jekyll s

[ilg-ul]

I'm not very happy with this configuration, compared to my previous, it generates ids with non ascii characters:

-<h4 id="os-iiie">µOS++ IIIe</h4>
+<h4 id="µos-iiie">µOS++ IIIe</h4>

how can we fix this?

[carlosdelfino]

I do not like it either, I did not realize that. I'll check it out here. How did you detect this? Did you use any script?

[ilg-ul]

no, I just did a build, and git compared with the existing version.

[carlosdelfino]

In travis-ci is possible check this before send to production.

I yet learning how to use jekyll, travis-ci and site checker for create a w3c certificate site.

[carlosdelfino]

in html 4.01 and html 5 this is not a problem, id can use unicode characters with no problems.

https://mathiasbynens.be/notes/html5-id-class

[ilg-ul]

id can use unicode characters with no problems.

I don't know what to say, I hope all browsers know this.

[carlosdelfino]

Even with internationalization features I do not like to use unicode in code and parameters, but I have seen that this is a trend and there is no going back. I'm avoiding as much as I avoid filenames and directories, but in the long run URLs are already becoming UNICODE friendly.