Tournant does not display Ingredient-lists correctly when Ingredient-groups have been used about tournant

[Zimbelstern]

I've never noticed ingredient groups in Gourmand so could you provide
a) a screenshot how they look like in Gourmand
b) the corresponding recipe file (or relevant section)
? That would speed things up because Gourmand is broken in Debian testing right now (well, at least on my machine).

[fsand1]

Flusskrebsmousse.txt

Sorry for some Typos in the German recipe text. Please disregard them.

The same behaviour of Tournant will happen when a recipe is constructed out of multiple recipes. Even the actual GOURMAND version (I am running Linux Mint 21 Cinnamon with GOURMAND 1.0.0-7) does not show the real content of the recipes. The old GOURMET version did it properly at least in printing. I attached the xml-code for this "problem" as well.

Hummercannelloni auf Fenchelgemüse mit kandierter Ananas und Hummerschaum.txt

I think in Tournant it would make sense to list the links for the sup-recipes to directly jump to like it is implemented in the actual version of GOURMAND.
I had to rename the xml-files to txt for uploading. Hope it will help you.
Sorry for spoiling your weekend.

[Zimbelstern]

Ah, I see. Ingredient groups are a useful feature indeed.
It will not be very difficult to implement these two features in Tournant but as it requires modifications in several classes I will not promise to get it done in October. :)

[fsand1]

Sorry, but after installing the new version 1.1.2 I could not recognize any changes in presentation.

[Zimbelstern]

I'll give you some information about how development usually works:
This issue was marked as closed with the referenced commit. From this moment on, the issue is fixed in the source code. In packages compiled from this source afterwards, this issue should be fixed.
Unless you build the package yourself (you are of course free to do so), you have to wait for the next release. When there are some more commits in the pipeline that are expected to be ready shortly after, I will wait with the new release to include them as well.

The next release is scheduled for today. :) If the issue is not fixed in version 1.1.4, please reopen.

By the way: Would you tell me where you get your packages from? Version 1.1.3 was released over a month ago.