@Rmano this one? tex.stackexchange.com/questions/570510/… You shouldn't need to define ver@color, xcolor takes care of that. (Actually I'm surprised you say that tikz has issues with color, It includes xcolor but loading xcolor and color should not hurt. (the extra groups you added are neeed of course!)
@Rmano I didn't actually try the example, I'll look in a bit. But in general if you load xcolor first it suppresses color (by defining ver@color), but if you load color first it should also work as xcolor takes care to redefine anything it wants to redefine
@Rmano if you load color the xcolor then xcolor silently handles the predefined colours like black and red, but if you define your own colours using the (standard, original and greatest) version of \definecolor then use that color it moans at you. (it could have not moaned and just fixed it but....)
The obvious solution is to switch it to l3color then blame @JosephWright for any problems.
@Rmano @JosephWright I think it doesn't come up often (and I had forgotten it was an issue) as usually when people load both they have \usepackage{color,xcolor}....\definecolor... which is harmless, it's only an issue if you make color package definitions then load xcolor.
Yes --- but I still do not know who to contact. I will try to search the info later... xcolor things are not dangerous, but I had color leaks in my last paper, so that should be fixed
@daleif this came up the other day with another one from the extended latin block, I think we just missed it. @egreg added an issue to add them I thought but I don't see it now
@daleif ah it was email not an issue, referenced from
if you type h to the error prompt it tells you:
! Package inputenc Error: Unicode character ḱ (U+1E31)
(inputenc) not set up for use with LaTeX.
See the inputenc package documentation for explanation.
Type H <return> for immediate help.
... ...
@daleif the suggestion in the email was to try to cover all these for translitertaed cyrillic ISO 9: g̀ǵëêžẑïǰl̂n̂ḱćŭčd̂šŝʺěèûâʼǎf̀ỳ Other: ġďīīľńćǵăģḟẏ
What I want is the ability to label things like: \cmpd{ln.eu.six} and get 10Eu.6H2O.
I've got the first part working., but chemnum out of the box only supports one level of sublabels.
There is a previous answer, but I don't understand it's code. I've got it partially working, but need help gettin...
@MarcelKrüger if I do something like \directlua{xxx=luatexbase.new_attribute ("blub")}, what function has the "blub"? Has it to be unique? Can one use it for something?
@Canageek I actually looked at it a bit in the morning. I don't really understand this numbering system you use, but I suspect that the idea to use sublevels is false here, even for the first level. I mean you have to define your labels in a very specific order to get this working, and this looks quite suspicious. Why can't you implement this with simple text that you attach to the number?
@UlrikeFischer There isn't a super great mechanism for that. I've already got the first sublevel defined and working all through my thesis, it works great. If there is a way to add arbitrary text to the end that would work fine. I could then make a macro for it
Should I make a second question outlining what I need rather then doing it through that mechanism?
@Canageek you could also add to the question itself. I mean adding text is easy, you could simply type \cmpd{label}.sometext, so it would be good to understand why this isn't enought.
@UlrikeFischer It should be unique and descriptive (it is written to the log). In addition to the logging the attribute number can be queried using luatexbase.attributes.blub.
@MarcelKrüger the new luacolor code does local color_attr = luatexbase.new_attribute("color"). Is that a good name? What happens if two code use the same name?
@MarcelKrüger ok, if I want to access the attribute value also in tex (for example to report it), does it make more sense to do mygloballuavar= luatexbase.new_attribute("blub") (in a sensible table naturally) or should one write dedicated access functions ?
@UlrikeFischer I think the only reason for using a access function would be if you are worried that other code might try to change your attribute variable, otherwise I think the variable (or just using luatexbase.attributes if you're name is sufficiently unique) is simpler.
@Skillmon Thanks I'll leave my reply for a bit in case the OP had copied that version. Why do people use massively complicated and wrong "templates" just to typeset a simple list?
@DavidCarlisle because they are new to LaTeX and think it is hard. So they search for a template they find visually appealing, without knowing what virus of a preamble they'll catch by doing so, and try to force it onto their contents?