Any clue why the license file shows up as a binary file?

Thanks.

Well apparently, even by setting the property (mime:type plain/text), Phabricator doesn't recognize it as at a text file https://stackoverflow.com/questions/2634043/svn-diff-file-marked-as-binary-type

In rP20489#25038, @Stan wrote:

Well apparently, even by setting the property (mime:type plain/text), Phabricator doesn't recognize it as at a text file https://stackoverflow.com/questions/2634043/svn-diff-file-marked-as-binary-type

Because the ñs in there are in some codepage and not in utf8. The file uses the wrong text encoding and according to https://secure.phabricator.com/book/phabricator/article/utf8/ that is most likely causing this.

Uhm, if that also wasn't the issue... @Itms Phabricator is stupid, trac works though.

Thanks for trying :-)

In rP20489#25074, @leper wrote:

Uhm, if that also wasn't the issue... @Itms Phabricator is stupid, trac works though.

Thanks for trying :-)

Is there anything we can do except making sure to use utf8? Since upstream documents that everything should be utf8 it's unlikely there is an easy patch to this problem.

Is there anything we can do except making sure to use utf8? Since upstream documents that everything should be utf8 it's unlikely there is an easy patch to this problem.

Well, unless you see something that makes rP20493 not be utf8, then I'm not sure if that is everything that is needed.

In rP20489#25081, @leper wrote:

Well, unless you see something that makes rP20493 not be utf8, then I'm not sure if that is everything that is needed.

It looks like it is considered binary because it was binary before the commit, no? For instance right now when browsing in Diffusion it is properly blame'd whereas looking at its history shows it as binary. I feel like if one commits a new change to it the commit will properly display the change, can't be sure though.