Is there a way to include comment when copying a file?

[Kucera]

Hi, the subject says it all - I spent a lot of time commenting the files, but when I copy them for backup, no comments made it across. Is it a windows limitation, or have I missed something obvious in configuration?
Regards Emil

[Marco]

As far as I remember, it is by design. No Win limitation.
Btw, this thing made me think, in the last days, about transferring all the label+tags+comment infos in an ADS of the desired file. I might code something if there's much interest...

[xycooper]

I for one would very much like a way to copy the label+tags+comments with a file.

[admin]

Hi, the subject says it all - I spent a lot of time commenting the files, but when I copy them for backup, no comments made it across. Is it a windows limitation, or have I missed something obvious in configuration?
Regards Emil

Yes, it is by design. The reason: The copied tags would end up in the central tag.dat and make it bigger and bigger, although your backup is probably sleeping on a removable disk in some freezer.

A solution would be a way to export tags (in an exported in-place tag.dat) together with the copied files, and a way to later import these tags if desired. This is technically possible but still needs a little thinking. It is on my list.

[Marco]

Yes, it is by design. The reason: The copied tags would end up in the central tag.dat and make it bigger and bigger, although your backup is probably sleeping on a removable disk in some freezer.

A solution would be a way to export tags (in an exported in-place tag.dat) together with the copied files, and a way to later import these tags if desired. This is technically possible but still needs a little thinking. It is on my list.

My 0.02€
Personally, I don't like when "service files" are added to my backups.
What's the problem exactly in tags.dat getting bigger? What's the performance impact in parsing a file of several thousands of lines?

[admin]

Yes, it is by design. The reason: The copied tags would end up in the central tag.dat and make it bigger and bigger, although your backup is probably sleeping on a removable disk in some freezer.

A solution would be a way to export tags (in an exported in-place tag.dat) together with the copied files, and a way to later import these tags if desired. This is technically possible but still needs a little thinking. It is on my list.

My 0.02€
Personally, I don't like when "service files" are added to my backups.
What's the problem exactly in tags.dat getting bigger? What's the performance impact in parsing a file of several thousands of lines?

When it becomes several hundred thousands you will slowly start to note it. (Depends on the machine, of course.)