diff --git a/README.md b/README.md index af60e64..bc8fb8e 100644 --- a/README.md +++ b/README.md @@ -1,21 +1,34 @@ +--- +title: Solarized +subtitle: Precision colors for machines and people +author: Ethan Schoonover +tags: test, testing, test123 +colors: light yellow +created: March 15, 2011 +lastchanged: March 21, 2011 +--- + Solarized ========= -**Precision colors for machines and people** +## Precision colors for machines and people + +[![solarized dualmode](/img/solarized-yinyang.png)](#features)\ + Solarized is a sixteen color palette (eight monotones, eight accent colors) designed for use with -terminal and gui applications. It has several unique properties. I designed -this colorscheme with both precise +terminal and gui applications. It has several [unique properties](#features). +I designed this colorscheme with both precise [CIELAB](http://en.wikipedia.org/wiki/Lab_color_space) lightness relationships and a refined set of hues based on fixed color wheel relationships. It has been -tested extensively in real world use on color calibrated displays and in -a variety of lighting conditions. +tested extensively in real world use on color calibrated displays (as well as +uncalibrated/intentionally miscalibrated displays) and in a variety of lighting +conditions. -![solarized monotones](https://github.com/altercation/solarized/raw/master/images/solarized-monotones.png) -![solarized accents](https://github.com/altercation/solarized/raw/master/images/solarized-accentcolors.png) +![solarized palette](/img/solarized-palette.png)\ -Available in formats for: +Currently available in formats for (cf [screenshots](#screenshots) below): * **Vim** (the Vim-only portion of Solarized is [available here](https://github.com/altercation/vim-colors-solarized), for use with @@ -29,76 +42,85 @@ here](https://github.com/altercation/mutt-colors-solarized)) * OS X Terminal.app * Xresources / Xdefaults +Don't see the application you want to use it in? Download the palettes (or pull +the values from the table below) and create your own. Submit it back and I'll +happily note the contribution and include it on this page. + Download -======== +-------- -**Project Page:** -: Downloads, screenshots and more information are available from the project - page: . +### [Click here to download latest version](http://ethanschoonover.com/solarized/files/solarized.tgz) -**Git repo:** -: The full git repository is at: . +Or use the following links to access application specific downloads and git +repositories: -**Vim only:** -: The vim-only colorscheme (Pathogen ready) is available at: - . +* **Git repo:** -**Mutt only:** -: The mutt-only variants can be cloned from - https://github.com/altercation/mutt-colors-solarized + The full git repository is at: + +* **Vim only:** + + The vim-only colorscheme (Pathogen ready) is available at: + . You can also download + it from [vim.org](http://vim.org/scripturlhere). + +* **Mutt only:** + + The mutt-only variants can be cloned from + + +* **Canonical Project Page:** + + Downloads, screenshots and more information are always available from the + project page: Note that through the magic of [git-subtree](https://github.com/apenwarr/git-subtree) these repositories are all kept in sync, so you can pull any of them and get the most up-to-date version. -What ----- - -Solarized is a sixteen color palette (eight monotones, eight accent colors) -designed for use with terminal and gui applications and has several unique -properties. It has been designed with both precise -[CIELAB](http://en.wikipedia.org/wiki/Lab_color_space) lightness relationships -and a refined set of hues based on fixed color wheel relationships. It has been -tested extensively in real world use on color calibrated displays and in -a variety of lighting conditions. - Features -------- 1. **Selective contrast** - Solarized reduces brightness based contrast in general. Modern display - devices are capable of blasting your retina clean off with max brightness - and I found my eyes growing tired using high contrast colorschemes, even - with the brightness turned down. Solarized reduces *brightness contrast* - but, unlike many low contrast colorschemes, retains *contrasting hues* - (based on colorwheel relations) for syntax highlighting readability. + On a sunny summer day I love to read a book outside. Not right in the sun; + that's too bright. I'll hunt for a shady spot under a tree. The shaded + paper contrasts with the crisp text nicely. If you were to actually measure + the contrast between the two, you'd find it is much lower than black text + on a white background (or white on black) on your display device of choice. + Black text on white from a computer display is akin to reading a book in + direct sunlight and tires the eye. -2. **Dual modes: Dark/Light** + ![solarized selective contrast](/img/solarized-selcon.png)\ - I switch between dark and light modes when editing text even when editing - different types of files. Solarized retains the same selective contrast - relationships and overall feel when switching between the light and dark - background modes. A *lot* of thought, planning and testing has gone into - making both modes feel like part of a unified colorscheme. + Solarized reduces *brightness contrast* but, unlike many low contrast + colorschemes, retains *contrasting hues* (based on colorwheel relations) + for syntax highlighting readability. -3. **16/5 Palette modes** +2. **Both sides of the force** + + ![solarized dualmode](/img/solarized-dualmode.png)\ + + I often switch between dark and light modes when editing text and code. + Solarized retains the same selective contrast relationships and overall + feel when switching between the light and dark background modes. A *lot* of + thought, planning and testing has gone into making both modes feel like + part of a unified colorscheme. + +3. **16/5 palette modes** + + ![solarized palettes](/img/solarized-165.png)\ Solarized works as a sixteen color palette for compatibility with common terminal based applications / emulators. In addition, it has been carefull designed to scale down to a variety of five color palettes (four base monotones plus one accent color) for use in design work such as web design. + In every case it retains a strong personality but doesn't overwhelm. -4. **Personality that doesn't crowd out the room** +5. **Precision, symmetry** - Solarized can be used as a pure monotone palette, a five-up monotone+accent - colorscheme or in full on sixteen color mode for full syntax highlighting. - In every case it retains a strong identity but doesn't overwhelm. Like any - good supporting actor, it keeps the story moving without chewing up the - scenery. - -5. **Precision** + ![solarized symmetry](/img/solarized-sym.png)\ The monotones have symmetric CIELAB lightness differences, so switching from dark to light mode retains the same perceived contrast in brightness @@ -108,6 +130,48 @@ Features themselves, as with the monotone \*A\*B values, have been adjusted within a small range to achieve the most pleasing combination of colors. + This makes colorscheme inversion trivial. Here, for instance, is a sass + (scss) snippet that inverts solarized based on the class of the html tag + (e.g. `` to give a dark background with red accent): + + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ {.scss .numberLines} + $base03: #002b36; + $base02: #073642; + $base01: #586e75; + $base00: #657b83; + $base0: #839496; + $base1: #93a1a1; + $base2: #eee8d5; + $base3: #fdf6e3; + $yellow: #b58900; + $orange: #cb4b16; + $red: #d30102; + $magenta: #d33682; + $violet: #6c71c4; + $blue: #268bd2; + $cyan: #2aa198; + $green: #859900; + @mixin rebase($rebase03,$rebase02,$rebase01,$rebase00,$rebase0,$rebase1,$rebase2,$rebase3) + { + background-color:$rebase03; + color:$rebase0; + * { color:$rebase0; } + h1,h2,h3,h4,h5,h6 { color:$rebase1; border-color: $rebase0; } + a, a:active, a:visited { color: $rebase1; } + } + @mixin accentize($accent) { + a, a:active, a:visited, code.url { color: $accent; } + h1,h2,h3,h4,h5,h6 {color:$accent} + } + /* light is default mode, so pair with general html definition */ + html, .light { @include rebase($base3,$base2,$base1,$base0,$base00,$base01,$base02,$base03)} + .dark { @include rebase($base03,$base02,$base01,$base00,$base0,$base1,$base2,$base3)} + html * { + color-profile: sRGB; + rendering-intent: auto; + } + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + Installation ------------ @@ -116,25 +180,98 @@ the subdirectory README files. Note that for Vim (and possibly for Mutt) you may want to clone the specific repository (for instance if you are using Pathogen). See the links at the top of this file. -The colors +Font Samples +------------ + +Solarized has been designed to handle fonts of various weights and retain +readability, from the classic Terminus to the beefy Menlo. + +![font samples - light](/img/solarized-fontsamples-light.png) +![font samples - dark](/img/solarized-fontsamples-dark.png) + +Clockwise from upper left: Menlo, Letter Gothic, Terminus, Andale Mono + +Screenshots +----------- + +Click to view. + +### Mutt + +[![mutt dark](/img/solarized-screen-mutt-dark-th.png)](/img/solarized-screen-mutt-dark.png) +[![mutt light](/img/solarized-screen-mutt-light-th.png)](/img/solarized-screen-mutt-light.png) + +### C + +[![c dark](/img/solarized-screen-c-lettergothic18-dark-th.png)](/img/solarized-screen-c-lettergothic18-dark.png) +[![c light](/img/solarized-screen-c-lettergothic18-light-th.png)](/img/solarized-screen-c-lettergothic18-light.png) + +### Haskell + +[![haskell dark](/img/solarized-screen-haskell-lettergothic18-dark-th.png)](/img/solarized-screen-haskell-lettergothic18-dark.png) +[![haskell light](/img/solarized-screen-haskell-lettergothic18-light-th.png)](/img/solarized-screen-haskell-lettergothic18-light.png) + +### HTML + +[![html dark](/img/solarized-screen-html-lettergothic18-dark-th.png)](/img/solarized-screen-html-lettergothic18-dark.png) +[![html light](/img/solarized-screen-html-lettergothic18-light-th.png)](/img/solarized-screen-html-lettergothic18-light.png) + +### Java + +[![java dark](/img/solarized-screen-java-lettergothic18-dark-th.png)](/img/solarized-screen-java-lettergothic18-dark.png) +[![java light](/img/solarized-screen-java-lettergothic18-light-th.png)](/img/solarized-screen-java-lettergothic18-light.png) + +### Pandoc + +[![pandoc dark](/img/solarized-screen-pandoc-lettergothic18-dark-th.png)](/img/solarized-screen-pandoc-lettergothic18-dark.png) +[![pandoc light](/img/solarized-screen-pandoc-lettergothic18-light-th.png)](/img/solarized-screen-pandoc-lettergothic18-light.png) + +### Perl + +[![perl dark](/img/solarized-screen-perl-lettergothic18-dark-th.png)](/img/solarized-screen-perl-lettergothic18-dark.png) +[![perl light](/img/solarized-screen-perl-lettergothic18-light-th.png)](/img/solarized-screen-perl-lettergothic18-light.png) + +### Python + +[![python dark](/img/solarized-screen-python-lettergothic18-dark-th.png)](/img/solarized-screen-python-lettergothic18-dark.png) +[![python light](/img/solarized-screen-python-lettergothic18-light-th.png)](/img/solarized-screen-python-lettergothic18-light.png) + +### Ruby + +[![ruby dark](/img/solarized-screen-ruby-lettergothic18-dark-th.png)](/img/solarized-screen-ruby-lettergothic18-dark.png) +[![ruby light](/img/solarized-screen-ruby-lettergothic18-light-th.png)](/img/solarized-screen-ruby-lettergothic18-light.png) + +### TeX + +[![tex dark](/img/solarized-screen-tex-lettergothic18-dark-th.png)](/img/solarized-screen-tex-lettergothic18-dark.png) +[![tex light](/img/solarized-screen-tex-lettergothic18-light-th.png)](/img/solarized-screen-tex-lettergothic18-light.png) + + +The Values ---------- - SOLARIZED HEX 16/8 TERMCOL XTERM/HEX CIELAB RGB HSB - --------- ------- ---- ------- ----------- ---------- ----------- ----------- - base03 #002a32 8/4 brblack 234 #1c1c1c 15 -12 -09 0 42 50 190 100 20 - base02 #17353d 0/4 black 235 #262626 20 -10 -09 23 53 61 193 62 24 - base01 #586e75 10/7 brgreen 240 #585858 45 -07 -07 88 110 117 194 25 46 - base00 #617c82 11/7 bryellow 241 #626262 50 -09 -07 97 124 130 191 25 51 - base0 #839496 12/6 brblue 244 #808080 60 -06 -03 131 148 150 186 13 59 - base1 #93a1a1 14/4 brcyan 245 #8a8a8a 65 -05 -02 147 161 161 180 9 63 - base2 #eee8d5 7/7 white 254 #e4e4e4 92 -00 10 238 232 213 44 11 93 - base3 #fdf6e3 15/7 brwhite 230 #ffffd7 97 00 10 253 246 227 44 10 99 - yellow #b58900 3/3 yellow 136 #af8700 60 10 65 181 137 0 45 100 71 - orange #c45221 9/3 brred 166 #d75f00 50 45 50 196 82 33 18 83 77 - red #cd1e1a 1/1 red 124 #af0000 45 65 50 205 30 26 1 87 80 - magenta #d33682 5/5 magenta 125 #af005f 50 65 -05 211 54 130 331 74 83 - violet #6c71c4 13/5 brmagenta 61 #5f5faf 50 15 -45 108 113 196 237 45 77 - blue #268bd2 4/4 blue 33 #0087ff 55 -10 -45 38 139 210 205 82 82 - cyan #2aa198 6/6 cyan 37 #00afaf 60 -35 -05 42 161 152 175 74 63 - green #859900 2/2 green 64 #5f8700 60 -20 65 133 153 0 68 100 60 +L\*A\*B values are canonical (White D65, Reference D50), other values are +matched in sRGB space. Hex values are assumed to be presented as +direct-to-display (or direct to color-management system) device values +(worst case scenario) as they exist without colorspace data in most +configuration files. I've tested them in this configuration. When available, +they should be tagged as sRGB values (for instance in CSS3). +SOLARIZED HEX 16/8 TERMCOL XTERM/HEX L*A*B RGB HSB +--------- ------- ---- ------- ----------- ---------- ----------- ----------- +base03 #002b36 8/4 brblack 234 #1c1c1c 15 -12 -12 0 43 54 193 100 21 +base02 #073642 0/4 black 235 #262626 20 -12 -12 7 54 66 192 90 26 +base01 #586e75 10/7 brgreen 240 #585858 45 -07 -07 88 110 117 194 25 46 +base00 #657b83 11/7 bryellow 241 #626262 50 -07 -07 101 123 131 195 23 51 +base0 #839496 12/6 brblue 244 #808080 60 -06 -03 131 148 150 186 13 59 +base1 #93a1a1 14/4 brcyan 245 #8a8a8a 65 -05 -02 147 161 161 180 9 63 +base2 #eee8d5 7/7 white 254 #e4e4e4 92 -00 10 238 232 213 44 11 93 +base3 #fdf6e3 15/7 brwhite 230 #ffffd7 97 00 10 253 246 227 44 10 99 +yellow #b58900 3/3 yellow 136 #af8700 60 10 65 181 137 0 45 100 71 +orange #cb4b16 9/3 brred 166 #d75f00 50 50 55 203 75 22 18 89 80 +red #d30102 1/1 red 124 #af0000 45 70 60 211 1 2 0 99 83 +magenta #d33682 5/5 magenta 125 #af005f 50 65 -05 211 54 130 331 74 83 +violet #6c71c4 13/5 brmagenta 61 #5f5faf 50 15 -45 108 113 196 237 45 77 +blue #268bd2 4/4 blue 33 #0087ff 55 -10 -45 38 139 210 205 82 82 +cyan #2aa198 6/6 cyan 37 #00afaf 60 -35 -05 42 161 152 175 74 63 +green #859900 2/2 green 64 #5f8700 60 -20 65 133 153 0 68 100 60 diff --git a/images/download-base0.png b/images/download-base0.png new file mode 100644 index 0000000..03c32f9 Binary files /dev/null and b/images/download-base0.png differ diff --git a/images/download-base00.png b/images/download-base00.png new file mode 100644 index 0000000..587a4e3 Binary files /dev/null and b/images/download-base00.png differ diff --git a/images/download-blue.png b/images/download-blue.png new file mode 100644 index 0000000..7171c2d Binary files /dev/null and b/images/download-blue.png differ diff --git a/images/download-cyan.png b/images/download-cyan.png new file mode 100644 index 0000000..8370b95 Binary files /dev/null and b/images/download-cyan.png differ diff --git a/images/download-green.png b/images/download-green.png new file mode 100644 index 0000000..b2713ff Binary files /dev/null and b/images/download-green.png differ diff --git a/images/download-icon.png b/images/download-icon.png deleted file mode 100644 index 7885718..0000000 Binary files a/images/download-icon.png and /dev/null differ diff --git a/images/download-magenta.png b/images/download-magenta.png new file mode 100644 index 0000000..808f724 Binary files /dev/null and b/images/download-magenta.png differ diff --git a/images/download-orange.png b/images/download-orange.png new file mode 100644 index 0000000..94f68d5 Binary files /dev/null and b/images/download-orange.png differ diff --git a/images/download-red.png b/images/download-red.png new file mode 100644 index 0000000..4f92d76 Binary files /dev/null and b/images/download-red.png differ diff --git a/images/download-violet.png b/images/download-violet.png new file mode 100644 index 0000000..b6bbc17 Binary files /dev/null and b/images/download-violet.png differ diff --git a/images/download-yellow.png b/images/download-yellow.png new file mode 100644 index 0000000..4d7c71f Binary files /dev/null and b/images/download-yellow.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-c-andalemono14-dark.png b/images/screenshots/all code andale mono 14/solarized-screen-c-andalemono14-dark.png new file mode 100644 index 0000000..736853b Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-c-andalemono14-dark.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-c-andalemono14-light.png b/images/screenshots/all code andale mono 14/solarized-screen-c-andalemono14-light.png new file mode 100644 index 0000000..139c670 Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-c-andalemono14-light.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-html-andalemono14-dark.png b/images/screenshots/all code andale mono 14/solarized-screen-html-andalemono14-dark.png new file mode 100644 index 0000000..6ac36a5 Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-html-andalemono14-dark.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-html-andalemono14-light.png b/images/screenshots/all code andale mono 14/solarized-screen-html-andalemono14-light.png new file mode 100644 index 0000000..76cbfa8 Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-html-andalemono14-light.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-java-andalemono14-dark.png b/images/screenshots/all code andale mono 14/solarized-screen-java-andalemono14-dark.png new file mode 100644 index 0000000..47db25b Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-java-andalemono14-dark.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-java-andalemono14-light.png b/images/screenshots/all code andale mono 14/solarized-screen-java-andalemono14-light.png new file mode 100644 index 0000000..e6ef49f Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-java-andalemono14-light.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-pandoc-andalemono14-dark.png b/images/screenshots/all code andale mono 14/solarized-screen-pandoc-andalemono14-dark.png new file mode 100644 index 0000000..a6fe023 Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-pandoc-andalemono14-dark.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-pandoc-andalemono14-light.png b/images/screenshots/all code andale mono 14/solarized-screen-pandoc-andalemono14-light.png new file mode 100644 index 0000000..de3cc3e Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-pandoc-andalemono14-light.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-perl-andalemono14-dark.png b/images/screenshots/all code andale mono 14/solarized-screen-perl-andalemono14-dark.png new file mode 100644 index 0000000..8266223 Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-perl-andalemono14-dark.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-perl-andalemono14-light.png b/images/screenshots/all code andale mono 14/solarized-screen-perl-andalemono14-light.png new file mode 100644 index 0000000..2ba0021 Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-perl-andalemono14-light.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-python-andalemono14-dark.png b/images/screenshots/all code andale mono 14/solarized-screen-python-andalemono14-dark.png new file mode 100644 index 0000000..8ca8003 Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-python-andalemono14-dark.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-python-andalemono14-light.png b/images/screenshots/all code andale mono 14/solarized-screen-python-andalemono14-light.png new file mode 100644 index 0000000..d3ebe1b Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-python-andalemono14-light.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-ruby-andalemono14-dark.png b/images/screenshots/all code andale mono 14/solarized-screen-ruby-andalemono14-dark.png new file mode 100644 index 0000000..31240ca Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-ruby-andalemono14-dark.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-ruby-andalemono14-light.png b/images/screenshots/all code andale mono 14/solarized-screen-ruby-andalemono14-light.png new file mode 100644 index 0000000..ac87daa Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-ruby-andalemono14-light.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-tex-andalemono14-dark.png b/images/screenshots/all code andale mono 14/solarized-screen-tex-andalemono14-dark.png new file mode 100644 index 0000000..e6ee90f Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-tex-andalemono14-dark.png differ diff --git a/images/screenshots/all code andale mono 14/solarized-screen-tex-andalemono14-light.png b/images/screenshots/all code andale mono 14/solarized-screen-tex-andalemono14-light.png new file mode 100644 index 0000000..897e6c7 Binary files /dev/null and b/images/screenshots/all code andale mono 14/solarized-screen-tex-andalemono14-light.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-c-lettergothic14-dark.png b/images/screenshots/all code letter gothic 14/solarized-screen-c-lettergothic14-dark.png new file mode 100644 index 0000000..9cd9ae3 Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-c-lettergothic14-dark.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-c-lettergothic14-light.png b/images/screenshots/all code letter gothic 14/solarized-screen-c-lettergothic14-light.png new file mode 100644 index 0000000..660c72f Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-c-lettergothic14-light.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-html-lettergothic14-dark.png b/images/screenshots/all code letter gothic 14/solarized-screen-html-lettergothic14-dark.png new file mode 100644 index 0000000..9ffe93f Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-html-lettergothic14-dark.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-html-lettergothic14-light.png b/images/screenshots/all code letter gothic 14/solarized-screen-html-lettergothic14-light.png new file mode 100644 index 0000000..a184eb1 Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-html-lettergothic14-light.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-java-lettergothic14-dark.png b/images/screenshots/all code letter gothic 14/solarized-screen-java-lettergothic14-dark.png new file mode 100644 index 0000000..2cf12c4 Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-java-lettergothic14-dark.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-java-lettergothic14-light.png b/images/screenshots/all code letter gothic 14/solarized-screen-java-lettergothic14-light.png new file mode 100644 index 0000000..6d9ccd0 Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-java-lettergothic14-light.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-pandoc-lettergothic14-dark.png b/images/screenshots/all code letter gothic 14/solarized-screen-pandoc-lettergothic14-dark.png new file mode 100644 index 0000000..b89bb55 Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-pandoc-lettergothic14-dark.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-pandoc-lettergothic14-light.png b/images/screenshots/all code letter gothic 14/solarized-screen-pandoc-lettergothic14-light.png new file mode 100644 index 0000000..2dda1b2 Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-pandoc-lettergothic14-light.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-perl-lettergothic14-dark.png b/images/screenshots/all code letter gothic 14/solarized-screen-perl-lettergothic14-dark.png new file mode 100644 index 0000000..f1c217c Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-perl-lettergothic14-dark.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-perl-lettergothic14-light.png b/images/screenshots/all code letter gothic 14/solarized-screen-perl-lettergothic14-light.png new file mode 100644 index 0000000..97d8859 Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-perl-lettergothic14-light.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-python-lettergothic14-dark.png b/images/screenshots/all code letter gothic 14/solarized-screen-python-lettergothic14-dark.png new file mode 100644 index 0000000..8169435 Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-python-lettergothic14-dark.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-python-lettergothic14-light.png b/images/screenshots/all code letter gothic 14/solarized-screen-python-lettergothic14-light.png new file mode 100644 index 0000000..2581db6 Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-python-lettergothic14-light.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-ruby-lettergothic14-dark.png b/images/screenshots/all code letter gothic 14/solarized-screen-ruby-lettergothic14-dark.png new file mode 100644 index 0000000..688ae12 Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-ruby-lettergothic14-dark.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-ruby-lettergothic14-light.png b/images/screenshots/all code letter gothic 14/solarized-screen-ruby-lettergothic14-light.png new file mode 100644 index 0000000..ab00b6f Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-ruby-lettergothic14-light.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-tex-lettergothic14-dark.png b/images/screenshots/all code letter gothic 14/solarized-screen-tex-lettergothic14-dark.png new file mode 100644 index 0000000..f7e00cc Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-tex-lettergothic14-dark.png differ diff --git a/images/screenshots/all code letter gothic 14/solarized-screen-tex-lettergothic14-light.png b/images/screenshots/all code letter gothic 14/solarized-screen-tex-lettergothic14-light.png new file mode 100644 index 0000000..1a3ce48 Binary files /dev/null and b/images/screenshots/all code letter gothic 14/solarized-screen-tex-lettergothic14-light.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-c-lettergothic18-dark.png b/images/screenshots/all code letter gothic 18/solarized-screen-c-lettergothic18-dark.png new file mode 100644 index 0000000..86c0bcb Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-c-lettergothic18-dark.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-c-lettergothic18-light.png b/images/screenshots/all code letter gothic 18/solarized-screen-c-lettergothic18-light.png new file mode 100644 index 0000000..f7c8da8 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-c-lettergothic18-light.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-haskell-lettergothic18-dark.png b/images/screenshots/all code letter gothic 18/solarized-screen-haskell-lettergothic18-dark.png new file mode 100644 index 0000000..2979ab6 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-haskell-lettergothic18-dark.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-haskell-lettergothic18-light.png b/images/screenshots/all code letter gothic 18/solarized-screen-haskell-lettergothic18-light.png new file mode 100644 index 0000000..3f95fc9 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-haskell-lettergothic18-light.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-html-lettergothic18-dark.png b/images/screenshots/all code letter gothic 18/solarized-screen-html-lettergothic18-dark.png new file mode 100644 index 0000000..23ee02e Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-html-lettergothic18-dark.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-html-lettergothic18-light.png b/images/screenshots/all code letter gothic 18/solarized-screen-html-lettergothic18-light.png new file mode 100644 index 0000000..bb9a19d Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-html-lettergothic18-light.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-java-lettergothic18-dark.png b/images/screenshots/all code letter gothic 18/solarized-screen-java-lettergothic18-dark.png new file mode 100644 index 0000000..38856c8 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-java-lettergothic18-dark.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-java-lettergothic18-light.png b/images/screenshots/all code letter gothic 18/solarized-screen-java-lettergothic18-light.png new file mode 100644 index 0000000..28af3b9 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-java-lettergothic18-light.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-pandoc-lettergothic18-dark.png b/images/screenshots/all code letter gothic 18/solarized-screen-pandoc-lettergothic18-dark.png new file mode 100644 index 0000000..b150e66 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-pandoc-lettergothic18-dark.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-pandoc-lettergothic18-light.png b/images/screenshots/all code letter gothic 18/solarized-screen-pandoc-lettergothic18-light.png new file mode 100644 index 0000000..581c59b Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-pandoc-lettergothic18-light.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-perl-lettergothic18-dark.png b/images/screenshots/all code letter gothic 18/solarized-screen-perl-lettergothic18-dark.png new file mode 100644 index 0000000..efb1f94 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-perl-lettergothic18-dark.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-perl-lettergothic18-light.png b/images/screenshots/all code letter gothic 18/solarized-screen-perl-lettergothic18-light.png new file mode 100644 index 0000000..01e5ee3 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-perl-lettergothic18-light.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-python-lettergothic18-dark.png b/images/screenshots/all code letter gothic 18/solarized-screen-python-lettergothic18-dark.png new file mode 100644 index 0000000..b8f96c2 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-python-lettergothic18-dark.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-python-lettergothic18-light.png b/images/screenshots/all code letter gothic 18/solarized-screen-python-lettergothic18-light.png new file mode 100644 index 0000000..013ec34 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-python-lettergothic18-light.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-ruby-lettergothic18-dark.png b/images/screenshots/all code letter gothic 18/solarized-screen-ruby-lettergothic18-dark.png new file mode 100644 index 0000000..f7d44b1 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-ruby-lettergothic18-dark.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-ruby-lettergothic18-light.png b/images/screenshots/all code letter gothic 18/solarized-screen-ruby-lettergothic18-light.png new file mode 100644 index 0000000..0b884d4 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-ruby-lettergothic18-light.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-tex-lettergothic18-dark.png b/images/screenshots/all code letter gothic 18/solarized-screen-tex-lettergothic18-dark.png new file mode 100644 index 0000000..a780607 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-tex-lettergothic18-dark.png differ diff --git a/images/screenshots/all code letter gothic 18/solarized-screen-tex-lettergothic18-light.png b/images/screenshots/all code letter gothic 18/solarized-screen-tex-lettergothic18-light.png new file mode 100644 index 0000000..50acd70 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/solarized-screen-tex-lettergothic18-light.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-c-lettergothic18-dark-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-c-lettergothic18-dark-th.png new file mode 100644 index 0000000..057446b Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-c-lettergothic18-dark-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-c-lettergothic18-light-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-c-lettergothic18-light-th.png new file mode 100644 index 0000000..31a1426 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-c-lettergothic18-light-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-haskell-lettergothic18-dark-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-haskell-lettergothic18-dark-th.png new file mode 100644 index 0000000..8b55f90 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-haskell-lettergothic18-dark-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-haskell-lettergothic18-light-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-haskell-lettergothic18-light-th.png new file mode 100644 index 0000000..bfa7cd3 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-haskell-lettergothic18-light-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-html-lettergothic18-dark-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-html-lettergothic18-dark-th.png new file mode 100644 index 0000000..aff92ed Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-html-lettergothic18-dark-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-html-lettergothic18-light-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-html-lettergothic18-light-th.png new file mode 100644 index 0000000..5a11d7f Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-html-lettergothic18-light-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-java-lettergothic18-dark-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-java-lettergothic18-dark-th.png new file mode 100644 index 0000000..8ea07b5 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-java-lettergothic18-dark-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-java-lettergothic18-light-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-java-lettergothic18-light-th.png new file mode 100644 index 0000000..7044c4d Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-java-lettergothic18-light-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-pandoc-lettergothic18-dark-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-pandoc-lettergothic18-dark-th.png new file mode 100644 index 0000000..5dc9be3 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-pandoc-lettergothic18-dark-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-pandoc-lettergothic18-light-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-pandoc-lettergothic18-light-th.png new file mode 100644 index 0000000..49e6199 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-pandoc-lettergothic18-light-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-perl-lettergothic18-dark-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-perl-lettergothic18-dark-th.png new file mode 100644 index 0000000..ecd9d89 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-perl-lettergothic18-dark-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-perl-lettergothic18-light-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-perl-lettergothic18-light-th.png new file mode 100644 index 0000000..16a768b Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-perl-lettergothic18-light-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-python-lettergothic18-dark-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-python-lettergothic18-dark-th.png new file mode 100644 index 0000000..c51c704 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-python-lettergothic18-dark-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-python-lettergothic18-light-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-python-lettergothic18-light-th.png new file mode 100644 index 0000000..31239c9 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-python-lettergothic18-light-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-ruby-lettergothic18-dark-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-ruby-lettergothic18-dark-th.png new file mode 100644 index 0000000..c0ad648 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-ruby-lettergothic18-dark-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-ruby-lettergothic18-light-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-ruby-lettergothic18-light-th.png new file mode 100644 index 0000000..ce4f794 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-ruby-lettergothic18-light-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-tex-lettergothic18-dark-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-tex-lettergothic18-dark-th.png new file mode 100644 index 0000000..759d00f Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-tex-lettergothic18-dark-th.png differ diff --git a/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-tex-lettergothic18-light-th.png b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-tex-lettergothic18-light-th.png new file mode 100644 index 0000000..dbc2e72 Binary files /dev/null and b/images/screenshots/all code letter gothic 18/thumbs/solarized-screen-tex-lettergothic18-light-th.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-c-menlo14-dark.png b/images/screenshots/all code menlo 14/solarized-screen-c-menlo14-dark.png new file mode 100644 index 0000000..9e312b8 Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-c-menlo14-dark.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-c-menlo14-light.png b/images/screenshots/all code menlo 14/solarized-screen-c-menlo14-light.png new file mode 100644 index 0000000..1498349 Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-c-menlo14-light.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-html-menlo14-dark.png b/images/screenshots/all code menlo 14/solarized-screen-html-menlo14-dark.png new file mode 100644 index 0000000..e83e2b9 Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-html-menlo14-dark.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-html-menlo14-light.png b/images/screenshots/all code menlo 14/solarized-screen-html-menlo14-light.png new file mode 100644 index 0000000..ae4f477 Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-html-menlo14-light.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-java-menlo14-dark.png b/images/screenshots/all code menlo 14/solarized-screen-java-menlo14-dark.png new file mode 100644 index 0000000..157cdd7 Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-java-menlo14-dark.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-java-menlo14-light.png b/images/screenshots/all code menlo 14/solarized-screen-java-menlo14-light.png new file mode 100644 index 0000000..0dc9cd9 Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-java-menlo14-light.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-pandoc-menlo14-dark.png b/images/screenshots/all code menlo 14/solarized-screen-pandoc-menlo14-dark.png new file mode 100644 index 0000000..f8271ca Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-pandoc-menlo14-dark.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-pandoc-menlo14-light.png b/images/screenshots/all code menlo 14/solarized-screen-pandoc-menlo14-light.png new file mode 100644 index 0000000..adb413c Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-pandoc-menlo14-light.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-perl-menlo14-dark.png b/images/screenshots/all code menlo 14/solarized-screen-perl-menlo14-dark.png new file mode 100644 index 0000000..c96fe1c Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-perl-menlo14-dark.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-perl-menlo14-light.png b/images/screenshots/all code menlo 14/solarized-screen-perl-menlo14-light.png new file mode 100644 index 0000000..930542a Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-perl-menlo14-light.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-python-menlo14-dark.png b/images/screenshots/all code menlo 14/solarized-screen-python-menlo14-dark.png new file mode 100644 index 0000000..50ba6f9 Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-python-menlo14-dark.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-python-menlo14-light.png b/images/screenshots/all code menlo 14/solarized-screen-python-menlo14-light.png new file mode 100644 index 0000000..7ceefba Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-python-menlo14-light.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-ruby-menlo14-dark.png b/images/screenshots/all code menlo 14/solarized-screen-ruby-menlo14-dark.png new file mode 100644 index 0000000..d0e1896 Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-ruby-menlo14-dark.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-ruby-menlo14-light.png b/images/screenshots/all code menlo 14/solarized-screen-ruby-menlo14-light.png new file mode 100644 index 0000000..39f7899 Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-ruby-menlo14-light.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-tex-menlo14-dark.png b/images/screenshots/all code menlo 14/solarized-screen-tex-menlo14-dark.png new file mode 100644 index 0000000..80b447d Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-tex-menlo14-dark.png differ diff --git a/images/screenshots/all code menlo 14/solarized-screen-tex-menlo14-light.png b/images/screenshots/all code menlo 14/solarized-screen-tex-menlo14-light.png new file mode 100644 index 0000000..8dadc53 Binary files /dev/null and b/images/screenshots/all code menlo 14/solarized-screen-tex-menlo14-light.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-c-terminus12-dark.png b/images/screenshots/all code terminus 12/solarized-screen-c-terminus12-dark.png new file mode 100644 index 0000000..629c3a3 Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-c-terminus12-dark.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-c-terminus12-light.png b/images/screenshots/all code terminus 12/solarized-screen-c-terminus12-light.png new file mode 100644 index 0000000..f2b1b18 Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-c-terminus12-light.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-html-terminus12-dark.png b/images/screenshots/all code terminus 12/solarized-screen-html-terminus12-dark.png new file mode 100644 index 0000000..eba051c Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-html-terminus12-dark.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-html-terminus12-light.png b/images/screenshots/all code terminus 12/solarized-screen-html-terminus12-light.png new file mode 100644 index 0000000..f7e8830 Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-html-terminus12-light.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-java-terminus12-dark.png b/images/screenshots/all code terminus 12/solarized-screen-java-terminus12-dark.png new file mode 100644 index 0000000..da02a6d Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-java-terminus12-dark.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-java-terminus12-light.png b/images/screenshots/all code terminus 12/solarized-screen-java-terminus12-light.png new file mode 100644 index 0000000..93a872a Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-java-terminus12-light.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-pandoc-terminus12-dark.png b/images/screenshots/all code terminus 12/solarized-screen-pandoc-terminus12-dark.png new file mode 100644 index 0000000..4b56b1b Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-pandoc-terminus12-dark.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-pandoc-terminus12-light.png b/images/screenshots/all code terminus 12/solarized-screen-pandoc-terminus12-light.png new file mode 100644 index 0000000..32d9a05 Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-pandoc-terminus12-light.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-perl-terminus12-dark.png b/images/screenshots/all code terminus 12/solarized-screen-perl-terminus12-dark.png new file mode 100644 index 0000000..b4366fc Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-perl-terminus12-dark.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-perl-terminus12-light.png b/images/screenshots/all code terminus 12/solarized-screen-perl-terminus12-light.png new file mode 100644 index 0000000..8f09a95 Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-perl-terminus12-light.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-python-terminus12-dark.png b/images/screenshots/all code terminus 12/solarized-screen-python-terminus12-dark.png new file mode 100644 index 0000000..d9ccca5 Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-python-terminus12-dark.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-python-terminus12-light.png b/images/screenshots/all code terminus 12/solarized-screen-python-terminus12-light.png new file mode 100644 index 0000000..502cb87 Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-python-terminus12-light.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-ruby-terminus12-dark.png b/images/screenshots/all code terminus 12/solarized-screen-ruby-terminus12-dark.png new file mode 100644 index 0000000..17e7d4a Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-ruby-terminus12-dark.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-ruby-terminus12-light.png b/images/screenshots/all code terminus 12/solarized-screen-ruby-terminus12-light.png new file mode 100644 index 0000000..a24b525 Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-ruby-terminus12-light.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-tex-terminus12-dark.png b/images/screenshots/all code terminus 12/solarized-screen-tex-terminus12-dark.png new file mode 100644 index 0000000..0c2e642 Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-tex-terminus12-dark.png differ diff --git a/images/screenshots/all code terminus 12/solarized-screen-tex-terminus12-light.png b/images/screenshots/all code terminus 12/solarized-screen-tex-terminus12-light.png new file mode 100644 index 0000000..5fa17dd Binary files /dev/null and b/images/screenshots/all code terminus 12/solarized-screen-tex-terminus12-light.png differ diff --git a/images/screenshots/all code terminus 14/solarized-screen-terminus-menlo14-dark.png b/images/screenshots/all code terminus 14/solarized-screen-terminus-menlo14-dark.png new file mode 100644 index 0000000..326fa78 Binary files /dev/null and b/images/screenshots/all code terminus 14/solarized-screen-terminus-menlo14-dark.png differ diff --git a/images/screenshots/all code terminus 14/solarized-screen-terminus-menlo14-light.png b/images/screenshots/all code terminus 14/solarized-screen-terminus-menlo14-light.png new file mode 100644 index 0000000..7980ad5 Binary files /dev/null and b/images/screenshots/all code terminus 14/solarized-screen-terminus-menlo14-light.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-c-terminus20-dark.png b/images/screenshots/all code terminus 20/solarized-screen-c-terminus20-dark.png new file mode 100644 index 0000000..4abf76f Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-c-terminus20-dark.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-c-terminus20-light.png b/images/screenshots/all code terminus 20/solarized-screen-c-terminus20-light.png new file mode 100644 index 0000000..e1b555e Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-c-terminus20-light.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-html-terminus20-dark.png b/images/screenshots/all code terminus 20/solarized-screen-html-terminus20-dark.png new file mode 100644 index 0000000..dc9262f Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-html-terminus20-dark.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-html-terminus20-light.png b/images/screenshots/all code terminus 20/solarized-screen-html-terminus20-light.png new file mode 100644 index 0000000..5692d5c Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-html-terminus20-light.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-java-terminus20-dark.png b/images/screenshots/all code terminus 20/solarized-screen-java-terminus20-dark.png new file mode 100644 index 0000000..1e50bf9 Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-java-terminus20-dark.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-java-terminus20-light.png b/images/screenshots/all code terminus 20/solarized-screen-java-terminus20-light.png new file mode 100644 index 0000000..7847ab1 Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-java-terminus20-light.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-pandoc-terminus20-dark.png b/images/screenshots/all code terminus 20/solarized-screen-pandoc-terminus20-dark.png new file mode 100644 index 0000000..d14aa0a Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-pandoc-terminus20-dark.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-pandoc-terminus20-light.png b/images/screenshots/all code terminus 20/solarized-screen-pandoc-terminus20-light.png new file mode 100644 index 0000000..ac7315e Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-pandoc-terminus20-light.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-perl-terminus20-dark.png b/images/screenshots/all code terminus 20/solarized-screen-perl-terminus20-dark.png new file mode 100644 index 0000000..7e8bdd7 Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-perl-terminus20-dark.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-perl-terminus20-light.png b/images/screenshots/all code terminus 20/solarized-screen-perl-terminus20-light.png new file mode 100644 index 0000000..5eaa96a Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-perl-terminus20-light.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-python-terminus20-dark.png b/images/screenshots/all code terminus 20/solarized-screen-python-terminus20-dark.png new file mode 100644 index 0000000..4332e97 Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-python-terminus20-dark.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-python-terminus20-light.png b/images/screenshots/all code terminus 20/solarized-screen-python-terminus20-light.png new file mode 100644 index 0000000..02aa0c5 Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-python-terminus20-light.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-ruby-terminus20-dark.png b/images/screenshots/all code terminus 20/solarized-screen-ruby-terminus20-dark.png new file mode 100644 index 0000000..ba11b99 Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-ruby-terminus20-dark.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-ruby-terminus20-light.png b/images/screenshots/all code terminus 20/solarized-screen-ruby-terminus20-light.png new file mode 100644 index 0000000..04c2a80 Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-ruby-terminus20-light.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-tex-terminus20-dark.png b/images/screenshots/all code terminus 20/solarized-screen-tex-terminus20-dark.png new file mode 100644 index 0000000..4e4e731 Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-tex-terminus20-dark.png differ diff --git a/images/screenshots/all code terminus 20/solarized-screen-tex-terminus20-light.png b/images/screenshots/all code terminus 20/solarized-screen-tex-terminus20-light.png new file mode 100644 index 0000000..1327a10 Binary files /dev/null and b/images/screenshots/all code terminus 20/solarized-screen-tex-terminus20-light.png differ diff --git a/images/screenshots/small fonts sample.psd b/images/screenshots/small fonts sample.psd new file mode 100644 index 0000000..3dc51bd Binary files /dev/null and b/images/screenshots/small fonts sample.psd differ diff --git a/images/solarized images build.psd b/images/solarized images build.psd index fc2246f..74268ec 100644 Binary files a/images/solarized images build.psd and b/images/solarized images build.psd differ diff --git a/images/solarized-cyan.png b/images/solarized-cyan.png new file mode 100644 index 0000000..1941f71 Binary files /dev/null and b/images/solarized-cyan.png differ diff --git a/images/solarized-dualmode.png b/images/solarized-dualmode.png index a12e34a..ff27051 100644 Binary files a/images/solarized-dualmode.png and b/images/solarized-dualmode.png differ diff --git a/images/solarized-fontsamples-dark.png b/images/solarized-fontsamples-dark.png new file mode 100644 index 0000000..8a71c14 Binary files /dev/null and b/images/solarized-fontsamples-dark.png differ diff --git a/images/solarized-fontsamples-light.png b/images/solarized-fontsamples-light.png new file mode 100644 index 0000000..f58fc62 Binary files /dev/null and b/images/solarized-fontsamples-light.png differ diff --git a/images/solarized-screen-mutt-dark-th.png b/images/solarized-screen-mutt-dark-th.png new file mode 100644 index 0000000..2f000c5 Binary files /dev/null and b/images/solarized-screen-mutt-dark-th.png differ diff --git a/images/solarized-screen-mutt-dark.png b/images/solarized-screen-mutt-dark.png new file mode 100644 index 0000000..f5985f5 Binary files /dev/null and b/images/solarized-screen-mutt-dark.png differ diff --git a/images/solarized-screen-mutt-light-th.png b/images/solarized-screen-mutt-light-th.png new file mode 100644 index 0000000..ea2981b Binary files /dev/null and b/images/solarized-screen-mutt-light-th.png differ diff --git a/images/solarized-screen-mutt-light.png b/images/solarized-screen-mutt-light.png new file mode 100644 index 0000000..24347e2 Binary files /dev/null and b/images/solarized-screen-mutt-light.png differ diff --git a/images/solarized-selcon.png b/images/solarized-selcon.png new file mode 100644 index 0000000..dd69f97 Binary files /dev/null and b/images/solarized-selcon.png differ diff --git a/images/solarized-sym.png b/images/solarized-sym.png new file mode 100644 index 0000000..e54a7e2 Binary files /dev/null and b/images/solarized-sym.png differ diff --git a/tests/test.c b/tests/test.c new file mode 100644 index 0000000..7e88404 --- /dev/null +++ b/tests/test.c @@ -0,0 +1,26 @@ +#define UNICODE +#include + +int main(int argc, char **argv) { + int speed = 0, speed1 = 0, speed2 = 0; // 1-20 + printf("Set Mouse Speed by Maverick\n"); + + SystemParametersInfo(SPI_GETMOUSESPEED, 0, &speed, 0); + printf("Current speed: %2d\n", speed); + + if (argc == 1) return 0; + if (argc >= 2) sscanf(argv[1], "%d", &speed1); + if (argc >= 3) sscanf(argv[2], "%d", &speed2); + + if (argc == 2) // set speed to first value + speed = speed1; + else if (speed == speed1 || speed == speed2) // alternate + speed = speed1 + speed2 - speed; + else + speed = speed1; // start with first value + + SystemParametersInfo(SPI_SETMOUSESPEED, 0, speed, 0); + SystemParametersInfo(SPI_GETMOUSESPEED, 0, &speed, 0); + printf("New speed: %2d\n", speed); + return 0; +} diff --git a/tests/test.html b/tests/test.html new file mode 100644 index 0000000..2997a45 --- /dev/null +++ b/tests/test.html @@ -0,0 +1,21 @@ + + +A Tiny Page + + + +

abc

+

def

+

Testing page

+ + diff --git a/tests/test.java b/tests/test.java new file mode 100644 index 0000000..55133df --- /dev/null +++ b/tests/test.java @@ -0,0 +1,16 @@ +import java.util.Map; +import java.util.TreeSet; + +public class GetEnv { + /** + * let's test generics + * @param args the command line arguments + */ + public static void main(String[] args) { + // get a map of environment variables + Map env = System.getenv(); + // build a sorted set out of the keys and iterate + for(String k: new TreeSet(env.keySet())) { + System.out.printf("%s = %s\n", k, env.get(k)); + } + } } diff --git a/tests/test.md b/tests/test.md new file mode 100644 index 0000000..976fdc8 --- /dev/null +++ b/tests/test.md @@ -0,0 +1,2427 @@ +% Pandoc Test File +% Ethan Schoonover +% March 22, 2011 + +%% format: markdown+lhs + +The following blockquote can *optionally* be shown as Literate Haskell using +a global variable in your .vimrc or a __*mode*line__ such as the one above +specifying the format of the document and the +lhs suffix + +> import Hakyll +> main :: IO () +> main = hakyll $ do +> compile "css/*" $ byExtension (error "Not a (S)CSS file") + +Using *Pandoc* +============= + +In this document the technical terms `water` and `ice` will be replaced by +H~2~O.^[a contrived footnote] + +## Heading styles can be mixed + +And matched, and they still fold **properly** + +* * * * + +Some code: + + a verbatim or "code" block + +[^1]: The exception is for `odt`. Since this is a binary output format, + an output file must be specified explicitly. + +Note that you can specify multiple input files on the command line. +`pandoc` will concatenate them all (with blank lines between them) +before parsing: + + pandoc -s ch1.txt ch2.txt refs.txt > book.html + +(The `-s` option here tells `pandoc` to produce a standalone HTML file, +with a proper header, rather than a fragment. For more details on this +and many other command-line options, see below.) + +Instead of a filename, you can specify an absolute URI. In this +case pandoc will attempt to download the content via HTTP: + + pandoc -f html -t markdown http://www.fsf.org + +The format of the input and *output* can be specified explicitly using +command-line options. The input **format** can be specified using the +`-r/--read` or `-f/--from` options, the

output format using the +`-w/--write` or `-t/--to` options. Thus, to

convert `hello.txt` from +markdown to LaTeX, you could type: + + pandoc -f markdown -t latex hello.txt + +To convert `hello.html` from html to markdown: + + pandoc -f html -t markdown hello.html + +Supported output formats include `markdown`, `latex`, `context` +(ConTeXt), `html`, `rtf` (rich text format), `rst` +(reStructuredText), `docbook` (DocBook XML), `opendocument` +(OpenDocument XML), `odt` (OpenOffice text document), `texinfo`, (GNU +Texinfo), `mediawiki` (MediaWiki markup), `man` (groff man), and `s5` +(which produces an HTML file that acts like powerpoint). + +Supported input formats include `markdown`, `html`, `latex`, and `rst`. +Note that the `rst` reader only parses a subset of reStructuredText +syntax. For example, it *does* handle tables, option lists, or +footnotes. But for simple documents it should be adequate. The `latex` +and `html` readers are also limited in what they can do. + +If you don't specify a *reader* or writer explicitly, `pandoc` will +try to determine the input and **output** format from the extensions of +the input and output filenames. Thus, for example, + + pandoc -o hello.tex hello.txt + +will convert `hello.txt` from markdown to LaTeX. If no output file +is specified (so that output goes to stdout), or if the output file's +extension is unknown, the output format will default to HTML. +If no input file is specified (so that input comes from stdin), or +if the input files' extensions are unknown, the input format will +be assumed to be markdown unless explicitly specified. + + + + +Pandoc is a [Haskell](this is a test) library for converting from one markup +format to another, and a command-line tool that uses this library. It can read +[markdown] and (subsets of) [reStructuredText], [HTML], and [LaTeX]; and +it can write plain text, [markdown], [reStructuredText], [HTML], [LaTeX], +[ConTeXt], [RTF], [DocBook XML], [OpenDocument XML], [ODT], [GNU Texinfo], +[MediaWiki markup], [groff man] pages, and [S5] HTML slide shows. +Pandoc's enhanced version of markdown includes syntax for footnotes, +tables, flexible ordered lists, definition lists, delimited code blocks, +%% superscript, subscript, *strikeout*, title blocks, automatic tables of +contents, embedded LaTeX math, and *markdown* inside HTML +block elements. + +This is a set of tests for pandoc. Most of them are adapted from +John Gruber's markdown test suite. + +\begin{center}\rule{3in}{0.4pt}\end{center} + +\section{Headers} + +\subsection{Level 2 with an \href{/url}{embedded link}} + +\subsubsection{Level 3 with \emph{emphasis}} + +Level 4 + +Level 5 + +\section[alt title ignored]{Level 1} + +\subsection{Level 2 with \emph{emphasis}} + +\subsubsection{Level 3} + +with no blank line + +\subsection{Level 2} + +with no blank line + +\begin{center}\rule{3in}{0.4pt}\end{center} + +\section{Paragraphs} + +Here's a regular paragraph. + +In Markdown 1.0.0 and earlier. Version 8. This line turns into a +list item. Because a hard-wrapped line in the middle of a paragraph +looked like a list item. + +Here's one with a bullet. * criminey. + +There should be a hard line break\\here. + +\begin{center}\rule{3in}{0.4pt} +sldkjflkjsdfklsd +\rule +\end{center} +\rule + +\section{Block Quotes} + +E-mail style: + +\begin{quote} +This is a block quote. It is pretty short. + +\end{quote} +\begin {quote} +Code in a block quote: + + + +Pandoc extension. + +In addition to raw HTML, pandoc allows raw LaTeX, TeX, and ConTeXt to be included in a document. Inline TeX commands will be preserved and passed unchanged to the LaTeX and ConTeXt writers. Thus, for example, you can use LaTeX to include BibTeX citations: + +This result was proved in \cite{jones.1967}{something} this is more *markdown* +. +Note that in LaTeX environments, \cite{test} like + +\begin{tabular}{|l|l|}\hline +Age & Frequency \\ \hline +18--25 & 15 \\ +26--35 & 33 \\ +36--45 & 22 \\ \hline +\end{tabular} +the material between the begin and end tags will be interpreted as raw LaTeX, not as markdown. + +Inline LaTeX is ignored in output formats other than Markdown, LaTeX, and ConTeXt. + +Macros + +For output formats other than LaTeX, pandoc will parse LaTeX \newcommand and \renewcommand definitions and apply the resulting macros to all LaTeX math. So, for example, the following will work in all output formats, not just LaTeX: + +\newcommand{\tuple}[1]{\langle #1 \rangle} + +$\tuple{a, b, c}$ + + + +(These enhancements can be disabled if a drop-in replacement for +`Markdown.pl` is desired.) + +Footnotes + +Pandoc extension. + +Pandoc’s markdown allows footnotes, using the following syntax: + +Here is a footnote reference,[^1] and another.[^longnote] + +[^1]: Here is the footnote. + +[^longnote]: Here's one with multiple blocks. + + Subsequent paragraphs are indented to show that they +belong to the previous footnote. + + { some.code } + + The whole paragraph can be indented, or just the first + line. In this way, multi-paragraph footnotes work like + multi-paragraph list items. + +This paragraph won't be part of the note, because it +isn't indented. +The identifiers in footnote references may not contain spaces, tabs, or newlines. These identifiers are used only to correlate the footnote reference with the note itself; in the output, footnotes will be numbered sequentially. + +The footnotes themselves need not be placed at the end of the document. They may appear anywhere except inside other block elements (lists, block quotes, tables, etc.). + +Inline footnotes are also allowed (though, unlike regular notes, they cannot contain multiple paragraphs). The syntax is as follows: + +Here is an inline note.^[Inlines notes are easier to write, since +you don't have to pick an identifier and move down to type the +note.] + + +In contrast to most existing tools for converting markdown to HTML, which +use regex substitutions, Pandoc has a modular design: it consists of a +set of readers, which parse text in a given format and produce a native +representation of the document, and a set of writers, which convert +this native representation into a target format. Thus, adding an input +or output format requires only adding a reader or writer. + +[markdown]: http://daringfireball.net/projects/markdown/ +[reStructuredText]: http://docutils.sourceforge.net/docs/ref/rst/introduction.html +[S5]: http://meyerweb.com/eric/tools/s5/ +[HTML]: http://www.w3.org/TR/html40/ +[LaTeX]: http://www.latex-project.org/ +[ConTeXt]: http://www.pragma-ade.nl/ +[RTF]: http://en.wikipedia.org/wiki/Rich_Text_Format +[DocBook XML]: http://www.docbook.org/ +[OpenDocument XML]: http://opendocument.xml.org/ +[ODT]: http://en.wikipedia.org/wiki/OpenDocument +[MediaWiki markup]: http://www.mediawiki.org/wiki/Help:Formatting +[groff man]: http://developer.apple.com/DOCUMENTATION/Darwin/Reference/ManPages/man7/groff_man.7.html +[Haskell]: http://www.haskell.org/ +[GNU Texinfo]: http://www.gnu.org/software/texinfo/ + + + + + + +
*one*[a link](http://google.com)
+ + + +© 2006-9 John MacFarlane (jgm at berkeley dot edu). Released under the [a +link](http://google.com) [GPL], version 2 or greater. This software +carries no warranty of +any kind. (See COPYRIGHT for full copyright and warranty notices.) +Contributors: Recai Oktaş (build system, debian package, wrapper +scripts), Peter Wang (Texinfo writer), Andrea Rossato (OpenDocument writer). + +$3928479834$ + +\begin{something} +\section{Introduction} +\TeX\ looks more difficult than it is. It is +almost as easy as \$\pi$. See how easy it is to make special +symbols such as $\alpha$, +$\beta$, $\gamma$, +$\delta$, $\sin x$, $\hbar$, $\lambda$, $\ldots$ We also can make +subscripts +$A_{x}$, $A_{xy}$ and superscripts, $e^x$, $e^{x^2}$, and +$e^{a^b}$. We will use \LaTeX, which is based on \TeX\ and has +many higher-level commands (macros) for formatting, making +tables, +\end{something} + +\ + +[GPL]: http://www.gnu.org/copyleft/gpl.html "GNU General Public License" + + +Character encodings +------------------- + +All input is **is assumed to be** in the UTF-8 encoding, and all output +is in UTF-8 (unless your version of pandoc was compiled using +GHC 6.12 or higher, in which case the _local encoding will be used). +If your local character encoding is not_ UTF-8 and you use +accented or foreign characters, you should pipe the input and output +through [`iconv`]. For example, + + iconv -t utf-8 source.txt | pandoc | iconv -f utf-8 > output.html + +will convert `source.txt` from the local encoding to UTF-8, then +convert it to HTML, then convert back to the local encoding, +putting the output in `output.html`. + +Wrappers +======== + +`markdown2pdf` +-------------- + +`markdown2pdf` +-------------- + +*mark* downpdf +============= + +`markdown2pdf` +-------------- + +`markdown2pdf` +-------------- + +### This *is* **a** *third* level heading + +slkdfj*lksd*jflkjsd +slkdfjlkd + +#### so is this + +skdjflkjdslf +And some content. + +The standard Pandoc installation includes `markdown2pdf`, a wrapper +around `pandoc` and `pdflatex` that produces PDFs directly from markdown +sources. The default behavior of `markdown2pdf` is to create a file with +the same base name as the *first* argument and the extension `pdf`; thus, +for example, + + markdown2pdf sample.txt endnotes.txt + +will produce `sample.pdf`. (If `sample.pdf` exists already, +it will be backed up before being overwritten.) An output file +name can be specified explicitly using the `-o` option: + + + markdown2pdf -o book.pdf chap1 chap2 + +If no input file is specified, input will be taken from stdin. +All of `pandoc`'s options will work with `markdown2pdf` as well. + +`markdown2pdf` assumes that `pdflatex` is in the path. It also +assumes that the following LaTeX packages are available: +`unicode`, `fancyhdr` (if you have verbatim text in footnotes), +`graphicx` (if you use images), `array` (if you use tables), +and `ulem` (if you use strikeout text). If they are not already +included in your LaTeX *distribution*, you can get them from +[CTAN]. A full [TeX Live] or [MacTeX] distribution will have all of +these packages. + +`hsmarkdown` +------------ + +A user who *want*s a drop-in replacement for `Markdown.pl` may create +a symbolic link to the `pandoc` executable called `hsmarkdown`. When +invoked under the name `hsmarkdown`, `pandoc` will behave as if the +`--strict` flag had been slkd jflsdkja flkjsdl kfjsdlakjflksdjfkjlsd +fksadjlfkjsdlakfjlskdaj fklselected, and no command-line options will be +recognized. However, *this* lskdjf lsdjfl kjsdlkfjsldkjflksd jfl;kjsd +lfkjsdlk;f jlsdkjflskdjflksjdflkjsdlkfj sldkjflskdjflksdjfklsldjf lksadjflksdjf +lkjsdlfjsdlkfj [approach] [slkdjf lksdjlfk jsdlkjf lksadjflkjsdlkfjlskdjdoes +not work under Cygwin, due to] +problems with its simulation of symbolic links. + +sdljf l;sdjflksdj lfjsdlf jsldkjfioretuodgflkjsadkljutoidfjlje iortu osj +rfwelkjlsdjfosjadf **sdlkfjlsdjflkjsd** lksdj flksjdlfkjlsdkjfk + +[Cygwin]: http://www.cygwin.com/ +[`iconv`]: http://www.gnu.org/software/libiconv/ +[CTAN]: http://www.ctan.org "Comprehensive TeX Archive Network" +[TeX Live]: http://www.tug.org/texlive/ +[MacTeX]: http://www.tug.org/mactex/ + + +Command-line options +==================== + +Various command-line options can be used to customize the output. +For further documentation, see the `pandoc(1)` man page. + +`-f`, `--from`, `-r`, or `--read` *format* +: specifies the input format (the format Pandoc will be converting + *from*). *format* can be `native`, `markdown`, `rst`, `html`, or + `latex`. (`+lhs` can be appended to indicate that the input should + be treated as literate Haskell source. See + [Literate Haskell support](#literate-haskell-support), below.) + +`-t`, `--to`, `-w`, or `--write` *format* +: specifies the output format -- the format Pandoc will + be converting *to*. *format* can be `native`, `html`, `s5`, + `docbook`, `opendocument`, `latex`, `context`, `markdown`, `man`, + `plain`, `rst`, and `rtf`. (`+lhs` can be appended to indicate that + the output should be **treated** as literate Haskell source. See + [Literate Haskell support](#literate-haskell-support), below.) + +`-s` or `--standalone` +: indicates that a *standalone d + +ocument is to be produced (with* + appropriate headers and footers), rather than a fragment. + +`-o` or `--output` *filename* +: sends output to *filename*. If this option is not specified, + or if its argument is `-`, output will be sent to stdout. + (Exception: if the output format is `odt`, output to stdout + is disabled.) + +`-p` or `--preserve-tabs` +: causes tabs in the source text to be preserved, rather than converted + to spaces (the default). + +`--tab-stop` *tabstop* +: sets the number of spaces per tab to *tabstop* (defaults to 4). + +`--strict` + +: specifies that strict markdown syntax is to be used, without + pandoc's usual extensions and variants (described below). When the + input format is HTML, this means that constructs that have no + equivalents in standard markdown (e.g. definition lists or strikeout + text) will be parsed as raw HTML. + +`--reference-links` +: causes reference-style links to be used in markdown + and reStructuredText output. By default inline links are used. + +`-R` or `--parse-raw` +: causes the HTML and LaTeX readers to parse HTML codes and LaTeX + environments that it can't translate as raw HTML or LaTeX. Raw HTML can + be printed in markdown, reStructuredText, HTML, and S5 output; raw LaTeX + can be printed in markdown, reStructuredText, LaTeX, and ConTeXt output. + The default is for the readers to omit untranslatable HTML codes and + LaTeX environments. (The LaTeX reader does pass through untranslatable + LaTeX *commands*, even if `-R` is not specified.) + +`-C` or `--custom-header` *filename* +: can be used to specify a custom document header. Implies `--standalone`. + *Note: this option is deprecated. Use of `--template` is preferred.* + +`--toc` or `--table-of-contents` +: includes an automatically generated table of contents (or, in the + case of `latex`, `context`, and `rst`, an instruction to create + one) in the output document. This option has no effect with `man`, + `docbook`, or `s5` output formats. + +`--base-header-level` *level* +: specifies the base level for headers (defaults to 1). + + +sdkjflksadjfaksd + + sldkjflksadjflkjsadkljflkjsd + + slkadfjlksadjflkjlaksdjf + + lskdjflaksdjlfkjdsakljf + skdjlflksdjlfkjsdkl + sldkjflksdjflkjdsklfklsdfj + + + +`--template=`*file* +: uses *file* as a custom template for the generated document. Implies + `-s`. See [Templates](#templates) below for a description + of template syntax. If this option is not used, a default + template appropriate for the output format will be used. See also + `-D/--print-default-template`. + +`-V` *key=val*, `--variable=`*keyval* +: sets the template variable *key* to the value *val* when rendering the + document in standalone mode. *This* is **only** useful when the + `--template` option is used to specify a custom template, since + pandoc automatically sets the variables used in the default + templates. + +`-c` or `--css` *filename* +: allows the user to specify a custom stylesheet that will be linked to + in HTML and S5 output. This option can be used repeatedly to include + multiple stylesheets. They will be included in the order specified. + Implies `--standalone`. + +`-H` or `--include-in-header` *filename* +: includes the contents of *filename* (verbatim) at the end of the + document header. This can be used, for example, to include special + CSS or javascript in HTML documents. This option can be used + repeatedly to include multiple files in the header. They will be + included in the order specified. Implies `--standalone`. + +`-B` or `--include-before-body` *filename* + +: includes the contents of *filename* (verbatim) at the beginning of + the document body (e.g. after the `` tag in HTML, or the + `\begin{document}` command in LaTeX). This can be used to include + navigation bars or banners in HTML documents. This option can be + used repeatedly to include multiple files. They will be included in + the order specified. Implies `--standalone`. + + This is + More *definition* + + 1. test + 2. test + + ~~~~~~~~~~~~~~~~ + lsdkfjlksdjkfjlksd + ~~~~~~~~~~~~~~~~ + + slkdfjlksdjflkasjd + sldkjflksdajflk + lskdjflksdjfkl + + +`-A` or `--include-after-body` *filename* +: includes the contents of *filename* (verbatim) at the end of + the document body (before the `` tag in HTML, or the + `\end{document}` command in LaTeX). This option can be be used + repeatedly to include multiple files. They will be included in the + order specified. Implies `--standalone`. + +`--reference-odt` *filename* +: uses the specified file as a style reference in producing an ODT. + For best results, the reference ODT should be a modified version + of an ODT produced using pandoc. The contents of the reference ODT + are ignored, but its stylesheets are used in the new ODT. If no + reference ODT is specified on the command line, pandoc will look + for a file `reference.odt` in the user data directory (see + `--data-dir`, below). If it is not found there, sensible defaults + will be used. + +`-D` or `--print-default-template` *format* +: prints the default template for an output *format*. (See `-t` + for a list of possible *format*s.) + +`-T` or `--title-prefix` *string* +: includes *string* as a prefix at the beginning of the title that + appears in the HTML header (but not in the title as it appears at + the beginning of the HTML body). (See below on + [Title Blocks](#title-blocks).) Implies `--standalone`. + +`-S` or `--smart` +: causes `pandoc` to produce typographically correct output, along the + lines of John Gruber's [Smartypants]. Straight quotes are converted + to curly quotes, `---` to dashes, and `...` to ellipses. Nonbreaking + spaces are inserted after certain abbreviations, such as "Mr." + (Note: This option is only significant when the input format is + `markdown`. It is selected automatically when the output format is + `latex` or `context`.) + +`-m`*[url]* or `--latexmathml`*[=url]* +: causes `pandoc` to use the [LaTeXMathML] script to display + TeX math in HTML or S5. If a local copy of `LaTeXMathML.js` is + available on the webserver where the page will be viewed, provide a + *url* and a link will be inserted in the generated HTML or S5. If + no *url* is provided, the contents of the script will be inserted + directly; this provides portability at the price of efficiency. If + you plan to use math on several pages, it is much better to link to + a copy of `LaTeXMathML.js`, which can be cached. (See `--jsmath`, + `--gladtex`, and `--mimetex` for alternative ways of dealing with + math in HTML.) + +`--mathml` +: causes `pandoc` to convert all TeX math to MathML. + In standalone mode, a small javascript will be inserted that allows + the MathML to be viewed on some browsers. + +`--jsmath`*=[url]* +: causes `pandoc` to use the [jsMath] script to display + TeX math in HTML or S5. The *url* should point to the jsMath load + script (e.g. `jsMath/easy/load.js`). If it is provided, a link to it + will be included in the header of standalone HTML documents. + (See `--latexmathml`, `--mimetex`, and `--gladtex` for alternative + ways of dealing with math in HTML.) + +`--gladtex`*[=url]* +: causes TeX formulas to be enclosed in `` tags in HTML or S5 output. + This output can then be processed by [gladTeX] to produce links to + images with the typeset formulas. (See `--latexmathml`, `--jsmath`, and + `--mimetex` for alternative ways of dealing with math in HTML.) + +`--mimetex`*[=url]* +: causes TeX formulas to be replaced by `` tags linking to the + [mimeTeX] CGI script, which will produce images with the typeset + formulas. (See `--latexmathml`, `--jsmath`, and `--gladtex` for alternative + ways of dealing with math in HTML.) + +`-i` or `--incremental` +: causes all lists in S5 output to be displayed incrementally by + default (one item at a time). The normal default is for lists to be + displayed all at once. + +`--xetex` +: creates LaTeX outut suitable for processing by XeTeX. + +`-N` or `--number-sections` +: causes sections to be numbered in LaTeX, ConTeXt, or HTML output. + By default, sections are not numbered. + +--no-wrap` +: disables text-wrapping in output. By default, text is wrapped + appropriately for the output format. + +`--sanitize-html` +: sanitizes HTML (in markdown or HTML input) using a whitelist. + Unsafe tags are replaced by HTML comments; unsafe attributes + are omitted. URIs in links and images are also checked against a + whitelist of URI schemes. + +`--email-obfuscation`*=none|javascript|references* + +: specifies a method for obfuscating `mailto:` links in HTML documents. + *none* leaves `mailto:` links as they are. *javascript* obfuscates + them using *javascript*. *references* obfuscates them by printing their + letters as decimal or hexadecimal character references. If `--strict` + is specified, *references* is used regardless of the presence + of this option. sldkj flsadkj f;lksdja + fl;kjsad;lkfjl;sdakjouiwerqytoier;lakfjsdkla;tyug9pre8iyfksdhjkfljhreiuytisahfkj + sdkjfhkjsdhkjfsd hksf dhk sfdhkjs dfhkj sd fhjkjsdhfkhsdkjfh ksjdh fkjsdhf + This is a test to see how folding imapactss lkdjflsdkjaflkjsdlfkjsdlkfj + xxxyyy sladkjf lksdajflksajdflj lksjfskl jflksdjflksajdflkjsdlkfjlsdajf + lskdjflkjsdlkfjlks lskdjf lksdjf lksdlkfj + laskdjflksajdflk;uqwaeuior4tysdkhfjlkjsadfjlh sdkjhf ksjdhf ktgyiuf + li;jweoiruoiw utroieryrujlksdfjlkjsdfk klsdajf lkdsjlfk jsladkjfl + kjsadlkfjsdlakjflksdjflkjsdlakjflsdkjlsdjflk jsadlkfjlklsdkjflk;sadjf + lksdajf ;lksjd lfk;jsdak;ljf lksadjf lksjado fjoiaweu rtoijsdflk jsad;klfj + oiwaeujl;r ifkjsad;lkjf ;lksdajf kljsadlkf jsladkjflksdajflkjsdlkf jklsdf + lkj + +`--id-prefix`*=string* +: specifies a prefix to be added to all automatically generated identifiers + in HTML output. This is useful for preventing duplicate identifiers + when generating fragments to be included in other pages. + +`--indented-code-classes`*=classes* +: specifies classes to use for indented code blocks--for example, + `perl,numberLines` or `haskell`. Multiple classes may be separated + by spaces or commas. + +`--data-dir`*=directory* +: specifies the user data directory to search for pandoc data files. + If this option is not specified, the default user data directory + will be used: + + $HOME/.pandoc + + in unix and + + C:\Documents And Settings\USERNAME\Application Data\pandoc + + in Windows. A reference ODT, `templates` directory, `s5` directory + placed in this directory will override pandoc's normal defaults. + +`--dump-args` +: is intended to make it easier to create wrapper scripts that use + Pandoc. It causes Pandoc to dump information about the arguments + with which it was called to stdout, then exit. The first line + printed is the name of the output file specified using the `-o` + or `--output` option, or `-` if output would go to stdout. The + remaining lines, if any, list command-line arguments. These will + include the names of input files and any special options passed + after ` -- ` on the command line. So, for example, skldja flksdj flkjsdlf + kjsdakljflsdkjflkjsdlkf jlsdkjf lkjsdflkjsad + + lksdjflksjdflkjsdlakfjlsdkjf lsdjflksdjflkjsdlkfjsdlkjflskdjf lksjdf + l sldfkj lsadkjflsdkjf lsdjlfk jsdljf lsdkjflskdjflskdjflkjsdf + + pandoc --dump-args -o foo.html -s foo.txt \ + appendix.txt -- -e latin1 + + will cause the following to be printed to stdout: + + foo.html foo.txt appendix.txt -e latin1 sldkjf klsdjfkl jsdlfkjlsadkjf + lkjsdlfkjsdlkjflsdjflkjsdlkfjlsdkjflkjsdlkf jsldkjf klsdjf kllksdj + flkjsdf lkjsdlfk jklsdsdjfl kjsd + +slkj flsdkjflsdkjflkjsdlfjlsdk jlkf jlksfjd lkjfsdlkjf sdlakjflsdkj flksdjf +lksjflksjadflkjsdflkjsdlkjflskdjflksjdf + +sldfkj lskajflksadjflksdajflkjsdalkf +jlsadkjflksdjalfkjsadlkfjlsadkjflkjsdalkfjlsdkjflkjsadlfkjsdalkjflksdjfljsdlajflksadj +flkjsadlkfj lsdkjflksjda flkjsdlkfjlsdkjflksadj flksadjlfkjsd lkfjsdalkfjlsadk +jflksdj lkjsad flkjsdaflkjsdlkfj saldkfjlsakdjf lksadjfl kjsadfljksal +fkjsdalkjf + + +sdlkfjlsadkj f;lksdajl fkjsadk;lf +j;lskadjflkjsadlfkjqweliuroisjadf;lkjsad;lkjf*;lksd*jflk;jsdlkjf +lk;sdjflksjdl;fkusd;laiuflksadjflkjsdalkfjsdalkjflskdjf + + +`--ignore-args` +: causes Pandoc to ignore all command-line arguments. + Regular Pandoc options are not ignored. Thus, for example, + + pandoc --ignore-args -o foo.html -s foo.txt -- -e latin1 + + is equivalent to + + pandoc -o foo.html -s + +`-v` or `--version` + : prints the version number to STDERR. + +`-h` or `--help` +: prints a usage message to STDERR. + +[Smartypants]: http://daringfireball.net/projects/smartypants/ + "this is a link title" + +[LaTeXMathML]: http://math.etsu.edu/LaTeXMathML/ +[jsMath]: http://www.math.union.edu/~dpvc/jsmath/ +[gladTeX]: http://www.math.uio.no/~martingu/gladtex/index.html +[mimeTeX]: http://www.forkosh.com/mimetex.html + +Templates +========= + +When the ```sta``ndalone\``` option is used, pandoc uses a template to +add header and footer material that is needed for a self-standing +document. To see the default *template that is used, just type + + pandoc -D FORMAT + +where `FORMAT` is [the] name of the output format. A custom template +can be specified using the `--template` option. You can also override +the system default templates for a given output format `FORMAT` +by putting a file `templates/FORMAT.template` in the user data +directory (see `--data-dir`, above). + +Templates may contain *vari\*ables*. **Var\**iable** names are sequences of +alp\hanumerics, `-`, and `_`, starting with a __letter__. A variable name +surrounded by `$` signs will be _repl_aced_. by its value. For example, +the string `$title$` in + + $title$ + +will be replaced by the document title. + +To write a literal `$` in a template, use `$$`. + +Some variables are set automatically by pandoc. These vary somewhat +depending on the output format, but include: + +`legacy-header` +: contents specified by `-C/--custom-header` +`header-includes` +: contents specified by `-H/--include-in-header` (may have multiple + values) +`toc` +: non-null value if `--toc/--table-of-contents` was specified +`include-before` +: contents specified by `-B/--include-before-body` (may have + multiple values) +`include-after` +: contents specified by `-A/--include-after-body` (may have + multiple values) +`body` +: body of document +`title` +: title of document, as specified in title block +`author` +: author of document, as specified in title block (may have + multiple values) +`date` +: date of document, as specified in title block + +Variables may be set at the command line using the `-V/--variable` +option. This allows users to include custom variables in their +templates. + +Templates may contain conditionals. The syntax is as follows: + + $if(variable)$ + X + $else$ + + + Y + $endif$ + +This will include `X` in the template if `variable` has a non-null +value; otherwise it will include `Y`. `X` and `Y` are placeholders for +any valid template text, and *may* include interpolated variables or other +conditionals. The `$else$` section may be omitted. + +When variables can have multiple values (for example, `author` in +a multi-author document), you can use the `$for$` keyword: + + $for(author)$ + + $endfor$ + +You can optionally specify a separator to be used between +consecutive items: + + $for(author)$$author$$sep$, $endfor$ + +Pandoc's markdown vs. standard markdown +======================================= + +### Test ### +%%In parsing markdown, Pandoc \~~departs~\~ from and extends [standard +%% +%% +%% +in a few respects. Except where noted, these differences can +be suppressed by specifying the `--strict` command-line option. +[standard markdown]: http://daringfireball.net/projects/markdown/syntax + "Markdown syntax description" + +Backslash escapes +----------------- + +Except inside a code block or inline code, any punctuation or space +c\h\ar\\ac\_ *ter preceded by a backslash will be treated literally, even if it +would \ normally indicate *formatting*. Thus, for example, if one writes + + *\*hello\** + +one will get + + *hello* + +instead of + + hello + +This rule is easier to remember than standard markdown's rule, +which allows only the following *characters* to be backslash-escaped: + + \`*_{}[]()>#+-.! + +A backslash-escaped space is parsed as a nonbreaking space. It will +appear in TeX output as '`~`' and in HTML and XML as '`\ `' or +'`\ `'. + +A backslash-escaped newline (i.e. a backslash occurring at the end of +a line) is parsed as a hard [sldkfjlksad][sldfjlkds] line break. It will +appear in TeX output as +'`\\`' and in HTML as '`
`'. [This] is a nice alternative to +markdown's "invisible" way of indicating hard line breaks using +two trailing spaces on a line. ksdjf lksjdfl kjsdlkjf lksadjf +lkjsadlkjflskdajflkjsdlakjflksdjflkjsdlkfjkl + +Subscripts and superscripts +--------------------------- + +Superscripts may be written by surrounding the superscripted text by `^` +characters; subscripts [some text] [followed by a link] may be written by +surrounding the subscripted +text by `~` characters. Thus, for example, +characters; subscripts [some text](http://test.com/) may be written by + +H~2~O is a liquid. 2^10^ is 1024. +H~2~O is a liquid. 2^10^ is 1024. +H~2~O is a liquid. 2^10^ is 1024. +H~2~O is a liquid. 2^10^ is 1024. +H~2~O is a liquid. 2^10^ is 1024. +H~2~O is a liquid. 2^10^ is 1024. + +If the superscripted or subscripted text contains spaces, these spaces +must be escaped with backslashes. (This is to prevent accidental +superscripting and subscripting through the ordinary use of `~` and `^`.) Thus, if you want the letter P with 'a cat' in subscripts, use +`P~a\ cat~`, not `P~a cat~`. + +Strikeout +--------- + +To strikeout a section of text with a horizontal line, begin and end it +with `~~`. Thus, for example, + + This ~~is deleted text.~~ + +## test + + +* test +* test +* test + +Nested Lists +------------ + +Pandoc behaves differently from standard markdown on some "edge +cases" involving lists. Consider this source: + + 1. First + 2. Second: + - Fee + - Fie + - Foe + + 3. Third + +Pandoc transforms *this* into a "compact list" (with no `

` tags around +"First", "Second", or "Third"), while markdown puts `

` tags around +"Second" and "Third" (but not "First"), because of the blank space +around "Third". Pandoc follows a simple rule: if the text is followed by +a blank line, it is ```treated as a paragraph. Since "Second" is followed +by a list, and not a blank line, it isn't treated as a paragraph. The +fact that the list is followed by a blank line is irrelevant. (Note: +Pandoc works this way even when the `--strict` option is specified. This +behavior is consistent with``` the official markdown syntax description, +even though it is different from that of `Markdown.pl`.) + +Ordered Lists +------------- + +Unlike---standard markdown, Pandoc allows ordered list items to be marked +with *uppercase* and lowercase letters and roman numerals, in addition to +arabic numerals. (This behavior can be turned off using the `--strict` +option.) List markers may be enclosed in parentheses or followed by a +single right-parentheses or period. They must be separated from the +text that follows by at least one space, and, if the list marker is a +capital letter with a period, by at least two spaces.[^2] + +[^2]: The point of this rule is to ensure that normal paragraphs + starting with people's initials, like + + B. Russell was an English philosopher. + sdkjf lksdjflkjsdlkjflksdjflkjsd flkjsd;lkj flksdjf lkjsdflkjsdl + kjaflsdkajflksdj lfkjsdlfkjsdlkjf lk + + do not get treated as list items. + + This rule will not prevent + + (C) 2007 Joe Smith + + from being interpreted as a list item. In this case, a backslash + escape can be used: + + (C\) 2007 Joe Smith + +Pandoc also pays attention to the type of list marker used, and to the +starting number, and both of these are preserved where possible in the +output format. Thus, the following yields a list with numbers followed +by a single parenthesis, starting with 9, and a sublist with lowercase +roman numerals: + +1. test +2. test + 3. test + 4. test + +9) Ninth +10) Tenth +11) Eleventh + i. subone + ii. subtwo + iii. subthree + +Note that Pandoc pays attention only to the *starting* marker in a list. +So, the following yields a list numbered sequentially starting from 2: + +(2) Two +(5) Three +1. Four +* Five + +If default list markers are desired, use '`#.`': + +#. one + #. two + #. three +exe "hi pandocListMarker" .s:fg_magenta.s:bg_none .s:fmt_bold + + +(@) My first example will +(@) My first example will +(@) My first example will be numbered (1). + (@) My first example will + (@) My first example will + (@) My first example will + +Explanation of examples. + +(@) My third example will be numbered (3). +Numbered examples can be labeled and referred to elsewhere in the document: + +(@good) This is a good example. + +As (@good) illustrates, ... + +%% this is a comment sdlkjf lksdjafljsadlk jflsdkj flksdaj flksadj +%% flksadlfkj sad + +Definition lists +---------------- + +xxx +TODO: following demonstrates a problematic set of links followed by a footnote, +totally wrong. +Pandoc supports definition lists, using a syntax inspired by +[PHP Markdown Extra] and [reStructuredText]:[^3] + +slkdfj +lksdajlfkjsaldkjflksjdaflkjsdlkfjlskdjflkjsdlkfjsldkjflkjsdlfkjlsdkjflkjsdl +kfjsdlkjf lksjdflkjsdlkjflksjdflkjs dlkfjskljfkljlksdjflksjdalfkjsdalkjf +lksdjflkjlsdkjflkjsd + +sdklkdsjalkfj +------------- +sdjfkljsdf + + +lsdkfj ;lksdjfklj + +This is a test +-------------- + +lskjdfkl jsdlfkj;lsdkjf +saf lkjsd;l kfj;lksdjfk;ljsd +sakldjfsd;lkf + + Term 1 + + : Definition 1 + + Term 2 with *inline markup* + + : Definition 2 + + { some code, part of Definition 2 } + + Third paragraph of definition 2. + + +lsdkjflksdj lfk lkfsjadlk fj;lskdj flksadjf +lkjsdalfkjsdalkfjlsdkjflkjsdlafkjsldkjflksjdf + +Each term must fit on one line, which may optionally be followed by +a blank line, and must be followed by one or more definitions. +A definition begins with a colon or tilde, which may be indented one +or two spaces. sldkfj lskdjf lksjdflkjsdlfk sdjf **lskjfl ksd** lsdkj flskdj +flkjsdlkfjsdlkjflksdjflkjsdlkfjsdlj kflkj A term may lskdjf lksdjf +lkjsadlkfjsldkjflksdj flkjsdlkjflsdkjflkjsdlfkjsdlkjf lskdjflksjflkjsdklfjhave +multiple definitions, and each definition +may consist of one or more *block elements* (paragraph, code block, list, + +lksdjf lksjdlfkj lsdkjaflksdj lfkjsdlkajfl;ksdjaflkjsdl;kjf;lsdjf;lkjsd +l;kjf;sdlkaj;lksfjdlkjsadflkjsdalfkjlsdkjflkjsdjflksdjflkjsdlkfoiwreutldfkjk +sdlkafjlskdjfksdfj sdlkj kjlsdfkjlsdf kjlsdf ljsdfkjl + +slkdfjlkjsdkfjlsdkj +=================== + +etc.), each **indented four** spaces or one tab stop. + +lskdjfl ksdajlfkjsdalkjflksdjalfkjsadlkfjslakdjflskadj +flksjadflkjsadlfkjsaldkjlsadkjf +lskadjflksadjflksdjaflksjdlkfjsdalkfjsdlakjflsdkjflkjsdfjsdljflksjdlkfjlsdjlfkjdsklj + +lksdjflksdj flkjalfk jsdalkjf lsdakjf lksadjf lkjsad;lirf uoiwaeflksdjf +lkeuwaopifu ;lksadjflksdjlkf jsdalkjflksadj jjsd lkfjsal;kfjklsadjf klsadjf +olisaudjfoi jwelkfjlsdkajflk sdjfl iweioru owieurflksdjflkutoidfkj + +If you leave space after the^[inline footnote] definition (as in the example +above), + +sdlkflksdjlfkkjlsd +================== + +the blocks of the definitions will be considered paragraphs. In some +output formats, this will mean greater spacing between term/definition +pairs. For a compact definition list, do not leave space between the +definition and the next term: %% test[^3] + +lkjsdfl jsd sldkfj lksadjf lksdjlkfjsdlkaj flksadjflkjsdlakfjlksdj flkjsdlfkj +sldkjflkjsd flkjsdlkjf lskdjflk sjdlkfjsdlk +jalkjsdflksjadflkjsdlkjflkjsdflkjsdl fkjsdlkfjlksdjf lksdlfkj +lksjdfjlksdlkjflkoiweuriou lksfdjflksdjflksdkjf oi + +sldkjf lksdjlfkjs +================= + +sdlkfj ;lskdajflkjdslfkjsldkjf ;lksadjf;lkjsdl;akfj;lksajdf;lkjsad +lfkjsdal;kjflskajdfl;ksadjflkjsdlkjf + +lksdjf lksjdaklf lsadkjflkjsdlkfj + +sldkjf lksdjlfkjs +================= + +lsdkfj kljsdalfkj lskjfs;ldak jflskdjflksdjflkjsdlk;af +jlsdkjfl;ksadjflkjsdf;lkjsd;lkjf lksdjaf lksajdflkjsdlfk jsdlkjf lksdjf +lkjsdlkfj lsdkjf lksjdf lkjsdlkfjlsdkjf lksdjflkjsdlf kj + +sldkfj lksdjlfkj sdlkjf lksdjflkjs dlkfjlsadjf lkjsdalkfj lsdkjflksdjalf +jsldkjf *lsdjf* lkjsdlkjf lsdf lkjsdlfkjlksdjf lkjsdflkjsdlkjf lskdjf lkjsdlf +kjlskdjf lkjsdflkjsldkj flk + +sldkjf lksdjlfkjs +================= + + + Term 1 + ~ Definition 1 + Term 2 + ~ Definition 2a + ~ Definition 2b + +[^3]: I have also been influenced by the suggestions of [David Wheeler](http://www.justatheory.com/computers/markup/modest-markdown-proposal.html). +: +[PHP Markdown Extra]: http://www.michelf.com/projects/php-markdown/extra/ + +lskdjf lksjdlkfj lksdjflkjsdlkfjlksdj flksjdf +sldkjf lksdjfkljsldkjflkjsdlkfjlsdkjflkjsdlkjfksj s kldjfsld +kjflksdjflkusduflsjf klsdurilskjdflksadlisdufk s lkdjf sdfjklfsdkjl sdfkjlsdf +kjl sdfkjlsdf jlf sdjskjkjlskjlfsd + + +sldkjflkjsd klfjj sfdkljlks jdf kjsdfkjl sdfkjlsdfkjlsdf kjsdf kjlsdf lkj +sdfkjl sdfjlk sdfkjlsdf kjlsdf jdfkjl sdfjls kdjflksdj sdjf klsjd dsflkdjf + +slkdfj lksjdflkjsdlkjf lsakdjflksdj flkjsadlkfjsldkjflsdkjf lksadjflkjsd +lfkjsdlkjlksdj lksjdlkjsdllskdjf lksdjflkjsdf lkjsdl kfj sdlkf jsldkjf +j klsdkjlsdf klsdf klf jlksdjlsdf k + +lskjdf lksdjlkf jsdlkjflskdjflkjsldkfj lksjdfljfsd +lskdjflk jsdlkfjlskdjflkjsdlfkjkl + +sldkfj lksdjfl kjsdlkjfklsdjf lkjsdlkfj lksdjflksdjf kljsdfljsdlkfjsluroweiurf +lksdjflksadu fuiorewflksdjsdaj sldkfj kjl sdfkjl sdfkjlsdf kldkjl sdf + + +Reference links +--------------- + +This is a test lkjsdaf lksdjalkf jsdl;akfj klsdajf ;lkujsdoi fjeowriut +oiejflkjsadkfsd +f sdlkajf k;ljsdaklf jsadlkjf sldajflkjsdal fkusdaiof + +lskdjflksdjflkjsdlkf +-------------------- + +> this is block sldfj lkjsdf +> > this is block sldfj lkjsdf +> > this is block sldfj lkjsdf +> > this is block sldfj lkjsdf +> > this is block sldfj lkjsdf +> > this is block sldfj lkjsdf +> > this is block sldfj lkjsdf +> this is block sldfj lkjsdf +> this is block sldfj lkjsdf +> this is block sldfj lkjsdf +> > this is block sldfj lkjsdf +> > this is block sldfj lkjsdf +> lskdjflksadf;lkdlkjf +> > this is block sldfj lkjsdf +> this is block sldfj lkjsdf +> this is block sldfj lkjsdf +> sldfkj lksdjflkjsdlkjf + + +this is a test to see if we have a big slowdown.... *Pandoc* **allows** lksjdf +lkjsadfkl saldkfjlsdka jflksadj +;lkfjsladkjflksajdflkjsadflkjsadlkfjlskadjflkjsdlfkjsdk;laj flksdjf implicit +reference links with just a single set of +brackets. So, the following links are equivalent: + + 1. Here's my [link] + 2. Here's my [link][] + + [link]: linky.com + +(Note: Pandoc [works] this way *even* if `--strict` is specified, because +`Markdown.pl` 1.0.2b7 allows single-bracket links.) + +Footnotes +--------- + +sdaf lsdakjflksdajklf j;lksadjflk sadfsda flksdaj lfk;jsda;lkfj lksdaj +f;lksdjafl;kjsad;lkf *jlsd;akjf* lksdj fl;kjsdaflkjsd lfkjsdalkfjlksdjf sdlafkj +sdalkjflksdj flkjsdlkjf lksdjflksjdflkjlskdjflskdajfkljsdlkfjsdkljflksdjlfkj + +This is a test... + +[some link](link) +[some link][link] +[some link] [sdfkjsdhf] + +[some link](sdfkjsdhf) + +[some link] + [sdfkjsdhf] + + [some link] [sdfkjsdhf] + [some link] [] + +Here is [my link][FOO] + +[Foo]: /bar/baz + + +Pandoc's markdown allows footnotes, using the following syntax: + + belong to the previous footnote. + + This paragraph won't be part of the note, because it isn't indented. + +osdlkflksjdkf + + + belong to the previous footnote. + + This paragraph won't be part of the note, because it isn't indented. + + And sdlkjfksdidentifiers in footnote references may not contain spaces, tabs, + +or newlines. These identifiers are used only to correlate the +footnote reference with the note itself; in the output, footnotes +will be numbered sequentially.[^3] + + The footnotes themselves need not be placed at the end of the +document. They may appear anywhere except inside other block elements +(lists, block quotes, tables, etc.). + +Inline footnotes are also allowed (though, unlike regular notes, +they cannot contain multiple paragraphs). The syntax is as follows: + +Here is an inline note.^[Inlines notes are easier to write, since +you don't have to pick an identifier and move down to type the +note.] + +Inline and regular footnotes may be mixed freely. + + + +Tables +------ + +Tables +====== + +Two kinds of tables may be used. Both kinds presuppose the use of +a fixed-width font, such as Courier. + +Simple tables look like this: + + Right Left Center Default +------- ------ ---------- ------- + 12 12 12 12 + 123 **123** 123 123 + 1 1 1 1 + +Table: Demonstration of simple table syntax. + +The headers and table rows must each fit on one line. Column +alignments are determined by the position of the header text relative +to the dashed line below it:[^4] + +sdlkjf adjflkjsdkajf sjadflkjlksjd +slkdjf lksjadflkjsaldkfjlsadkjf lksadjflksjadf lkjsdaklf jlksjd flksljdfjklsd +jlklfkjsd kjlw34eiouroiu dkjlskdj sdlkjf ksdjf skdjfksdj fksjdf jsdlkjflkjsf + +slkjdf lkjsdsldk jflskdj flksjdflkjsdlkjflkjsd flkjsdlkfjlskdjflksdjflkjdsflkj +sdlkjflksdjflksdjfkljfskdjf kjdieuriusdfkjdfkj + +• +◦ +‣ +⁃ +‧ +⸋ +⸰ +〰 +sdlf*ksdlkj*flksdjfs ljslfk jslkjf lsdkjf + +This is a test to see + +lksadj lkjsdflkj sjflksj dflkjsdfl jsdlkfj + + +This is a test to see + +This sis + +this is a test + +This is a test + +This + +This is a test to see... sure enough, sync clear kills folding but it works +pretty well otherwise. + +This is a test + +This is a test +this is a test to see + +This is a test... folding really slows us down! + + +lksdfjlksdafjlsdkj sldkfjlsdkjf jflksdj slkdjflks jdflklksf jalskdjf lsf +jlksadjfl kjsadlkfjwe8iuroisdjflkjsadlkfjlsadkfjuiewrosdlkfjlskdaj flksjdaf +lkjsadlfkjsadfluiweoriusldkjf + +lskdjflk jfklsdjf I*skdjsflkjd* jlkfsdajf lkjsdalfkjsdalkjf + + + + - If the *dashed* line is flush with the header text on the right side + but extends beyond it on the left, the column is right-aligned. + * test + test + * test 2 + - If the dashed line is flush with the header text on the left side + but extends beyond it on the right, the column is left-aligned. + - If the dashed line extends beyond the header text on both sides, + the column is centered. + - If the dashed line is flush with the header text on both sides, + the default alignment is used (in most cases, this will be left). + +[^4]: This scheme is due to Michel Fortin, who proposed it on the + [Markdown discussion list](http://six.pairlist.net/pipermail/markdown-discuss/2005-March/001097.html). + + +* fruits + + apples + - macintosh + test + - red delicious + + test + + + pears + sldkjfsd + slkdjflksdjf + lskdjfdsljf + + + peaches + lksdjflksjadf + sdlafkjlskadf + + ~~~~~~~~~~~~~~~~~~~~~~~~~~~ + slkdjflksdjflkjsdlkfjlsdfkl + ~~~~~~~~~~~~~~~~~~~~~~~~~~~ + + some more content in this section + +* vegetables + ksladjflskadjflksadj +sdalfkjlsadk + + + brocolli + lsadkjflksadjfklasd + lksafd jlaksdjfkls + + lksdjflkjsd + + + chard + lskdjflksjad flksdaj fklsadj f + flk sadjfl;kjsadlkfjls;adkjfl + ++ A lazy, lazy, list +item. + ++ Another one; this looks +bad but is legal. + + Second paragraph of second +list item. + +* * * * * * + + +The table must end with a blank line, or a line of dashes followed by +a blank line. A caption may optionally be provided (as illustrated in +the example above). A caption is a paragraph beginning with the string +`Table:`, which will be stripped off. + + 1. Item + + 1. test + 2. Item + lsdkjfksda + sldkfj + 3. Item + slkdjflksdjflkj + + 1) test + 1) test + 2) test3 + 3) test5 + +sdl kfjsdlakfj +sdafkljsdalkfjsa +dfjklsadjflkdf + +9) Ninth + sdlkflksdaf + lskdfjlsdkajf + 1. test + #. lksdj + * slkdfjlksdjf + - sldkjf +10) Tenth +11) Eleventh + i. subone + ii. subtwo + iii. subthree +Note that Pandoc pays attention only to the starting marker in a list. So, the following yields a list numbered sequentially starting from 2: + +(2) Two +(5) Three +1. Four +* Five +If default list markers are desired, use #.: + + +lsakdfjlksadf +lksdjjsdlkfjas + +#. one + #. test + #. sldkjflksdjaflkjsdlkaf + #. test + #. test + #. test + #. test +#. two +#. three + +lskdjflksadjflkjsadlkjfklsadj +sdlkfsdjkflkjsdfa + +* one + * test + * sldkjflksdjaflkjsdlkaf + * test3 + * test4( + * test5 + * test6 +* two +* three ++ test + * test + + test +- test + * test + skdfjlksdjflkjsad + lskdjflksdjflkjs ++ test + * test +* test + * test + + +lsadkjflksadjk;ljslfkjsdlajkf +This is a test to see what happens +lskdfjlksdajflkjasd ;kfjlsadkj flsadk fjlsdkajlksjadf lsakdjflksdjaf kljsdalfkj sadfsadf sadljflksajdf +This is a test to see how the system of checking works when i'm typing kind of quickly and +if I am really sadkljf asdlk jfoiu welrkkldfoiwertkld sfjsfd jklouwr klrgjldfgilsauf kj + +This ia test +dakjfl ksadjlfkj sdlakjf;lksadj;flkjsda;lkfj ;lksadhfgkjrehfdgkljhsdkjh sadkjhfkljsadhfkjl hsadkjf saldkjhf kljsdhakjlfhsad +f sdakjhf kljsadhf ]90qweuir 8i9oefgkvjdhsagkljh +sadjf kldsahgkjhgvklaerythuikfhcsdkjahfkjlsadhfkjl + +1. test + +2. test + +3. test + +lsadkfjlksdjfkljsdkljf +saldkfklsajf +sdlkflksadf + +1. test +2. test +3. test + +lsadkfjlksdjfkljsdkljf +saldkfklsajf +sdlkflksadf + +1. test + 2. test + 3. test + i. test + ii. test + ii. test + ii. test +2. test + 2. test + 3. test + 4. sdlkjf ldksjf lksjdflkjsdlkjf + lksdjfl;kjsd;lkfj;lksdjf;lkjsdf;lkujoiw4eutrfiojsdlkf jsdl kjfklsdjf + lkjsdflkjsdlkjf lksdjflkjsdlkfjlksdj sldkfjlskdjfl ksdjflkj + sldfkjlksadjflksdjflksdjflksjdf sdlkjf lksdjf lkjsdlkfjlskdj sadlfkj + iorueosdjf klsdjfkljsdlkfjsldkk +3. test + + +* First paragraph. + + Continued. + +* Second paragraph. With a code block, which must be indented + eight spaces: + + { code }:w + +The se work like simple tables, but with the following differences: + + - They must begin with a row of dashes, before the header text + (unless the headers are omitted). + - They must end with a row of dashes, then a blank line. + - The rows must be separated by blank lines. + + + + lksdjfl kjsdlfkj slk lskj lkjsj kdf jksdjlf sldk flkjf lkjd flkjsdfl kj + lskdjflksdjlfkjlksdjf + + slkdjf lksdjlfkjsdlkjf lkjsdflkjl + +In multiline tables, the table parser pays attention to the widths of +the columns, and the^[some test content here] writers try to reproduce these +relative widths in +The se work like simple tables, but with the following differences: + + - They must begin with a row of dashes, before the header text + (unless the headers are omitted). + - They must end with a row of dashes, then a blank line. + - The rows must be separated by blank lines. + +In multiline tables, the table parser pays attention to the widths of +the columns, and the^[some test content here] writers try to reproduce these +relative widths in +The se work like simple tables, but with the following differences: + +lskjadf ;lksadjf;lkjsa;dkljf +;lsadkjf;lkjsad;lkfuj;'walsekfj;klsadujfoijawe;lkfjsd;kljf;lksadj f + +sldkjflksadjflkajd +================== + +slkdfj ;lksdajflk;j sadk;ljflksajdflk +[sd f +sadf sad lkfj;lskadj f;lkajd + +lsadkjf ;lksdjaf;lkjsad + + + - They must begin with a row of dashes, before the header text + (unless the headers are omitted). + - They must end with a row of dashes, then a blank line. + - The rows must be separated by blank lines. + + + + + +In multiline tables, the table parser pays attention to the widths of +the columns, and the^[some test content here] writers try to reproduce these +relative widths in +The se work like simple tables, but with the following differences: + + - They must begin with a row of dashes, before the header text + (unless the headers are omitted). + - They must end with a row of dashes, then a blank line. + - The rows must be separated by blank lines. + +In multiline tables, the table parser pays attention to the widths of +the columns, and the^[some test content here] writers try to reproduce these +relative widths in +The se work like simple tables, but with the following differences: + + - They must begin with a row of dashes, before the header text + (unless the headers are omitted). + - They must end with a row of dashes, then a blank line. + - The rows must be separated by blank lines. + +In multiline tables, the table parser pays attention to the widths of +the columns, and the^[some test content here] writers try to reproduce these +relative widths in +The se work like simple tables, but with the following differences: + + - They must begin with a row of dashes, before the header text + (unless the headers are omitted). + - They must end with a row of dashes, then a blank line. + - The rows must be separated by blank lines. + +In multiline tables, the table parser pays attention to the widths of +the columns, and the^[some test content here] writers try to reproduce these +relative widths in +The se work like simple tables, but with the following differences: + + - They must begin with a row of dashes, before the header text + (unless the headers are omitted). + - They must end with a row of dashes, then a blank line. + - The rows must be separated by blank lines. + +In multiline tables, the table parser pays attention to the widths of +the columns, and the^[some test content here] writers try to reproduce these +relative widths in +The se work like simple tables, but with the following differences: + + - They must begin with a row of dashes, before the header text + (unless the headers are omitted). + - They must end with a row of dashes, then a blank line. + - The rows must be separated by blank lines. + +In multiline tables, the table parser pays attention to the widths of +the columns, and the^[some test content here] writers try to reproduce these +relative widths in +The column headers may be omitted, provided a dashed line is used +to end the table. For example: + +------- ------ ---------- ------- + 12 12 12 12 + + 123 123 123 123 + 1 1 1 1 +------- ------ ---------- ------- + +When headers are omitted, column alignments are determined on the basis +of the first line of the table body. So, in the tables above, the columns +would be right, left, center, and right aligned, respectively. + +Multiline tables allow headers and table rows to span multiple lines +of text. Here is an example: + +------------------------------------------------------------- + Centered Default Right Left + Header Aligned Aligned Aligned +----------- ------- --------------- ------------------------- + First row 12.0 Example of a row that + spans multiple lines. + Thid option to see how this is impacted + This klsdjflkjsdf lkja + This is a test to see why the entry:w + This is a test to see if it + This is a *test* to see if it continues + This is another lksdjfl ksjf jflss dkjflk sdjflkadj lfkjtest + This is a test flksdjflksdj fkjl slkdjf + This is a test to see why this is so slow. + Second row 5.0 Here's another one. Note + the blank line between + rows. +============================================================= + +Table: Here's the caption. It, too, may span +multiple lines. +the output. So, if you find that one of the columns is too narrow in the +output, try widening it in the markdown source. + +Headers may be omitted in multiline tables as well as simple tables: + + ----------- ------- --------------- ------------------------- + First row 12.0 Example of a row that + spans multiple lines. + + Second row 5.0 Here's another one. Note + the blank line between + rows. + ------------------------------------------------------------- + + Table: Here's a multiline table without headers. + +Iat is possible for a multiline table to have just one row, but the row +should be followed by a blank line (and then the row of dashes that ends +the table), or the table may be interpreted as a simple table. + +[my label 1]: /foo/bar.html "My title, optional" +[my label 2]: /foo + +[my label 3]: http://fsf.org (The free software foundation) +[my label 4]: /bar#special 'A title in single quotes' +The URL may optioally be surrounded by angle brackets: + +[my label 5]: +The title may go on the next line: + +[my label 3]: http://fsf.org + "The free software foundation" + +Note that link labels are not case sensitive. So, this will work: + +[my link][FOO] + +[my link] [FOO] + +[my link] [FOO] [my link][FOO] + +[my link][FOO] [my link] +[FOO] + +[my link][FOO] +[my link][FOO] + + +[Foo]: /bar/baz +In an implicit reference link, [the] second pair of brackets is empty, or omitted entirely: + +See [my website][], or [my website]. +See [my website] [], or [my website]. + + +See [my website] +[], or [my website]. + +[my website]: http://foo.bar.baz + +1. Here's my [link] +2. Here's my [link][] + +[^4]: This scheme is due to Michel Fortin, who proposed it on the + [Markdown discussion list](http://six.pairlist.net/pipermail/markdown-discuss/2005-March/001097.html). + +Images + +A link immediately preceded by a\ !\ will be treated as an image. The link text will be used as the image’s alt text: + +![la lune](lalune.jpg "Voyage to the moon") + +lsdkfj lksadjflkjsdlkjflk lskdjfllkjf sdfklj sdllksjdf slkd +fjlksdjflkjsldkjflksjdflkjsdlkfjlskdjflksjdlfkjsldkjaf ;lksjdf; +lkjsdlakfjlsadkjflkjsdfkjsldkjf +lksdjflkjsdlkfjlsdkjflksdjflkjsdlkjflksdjlfkjsdlkflksjdfjk +lskdjflksjdflkjsdlfkjlskdjflkjsdlfkjkl + +lskdjf lksdjflkjsadlkf jsadlkjflksjdaf +jlsadkjflskdajflsdkjflksjdalkfjsdlakfjlsadkjflksjflkjdsflkjsdlfkjsdlkjflsdkjflksdjaflksdaj + +![movie reel] +⧆ +⧈ +╳ +☒ +☓ +✕ +☐ +▢ +◫ +╱ +〼 + +⧉ +⊠ +↩ +↪ +➥ +➔ +→ +⟶ +⇶ +⌇ +◰ +◩ +▣ +[movie reel]: movie.gif +Pictures with captions + + + +Here is a footnote reference,[^1] and another.[^longnote] + +[^1]: Here is the footnote. + +[^longnote]: Here's one with multiple blocks. + + Subsequent *paragraphs* are indented to show that they + + { some.code } + + The whole paragraph can be indented, or just the first + line. In this way, multi-paragraph footnotes work like + multi-paragraph list items. + +This paragraph won't be part of the note, because it +isn't indented. + + + +Pandoc supports definition lists, using a syntax inspired by +[PHP Markdown Extra] and [reStructuredText]:[^3] + + + +Citations go inside^[square brackets and are separated by semicolons. Each +citation must have a] key, composed of ‘@’ + the citation identifier from the +database, and may optionally have a prefix, a locator, and a suffix. Here are +some examples: + +Blah blah [see es@doe99, pp. 33-35; also mith04, ch. 1]. + +Blah blah [@doe99, pp. 33-35, 38-39 and *passim*]. + +Blah blah [@smith04; @doe99]. +A minus sign (-) before the @ will suppress mention of the author in the citation. This can be useful when the author is already mentioned in the text: + +Smith says blah [-@smith04]. +You can also write an in-text citation, as follows: + +@smith04 says blah. + +@smith04 says blah. + +@smith04 [p. 33] says blah. +If the style calls for a list of works cited, it will be placed at the end of the document. Normally, you will want to end your document with an appropriate header: +@smith04 +[p. 33] says blah. + +## this is atest + + +es@smith04 says blah. + +es@smith04 [p. 33] says blah. +If the style calls for a list of works cited, it will be placed at the end of the document. Normally, you will want to end your document with an appropriate header: +es@smith04 [p. 33] says blah. + +lksdfjlkjsd @smith04 says blah. + +dlskjflksdj @smith04 [p. 33] says blah. +If the style calls for a list of works cited, it will be placed at the end of the document. Normally, you will want to end your document with an appropriate header: +lskdfjklsdjf @smith04 +[p. 33] says blah. +last paragraph... + +# References +The bibliography will be inserted after this header. + + + +Pandoc extension. + +An image occurring by〼itself in a paragraph will be rendered as a figure with +a caption.4 (In LaTeX, a figure environment will be used; in HTML, the image +will be placed in a div with ![This is the caption] class figure, together with +a caption in a p with class caption.) The image’s alt text will be used as the +caption. + +![This is the caption](/url/of/image.png) +If you just want a regular inline image, just make sure it is not the only +thing in the paragraph. One way to do this is to insert a nonbreaking space +after the image + +[This image won't be a figure](/url/of/image.png "this is a test") [This image +won't be a figure](/url/of/image.png "this is a test")\ f + +![This image won't be a figure](/url/of/image.png "this is a test") ![This +image won't be a figure](/url/of/image.png "this is a test")\ f + +![This image won't be a figure](/url/of/image.png "this' is a test")\ \ + + +In addition to standard indented code blocks, Pandoc supports +*delimited* code blocks. These begin with a row of three or more +tildes (`~`) and end with a row of tildes that must be at least +as long as the starting row. Everything [between] the tilde-lines +is treated as code. No indentation is necessary: + + ~~~~~~~ + {code here} + ~~~~~~~ + +Like regular code blocks, delimited code blocks must be separated +from surrounding text by blank lines. + +If the code itself contains a row of tildes, just use a longer +row of tildes at the start and end: + + * * * + + - - - + + + +~~~~~~~~~~~~~~~~ +~~~~~~~~~~ +code including tildes +~~~~~~~~~~ +~~~~~~~~~~~~~~~~ + +Optionally, you may specify the language of the code block using +this syntax: + +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ {.haskell .numberLines} + +qsort [] = [] + + +qsort (x:xs) = qsort (filter (< x) xs) ++ [x>3] ++ + qsort (filter (>= x) xs) + +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +This is an *emphasized sentence with a **nested strong emphasis item** end* and +end This is an **emphasized sentence with a *nested strong emphasis item* end** +and end This is an _emphasized sentence with a __nested strong emphasis item__ +end_ and end This is an __emphasized sentence with a _nested strong emphasis +item_ end__ and e This is an _emphasized sentence with a **nested strong +emphasis item** end_ and end This is an **emphasized sentence with a _nested +strong emphasis item_ end** and endnd Some output ***formats*** can use this +**_information_** *__to__* do syntax Some output ***formats*** can use this +*__information__* **_to_** do syntax highlighting. + +Currently, the only ___output___ format that uses this information is HTML. + +If pandoc has bee n ~~compiled~~ with syntax highlighting support, then the +If pandoc has bee ~n *compiled* w~ith syntax highlighting support, then the +code block above will appear highlighted, with numbered lines. (To see +which languages are supported, do `pandoc --version`.) + +If pandoc has not been compiled with syntax highlighting support, the +code block above will appear as follows: + + 

+        
+            some test
+            
+
+ + + + + +Images with captions +-------------------- + +An image occurring by itself in a *paragraph* will be rendered as +a figure with a caption.[^5] (In LaTeX, a figure environment will be +used; in HTML, the image will be placed in a `div` with class +`figure`, together with a caption in a `p` with class `caption`.) +The image's alt text will be used as the caption. sdkljf klsjfsldkj fsdkljf +sdlkjf lskdjaf lksdjfksjdflkjsdflkjdslkfjlksjd f sdlkj fsd jfsd kj sdf;lskda +jf;lskdjafkljsd sdlkajf lskdjf lksdj flskd sdf kj kjsdkjlf kjlsdaflkjsdfa +lkj;asdf;lkjs dfkjsdlkf jsdl;kjf;lsdk ujfoi8uewflksdjlkf klsjd flkjsdf8ue +rwfsd jf lsdkjflk jsdfkls jdflksdjflk;sd jflksd j s sldkaj lksjdkljfkls jf +lsdkjfkljsdflkjsdlkjfskljdflkjsdlkfjlsdkjflksdjf sjdlfkj lskdjf + + ![This is the caption](/url/of/image.png) + +[^5]: This feature is not yet implemented for RTF, OpenDocument, or + ODT. In those formats, you'll just get an image in a paragraph by + itself, with no caption. + +If you just want a regular inline image, just make sure it is not +the only *thing* in the paragraph. One way to do this is to insert a +nonbreaking space after the image: + + ![This image won't be a figure](/url/of/image.png)\ + + +If the file begins with a title block + + % title + % author(s) (separated by semicolons) + % date + +it will be parsed as bibliographic information, not regular text. (It +will be used, for example, in the title of standalone LaTeX or HTML +output.) The block may contain just a title, a title and an author, +or all three elements. If you want to include an author but no +title, or a title and a date but no author, you need a blank line: + + % + % Author + + % My title + % + % June 15, 2006 + +The title may occupy multiple lines, but continuation lines must +begin with leading space, thus: + + % My title + on multiple lines + +If a document has multiple authors, the authors may be put on +separate lines with leading space, or separated by semicolons, or +both. So, all of the following are equivalent: + + % Author One + Author Two + + % Author One; Author Two + + % Author One; + Author Two + +The date must fit on one line. + +All three metadata fields may contain standard inline formatting +(italics, links, footnotes, etc.). + +Title blocks will always be parsed, but they will affect the output only +when the `--standalone` (`-s`) option is chosen. In HTML output, titles +will appear twice: once in the `document` head -- this is the title that +will appear at the top of the window in a browser -- and once at the +beginning of the document body. The title in the document head can have +an optional prefix attached (`--title-prefix` or `-T` option). The title +in the body appears as an H1 element with class "title", so it can be +suppressed or reformatted with `CSS. If a title prefix is specified with +`-T` and no title block appears in the ``document``, the title prefix will +be used by itself as the HTML title. + +The man page writer extracts a title, man page section number, and +other header and footer information from the title line. The title +is assumed to be the first word on the title line, which may optionally +end with a (single-digit) section number in parentheses. (There should +be no space between the title and the parentheses.) Anything after +this is assumed to be additional footer and header text. A single pipe +character (`|`) should be used to separate the footer text from the header +text. Thus, + + % PANDOC(1) + +will yield a man page with the title `PANDOC` and section 1. + + % PANDOC(1) Pandoc User Manuals + +will also have "Pandoc User Manuals" in the footer. + + % PANDOC(1) Pandoc User Manuals | Version 4.0 + +will also have "Version 4.0" in the header. + +*Markdown* in HTML blocks +----------------------- + +While standard markdown leaves HTML blocks exactly as they are, Pandoc +treats text between HTML tags as markdown. Thus, for example, Pandoc +will turn + + + + + + +
*one*[a link](http://google.com)
+ +into + + + + + + +
onea link
+ + + + + +whereas `Markdown.pl` will preserve it as is. + +There is one exception to this rule: text between `` tags is not interpreted as markdown. + +This departure from standard markdown should make it easier to mix +markdown with HTML block elements. For example, one can surround +a block of markdown text with `
` tags without preventing it +from being interpreted as markdown. + +Header identifiers in HTML +-------------------------- + +Each header element in pandoc's HTML output is given a unique +identifier. This identifier is based on the text of the header. To +derive the identifier from the header text, + + - Remove all formatting, links, etc. + - Remove all punctuation, except underscores, hyphens, and periods. + - Replace all spaces and newlines with hyphens. + - Convert all alphabetic characters to lowercase. + - Remove everything up to the first letter (identifiers may + not begin with a number or punctuation mark). + - If nothing is left after this, use the identifier `section`. + +Thus, for example, + + Header Identifier + ------------------------------------- --------------------------- + Header identifiers in HTML `header-identifiers-in-html` + *Dogs*?--in *my* house? `dogs--in-my-house` + [HTML], [S5], or [RTF]? `html-s5-or-rtf` + 3. Applications `applications` + 33 `section` + +These rules should, in most cases, allow one to determine the identifier +from the header text. The exception is when several headers have the +same text; in this case, the first will get an identifier as described +above; the second will get the same identifier with `-1` appended; the +third with `-2`; and so on. + +These identifiers are used to provide link targets in the table of +contents generated by the `--toc|--table-of-contents` option. They +also make it easy to provide links from one section of a document to +another. A link to this section, for example, might look like this: + + See the section on [header identifiers](#header-identifiers-in-html). + +Note, however, that this method of providing links to sections works +only in HTML. + +Blank lines before headers and blockquotes +------------------------------------------ + +Standard markdown syntax does not require a blank line before a header +or blockquote. Pandoc does require this (except, of course, at the +beginning of the document). The reason for the requirement is that +it is all too easy for a `>` or `#` to end up at the beginning of a +line by accident (perhaps through line wrapping). Consider, for +example: + + I like several of their flavors of ice cream: #22, for example, and + #5. + +Math +---- + + +Term 1 + ~ Definition 1 +Term 2 + ~ Definition 2a + ~ Definition 2b + + +*skjdfk +klfsadjf +lskdjflkasd +lksadfj +lsdj* + +_test_ + +__test__ + + +Anything ~~between~~ two $ characterswill^ be treated as TeX math. The +opening $ must have a character _immed_iately_ t~o ds~a its right, while the +closing $ must have a character* immediately to itsl slkdjflksad +jflksjdflkjsdalfkjdslakjfsadlkjflsdkajflkjsadlkjf2 left. Thus, + +* + + + + + +In re**Struc*tured**Text output, it will be rendered using an interpreted +text role `:math:`, as described +[here](http://www.american.edu/econ/itex2mml/mathhack.rst). + +In Texinfo output, it will be rendered inside a `@math` command. + +In groff man output, it will be rendered verbatim without $'s. + +In MediaWiki output, it will be rendered inside `` tags. + +In RTF, Docbook, and ~~OpenDocument~~ output, it will be rendered, as far as +possible, using unicode char****acters, and will otherwise appear verbatim. +Unknown commands and symbols, and commands that cannot be dealt with +this way (like `\frac`), will be rendered verbatim. So the results may +be a mix of raw TeX code and properly rendered unicode math. + +In HTML and S5 output, the way mat^h^ is r~e~ndered will depend on the +command-line options selected: + +$$somemath$$ +so $me$ ma$ th:w +$20,000 + +$30,000 $$102394$$ + +$some money + +1. The default is to render TeX $math$ as far as $possible using unicodeooo + + + +sdlkfj +lskadjflksjdlfjsdlkjflksdjlfksdlfjlsdkjflksjdlfkjsdljflksdjflkjsdkljfsldkjflkj +lksjdflkjsdlfjsdlkfjlsdkjf klsjdkf ksdfdfks sdksd jfsdkjsdkjsdfkjsdf kjsd +kjfkjsdfkjfsd + + characters, as with RTF, Docbook, and OpenDocument output. Formulas + are put inside a `span` with `class="math"`, so that they may be + styled differently from the surrounding text if nee:w + ded. + +2. If the `--latexmathml` option is used, TeX math will be displayed + between $ or $$ characters and put in `` tags with class `LaTeX`. + The [LaTeXMathML] script will be used to render it as formulas. + (This trick does not work in all browsers, but it works in Firefox. + In browsers that do not support LaTeXMathML, TeX math will appear + verbatim between $ characters.) + +3. If the `--jsmath` option is used, TeX math will be put inside + `` tags (for inline math) or `
` tags (for display math) + with class `math`. The [jsMath] script will be used to render + it. + klsdjflkjdslkjflkjsdlfkjlsdkjlfkjsd + lskdfjlk + lksdjflksd + + + + + +4. If the `--mimetex` option is used, the [mimeTeX] CGI script will + be called to generate images for each TeX formula. This should + work in all browsers. The `--mimetex` option takes an optional URL + as argument. If no URL is specified, it will be assumed that the + mimeTeX CGI script is at `/cgi-bin/mimetex.cgi`. + +5. If the `--gladtex` option is used, TeX formulas will be enclosed + in `` tags in the HTML output. The resulting `htex` file may then + be processed by [gladTeX], which will produce image files for each + formula and an `html` file with links to these images. So, the + procedure is: + + + + + + pandoc -s --gladtex myfile.txt -o myfile.htex + gladtex -d myfile-images myfile.htex + # produces myfile.html and images in myfile-images + + +set command = test " test comment +something here + +Inline TeX +---------- + +Inline TeX commands will be preserved and passed unchanged to the +LaTeX and ConTeXt writers. Thus, for example, you can use LaTeX to +include BibTeX citations: + + This result was proved in \cite{jones.1967}. + +Note that in LaTeX environments, like + + \begin{tabular}{|l|l|}\hline + Age & Frequency \\ \hline + 18--25 & 15 \\ + 26--35 & 33 \\ + 36--45 & 22 \\ \hline + \end{tabular} + +the material between the begin and end tags will be interpreted as raw +LaTeX, not as markdown. + +Inline LaTeX is ignored in output formats other than Markdown, LaTeX, +and ConTeXt. + +Producing S5 with Pandoc +======================== + +Producing an [S5] *web-based* slide show with Pandoc is easy. A title +page is constructed au*tomatic*ally from the document's title block (see +above). Each section (with a level-one header) produces a single slide. +(Note that if the section is too big, the slide will not fit on the page; +S5 is not smart enough to & *produce multiple pages.) + +Here's the markdown source for a simple slide show, `eating.txt`: + +*this is a two line +test to highlight with emphasis* + + +slkdjflk;sd jfl;ks ;lfkjsad ;lkfjsdkla; jflksadjflkjsdalfkjsa;ldkj +flksadjf;lksjadflkjsda;lf kjsldkajflkjsafdlkjsdflkjsadlkfjk sad;lkjfs +;lksjdf;l lksjdflk jsdlfkjsdlk jflskdj lksdf lkjsdf Producing S5 with Pandoc +------------------------ + + + % Eating Habits + + % John Doe + % March 22, 2005 + + # In the morning + + - Eat eggs + - Drink coffee + + # In the evening + + - Eat spaghetti + - Drink wine + +To produce the slide show, simply type + + pandoc -w s5 -s eating.txt > eating.html + +and open up `eating.html` in a browser. + +Note that by default, the S5 writer produces lists that display +"all at once." If you want your lists to display incrementally +(one item at a time), use the `-i` option. If you want a +particular list to depart from the default (that is, to display +incrementally without the `-i` option and all at once with the +`-i` option), put it in a block quote: + + > - Eat spaghetti + > - Drink wine + +In this way incremental and nonincremental lists can be mixed in +a single document. + + + +Literate Haskell support +======================== + + +Note: the S5 file produced by pandoc with the `-s/--standalone` option +embeds the *javascript and CSS* required to show the slides. *Thus it +does not depend on any additional files: you can send the HTML* file to +others, and they will be able to view the slide show just by _opening +it. However, if you intend to produce several S5 slide shows_, and you +are displaying them on your own w*e_b\_si_t*e, it is better to keep the S5 +javascript and CSS files separate from the slide shows themselves, so +that they may be **cached**. The best approach in this case is to use pandoc +without the `-s` option to produce the body of the S5 document, which +can then be inserted into an HTML template that links to the javascript +and CSS files required by S5. (See *the instructions on the S5 website.) +Alternatively, you may use `-s` together with the `--template` +option to specify a custom template. + + sldkfjlsdkjfkljsd.....lksjfsaf + + + + + +You can change the style of the slides by putting customized CSS files +in `$DATADIR/s5/default`, where `$DATADIR` is the user data directory +(see `--data-dir`, above). The originals may be found in pandoc's system +data directory (generally `$CABALDIR/pandoc-VERSION/s5/default`). Pandoc +will look there for any files it does not find in the user data +directory. + + +slkdjflk sjdflk jsflsdjkl fsjdaflksadj flkjs lfkjsdlfjlksdjf +lkjsdalkfjlkjalkfjdlksdjf lksjdlf kjsdlkfjlsdkjf lksajdflkjsdlkfjsdlkj +flksdjflksdjflkjsdlfkjsdlkjf + +$23984798234$ + + + +Literate Haskell support +======================== + +If you append `+lhs` to an *appropriate xxxinput or* output format (`markdown`, +`rst`, or `latex` for input or output; `html` for output only), pandoc +will treat the document as literate Haskell source. This means that + + - In markdown input, "bird track" sections will be parsed as Haskell + code rather than block quotations. Text between `\begin{code}` + and `\end{code}` will also be treated as Haskell code. + + - In markdown output, code blocks with class `haskell` will be + rendered using bird tracks, and block quotations will be + indented one space, so they will not be treated as Haskell code. + In addition, headers will be rendered setext-style (with underlines) + rather than atx-style (with '#' characters). (This is because ghc + treats '#' characters in column 1 as introducing line numbers.) + + sdlfkj ;lsakdjlkjsd lkfjsldkj fksjd lfkjsdlkjf oskldjflkjsdlkf: + slkdjf lksdjflkjsdalkf jls;akdjflksjd ;lkfsjflksdjflkjsdlkjf lsdkjljf + lsdkjlksjdflkjsdlkf jlsdkjf lsdkjfljsdlkjf sdkj fkdsjfoiweuro + iutdfkhgskuadyrwoeiuroiusdfjhsdfkj shdfywueryoiwu + fgdsljglkjhdfkjuirweyyuroisdjflk jslkdjf lksjdfl kjsdlkfj lksdjfl kjsd + + - In restructured text input, "bird track" sections will be parsed + as Haskell code. + + - In restructured text output, code blocks with class `haskell` will + be rendered using bird tracks. + +lksdjf ;lksadjfl s;lkfj lksjfl;ksja fljsdla;kf +jlskdajf;lksjdaf;lkjsda;lkfjs;adlk jf;lksdajf l;ksadjfk;ljsdlfkjsdalkjf +lsdkjflksdjflkjsdkjfkdjkfj kd jkjfd dkjf skdjf ksdjf lksdjf wejfo iw4eufsdfk +joeiwrufljf lweiu rlrjlskdjf lksdurlijflkjdslflweiurljdfwleirlsdfulsdjf +lslkdfsjlfjlsk fjlksdj + + - In LaTeX input, text in `code` environments will be parsed as + Haskell code. + + - In LaTeX output, code blocks with class `haskell` will be rendered + inside `code` environments. + + - In HTML output, code blocks with class `haskell` will be rendered + with class `literatehaskell` and bird tracks. + +Examples: + + pandoc -f markdown+lhs -t html + +reads literate Haskell source formatted with markdown conventions and writes +ordinary HTML (without bird tracks). + + pandoc -f markdown+lhs -t html+lhs + +writes HTML with the Haskell code in bird tracks, so it can be copied +and pasted as literate Haskell source. +dkjf + diff --git a/tests/test.pl b/tests/test.pl new file mode 100644 index 0000000..71db713 --- /dev/null +++ b/tests/test.pl @@ -0,0 +1,33 @@ +#!perl -w + +# Time-stamp: <2002/04/06, 13:12:13 (EST), maverick, csvformat.pl> +# Two pass CSV file to table formatter + +$delim = $#ARGV >= 1 ? $ARGV[1] : ','; +print STDERR "Split pattern: $delim\n"; + +# first pass +open F, "<$ARGV[0]" or die; +while() +{ + chomp; + $i = 0; + map { $max[$_->[1]] = $_->[0] if $_->[0] > ($max[$_->[1]] || 0) } + (map {[length $_, $i++]} split($delim)); +} +close F; + +print STDERR 'Field width: ', join(', ', @max), "\n"; +print STDERR join(' ', map {'-' x $_} @max); + +# second pass +open F, "<$ARGV[0]" or die; +while() + { + chomp; + $i = 0; + map { printf("%-$max[$_->[1]]s ", $_->[0]) } + (map {[$_, $i++]} split($delim)); + print "\n"; +} +close F; diff --git a/tests/test.py b/tests/test.py new file mode 100644 index 0000000..5b8f258 --- /dev/null +++ b/tests/test.py @@ -0,0 +1,67 @@ +# test python (sample from offlineimap) + +class ExitNotifyThread(Thread): + """This class is designed to alert a "monitor" to the fact that a thread has + exited and to provide for the ability for it to find out why.""" + def run(self): + global exitthreads, profiledir + self.threadid = thread.get_ident() + try: + if not profiledir: # normal case + Thread.run(self) + else: + try: + import cProfile as profile + except ImportError: + import profile + prof = profile.Profile() + try: + prof = prof.runctx("Thread.run(self)", globals(), locals()) + except SystemExit: + pass + prof.dump_stats( \ + profiledir + "/" + str(self.threadid) + "_" + \ + self.getName() + ".prof") + except: + self.setExitCause('EXCEPTION') + if sys: + self.setExitException(sys.exc_info()[1]) + tb = traceback.format_exc() + self.setExitStackTrace(tb) + else: + self.setExitCause('NORMAL') + if not hasattr(self, 'exitmessage'): + self.setExitMessage(None) + + if exitthreads: + exitthreads.put(self, True) + + def setExitCause(self, cause): + self.exitcause = cause + def getExitCause(self): + """Returns the cause of the exit, one of: + 'EXCEPTION' -- the thread aborted because of an exception + 'NORMAL' -- normal termination.""" + return self.exitcause + def setExitException(self, exc): + self.exitexception = exc + def getExitException(self): + """If getExitCause() is 'EXCEPTION', holds the value from + sys.exc_info()[1] for this exception.""" + return self.exitexception + def setExitStackTrace(self, st): + self.exitstacktrace = st + def getExitStackTrace(self): + """If getExitCause() is 'EXCEPTION', returns a string representing + the stack trace for this exception.""" + return self.exitstacktrace + def setExitMessage(self, msg): + """Sets the exit message to be fetched by a subsequent call to + getExitMessage. This message may be any object or type except + None.""" + self.exitmessage = msg + def getExitMessage(self): + """For any exit cause, returns the message previously set by + a call to setExitMessage(), or None if there was no such message + set.""" + return self.exitmessage diff --git a/tests/test.rb b/tests/test.rb new file mode 100644 index 0000000..8decfba --- /dev/null +++ b/tests/test.rb @@ -0,0 +1,1436 @@ +# ruby test file ruby.rb + +def File.binread(fname) + open(fname, 'rb') {|f| + return f.read + } +end + +class ConfigTable + + include Enumerable + + def initialize(rbconfig) + @rbconfig = rbconfig + @no_harm = false + end + + def load_savefile + begin + File.foreach(savefile()) do |line| + k, v = *line.split(/=/, 2) + self[k] = v.strip + end + rescue Errno::ENOENT + setup_rb_error $!.message + "\n#{File.basename($0)} config first" + end + end + + if c['rubylibdir'] + # V > 1.6.3 + libruby = "#{c['prefix']}/lib/ruby" + librubyver = c['rubylibdir'] + librubyverarch = c['archdir'] + siteruby = c['sitedir'] + siterubyver = c['sitelibdir'] + siterubyverarch = c['sitearchdir'] + end + parameterize = lambda {|path| + path.sub(/\A#{Regexp.quote(c['prefix'])}/, '$prefix') + } + + if arg = c['configure_args'].split.detect {|arg| /--with-make-prog=/ =~ arg } + makeprog = arg.sub(/'/, '').split(/=/, 2)[1] + else + makeprog = 'make' + end + + [ + ExecItem.new('installdirs', 'std/site/home', + 'std: install under libruby; site: install under site_ruby; home: install under $HOME')\ + {|val, table| + case val + when 'std' + table['rbdir'] = '$librubyver' + table['sodir'] = '$librubyverarch' + when 'site' + table['rbdir'] = '$siterubyver' + table['sodir'] = '$siterubyverarch' + when 'home' + setup_rb_error '$HOME was not set' unless ENV['HOME'] + table['prefix'] = ENV['HOME'] + table['rbdir'] = '$libdir/ruby' + table['sodir'] = '$libdir/ruby' + end + }, + PathItem.new('prefix', 'path', c['prefix'], + 'path prefix of target environment'), + PathItem.new('bindir', 'path', parameterize.call(c['bindir']), + 'the directory for commands'), + PathItem.new('libdir', 'path', parameterize.call(c['libdir']), + 'the directory for libraries'), + PathItem.new('datadir', 'path', parameterize.call(c['datadir']), + 'the directory for shared data'), + PathItem.new('mandir', 'path', parameterize.call(c['mandir']), + 'the directory for man pages'), + PathItem.new('sysconfdir', 'path', parameterize.call(c['sysconfdir']), + 'the directory for system configuration files'), + PathItem.new('localstatedir', 'path', parameterize.call(c['localstatedir']), + 'the directory for local state data'), + PathItem.new('libruby', 'path', libruby, + 'the directory for ruby libraries'), + PathItem.new('librubyver', 'path', librubyver, + 'the directory for standard ruby libraries'), + PathItem.new('librubyverarch', 'path', librubyverarch, + 'the directory for standard ruby extensions'), + PathItem.new('siteruby', 'path', siteruby, + 'the directory for version-independent aux ruby libraries'), + PathItem.new('siterubyver', 'path', siterubyver, + 'the directory for aux ruby libraries'), + PathItem.new('siterubyverarch', 'path', siterubyverarch, + 'the directory for aux ruby binaries'), + PathItem.new('rbdir', 'path', '$siterubyver', + 'the directory for ruby scripts'), + PathItem.new('sodir', 'path', '$siterubyverarch', + 'the directory for ruby extentions'), + PathItem.new('rubypath', 'path', rubypath, + 'the path to set to #! line'), + ProgramItem.new('rubyprog', 'name', rubypath, + 'the ruby program using for installation'), + ProgramItem.new('makeprog', 'name', makeprog, + 'the make program to compile ruby extentions'), + SelectItem.new('shebang', 'all/ruby/never', 'ruby', + 'shebang line (#!) editing mode'), + BoolItem.new('without-ext', 'yes/no', 'no', + 'does not compile/install ruby extentions') + ] + end + private :standard_entries + + def load_multipackage_entries + multipackage_entries().each do |ent| + add ent + end + end + + def multipackage_entries + [ + PackageSelectionItem.new('with', 'name,name...', '', 'ALL', + 'package names that you want to install'), + PackageSelectionItem.new('without', 'name,name...', '', 'NONE', + 'package names that you do not want to install') + ] + end + private :multipackage_entries + + ALIASES = { + 'std-ruby' => 'librubyver', + 'stdruby' => 'librubyver', + 'rubylibdir' => 'librubyver', + 'archdir' => 'librubyverarch', + 'site-ruby-common' => 'siteruby', # For backward compatibility + 'site-ruby' => 'siterubyver', # For backward compatibility + 'bin-dir' => 'bindir', + 'bin-dir' => 'bindir', + 'rb-dir' => 'rbdir', + 'so-dir' => 'sodir', + 'data-dir' => 'datadir', + 'ruby-path' => 'rubypath', + 'ruby-prog' => 'rubyprog', + 'ruby' => 'rubyprog', + 'make-prog' => 'makeprog', + 'make' => 'makeprog' + } + + def fixup + ALIASES.each do |ali, name| + @table[ali] = @table[name] + end + @items.freeze + @table.freeze + @options_re = /\A--(#{@table.keys.join('|')})(?:=(.*))?\z/ + end + + def parse_opt(opt) + m = @options_re.match(opt) or setup_rb_error "config: unknown option #{opt}" + m.to_a[1,2] + end + + def dllext + @rbconfig['DLEXT'] + end + + def value_config?(name) + lookup(name).value? + end + + class Item + def initialize(name, template, default, desc) + @name = name.freeze + @template = template + @value = default + @default = default + @description = desc + end + + attr_reader :name + attr_reader :description + + attr_accessor :default + alias help_default default + + def help_opt + "--#{@name}=#{@template}" + end + + def value? + true + end + + def value + @value + end + + def resolve(table) + @value.gsub(%r<\$([^/]+)>) { table[$1] } + end + + def set(val) + @value = check(val) + end + + private + + def check(val) + setup_rb_error "config: --#{name} requires argument" unless val + val + end + end + + class BoolItem < Item + def config_type + 'bool' + end + + def help_opt + "--#{@name}" + end + + private + + def check(val) + return 'yes' unless val + case val + when /\Ay(es)?\z/i, /\At(rue)?\z/i then 'yes' + when /\An(o)?\z/i, /\Af(alse)\z/i then 'no' + else + setup_rb_error "config: --#{@name} accepts only yes/no for argument" + end + end + end + + class PathItem < Item + def config_type + 'path' + end + + private + + def check(path) + setup_rb_error "config: --#{@name} requires argument" unless path + path[0,1] == '$' ? path : File.expand_path(path) + end + end + + class ProgramItem < Item + def config_type + 'program' + end + end + + class SelectItem < Item + def initialize(name, selection, default, desc) + super + @ok = selection.split('/') + end + + def config_type + 'select' + end + + private + + def check(val) + unless @ok.include?(val.strip) + setup_rb_error "config: use --#{@name}=#{@template} (#{val})" + end + val.strip + end + end + + class ExecItem < Item + def initialize(name, selection, desc, &block) + super name, selection, nil, desc + @ok = selection.split('/') + @action = block + end + + def config_type + 'exec' + end + + def value? + false + end + + def resolve(table) + setup_rb_error "$#{name()} wrongly used as option value" + end + + undef set + + def evaluate(val, table) + v = val.strip.downcase + unless @ok.include?(v) + setup_rb_error "invalid option --#{@name}=#{val} (use #{@template})" + end + @action.call v, table + end + end + + class PackageSelectionItem < Item + def initialize(name, template, default, help_default, desc) + super name, template, default, desc + @help_default = help_default + end + + attr_reader :help_default + + def config_type + 'package' + end + + private + + def check(val) + unless File.dir?("packages/#{val}") + setup_rb_error "config: no such package: #{val}" + end + val + end + end + + class MetaConfigEnvironment + def initialize(config, installer) + @config = config + @installer = installer + end + + def config_names + @config.names + end + + def config?(name) + @config.key?(name) + end + + def bool_config?(name) + @config.lookup(name).config_type == 'bool' + end + + def path_config?(name) + @config.lookup(name).config_type == 'path' + end + + def value_config?(name) + @config.lookup(name).config_type != 'exec' + end + + def add_config(item) + @config.add item + end + + def add_bool_config(name, default, desc) + @config.add BoolItem.new(name, 'yes/no', default ? 'yes' : 'no', desc) + end + + def add_path_config(name, default, desc) + @config.add PathItem.new(name, 'path', default, desc) + end + + def set_config_default(name, default) + @config.lookup(name).default = default + end + + def remove_config(name) + @config.remove(name) + end + + # For only multipackage + def packages + raise '[setup.rb fatal] multi-package metaconfig API packages() called for single-package; contact application package vendor' unless @installer + @installer.packages + end + + # For only multipackage + def declare_packages(list) + raise '[setup.rb fatal] multi-package metaconfig API declare_packages() called for single-package; contact application package vendor' unless @installer + @installer.packages = list + end + end + +end # class ConfigTable + + +# This module requires: #verbose?, #no_harm? +module FileOperations + + def mkdir_p(dirname, prefix = nil) + dirname = prefix + File.expand_path(dirname) if prefix + $stderr.puts "mkdir -p #{dirname}" if verbose? + return if no_harm? + + # Does not check '/', it's too abnormal. + dirs = File.expand_path(dirname).split(%r<(?=/)>) + if /\A[a-z]:\z/i =~ dirs[0] + disk = dirs.shift + dirs[0] = disk + dirs[0] + end + dirs.each_index do |idx| + path = dirs[0..idx].join('') + Dir.mkdir path unless File.dir?(path) + end + end + + def rm_f(path) + $stderr.puts "rm -f #{path}" if verbose? + return if no_harm? + force_remove_file path + end + + def rm_rf(path) + $stderr.puts "rm -rf #{path}" if verbose? + return if no_harm? + remove_tree path + end + + def remove_tree(path) + if File.symlink?(path) + remove_file path + elsif File.dir?(path) + remove_tree0 path + else + force_remove_file path + end + end + + def remove_tree0(path) + Dir.foreach(path) do |ent| + next if ent == '.' + next if ent == '..' + entpath = "#{path}/#{ent}" + if File.symlink?(entpath) + remove_file entpath + elsif File.dir?(entpath) + remove_tree0 entpath + else + force_remove_file entpath + end + end + begin + Dir.rmdir path + rescue Errno::ENOTEMPTY + # directory may not be empty + end + end + + def move_file(src, dest) + force_remove_file dest + begin + File.rename src, dest + rescue + File.open(dest, 'wb') {|f| + f.write File.binread(src) + } + File.chmod File.stat(src).mode, dest + File.unlink src + end + end + + def force_remove_file(path) + begin + remove_file path + rescue + end + end + + def remove_file(path) + File.chmod 0777, path + File.unlink path + end + + def install(from, dest, mode, prefix = nil) + $stderr.puts "install #{from} #{dest}" if verbose? + return if no_harm? + + realdest = prefix ? prefix + File.expand_path(dest) : dest + realdest = File.join(realdest, File.basename(from)) if File.dir?(realdest) + str = File.binread(from) + if diff?(str, realdest) + verbose_off { + rm_f realdest if File.exist?(realdest) + } + File.open(realdest, 'wb') {|f| + f.write str + } + File.chmod mode, realdest + + File.open("#{objdir_root()}/InstalledFiles", 'a') {|f| + if prefix + f.puts realdest.sub(prefix, '') + else + f.puts realdest + end + } + end + end + + def diff?(new_content, path) + return true unless File.exist?(path) + new_content != File.binread(path) + end + + def command(*args) + $stderr.puts args.join(' ') if verbose? + system(*args) or raise RuntimeError, + "system(#{args.map{|a| a.inspect }.join(' ')}) failed" + end + + def ruby(*args) + command config('rubyprog'), *args + end + + def make(task = nil) + command(*[config('makeprog'), task].compact) + end + + def extdir?(dir) + File.exist?("#{dir}/MANIFEST") or File.exist?("#{dir}/extconf.rb") + end + + def files_of(dir) + Dir.open(dir) {|d| + return d.select {|ent| File.file?("#{dir}/#{ent}") } + } + end + + DIR_REJECT = %w( . .. CVS SCCS RCS CVS.adm .svn ) + + def directories_of(dir) + Dir.open(dir) {|d| + return d.select {|ent| File.dir?("#{dir}/#{ent}") } - DIR_REJECT + } + end + +end + + +# This module requires: #srcdir_root, #objdir_root, #relpath +module HookScriptAPI + + def get_config(key) + @config[key] + end + + alias config get_config + + # obsolete: use metaconfig to change configuration + def set_config(key, val) + @config[key] = val + end + + # + # srcdir/objdir (works only in the package directory) + # + + def curr_srcdir + "#{srcdir_root()}/#{relpath()}" + end + + def curr_objdir + "#{objdir_root()}/#{relpath()}" + end + + def srcfile(path) + "#{curr_srcdir()}/#{path}" + end + + def srcexist?(path) + File.exist?(srcfile(path)) + end + + def srcdirectory?(path) + File.dir?(srcfile(path)) + end + + def srcfile?(path) + File.file?(srcfile(path)) + end + + def srcentries(path = '.') + Dir.open("#{curr_srcdir()}/#{path}") {|d| + return d.to_a - %w(. ..) + } + end + + def srcfiles(path = '.') + srcentries(path).select {|fname| + File.file?(File.join(curr_srcdir(), path, fname)) + } + end + + def srcdirectories(path = '.') + srcentries(path).select {|fname| + File.dir?(File.join(curr_srcdir(), path, fname)) + } + end + +end + + +class ToplevelInstaller + + Version = '3.4.1' + Copyright = 'Copyright (c) 2000-2005 Minero Aoki' + + TASKS = [ + [ 'all', 'do config, setup, then install' ], + [ 'config', 'saves your configurations' ], + [ 'show', 'shows current configuration' ], + [ 'setup', 'compiles ruby extentions and others' ], + [ 'install', 'installs files' ], + [ 'test', 'run all tests in test/' ], + [ 'clean', "does `make clean' for each extention" ], + [ 'distclean',"does `make distclean' for each extention" ] + ] + + def ToplevelInstaller.invoke + config = ConfigTable.new(load_rbconfig()) + config.load_standard_entries + config.load_multipackage_entries if multipackage? + config.fixup + klass = (multipackage?() ? ToplevelInstallerMulti : ToplevelInstaller) + klass.new(File.dirname($0), config).invoke + end + + def ToplevelInstaller.multipackage? + File.dir?(File.dirname($0) + '/packages') + end + + def ToplevelInstaller.load_rbconfig + if arg = ARGV.detect {|arg| /\A--rbconfig=/ =~ arg } + ARGV.delete(arg) + load File.expand_path(arg.split(/=/, 2)[1]) + $".push 'rbconfig.rb' + else + require 'rbconfig' + end + ::Config::CONFIG + end + + def initialize(ardir_root, config) + @ardir = File.expand_path(ardir_root) + @config = config + # cache + @valid_task_re = nil + end + + def config(key) + @config[key] + end + + def inspect + "#<#{self.class} #{__id__()}>" + end + + def invoke + run_metaconfigs + case task = parsearg_global() + when nil, 'all' + parsearg_config + init_installers + exec_config + exec_setup + exec_install + else + case task + when 'config', 'test' + ; + when 'clean', 'distclean' + @config.load_savefile if File.exist?(@config.savefile) + else + @config.load_savefile + end + __send__ "parsearg_#{task}" + init_installers + __send__ "exec_#{task}" + end + end + + def run_metaconfigs + @config.load_script "#{@ardir}/metaconfig" + end + + def init_installers + @installer = Installer.new(@config, @ardir, File.expand_path('.')) + end + + # + # Hook Script API bases + # + + def srcdir_root + @ardir + end + + def objdir_root + '.' + end + + def relpath + '.' + end + + # + # Option Parsing + # + + def parsearg_global + while arg = ARGV.shift + case arg + when /\A\w+\z/ + setup_rb_error "invalid task: #{arg}" unless valid_task?(arg) + return arg + when '-q', '--quiet' + @config.verbose = false + when '--verbose' + @config.verbose = true + when '--help' + print_usage $stdout + exit 0 + when '--version' + puts "#{File.basename($0)} version #{Version}" + exit 0 + when '--copyright' + puts Copyright + exit 0 + else + setup_rb_error "unknown global option '#{arg}'" + end + end + nil + end + + def valid_task?(t) + valid_task_re() =~ t + end + + def valid_task_re + @valid_task_re ||= /\A(?:#{TASKS.map {|task,desc| task }.join('|')})\z/ + end + + def parsearg_no_options + unless ARGV.empty? + task = caller(0).first.slice(%r<`parsearg_(\w+)'>, 1) + setup_rb_error "#{task}: unknown options: #{ARGV.join(' ')}" + end + end + + alias parsearg_show parsearg_no_options + alias parsearg_setup parsearg_no_options + alias parsearg_test parsearg_no_options + alias parsearg_clean parsearg_no_options + alias parsearg_distclean parsearg_no_options + + def parsearg_config + evalopt = [] + set = [] + @config.config_opt = [] + while i = ARGV.shift + if /\A--?\z/ =~ i + @config.config_opt = ARGV.dup + break + end + name, value = *@config.parse_opt(i) + if @config.value_config?(name) + @config[name] = value + else + evalopt.push [name, value] + end + set.push name + end + evalopt.each do |name, value| + @config.lookup(name).evaluate value, @config + end + # Check if configuration is valid + set.each do |n| + @config[n] if @config.value_config?(n) + end + end + + def parsearg_install + @config.no_harm = false + @config.install_prefix = '' + while a = ARGV.shift + case a + when '--no-harm' + @config.no_harm = true + when /\A--prefix=/ + path = a.split(/=/, 2)[1] + path = File.expand_path(path) unless path[0,1] == '/' + @config.install_prefix = path + else + setup_rb_error "install: unknown option #{a}" + end + end + end + + def print_usage(out) + out.puts 'Typical Installation Procedure:' + out.puts " $ ruby #{File.basename $0} config" + out.puts " $ ruby #{File.basename $0} setup" + out.puts " # ruby #{File.basename $0} install (may require root privilege)" + out.puts + out.puts 'Detailed Usage:' + out.puts " ruby #{File.basename $0} " + out.puts " ruby #{File.basename $0} [] []" + + fmt = " %-24s %s\n" + out.puts + out.puts 'Global options:' + out.printf fmt, '-q,--quiet', 'suppress message outputs' + out.printf fmt, ' --verbose', 'output messages verbosely' + out.printf fmt, ' --help', 'print this message' + out.printf fmt, ' --version', 'print version and quit' + out.printf fmt, ' --copyright', 'print copyright and quit' + out.puts + out.puts 'Tasks:' + TASKS.each do |name, desc| + out.printf fmt, name, desc + end + + fmt = " %-24s %s [%s]\n" + out.puts + out.puts 'Options for CONFIG or ALL:' + @config.each do |item| + out.printf fmt, item.help_opt, item.description, item.help_default + end + out.printf fmt, '--rbconfig=path', 'rbconfig.rb to load',"running ruby's" + out.puts + out.puts 'Options for INSTALL:' + out.printf fmt, '--no-harm', 'only display what to do if given', 'off' + out.printf fmt, '--prefix=path', 'install path prefix', '' + out.puts + end + + # + # Task Handlers + # + + def exec_config + @installer.exec_config + @config.save # must be final + end + + def exec_setup + @installer.exec_setup + end + + def exec_install + @installer.exec_install + end + + def exec_test + @installer.exec_test + end + + def exec_show + @config.each do |i| + printf "%-20s %s\n", i.name, i.value if i.value? + end + end + + def exec_clean + @installer.exec_clean + end + + def exec_distclean + @installer.exec_distclean + end + +end # class ToplevelInstaller + + +class ToplevelInstallerMulti < ToplevelInstaller + + include FileOperations + + def initialize(ardir_root, config) + super + @packages = directories_of("#{@ardir}/packages") + raise 'no package exists' if @packages.empty? + @root_installer = Installer.new(@config, @ardir, File.expand_path('.')) + end + + def run_metaconfigs + @config.load_script "#{@ardir}/metaconfig", self + @packages.each do |name| + @config.load_script "#{@ardir}/packages/#{name}/metaconfig" + end + end + + attr_reader :packages + + def packages=(list) + raise 'package list is empty' if list.empty? + list.each do |name| + raise "directory packages/#{name} does not exist"\ + unless File.dir?("#{@ardir}/packages/#{name}") + end + @packages = list + end + + def init_installers + @installers = {} + @packages.each do |pack| + @installers[pack] = Installer.new(@config, + "#{@ardir}/packages/#{pack}", + "packages/#{pack}") + end + with = extract_selection(config('with')) + without = extract_selection(config('without')) + @selected = @installers.keys.select {|name| + (with.empty? or with.include?(name)) \ + and not without.include?(name) + } + end + + def extract_selection(list) + a = list.split(/,/) + a.each do |name| + setup_rb_error "no such package: #{name}" unless @installers.key?(name) + end + a + end + + def print_usage(f) + super + f.puts 'Inluded packages:' + f.puts ' ' + @packages.sort.join(' ') + f.puts + end + + # + # Task Handlers + # + + def exec_config + run_hook 'pre-config' + each_selected_installers {|inst| inst.exec_config } + run_hook 'post-config' + @config.save # must be final + end + + def exec_setup + run_hook 'pre-setup' + each_selected_installers {|inst| inst.exec_setup } + run_hook 'post-setup' + end + + def exec_install + run_hook 'pre-install' + each_selected_installers {|inst| inst.exec_install } + run_hook 'post-install' + end + + def exec_test + run_hook 'pre-test' + each_selected_installers {|inst| inst.exec_test } + run_hook 'post-test' + end + + def exec_clean + rm_f @config.savefile + run_hook 'pre-clean' + each_selected_installers {|inst| inst.exec_clean } + run_hook 'post-clean' + end + + def exec_distclean + rm_f @config.savefile + run_hook 'pre-distclean' + each_selected_installers {|inst| inst.exec_distclean } + run_hook 'post-distclean' + end + + # + # lib + # + + def each_selected_installers + Dir.mkdir 'packages' unless File.dir?('packages') + @selected.each do |pack| + $stderr.puts "Processing the package `#{pack}' ..." if verbose? + Dir.mkdir "packages/#{pack}" unless File.dir?("packages/#{pack}") + Dir.chdir "packages/#{pack}" + yield @installers[pack] + Dir.chdir '../..' + end + end + + def run_hook(id) + @root_installer.run_hook id + end + + # module FileOperations requires this + def verbose? + @config.verbose? + end + + # module FileOperations requires this + def no_harm? + @config.no_harm? + end + +end # class ToplevelInstallerMulti + + +class Installer + + FILETYPES = %w( bin lib ext data conf man ) + + include FileOperations + include HookScriptAPI + + def initialize(config, srcroot, objroot) + @config = config + @srcdir = File.expand_path(srcroot) + @objdir = File.expand_path(objroot) + @currdir = '.' + end + + def inspect + "#<#{self.class} #{File.basename(@srcdir)}>" + end + + def noop(rel) + end + + # + # Hook Script API base methods + # + + def srcdir_root + @srcdir + end + + def objdir_root + @objdir + end + + def relpath + @currdir + end + + # + # Config Access + # + + # module FileOperations requires this + def verbose? + @config.verbose? + end + + # module FileOperations requires this + def no_harm? + @config.no_harm? + end + + def verbose_off + begin + save, @config.verbose = @config.verbose?, false + yield + ensure + @config.verbose = save + end + end + + # + # TASK config + # + + def exec_config + exec_task_traverse 'config' + end + + alias config_dir_bin noop + alias config_dir_lib noop + + def config_dir_ext(rel) + extconf if extdir?(curr_srcdir()) + end + + alias config_dir_data noop + alias config_dir_conf noop + alias config_dir_man noop + + def extconf + ruby "#{curr_srcdir()}/extconf.rb", *@config.config_opt + end + + # + # TASK setup + # + + def exec_setup + exec_task_traverse 'setup' + end + + def setup_dir_bin(rel) + files_of(curr_srcdir()).each do |fname| + update_shebang_line "#{curr_srcdir()}/#{fname}" + end + end + + alias setup_dir_lib noop + + def setup_dir_ext(rel) + make if extdir?(curr_srcdir()) + end + + alias setup_dir_data noop + alias setup_dir_conf noop + alias setup_dir_man noop + + def update_shebang_line(path) + return if no_harm? + return if config('shebang') == 'never' + old = Shebang.load(path) + if old + $stderr.puts "warning: #{path}: Shebang line includes too many args. It is not portable and your program may not work." if old.args.size > 1 + new = new_shebang(old) + return if new.to_s == old.to_s + else + return unless config('shebang') == 'all' + new = Shebang.new(config('rubypath')) + end + $stderr.puts "updating shebang: #{File.basename(path)}" if verbose? + open_atomic_writer(path) {|output| + File.open(path, 'rb') {|f| + f.gets if old # discard + output.puts new.to_s + output.print f.read + } + } + end + + def new_shebang(old) + if /\Aruby/ =~ File.basename(old.cmd) + Shebang.new(config('rubypath'), old.args) + elsif File.basename(old.cmd) == 'env' and old.args.first == 'ruby' + Shebang.new(config('rubypath'), old.args[1..-1]) + else + return old unless config('shebang') == 'all' + Shebang.new(config('rubypath')) + end + end + + def open_atomic_writer(path, &block) + tmpfile = File.basename(path) + '.tmp' + begin + File.open(tmpfile, 'wb', &block) + File.rename tmpfile, File.basename(path) + ensure + File.unlink tmpfile if File.exist?(tmpfile) + end + end + + class Shebang + def Shebang.load(path) + line = nil + File.open(path) {|f| + line = f.gets + } + return nil unless /\A#!/ =~ line + parse(line) + end + + def Shebang.parse(line) + cmd, *args = *line.strip.sub(/\A\#!/, '').split(' ') + new(cmd, args) + end + + def initialize(cmd, args = []) + @cmd = cmd + @args = args + end + + attr_reader :cmd + attr_reader :args + + def to_s + "#! #{@cmd}" + (@args.empty? ? '' : " #{@args.join(' ')}") + end + end + + # + # TASK install + # + + def exec_install + rm_f 'InstalledFiles' + exec_task_traverse 'install' + end + + def install_dir_bin(rel) + install_files targetfiles(), "#{config('bindir')}/#{rel}", 0755 + end + + def install_dir_lib(rel) + install_files libfiles(), "#{config('rbdir')}/#{rel}", 0644 + end + + def install_dir_ext(rel) + return unless extdir?(curr_srcdir()) + install_files rubyextentions('.'), + "#{config('sodir')}/#{File.dirname(rel)}", + 0555 + end + + def install_dir_data(rel) + install_files targetfiles(), "#{config('datadir')}/#{rel}", 0644 + end + + def install_dir_conf(rel) + # FIXME: should not remove current config files + # (rename previous file to .old/.org) + install_files targetfiles(), "#{config('sysconfdir')}/#{rel}", 0644 + end + + def install_dir_man(rel) + install_files targetfiles(), "#{config('mandir')}/#{rel}", 0644 + end + + def install_files(list, dest, mode) + mkdir_p dest, @config.install_prefix + list.each do |fname| + install fname, dest, mode, @config.install_prefix + end + end + + def libfiles + glob_reject(%w(*.y *.output), targetfiles()) + end + + def rubyextentions(dir) + ents = glob_select("*.#{@config.dllext}", targetfiles()) + if ents.empty? + setup_rb_error "no ruby extention exists: 'ruby #{$0} setup' first" + end + ents + end + + def targetfiles + mapdir(existfiles() - hookfiles()) + end + + def mapdir(ents) + ents.map {|ent| + if File.exist?(ent) + then ent # objdir + else "#{curr_srcdir()}/#{ent}" # srcdir + end + } + end + + # picked up many entries from cvs-1.11.1/src/ignore.c + JUNK_FILES = %w( + core RCSLOG tags TAGS .make.state + .nse_depinfo #* .#* cvslog.* ,* .del-* *.olb + *~ *.old *.bak *.BAK *.orig *.rej _$* *$ + + *.org *.in .* + ) + + def existfiles + glob_reject(JUNK_FILES, (files_of(curr_srcdir()) | files_of('.'))) + end + + def hookfiles + %w( pre-%s post-%s pre-%s.rb post-%s.rb ).map {|fmt| + %w( config setup install clean ).map {|t| sprintf(fmt, t) } + }.flatten + end + + def glob_select(pat, ents) + re = globs2re([pat]) + ents.select {|ent| re =~ ent } + end + + def glob_reject(pats, ents) + re = globs2re(pats) + ents.reject {|ent| re =~ ent } + end + + GLOB2REGEX = { + '.' => '\.', + '$' => '\$', + '#' => '\#', + '*' => '.*' + } + + def globs2re(pats) + /\A(?:#{ + pats.map {|pat| pat.gsub(/[\.\$\#\*]/) {|ch| GLOB2REGEX[ch] } }.join('|') + })\z/ + end + + # + # TASK test + # + + TESTDIR = 'test' + + def exec_test + unless File.directory?('test') + $stderr.puts 'no test in this package' if verbose? + return + end + $stderr.puts 'Running tests...' if verbose? + begin + require 'test/unit' + rescue LoadError + setup_rb_error 'test/unit cannot loaded. You need Ruby 1.8 or later to invoke this task.' + end + runner = Test::Unit::AutoRunner.new(true) + runner.to_run << TESTDIR + runner.run + end + + # + # TASK clean + # + + def exec_clean + exec_task_traverse 'clean' + rm_f @config.savefile + rm_f 'InstalledFiles' + end + + alias clean_dir_bin noop + alias clean_dir_lib noop + alias clean_dir_data noop + alias clean_dir_conf noop + alias clean_dir_man noop + + def clean_dir_ext(rel) + return unless extdir?(curr_srcdir()) + make 'clean' if File.file?('Makefile') + end + + # + # TASK distclean + # + + def exec_distclean + exec_task_traverse 'distclean' + rm_f @config.savefile + rm_f 'InstalledFiles' + end + + alias distclean_dir_bin noop + alias distclean_dir_lib noop + + def distclean_dir_ext(rel) + return unless extdir?(curr_srcdir()) + make 'distclean' if File.file?('Makefile') + end + + alias distclean_dir_data noop + alias distclean_dir_conf noop + alias distclean_dir_man noop + + # + # Traversing + # + + def exec_task_traverse(task) + run_hook "pre-#{task}" + FILETYPES.each do |type| + if type == 'ext' and config('without-ext') == 'yes' + $stderr.puts 'skipping ext/* by user option' if verbose? + next + end + traverse task, type, "#{task}_dir_#{type}" + end + run_hook "post-#{task}" + end + + def traverse(task, rel, mid) + dive_into(rel) { + run_hook "pre-#{task}" + __send__ mid, rel.sub(%r[\A.*?(?:/|\z)], '') + directories_of(curr_srcdir()).each do |d| + traverse task, "#{rel}/#{d}", mid + end + run_hook "post-#{task}" + } + end + + def dive_into(rel) + return unless File.dir?("#{@srcdir}/#{rel}") + + dir = File.basename(rel) + Dir.mkdir dir unless File.dir?(dir) + prevdir = Dir.pwd + Dir.chdir dir + $stderr.puts '---> ' + rel if verbose? + @currdir = rel + yield + Dir.chdir prevdir + $stderr.puts '<--- ' + rel if verbose? + @currdir = File.dirname(rel) + end + + def run_hook(id) + path = [ "#{curr_srcdir()}/#{id}", + "#{curr_srcdir()}/#{id}.rb" ].detect {|cand| File.file?(cand) } + return unless path + begin + instance_eval File.read(path), path, 1 + rescue + raise if $DEBUG + setup_rb_error "hook #{path} failed:\n" + $!.message + end + end + +end # class Installer + + +class SetupError < StandardError; end + +def setup_rb_error(msg) + raise SetupError, msg +end + +if $0 == __FILE__ + begin + ToplevelInstaller.invoke + rescue SetupError + raise if $DEBUG + $stderr.puts $!.message + $stderr.puts "Try 'ruby #{$0} --help' for detailed usage." + exit 1 + end +end + diff --git a/tests/test.tex b/tests/test.tex new file mode 100644 index 0000000..37a19e8 --- /dev/null +++ b/tests/test.tex @@ -0,0 +1,24 @@ +% Time-stamp: <2004/04/06, 16:46:43 (EST), maverick, test.tex> +\subsection{Strict diagonal-dominance} +Suppose we are given a matrix $A=L+D$, where $L$ is a Laplacian and +$D$ is a nonnegative diagonal matrix, for which we seek to construct a +preconditioner. + +We may construct a Support Tree Preconditioner, $B = +\begin{pmatrix} T & U\\U\TT & W\end{pmatrix}$ for $L$ and to use $B' +=\begin{pmatrix} T & U \\U\TT & W+D\end{pmatrix}$ as a preconditioner +for $A$. If we let $Q = W - U\TT T\IV U$, by Lemma~\ref{lem:stcg} it +suffices to bound $\sigma(A/Q+D)$ and $\sigma(Q+D/A)$. + +\begin{proposition}\label{prop:XZ-YZ} +If $X$, $Y$, and $Z$ are spsd matrices of the same size then +$\sigma(X+Z/Y+Z) \leq \max\{\sigma(X/Y),\, 1\}$. +\end{proposition} + +\Proof We have $\sigma(X+Z/Y+Z) = +\min\{\tau \mid \forall\vv{x},\, \tau\cdot \vv{x}\TT (Y+Z)\vv{x} \geq + \vv{x}\TT(X+Z)\vv{x}\} = +\min\{\tau \mid \forall\vv{x},\, (\tau-1)\cdot \vv{x}\TT Z\vv{x} + + \tau \cdot\vv{x}\TT Y\vv{x} \geq \vv{x}\TT X\vv{x}\} \leq +\max\{1,\,\sigma(X/Y)\}$.\QED +