From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sonic308-33.consmr.mail.ir2.yahoo.com ([77.238.178.169]:41058 "EHLO sonic308-33.consmr.mail.ir2.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753883AbdK1QPU (ORCPT ); Tue, 28 Nov 2017 11:15:20 -0500 Date: Tue, 28 Nov 2017 16:15:18 +0000 (UTC) From: Hin-Tak Leung Reply-To: Hin-Tak Leung To: Viacheslav Dubeyko , =?UTF-8?Q?Ernesto_A=2E_Fern=C3=A1ndez?= Cc: , tchou , Alexander Viro , Andrew Morton , =?UTF-8?Q?Ernesto_A=2E_Fern=C3=A1ndez?= Message-ID: <1999104027.7153972.1511885718712@mail.yahoo.com> Subject: Re: [PATCH] hfsplus: fix decomposition of Hangul characters MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable References: <1999104027.7153972.1511885718712.ref@mail.yahoo.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: -------------------------------------------- On Tue, 28/11/17, Ernesto A. Fern=C3=A1ndez wrote: > The algorithm is very simple, the best way to > understand it is just > looking at the code. I > don't know the first thing about Korean writing, so > I don't think I should attempt to explain > why the decomposition is done > this way. If > somebody else is interested in the details, they can > follow > the citation in the header comment of > the decompose_hangul function. =20 Apologies for coming into this a bit late. A couple of points: 1. Hangul canonical composition and decomposition is a separate topic from = compositions of latin characters with accents. It is described in=20 http://www.unicode.org/reports/tr15/tr15-18.html#Hangul among other sources. 2. I think the mount option is a bit of a red-herring. I think we should ju= st do what Mac OS X does - I think in the tech note it says something about= storing things always in the decomposed form or composed form. Ideally we = should make the differing mount options no-ops. Mac OS X does not need extr= a mount options, we shouldn't either.