With my book I am almost finished. Including indexes, mark by menu → Insert → Table of context and index → Index. The index has the standard grey background, en the font is in black. Just fine.
I want to add a few indexes, and now the font is in blue. There is no direct formatting, because I selected the text and deleted all direct formatting, but this did not make any difference.
As work around, I tried copy an existing index, and wanted to alter the content of the index later. But just copy the index change the new index font to blue. In the manual I could not find a solution, as not reading in previous threads on this forum.
As a check I made a preview in pdf, and there the font keeps to appear in blue. So the document can not be used for printing.
What is the reason for this, and how can this solved?
Not a lot of useful information in your question without a sample file. Just a guess: have you indexed URLs? Blue characters hint towards application of Internet Link character style. It is automatically applied by Writer when it recognises URLs or mail addresses.
Check inTools>AutoCorrect>AutoCorrect Options, Options tab whether Url Recognition is ticked.
No, it is not a hyperlink. I just wanted to make an example and make a screenshot. So I copied some data, created en new document, attached, the same template. With an existing index. This has a black font, and a grey background, as wanted and expected. Now I created an new index, and the font was the desired font.
So it seems to be document specific. Not the template, not general LO settings.
So now I copied the complete document, and stripped almost all text. And tried again. This was again good, with a black font. So within the document there must be somewhere a code which does mix-up the color.
So I deleted some text in the front of the desired index, until the font had the correct color. And copied the text back. In the end, the font stayed the correct color.
So it is solved, with a work-arround. I assume, there was a mix-up code in the document, and by copy, and past it back, this mix-up code was lost. Weird, I do not know what happened, but it is solved.
Thanks @ajlittoz you forced me, to pin to the detail of the error. And by doing so I found, with luck, a good work-arround solution.