Abdelrazak Younes wrote: > Your diagnosis and suggested fix are right. What would be the suggested fix?
asString(AS_STR_INSETS) or asString(AS_STR_LABEL | AS_STR_INSETS) IOW does the TOC need AS_STR_LABEL? I remember I have tried the latter and then the output was only correct in some cases (inset string disappearing again if you add some paragraphs after the heading or something like this). > IIRC we decided with JMarc > it was not worth going recursively into insets for toc purpose in order > to avoid potential visual problems (like big math insets or branch, > etc). So maybe we should add something between 'no inset' and 'all > insets'. I remember an old commit from JMarc that distinguish between > general insets and formating inset (like spaces, etc), maybe that can be > leveraged here. I agree that this is a rather minor problem for the navigation menu and outliner. However, this strings are also used for the TOC in plain text output. In that case, I'd consider this dataloss. Jürgen