Questions regarding WindowsUTF8 plan

[Chinmay Joshi]

Hello FUJIWARA Katsunori,

I am currently working on WindowsUTF8 plan under GSoC. As I learnt you 
contributed on WindowsUTF8 plan. I really thank you for your feedback on my 
patches until now. I understand you have the greater idea of this plan and 
I had a few queries for you, for which I expect some help from you (or 
anyone else). Any help will be highly appreciated.

The one question is regarding u16vfs class for Windows. Some discussion has 
taken place on #mercurial IRC channel. This class is supposed to be derived 
from vfs and should use "wide APIs internally" and give UTF-8 results in 
case of UTF-8 changeset. What I understand from this is using Pythons APIs
​ with unicode objects​
which use windows wide APIs to to give UTF-8 results. One another solution 
raised was using windows specific win32 APIs. This would need a lot work to 
match python's current implementation of filesystem functions used in vfs 
class.

One more issue was raised in today's meet up which is about not passing 
Unicode objects to any Mercurial APIs (
http://mercurial.selenic.com/wiki/EncodingStrategy#Unicode_strings).

As per discussion with mpm on irc, a concern is that people will want to 
convert their existing non-ASCII repositories to UTF-8. This will not work 
if previous commits remain unchanged. I was considering to convert 
repository with new commits with filenames in UTF-8. This doesn't look like 
ideal solution to me, Does any one have different views?

--
Chinmay Joshi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20140609/1510e571/attachment.html>