- From: Phillips, Addison <addison@lab126.com>
- Date: Tue, 9 Dec 2014 22:37:19 +0000
- To: Nico Williams <nico@cryptonector.com>, Matthew Kerwin <matthew@kerwin.net.au>
- CC: IETF Apps Discuss <apps-discuss@ietf.org>, "uri@w3.org" <uri@w3.org>
Although normalization is often a good idea... normalization might be a problem if the local filesystem allows normalized and non-normalized representations both to appear. You wouldn't be able to specify a non-normalized representation. Addison > -----Original Message----- > From: Nico Williams [mailto:nico@cryptonector.com] > Sent: Tuesday, December 09, 2014 2:27 PM > To: Matthew Kerwin > Cc: IETF Apps Discuss; uri@w3.org > Subject: Re: [apps-discuss] Fwd: FW: New Version Notification for draft- > kerwin-file-scheme-13.txt > > > FWIW, HFS+ normalizes to something close to NFD. Not adhering to the > recommendation to normalize might cause problems here. > > Also, if file: is intended for local use only, then there may not be any point to > normalizing. Hmmm, that will vary, no? It will generally depend on what the > filesystem does. Most just-use-8, some do better. > ZFS does normalization-insensitive matching; HFS+ normalizes to NFD. > > Anyways, normalizing to NFC is probably the best thing to do, but mentioning > the above might give implementors the sense of urgency they might need to > actually implement this recommendation (or a clue as to bug reports they run > into). > > Nico > --
Received on Tuesday, 9 December 2014 22:37:51 UTC