Christian Lohmaier wrote:
Hi Jürgen,
On Fri, Nov 11, 2005 at 02:39:11PM +0100, Jürgen Schmidt wrote:
Jürgen Schmidt wrote:
Christian Lohmaier wrote:
On Fri, Nov 04, 2005 at 10:47:17AM +0100, Jürgen Schmidt wrote:
Christian Lohmaier wrote:
On Thu, Nov 03, 2005 at 05:34:33PM +0100, Jürgen Schmidt wrote:
Problem:
I have updated the API IDL and the C++ UNO runtime reference on the
api project page. We use know an external css file for all styles.
It seems that this css files conflict with the css files from the
framework.
The effect is that it looks strange and isn't really usable.
I had a look at
http://api.openoffice.org/docs/DevelopersGuide/Preface/ReadersGuide.htm
and the corresponding stylesheet
http://api.openoffice.org/docs/DevelopersGuide/Preface//ReadersGuide.css
And, well, it is not cascading at all.. and overrides the color for all
elements of a given type, not only one of those in the body of the page
(body meaning the actual contents that is sourrounded by the
SC-framework, the body of the html-file in CVS).
Just at the start you'll see
a { text-decoration: none; }
a { text-decoration: none; }
a:link { color: #C44B01; }
a:visited { color: #638093; }
a:active { color: #9DCA12; }
And so on.. This definitely needs some cleaning up.
The problem is that this documents are generated automatically (xhtml
export, xslt tranformation + several scripts) and without the sc
framework arround everyhting looks fine.
Sure. I believe you. But you didn't get my point. The css is not
specific to the contents of the developers-guide, but sets properties
for "standard" HTML-tags like "anchor". It doesn't only format the links
defined in the document itself, but modifies the formatting of the
surrounding SC-framework as well. This results in the messed-up display.
After correcting some links the framework opens all generated
Developer's Guide pages separately with out any framework stuff around.
It looks quite better now but of course is not the intended behaviour. I
expect the resason for that is that we have changed the suffix to xhtml
because it is real xhtml. Any ideas?
No. The suffix is irrelevant. It is the css that causes the problem. An
realatively easy fix woud be to put all the contents of the page into a
<div id=devguide>..</div> and make all css-statements only valid for
elements inside that div.
This way you won't modify the templates of the surrounding css and thus
avoid the display-problems.
To make the css-statements only apply to the elements inside the div
with id "guide", prepend every selector with "#guide "
e.g. make
a { text-decoration: none; }
#guide a { text-decoration: none; }
thanks for the hints i will check and test it asap and will give feedback
Still I think it would be better to generate only one single css file
and include that in all pages of the guide instead of creating a
seperate css for every page.
i agree that it would be better but the DevGuide comes as a master
document with several child docs and the XSL transformation handle the
child docs separately. I will see what we can improve here.
Juergen
ciao
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
