Forwards-compatible syntax proposal
zwetan at gmail.com
Wed May 14 07:20:35 PDT 2008
2008/5/13 Mike Samuel <mikesamuel at gmail.com>:
> 2008/5/13 <es4-discuss-request at mozilla.org>:
> > what about
> > http://wiki.ecmascript.org/doku.php?id=proposals:versioning
> > and
> > http://wiki.ecmascript.org/doku.php?id=discussion:versioning
> On developer tools and mime-types, subversion will treat
> application/ecmascript as binary.
> Subversion treats the following files as text:
> Files with no svn:mime-type
> Files with a svn:mime-type starting "text/"
> Files with a svn:mime-type equal to "image/x-xbitmap"
> Files with a svn:mime-type equal to "image/x-xpixmap"
> All other files are treated as binary, meaning that Subversion will:
> Not attempt to automatically merge received changes with local changes
> during svn update or svn merge
> Not show the differences as part of svn diff
> Not show line-by-line attribution for svn blame
a little OT, but nevermind
two basic thing
1) application/ecmascript;version=5 is not necesary a mimetype
the full tag is <meta http-equiv="Content-Script-Type"
and I think this would be interpreted as plain text mimetype
2) even if all that was causing svn to see those files as binary
you can still force the mimetype by editing autoprops in your subversion config
*.es = svn:eol-style=native; svn:mime-type=text/plain
*.es3 = svn:eol-style=native; svn:mime-type=text/plain
*.es4 = svn:eol-style=native; svn:mime-type=text/plain
More information about the Es4-discuss