Hi, James. That's not a bad idea, but I'll have to think about it.
Unfortunately, I don't think the fix you made will actually change the way SJ has stored the files in question. If there's only one version of the file, then your fix will work. But if there's more than one, it won't. The binary/text designation is more than just informational. This determines how SJ archives previous version of the file. Binary files are compressed (zipped). Text files are stored as diffs. I would really like to add a feature that allows you to convert text files to binary and vice versa, and someday I'm sure I will. Thanks. --Rob --- James Saffery <[EMAIL PROTECTED]> wrote: > Hi Rob, > > We've been happily using SJ now since early Feb since you resolved the > initial "no name" folder problem. Thank you again for your support then and > for an excellent tool. > > Recently we had some text files (with .spec and .body extensions) which were > first checked in by a user who unfortunately had not configured his client > (account?) preferences for these extensions to be text. So then according to > SJ these files are binary, meaning we cannot do diffs / view them, and > presumably cannot do keyword expansion either. > > I think I have worked out how to reform the situation by editing the > appropriate 'file' XML file for each archive as shown by the ID under File > Info in the Properties dialog and changing the FileType to "2". The change > then takes effect after a restart of the server. > > This email then is just a suggestion for what I think would be an > improvement so the above does not happen to me or others in the future: make > the extension / file type associations attributes of the archive in question > rather than the user/client. Then the file types can be set up once for the > archive by the administrator and that will be it. No need to remember to > repeat this configuration across all users/clients, and no potential for the > above situation. > > Many thanks. > > Cheers, > > James > > > ____________________________________________________________ > This message may contain legally privileged or confidential > information and is therefore addressed to the named persons only. > The recipient should inform the sender and delete this message, > if he/she is not named as addressee. > The sender disclaims any and all liability for the integrity > and punctuality of this message. > The sender has activated an automatic virus scanning by > Messagelabs, but does not guarantee the virus free > transmission of this message. > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click > _______________________________________________ > SourceJammer-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/sourcejammer-users __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ SourceJammer-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sourcejammer-users
