Re: Comments on 'notes/unicode-composition-for-filenames'

2011-02-22 Thread Branko Čibej
On 22.02.2011 20:11, Daniel Shahaf wrote: > Branko Čibej wrote on Tue, Feb 22, 2011 at 19:41:12 +0100: >> On 22.02.2011 18:17, Julian Foad wrote: >>> For example, a solution that involves normalizing all input to NFD would >>> have the advantages that on MacOSX it would need to do *no* conversions

Re: Comments on 'notes/unicode-composition-for-filenames'

2011-02-22 Thread Daniel Shahaf
Branko Čibej wrote on Tue, Feb 22, 2011 at 19:41:12 +0100: > On 22.02.2011 18:17, Julian Foad wrote: > > For example, a solution that involves normalizing all input to NFD would > > have the advantages that on MacOSX it would need to do *no* conversions > > and would continue to work with old repos

Re: Comments on 'notes/unicode-composition-for-filenames'

2011-02-22 Thread Stefan Sperling
On Tue, Feb 22, 2011 at 07:41:12PM +0100, Branko Čibej wrote: > On 22.02.2011 18:17, Julian Foad wrote: > >> Proposed Support Library > >> > >> > >>Assumptions > >>--- > >> > >>The main assumption is that we'll keep using APR for character set > > s/char

Re: Comments on 'notes/unicode-composition-for-filenames'

2011-02-22 Thread Branko Čibej
On 22.02.2011 18:17, Julian Foad wrote: >> Proposed Support Library >> >> >>Assumptions >>--- >> >>The main assumption is that we'll keep using APR for character set > s/character set/character encoding/. > >>conversion, meaning that the recoding sol

Comments on 'notes/unicode-composition-for-filenames'

2011-02-22 Thread Julian Foad
> Proposed Support Library > > >Assumptions >--- > >The main assumption is that we'll keep using APR for character set s/character set/character encoding/. >conversion, meaning that the recoding solution to choose would not >need to provide a