Unfortunately, the stylesheet that came with the CDISC Metadata Submission Guideline inherits a lot from older versions of this stylesheet. The way it was developed does not separate style from markup. This makes it hard to have a cosistent styling. Also, the resulting HTML has many validation errors.
Having said that, you might want to try the following code, added to the table selector in the define.css file:
It actually worked when adding it to the css file!Thanks!!
but is there also a way to add it to the define.xsl? The thing is that I use the same define.css for define.xsl 1-0-0 and 2-0-0. In 1-0-0 I do not have this border problem, so I would suggest that there is something in the define.xsl 1-0-0 that makes it work. I am not really familiar with define, that’s why I am asking.
That is exactly the point that I was trying to make. When styling is not only in a .css file (or defined in a element), but also mixed with markup, it becomes very hard to maintain.
If you want to use one .css file for different XSL stylesheets, you should really move all styling from the XSL file into the .css file.
For Define-XML v2 I decided not to drag the Define v1 stylesheet forward, but start from scratch.
Btw: There is a LinkedIn group about Define-XML. It might make more sense to have these kind of non-OpenCDISC discussions about Define-XML there.
I am new here so I hope this is not a silly question.
I have created a define.xml (v2.0) in Pinnacle 21 and for some reason it does not show the stylesheet format, the styleesheet is saved in the right folder and it works with other .xml files in the same folder… Am I missing something?? When I view the xml file I created in Pinnacle 21 it just looks like black text on a white background.
In the CDISC Metadata submission package I have an define.xml example. when I open it I can see that some borders are not shown when fields are blank. This looks somehow not nice. Does anyone know why this is?
If I use the define.xsl 2-0-0 out of the package to create my define.xml.