Permalink
Browse files

Added messages, changelog.

  • Loading branch information...
1 parent a4b86a4 commit 2b7cd6fca184282eab380356d939bda2585af756 Daniel Shannon committed Mar 26, 2013
Showing with 61 additions and 0 deletions.
  1. +7 −0 Main.sublime-menu
  2. +11 −0 changelog.mdown
  3. +4 −0 messages.json
  4. +25 −0 messages/2.0.0.txt
  5. +14 −0 messages/install.txt
View
@@ -23,6 +23,13 @@
"caption": "README"
},
{
+ "command": "open_file", "args":
+ {
+ "file": "${packages}/Pandown/changelog.mdown"
+ },
+ "caption": "changelog"
+ },
+ {
"caption": "-"
},
{
View
@@ -0,0 +1,11 @@
+# Pandown for Sublime Text 2 and 3
+
+## Notes
+As of March 2013, Pandown is _fully compatible with Sublime Text 2 and Sublime Text 3_. "Pandown3" was ported back to ST2, bringing benefits to stability and performance, compatibility with Pandoc versions higher than 1.10, and dual-compatibility, in one Github repository and one project, with the two most recent versions of Sublime. "Pandown3" will no longer be supported; any changes and improvements made will be to the single repository available at <https://github.com/phyllisstein/Pandown>. The stable version is being assigned the number 2.0, and was completed on 25 March 2013.
+
+# Changes and Improvements---03/26/13
+* Dual compatibility with ST2 and ST3.
+* The `pandoc-config.json` file now uses a slightly different syntax. In order to accommodate Pandoc's new Markdown-extensions feature, the configuration files were split into two dictionaries, `"markdown_extensions"` and `"command_arguments"`. See the default configuration file at `{Packages}/default-pandoc-config.json`, or the settings files, for a guide to what now belongs where. _Users **must** update their `pandoc-config.json` and `{Packages}/User/Pandown.sublime-settings` files_.
+* Pandown now supports the CriticMarkup syntax, showcased at <http://criticmarkup.com>. Though disabled by default, it can be enabled by setting the `"preprocess_critic"` option to `true` in your `.sublime-settings` file and passing the variable `"critic": true` in your `pandoc-config.json` file. If you're not using the included "Github" template, you'll need to copy everything from `$if(critic)$` to the next `$endif$` out of that template and paste it into your own.
+* Pandown now builds considerably faster, and its code has been somewhat sanitized.
+* Brett's "Github" template has been further modified to increase compatibility with Pandoc. The aesthetics are all still his work, but some of the behind-the-scenes stuff has changed to improve---e.g.---code blocks with line numbers and some other small additional features.
View
@@ -0,0 +1,4 @@
+{
+ "install": "messages/install.txt",
+ "2.0.0": "messages/2.0.0.txt"
+}
View
@@ -0,0 +1,25 @@
+ PANDOWN FOR SUBLIME TEXT 2 & 3
+ by Daniel Shannon
+ ======================================
+ Please note that in this version
+ of Pandown, the syntax for the
+ configuration files has changed.
+ To see what the new format should
+ look like, check the settings
+ files or take a look at:
+{Packages}/Pandown/default-pandoc-config.json
+
+ The crux of the change is that the
+ settings have been split into two
+ dictionaries, one for Markdown
+ extensions and one for command-line
+ arguments, and the command-line
+ arguments are named with dashes
+ rather than underscores. This change
+ roughly halves the amount of code
+ in Pandown, and speeds it up
+ considerably.
+
+ Please feel free to write Daniel
+ with any questions or problems,
+ at d@daniel.sh.
View
@@ -0,0 +1,14 @@
+ PANDOWN FOR SUBLIME TEXT 2 & 3
+ by Daniel Shannon
+ ======================================
+ Thanks for installing Pandown!
+ If you haven't yet set up Pandoc,
+ at at least version 1.10, now
+ would be a good time to do so.
+ Grab a copy at:
+ http://johnmacfarlane.net/pandoc/
+
+ And be sure to check out the
+ README.mdown file and the change
+ log for information about this
+ version of Pandown.

0 comments on commit 2b7cd6f

Please sign in to comment.