Am Montag, dem 09.06.2025 um 18:03 +0200 schrieb mkri...@me.com: > Sorry, I must have expressed myself poorly. From the user > perspective there are now a lot more build in colors: the 752 colors > from the color package and the xcolor package. There is also the new > the capability to define additional “custom colors” in the setting > dialog. What I found surprising is that I can use my own custom > colors directly with the hyperref settings. Something like > “linkcolor=customcolor” does work! I don’t need to manually load a > color model. > > However, If I want to use one of the 752 colors it is a little > different. I can use an x11 color (such as Maroon3) if I have used > some x11 color somewhere in the document. Otherwise I get an error, > because the xcolor package has not been loaded. > > It is easy enough to work around this limitation by simply defining > all hyperref colors as custom colors or loading the corresponding > color package in the preamble. However, I was concerned that this > behavior may confuse people new to LyX. For instance, someone may > use an x11 color in the text, then define the link color as another > x11 color. Later the person deletes the part of the text where the > original x11 color was used and suddenly gets an error message that > the link color is not defined.
I think I understood in the fist place. However, the color support for hyperref is currently verbatim. To implement proper support, we would need a proper color UI in PDF settings. All possible, though certainly not for 2.5. We do not have a validate function in PDFOptions. A note in UG as you sketch would be possible, yes. But it wouldn't solve the whole problem. The same problem applies if you use such colors in ERT or the preamble. -- Jürgen -- lyx-devel mailing list lyx-devel@lists.lyx.org https://lists.lyx.org/mailman/listinfo/lyx-devel
