Infrastructure » Extensions

What exactly do you mean with "category"? Another top-level item next to Extension and Template (and probably Documentation) or a tag that bundles all extensions that affect the configuration. I tend to disagree with both since a category makes no sense and the tag always combines with something else. For example, Icons or Dictionaries are also part of the configuration. If your extension contains code it should go into macro anyway for security.

Ooops! Sorry, bad wording. I meant adding a "settings" or "configuration" tag. The extension I have just sets LibreOffice parameters (ie, the fonts replacement table).

I'm thinking about the tight integration dialog within the program. We added a button next to Icon Theme to get all extensions from the Icons tag. The more generic Configuration tag makes not much sense here. How would your extension work in this regards?

By "Icon Theme", do you refer to the Extensions website tags? If so, then no, my extension is NOT by any means an icon extension and has nothing in common with any icon thing. Again: it initializes the font substitution table as presented in Italo's blog post (see link in my first message). There's NO code involved, only a set of properties for registrymodifications.xcu. Note: The configuration set I'm talking about is accessed by the menu: Tools > Options > LibreOffice > Fonts.
So, yes, a specific tag is required for this kind of extension, unless you can propose an existing one that fits. "Icon" clearly doesn't. "Calc", "Writer", "Impress", etc. could do, but the purpose of the extension is global to LibreOffice, thus any single module tag would be an extrapolation and wouldn't clearly display the extension target.