History Of Ticket 3984e3768ddbf470e62e6af98715a33abad17b49
Not logged in
Ticket change [3d37a55bcd] (rid 4655) by kkinnell on 2009-04-07 15:19:39:
  1. Change comment to "While most of the world has switched to UTF-8, there are still some places where ISO-8859 is used. It would be nice if fossil kept the repository in UTF-8, but recoded on the fly to keep the local copy in the system encoding. <hr><i>kkinnell added on 2009-04-07 15:06:11:</i><br> Please see ticket [cc6557cfc5763fa80bb04eecea7f713b0751efc4]. Encodings are mostly about display. If all of your systems are set up to use Latin-1, then except in <i>very</i> rare <i>real</i> instances you'll get Latin-1 when you look at the repository (see below.) Fossil stores octets. You will <u>always</u> get back the octets you commit to the repository as source files. The only time the encoding actually matters is when the encoding is interacting with the repository itself. This kind of meta-circular stuff causes problems in any system. The canonical example in Fossil is multi-byte characters in a wikipage title, which display as "entified" UTF-8."
Ticket change [66a4b97134] (rid 4654) by kkinnell on 2009-04-07 15:18:28:
  1. Change comment to "While most of the world has switched to UTF-8, there are still some places where ISO-8859 is used. It would be nice if fossil kept the repository in UTF-8, but recoded on the fly to keep the local copy in the system encoding. <hr><i>kkinnell added on 2009-04-07 15:06:11:</i><br> Please see ticket [cc6557cfc5763fa80bb04eecea7f713b0751efc4]. Encodings are mostly about display. Fossil stores octets. If all of your systems are set up to use Latin-1, then except in <i>very</i> rare <i>real</i> instances you'll get Latin-1 when you look at the repository (see below.) You will <u>always</u> get back the octets you commit to the repository as source files. The only time the encoding actually matters is when the encoding is interacting with the repository itself. This kind of meta-circular stuff causes problems in any system. The canonical example in Fossil is multi-byte characters in a wikipage title, which display as "entified" UTF-8."
Ticket change [70b9336955] (rid 4653) by kkinnell on 2009-04-07 15:06:11:
  1. Appended to comment:

    kkinnell added on 2009-04-07 15:06:11:
    Please see ticket cc6557cfc5763fa80bb04eecea7f713b0751efc4.

  2. Change resolution to "Open"
Ticket change [1a434774ac] (rid 4647) by anonymous on 2009-04-06 16:27:13:
  1. Change comment to "While most of the world has switched to UTF-8, there are still some places where ISO-8859 is used. It would be nice if fossil kept the repository in UTF-8, but recoded on the fly to keep the local copy in the system encoding."
  2. Change foundin to "d63f87c003"
  3. Change private_contact to "4de91f48ceab788649292e850559a96cc7e17039"
  4. Change severity to "Important"
  5. Change status to "Open"
  6. Change title to "Support for non-UTF encodings"
  7. Change type to "Feature_Request"