Hello fossil-users: I was intrigued with Fossil after reading the enthusiastic LWN article [1]. Unfortunately I do not see any summary about Fossil and Internationalization (i18n). Let me contribute a summary which can be used on the Fossil wiki.
---8<--- <h1>Fossil and Internationalization (i18n)</h1> Current as of version [http://www.fossil-scm.org/fossil/info/84e755e213|84e755e213] (2011-03-16) <h2>Content</h2> Fossil does not modify or re-encode your content. For display with the internal web server, Fossil does not enforce any encoding, and leaves the encoding interpretation up to your browser. (e.g. no encoding specified in the html or doctype tags) <h2>File names</h2> Fossil does not attempt to store the encoding of the file name. File names are regenerated as is with no re-encoding. When working with Windows, Fossil will use the national code page for the encoding and not UTF-8.For example, for Japanese file names, the encoding will be Windows-31J (CP932) and not even UTF-16, due to the usage of mingw. In this respect, Fossil is not cross-platform, even between different Windows localizations. See ticket [d22946aa0c]. <h2>User Interface</h2> User interface is the command line and web page, and built-in help is provided in English, only. No other languages are supported. <h2>Commit message</h2> Same as Content. ---8<--- I have only spent a couple of hours with Fossil so please correct my mistaken observations. [1] https://lwn.net/Articles/433843/ Best regards, Clifford Caoile _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
