[tahoe-dev] [tahoe-lafs] #534: "tahoe cp" command encoding issue

[tahoe-lafs]

#534: "tahoe cp" command encoding issue
-----------------------------------+----------------------------------------
     Reporter:  francois           |       Owner:  francois                          
         Type:  defect             |      Status:  assigned                          
     Priority:  minor              |   Milestone:  1.3.1                             
    Component:  code-frontend-cli  |     Version:  1.2.0                             
   Resolution:                     |    Keywords:  cp encoding unicode filename utf-8
Launchpad_bug:                     |  
-----------------------------------+----------------------------------------
Changes (by francois):

  * keywords:  cp encoding => cp encoding unicode filename utf-8
  * milestone:  undecided => 1.3.1


Comment:

 Ok, we had plenty of discussion on the mailing-list. Zooko posted a
 summary available at http://allmydata.org/pipermail/tahoe-
 dev/2009-March/001379.html

 Basically, there are two cases:

   1. Filenames which, based on locale settings, can be decoded into
 unicode strings
   2. Filenames which, based on locale settings, cannot be decode into
 unicode strings

 Case 1 is what's currently implemented by my patches.

 Case 2 requires to optionally add two attributes to each file, a
 bytestring and a guessed encoding. As Brian pointed out, the bytesting
 attribute must be encoded as base32 to survive to a JSON trip.

 Now, I first want to focus on case 1 while raising an helpful error on
 case 2.

 Does it sound any good ?

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/534#comment:46>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid