https://issues.apache.org/ooo/show_bug.cgi?id=118191
--- Comment #13 from Regina Henschel <[email protected]> --- (In reply to lapsap7+ooo from comment #12) > (In reply to Regina Henschel from comment #11) > > Created attachment 84119 [details] > > updated patch as discussed on dev mailing list > > In file "03090600.xhp", line 426: > white, silver, gray, white, maroon, red, purple, fuchsia, green, lime, > olive, yellow, navy, blue, teal and aqua > > should have been > > white, silver, gray, black, maroon, red, purple, fuchsia, green, lime, > olive, yellow, navy, blue, teal and aqua > > But I'd like to suggest either an alphabetical order: > aqua, black, blue, fuchsia, gray, green, lime, maroon, navy, olive, purple, > red, silver, teal, white and yellow > > or a natural spectral order: > white, silver, gray, black, red, maroon, yellow, olive, lime, green, aqua, > teal, blue, navy, fuchsia and purple Thank you for finding this. I'll like the "natural spectral order" and will use that in my next patch version. > > On the other hand, I don't see the matching of cyan to aqua and magenta to > fuchsia in the "diff". That is in main/starmath/source/node.cxx, the method SmFontNode::Arrange, in "diff" line#206 and line#207. The color "aqua" is internally called COL_LIGHTCYAN and "fuchsia" is internally called "COL_LIGHTMAGENTA". > Yes, I understood this. I was just wondering if OO Math could do like this: > I type in "color cyan " in the editor > As soon as I press the spacebar after the word "cyan", the editor changes it > to "aqua" to make user aware that the new name is aqua. In theory it would be possible, but it would be much more work, and I would have to learn a lot more about the code to do it. -- You are receiving this mail because: You are on the CC list for the issue. You are watching all issue changes.
