From 00239f6034edce116634c9b11565704a19ab157b Mon Sep 17 00:00:00 2001 From: Julian Thilo Date: Wed, 15 Jan 2014 22:18:35 +0100 Subject: [PATCH 1/3] Set Jekyll encoding and tweak Windows notes --- README.md | 4 ++-- _config.yml | 1 + 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2732bd85ca..54fdef5e9e 100644 --- a/README.md +++ b/README.md @@ -64,9 +64,9 @@ Bootstrap's documentation, included in this repo in the root directory, is built ### Running documentation locally 1. If necessary, [install Jekyll](http://jekyllrb.com/docs/installation) (requires v1.x). - - **Windows users:** read [this unofficial guide](https://github.com/juthilo/run-jekyll-on-windows/) to get Jekyll up and running without problems. + - **Windows users:** Read [this unofficial guide](https://github.com/juthilo/run-jekyll-on-windows/) to get Jekyll up and running without problems. We use Pygments for syntax highlighting, so make sure to read the sections on installing Python and Pygments. 2. From the root `/bootstrap` directory, run `jekyll serve` in the command line. - - **Windows users:** For Ruby 2.0.0 run `chcp 65001` first to change the command prompt's character encoding ([code page](http://en.wikipedia.org/wiki/Windows_code_page)) to UTF-8 so Jekyll runs without errors. For Ruby 1.9.3 you can alternatively do `SET LANG=en_EN.UTF-8`. In addition, ensure you have Python installed and added in your `PATH` or the build will fail due to our Pygments dependency. + - **Windows users:** While we use Jekyll's `encoding` setting, you might still need to change the command prompt's character encoding ([code page](http://en.wikipedia.org/wiki/Windows_code_page)) to UTF-8 so Jekyll runs without errors. For Ruby 2.0.0 run `chcp 65001` first. For Ruby 1.9.3 you can alternatively do `SET LANG=en_EN.UTF-8`. 3. Open in your browser, and voilà. Learn more about using Jekyll by reading its [documentation](http://jekyllrb.com/docs/home/). diff --git a/_config.yml b/_config.yml index 6415d3a2e3..f2d7505df5 100644 --- a/_config.yml +++ b/_config.yml @@ -12,6 +12,7 @@ host: 0.0.0.0 port: 9001 baseurl: / url: http://localhost:9001 +encoding: UTF-8 # Custom vars current_version: 3.0.3 From 8dc1d00dd49786bb0cb748aed95a3499d9907cb7 Mon Sep 17 00:00:00 2001 From: Chris Rebert Date: Wed, 15 Jan 2014 13:44:23 -0800 Subject: [PATCH 2/3] add a couple commas --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 54fdef5e9e..d4c5bc1664 100644 --- a/README.md +++ b/README.md @@ -66,7 +66,7 @@ Bootstrap's documentation, included in this repo in the root directory, is built 1. If necessary, [install Jekyll](http://jekyllrb.com/docs/installation) (requires v1.x). - **Windows users:** Read [this unofficial guide](https://github.com/juthilo/run-jekyll-on-windows/) to get Jekyll up and running without problems. We use Pygments for syntax highlighting, so make sure to read the sections on installing Python and Pygments. 2. From the root `/bootstrap` directory, run `jekyll serve` in the command line. - - **Windows users:** While we use Jekyll's `encoding` setting, you might still need to change the command prompt's character encoding ([code page](http://en.wikipedia.org/wiki/Windows_code_page)) to UTF-8 so Jekyll runs without errors. For Ruby 2.0.0 run `chcp 65001` first. For Ruby 1.9.3 you can alternatively do `SET LANG=en_EN.UTF-8`. + - **Windows users:** While we use Jekyll's `encoding` setting, you might still need to change the command prompt's character encoding ([code page](http://en.wikipedia.org/wiki/Windows_code_page)) to UTF-8 so Jekyll runs without errors. For Ruby 2.0.0, run `chcp 65001` first. For Ruby 1.9.3, you can alternatively do `SET LANG=en_EN.UTF-8`. 3. Open in your browser, and voilà. Learn more about using Jekyll by reading its [documentation](http://jekyllrb.com/docs/home/). From 91c6419d0924dc36ad6599519c2afc53e6a33721 Mon Sep 17 00:00:00 2001 From: Chris Rebert Date: Wed, 15 Jan 2014 14:26:29 -0800 Subject: [PATCH 3/3] Getting Started: fix ID of heading so matches TOC --- docs/getting-started.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started.html b/docs/getting-started.html index b2edf0722b..bb4783b3bd 100644 --- a/docs/getting-started.html +++ b/docs/getting-started.html @@ -875,7 +875,7 @@ if (navigator.userAgent.match(/IEMobile\/10\.0/)) {

Navbar Dropdowns

The .dropdown-backdrop element isn't used on iOS in the nav because of the complexity of z-indexing. Thus, to close dropdowns in navbars, you must directly click the dropdown element (or any other element which will fire a click event in iOS).

-

Browser zooming

+

Browser zooming

Page zooming inevitably presents rendering artifacts in some components, both in Bootstrap and the rest of the web. Depending on the issue, we may be able to fix it (search first and then open an issue if need be). However, we tend to ignore these as they often have no direct solution other than hacky workarounds.

Android stock browser