Well that didn't work

add some folders (#3)

* add soft breaks to New Line logic

In our application we sometimes get substation alpha authors that put n at
the end of each line in the dialogue. Usually we would expect that they would
use N instead.  So we will add that to the conditions checked by the parse-
newLine function so that this doesn'
t cause a breaking behavior of actually printing out the literal n at
the end of each line of dialogue.

* bump version minor number

* trying to add some more files and see if browserify starts working

Trying to get the darn Browserify to work

add some folders (#3)

* add soft breaks to New Line logic

In our application we sometimes get substation alpha authors that put n at
the end of each line in the dialogue. Usually we would expect that they would
use N instead.  So we will add that to the conditions checked by the parse-
newLine function so that this doesn'
t cause a breaking behavior of actually printing out the literal n at
the end of each line of dialogue.

* bump version minor number

* trying to add some more files and see if browserify starts working

bumping version in the package.json

bump minor version number (#2)

* add soft breaks to New Line logic

In our application we sometimes get substation alpha authors that put n at
the end of each line in the dialogue. Usually we would expect that they would
use N instead.  So we will add that to the conditions checked by the parse-
newLine function so that this doesn'
t cause a breaking behavior of actually printing out the literal n at
the end of each line of dialogue.

* bump version minor number

Add soft break handling

Before this version, .SSA file authors that use "\n" in their dialogue will have the visible text literal "\n" in the output of the screen. Why libjass doesn't support "\n" tags might have something to do with the dismissive language of http://docs.aegisub.org/3.2/ASS_Tags/#wrapstyle when referring to the use of a soft line break.