Commits on Jul 25, 2016
  1. Update readmes

    committed Jul 25, 2016
  2. Set dates for 5.1.13

    committed Jul 25, 2016
  3. Updated Portuguese Translation

    committed Jul 25, 2016
Commits on Jul 22, 2016
  1. Fix problem with tiddler titled "undefined"

    Fixes #2507
    
    The problem stems from a JavaScript quirk: the fact that
    `({“undefined":"Me"})[undefined]` returns “Me”. The quirk is that the
    value `undefined` is coerced into the string “undefined” when used as
    an index.
    
    In this particular case, the code for `wiki.getTiddler()` was returning
    the tiddler with the title `”undefined”` when called with the title set
    to the value `undefined`. It happens that the pluginswitcher called
    `wiki.getTiddler(undefined)`.
    committed Jul 22, 2016
Commits on Jul 21, 2016
  1. Fix KaTeX rendering bug on Chrome

    Fixes #2500
    committed Jul 21, 2016
Commits on Jul 20, 2016
  1. Remove tiddler frame padding in print view

    It was wasting a border around each page.
    committed Jul 20, 2016
  2. Fix some typos from #2504

    committed Jul 20, 2016
  3. @sukima

    Prevent adding extra file extensions (#2504)

    Fixes #2503
    
    This bug was introduced in commit c4c7b18 where it would append
    additional .tid extensions to a file every time the node server was
    restarted.
    
    Here we check the filepath does not have the extension already before
    appending it.
    sukima committed with Jul 20, 2016
  4. Relax external link matching to ignore illegal characters

    Fixes #2501, and rolls back some of #2324
    committed Jul 20, 2016
Commits on Jul 15, 2016
  1. Ensure .tid extension when saving .tid files

    Missed off of a450623
    committed Jul 15, 2016
Commits on Jul 14, 2016
  1. Fix writing non-wikitext text tiddlers

    The plan had been to switch template depending on the content type, but
    we’d only implemented support for saving wikitext tiddlers. That meant
    that creating a tiddler with any non-wikitext content type failed to
    write the file correctly under Node.js.
    
    Now we just always save in .tid file format.
    committed Jul 14, 2016
  2. Correct thumbnail size

    committed Jul 14, 2016
Commits on Jul 13, 2016
  1. Prepare for 5.1.13-prerelease

    committed Jul 13, 2016
  2. Update readmes

    committed Jul 13, 2016
  3. Release dates for 5.1.12

    committed Jul 13, 2016
  4. @araname
  5. @araname
Commits on Jul 12, 2016
  1. Release note updates

    committed Jul 12, 2016
  2. Update contributors list

    committed Jul 12, 2016
Commits on Jul 11, 2016
  1. @sukima

    Add this.document to ES2016 documentation (#2314)

    In the sample example for using ES2016 it used the
    `$tw.utils.domMaker()`. I just found out that if this code is executed
    by Node.js instead of in the browser that it doesn't work because
    `window.document` doesn't exist. The expectation is that widgets pass in
    the fake `this.document`.
    
    I updated the example to reflect this.
    sukima committed with Jul 11, 2016
  2. @sukima

    Handle binary files better when saving on Node.JS (#2420)

    * Save binary tiddlers with meta file
    
    The filesystemadaptor plugin was a little simplistic in its
    understanding of a binary file. It was using the typeInfo dictionary to
    choose what tiddler types were binary (and hence needed a meta file when
    saving).
    
    I looked as if it was trying to be smart by looking for the hasMetaFile
    *OR* had the encoding of base64. Unfortunately the typeInfo only defined
    image/jpeg and so any other base64 encoded tiddler was assumed to be of
    type text/vnd.tiddlywiki.
    
    The net effect was only JPG images got a meta file and everything else
    were saved as .tid files with base64 encoding. It all still worked but
    made working with binary data in a Git repo a bit daunting.
    
    There is enough information in the $tw.config.contentTypeInfo to
    determine if a tiddler type is encoded with base64 or not. A better list
    is available from boot/boot.js who registers all the types thorough the
    registerFileType and marks then with base64 were appropriate.
    
    This commit uses the typeInfo dictionary first for any filesystem
    specific overrides, then the contentTypeInfo, and finally defaults to
    the typeInfo["text/vnd.tiddlywiki"]. It also eliminates the now
    unnecessary override for image/jpeg.
    
    I think this might have been the original intent from commit 10b192e.
    From my limited testing all files described in boot/boot.js (lines
    1832-1856) with an encoding of base64 now save as the original binary
    and a meta file. Meaning that when you start the node server and then
    drag-n-drop a binary file (i.e. image/png) it will PUT to the server
    and then save it on the filesystem as-is allowing the file to be managed
    as a binary file and not a text file. (Binary diffs are better and
    GitHub supports them as well).
    
    * Prevent duplicate file extensions
    
    A side effects of using the $tw.config.contentFileInfo in the previous
    commit is that it will always append a file extension to the tiddler
    title when saving. In most cases this is the correct course of action.
    However, sometimes that title is already a proper filename with an
    extension (for example importing 'foobar.png' would save a file named
    'foobar.png.png') which seemed silly.
    
    This commit simply checks to make sure the title does not already end
    with the file extension before appending it to the filename. A little
    convenience really.
    
    Since IE apparently doesn't have the String endsWith method I took the
    liberty to add a helper method to $tw.utils trying to follow the other
    polyfill patterns. I figured this was more generic and readable then
    attempting to use a one-off solution inline. I got the polyfill code
    from MDN.
    https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/endsWith#Polyfill
    
    Is strEndsWith the best method name?
    sukima committed with Jul 11, 2016
  3. @brentmaxwell

    Added mobile-web-app-capable meta tag for Android Chrome (#2456)

    * Added mobile-web-app-capable meta tag for Android Chrome
    
    * Added "mobile-web-app-capable" meta tag to the rest of the templates.
    brentmaxwell committed with Jul 11, 2016