--- Comment #6 from Harald Koester <[hidden email]> ---
(In reply to Regina Henschel from comment #5)
> Hi, it seems, that I was not clear enough. My uses case, that you have a
> drawing, that is used inside text as sign or ersatz for missing glyphs. Such
> occur in writing guides and the same shape might be used very often in the
> text. You might want shapes instead of images, because they can be better
> scaled, and better adapted in regard to color.
> I'm sure you do not want that such shapes are listed in Navigator or index.
Hi Regina, yes, I see the use case, that images and drawing objects (I think
text frames too.) may be used instead of characters (“Anchor as character”). I
also see, that the number of such signs within a single document may be quite a
lot. I would expect, that these 3 kinds of signs (images, drawings, text
frames) are treated equal with respect to naming, handling with the Navigator
or within an index, ... Currently this is not the case.
As far as I understand you your requirement to these kinds of signs are:
* A user should be able to decide if signs are displayed in the Navigator.
* A user should be able to decide if signs are listed in an index.
As far as I understand you, deleting names of such signs is not a requirement,
but a means to an end in order to fulfill the above requirements. To my opinion
deleting names is not a suitable solution for these requirements, because it is
not obvious for a user, it is not documented and currently it does not work for
all kind of signs. I believe it's just a random result. One should think about
another solution for these cases, perhaps an option to hide signs, that are
anchored as characters, in the Navigator and in indexes.
> (In reply to Harald Koester from comment #4)
> > Yes, it is possible to create drawing objects with the same name by using
> > copy&paste. But I think it is not intended.
> That was my point. If you delete the name, then there is no double name
> after copy&paste; workaround till the double-name bug is fixed.
Is there already a bug report written regarding this subject, I did not found