From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout-y-111.mailbox.org (mout-y-111.mailbox.org [91.198.250.236]) by sourceware.org (Postfix) with ESMTPS id 1C8B53870849 for ; Thu, 3 Sep 2020 09:47:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 1C8B53870849 Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mout-y-111.mailbox.org (Postfix) with ESMTPS id 4Bhwvp6FylzQlQ3 for ; Thu, 3 Sep 2020 11:47:34 +0200 (CEST) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp1.mailbox.org ([80.241.60.240]) by spamfilter05.heinlein-hosting.de (spamfilter05.heinlein-hosting.de [80.241.56.123]) (amavisd-new, port 10030) with ESMTP id iRbPM4BolRRC for ; Thu, 3 Sep 2020 11:47:31 +0200 (CEST) Date: Thu, 3 Sep 2020 11:47:30 +0200 From: Max Gautier To: libc-alpha@sourceware.org Subject: Re: [PATCH 0/5] iconv: module for MODIFIED-UTF-7 Message-ID: <20200903094730.GA7401@ol-mgautier.localdomain> Mail-Followup-To: Max Gautier , libc-alpha@sourceware.org References: <20200819230702.229822-1-mg@max.gautier.name> <87y2m9agmm.fsf@mid.deneb.enyo.de> <20200902152434.GA55993@ol-mgautier.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-MBO-SPAM-Probability: X-Rspamd-Score: -4.07 / 15.00 / 15.00 X-Rspamd-Queue-Id: DB9DE1355 X-Rspamd-UID: 5eba49 X-Spam-Status: No, score=-6.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, KAM_NUMSUBJECT, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Sep 2020 09:47:37 -0000 On Wed, Sep 02, 2020 at 05:01:14PM -0300, Adhemerval Zanella wrote: > The only worry I have if this encoding is really used in the wild that > justify its inclusion on glibc. The fact that it is defined for about > 17 years without anyone having the trouble to register it on IANA makes > me doubtful it is really that useful. AFAIK, it's only used for IMAP client and servers. Searching Google for "IMAP4 utf-7 usage" shows there exists some implementations already (PHP, Python, Perl (I think)) and several questions on Stack Overflow (over the years and until recently) on how to deal with that UTF-7. So it seems it's a narrow use case, but used by many. Since I suppose that many languages can interface with glibc, including that modified UTF-7 would avoid workarounds like converting to original UTF-7 then just replacing the shift character and '/' by ',', and that kind of things.