Re: [fossil-users] Question about the file formats.

2016-12-21 Thread Scott Robison
On Dec 20, 2016 10:59 PM, "John Found" wrote: Well, the compression is the last thing I am talking about. It is important, but not essential. I am talking about several people working on one file and then fossil merging the changes automatically (of course if there is no

Re: [fossil-users] Question about the file formats.

2016-12-21 Thread Joerg Sonnenberger
On Tue, Dec 20, 2016 at 08:48:27PM +0200, John Found wrote: > What makes the binary files different from the text files? The presence or > absence of > 0 bytes does not seems to make serious difference for processing by the same > algorithms. Many text formats allow merging changes from one

Re: [fossil-users] Question about the file formats.

2016-12-21 Thread Stephan Beal
On Dec 21, 2016 10:57 AM, "Warren Young" wrote: That is exactly what I’m talking about in my BMP vs PNG examples. If you wish to discuss a different file type than than bitmap graphics, give your own example. Until then, mine is the only concrete example we have available

Re: [fossil-users] Question about the file formats.

2016-12-20 Thread John Found
Well, the compression is the last thing I am talking about. It is important, but not essential. I am talking about several people working on one file and then fossil merging the changes automatically (of course if there is no conflicts in the edits). On Tue, 20 Dec 2016 16:58:18 -0700 Warren

Re: [fossil-users] Question about the file formats.

2016-12-20 Thread Warren Young
On Dec 20, 2016, at 3:57 PM, Warren Young wrote: > >> What if I design some text file format (containing only ascii characters) and >> it can't be properly processed by fossil? > > Then you should post it as a replicable test case for our study. I decided to take up my own

Re: [fossil-users] Question about the file formats.

2016-12-20 Thread Warren Young
On Dec 20, 2016, at 12:35 PM, John Found wrote: > > Under "fossil algorithms" I mean two (in my understanding most important in > what is called "version control": diff algorithm and 3-way merge algorithm. When I said that Fossil can’t diff two binary files, I meant that

Re: [fossil-users] Question about the file formats.

2016-12-20 Thread Andy Bradford
Thus said John Found on Tue, 20 Dec 2016 21:35:44 +0200: > For example, I can't see what is the problem to make diff of binary > files. As a result one will have the bytes that have to be > inserted/deleted from the first file in order to turn it into the > second. (Or I am

Re: [fossil-users] Question about the file formats.

2016-12-20 Thread John Found
I am not talking about the fossil heuristics in detection of what file is binary and what file is text. Imagine all detection is switched off. Under "fossil algorithms" I mean two (in my understanding most important in what is called "version control": diff algorithm and 3-way merge algorithm.

Re: [fossil-users] Question about the file formats.

2016-12-20 Thread Warren Young
On Dec 20, 2016, at 11:48 AM, John Found wrote: > > I know that fossil (and most other version control systems) can handle > properly > only text source files. Says who? There are some features of Fossil that simply don’t work when given a binary file, like “fossil

[fossil-users] Question about the file formats.

2016-12-20 Thread John Found
Hi. I know that fossil (and most other version control systems) can handle properly only text source files. I am designing a format for my application and have some questions about the files handling. They are very related, but in different form: What makes the binary files different from the