View Ticket
Not logged in
Ticket UUID: 5317b79552cc460c4ff9fd27d4589e7fb619e727
Title: i18n for filenames
Status: Open Type: Code_Defect
Severity: Severe Priority:
Subsystem: Resolution: Open
Last Modified: 2009-09-24 14:32:43
Version Found In: f969b6cdde
Description & Comments:
When I run "fossil.exe add dir" under Windows, fossil recursively adding all files. If there are files with non-ascii names (Russian in my case), they inserted into fossil repo using system default encoding ('windows-1251' in Windows with Russian locale), and fossil works with them w/o problems. But in the web-interface on the files page (/dir) these files shown with unreadable names. This is because of UTF-8
fprintf(g.httpOut, "Content-Type: %s; charset=utf-8\r\n", zContentType);
in the HTTP reply header (cgi.c).

Please delete "; charset=utf-8" part from Content-Type header because there no CP convertor in the fossil. This will allow to set any charset in the META tags in the page header template and use browser's internal CP convertor or CP autodetector.

This will also solve a problem from the ticket d23fb0b742ac2e989e36bfef98281f970ab34e8f, I think.


drh added on 2009-09-24 14:32:43:
The fossil repository should store all filenames as UTF8. I think the bug here is that the "fossil add" command is not converting the names from the microsoft encoding into UTF8 before storing them.