Jürgen Schmidt wrote:
Christian Lohmaier wrote:
Hi Jürgen,
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.
Would be a lot easier to tell where the problem is when you give links
to the problematic pages.
http://api.openoffice.org/docs/common/ref/com/sun/star/module-ix.html
Looks fine for me.
http://api.openoffice.org/docs/cpp/ref/index.html
looks fine (well, the font is a little bit large, but that is not
what I
would call "strange" or even "unusable" - <ctrl>+<scrollwheel> comes
handy here as well :-)
you should compare these sides with the appropriate pages in a
locally installed SDK. Browse through the reference and see that for
examples table borders are disabled, no background colors and so on
Still: What is so hard about providing a simple URL that demonstrates
the behaviour?
[...]
A second problem is with the online verison of the Developers Guide
where i have a similar problem. Independent of the fact that the
files are to large (will be solved) the framework causes problems
of the files online.
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.
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?
Juergen
Juergen
Furthermore it seems that every page uses its own css. This is bad.
And apparently there was some hard-formatting in the source-file, so
that styles for the hard-formatted text gets exported as well.
Fixing this by hand would take a while, and would have to be done again
whenever the file is regenerated.
I strongly suggest you fix the export itself.
@murb: This probably is one of the reason why the colors were defined as
important! in the inst/tigris.css
ciao
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
