Changes to ticket 838bde7990

By anonymous on 2008-12-03 02:56:00. See also: artifact content, and ticket history

1. Appended to comment:

   ---

   anonymous claiming to be kkinnell added on 2008-12-03 02:56:00:
   If I'm reading this correctly, you stored a file containing utf8 or uc16 encoded characters in a repository, and then got the zip for the repository by downloading it from the server. Then, when you unzipped it with one windows program, the file was encoded incorrectly, but when you unzipped it with a different windows program, the encoding was correct.

   If that is what happened, then the problem is how the programs you are using for unzipping the files are interpreting them. The one that gives you the correct version is using the same encoding that you used when you created the file, the other one is using something else.

   fossil itself uses SQLite BLOBs to store its artifacts. The storage doesn't encode the data in any way, it treats it as binary data.

2. Change resolution to "Open"