"dita.css" sent with oxygen \frameworks contains e

[Charlie Williams]

Hello,

I'm learning how to work with the files that are shipped with <oXygen> contained in the \frameworks folder. When I open "dita.css," it shows 10 errors. Here are a few of them:

URL: http://www.w3.org/TR/REC-CSS2/generate. ... ef-content

SystemID: C:\projects\AdminPassword\frameworks\dita\css\dita.css
Location: 603:0
Description: Context : image[placement="break"] in property : content
Invalid attr definition attr(X) : attr(href,url)

URL: http://www.w3.org/TR/REC-CSS2/generate. ... ef-content

SystemID: C:\projects\AdminPassword\frameworks\xhtml\css\html_cals_table.css
Location: 47:0
Description: Context : table[border], informaltable[border] in property : border-width
attr(border,px) is not a width value : attr(border,px)

URL: http://www.w3.org/TR/REC-CSS2/box.html# ... rder-width

SystemID: C:\projects\AdminPassword\frameworks\dita\css\folds.css
Location: 9:0
Description: Context : topic, section, example, table, simpletable in property : foldable
Property foldable doesn't exist : true

Does anyone know how I can fix the errors?
Should someone at <oXygen> think about fixing these errors. Could be considered a bug in the product?

Thanks
Charlie

[Dan]

The validation of the CSS file is done using the W3C CSS validator. It verifies if the CSS complies to the W3C CSS 2.1 specification.

The CSS files used by the DITA framework contain some CSS "extensions" specific to to CSS 3.0 and some recognized only by the Author mode of oXygen.

For instance, the CSS 2.1 specification does not allow to specify that an attribute of the element should be used to create an image and use it as a content. In CSS 3.0 however, this can be done using:attr(href,url). However, CSS 3.0 is not yet an accepted specification, so the validator consides these property constructs to be invalid.

To see all the all the CSS 3.0 properties oXygen Author recognizes, see:

http://www.oxygenxml.com/doc/ug-oxygen/ ... uthor.html
http://www.oxygenxml.com/doc/ug-oxygen/ ... ction.html
http://www.oxygenxml.com/doc/ug-oxygen/ ... sions.html

Regards,
Dan

[Charlie Williams]

Hi Dan,

Thanks for the reply and the clear explanation. I appreciate it.

Charlie

[ghudson]

Hello,
I also appreciated the clear explanation, however:
I'm wondering if there is a way to use a different validator. Here is an example from our CSS:

content: xpath("../../ChapterCite/TitleNumber/text()");

This is a new feature, valid in Oxygen, and works quite well

I don't want our users to see the validator error appear for something that is not an error. As a developer it doesn't bother me but you know how it goes.

Thanks,
Glenn

[Radu]

Hi Glenn,

Indeed we've had some requests to show CSS extensions which are supported only by Oxygen at least as warnings (and not as errors).
I added your opinion to the issue.
When this gets implemented (probably in a future version) we'll update this thread.

Regards,
Radu