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 D105B3851C36 for ; Thu, 20 Aug 2020 15:18:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D105B3851C36 Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:105:465:1:2:0]) (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 4BXSvn1j8hzQlHj; Thu, 20 Aug 2020 17:18:13 +0200 (CEST) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from smtp2.mailbox.org ([80.241.60.241]) by spamfilter02.heinlein-hosting.de (spamfilter02.heinlein-hosting.de [80.241.56.116]) (amavisd-new, port 10030) with ESMTP id I9E1owG8F3A9; Thu, 20 Aug 2020 17:18:10 +0200 (CEST) Date: Thu, 20 Aug 2020 17:19:56 +0200 From: Max Gautier To: Florian Weimer Cc: Max Gautier via Libc-alpha Subject: Re: [PATCH 0/5] iconv: module for MODIFIED-UTF-7 Message-ID: <20200820151956.GA231892@ol-mgautier.localdomain> Mail-Followup-To: Max Gautier , Florian Weimer , Max Gautier via Libc-alpha References: <20200819230702.229822-1-mg@max.gautier.name> <87y2m9agmm.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87y2m9agmm.fsf@mid.deneb.enyo.de> X-MBO-SPAM-Probability: X-Rspamd-Score: -4.38 / 15.00 / 15.00 X-Rspamd-Queue-Id: F34B717A4 X-Rspamd-UID: f13e52 X-Spam-Status: No, score=-7.2 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, 20 Aug 2020 15:18:16 -0000 Florian Weimer: > * Max Gautier via Libc-alpha: > > > I am unaware of an official name for the encoding, so I used > > "MODIFIED-UTF-7". There might be better choices, if someone has insights > > on that. > > Let's try to get it added to the IANA registry? It's odd that a > charset defined in an RFC is not already contained in it. > > The contact information for the registry seems to have atrophied a > bit. I will try to figure out the current process. Historically, > it's been Expert Review, so we shouldn't have to write an RFC for > this. Is the list here (and the linked RFC) not accurate ? [1]: https://www.iana.org/assignments/charset-info/charset-info.xhtml