Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 5 Oct 2021 09:07:16 +0200
From:   thomas@t-8ch.de
To:     Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc:     "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [BlueZ] Use accurate icons for headphones and headsets
Message-ID: <008c2b28-f830-46fe-bc51-9f1714695f37@t-8ch.de>
References: <20211003101834.45448-1-thomas@t-8ch.de>
 <61598804.1c69fb81.d279a.fe3f@mx.google.com>
 <CABBYNZ+-7QASvCoA9XJQ_Jmi8=e2-dZQSnL4Xft4Ci_WGb=nPA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CABBYNZ+-7QASvCoA9XJQ_Jmi8=e2-dZQSnL4Xft4Ci_WGb=nPA@mail.gmail.com>
Precedence: bulk

Hi Luiz,

On 2021-10-04T21:15-0700, Luiz Augusto von Dentz wrote:
> Shouldn't they be proposed to be added to the standard before we do
> these changes? I mean it is better to have an icon then not have
> anything or is there a fallback mechanism e.g. audio prefix fallback
> to audio-card?

The naming standard has not been updated since 2006, I'm not sure it is still
maintained.
Each theme can specify other themes it inherits from where missing icons
are looked up from. The themes I checked either contain these icons or they
inherit from some that do.
A standard fallback mechanism by name is not specified.

If you want I can try to submit the names to the standard but they seem already
be part of the de-facto standard.

Thomas