Hi Marcus,
Marcus schrieb:
[..]
Another thing is to take the compatibility to older documents into account.
When changing the colors so that they look like the user would expect
due to the standard, then OK. But if this means also that colors in
older documents will now look different, then ... hm ... it needs to be
investigated how bad it really would be.
I think, that the current situation is bad for "cyan" (and for "magenta"
as well), because
(1) The user writes "cyan" in Math. Rendering is "teal" as long as
StarMath is used, but in the included MathML - which is the only part
relevant for ODF - the color "aqua" is written.
(2) The user imports a .mml file with "aqua" and gets a rendering of "teal".
(3) The user writes "cyan" in number-format-code in Calc and it is
rendered as "aqua".
My suggestion is, to always handle "cyan" as "aqua". This would also be
in line with how these words are handled by the W3C, e.g.
http://www.w3.org/TR/SVG/types.html#ColorKeywords
The other option would be, that I write "teal" to MathML when the user
writes "cyan". That would solve the conflict between StarMath and
MathML. But that would be inconsistent to the use of the color name
"cyan" in Calc and to other places in the web.
You are right in that older documents will now have a light color where
they had a dark color before. But now not only 8 but all 16 basic html
colors will be supported, so the user can change the color name to
"teal" if he really wants the dark color. However older OpenOffice
versions don't know "teal" and will show a ?.
If the solution were obvious, I would not have brought it to the list.
Kind regards
Regina
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
