Bedienungsanleitung Kompozer 07 (Seite 56 von 58) (Englisch)

606646

Zoom out

Zoom in

Vorherige Seite

1/58

Nächste Seite

KompoZer User Guide — 17 December 2007 Based on version 0.7.10 56

tered though this may be modified using page-break-

before. This is usually satisfactory but may not be

optimal for lists and material in table cells however

page-break-inside is unsupported there is little you

can do about it.

A7.3.3.2 Images

Images are the one element that require the state-

ment just made to be modified a little. Images are not

normally broken so, when they will not fit in the space

remaining on a page, a page break will be thrown and

the image will appear on the following page. This is

entirely natural and what would be expected.

A7.3.3.3 Float

Where elements are floated a number of problems

can occur. A simple way to overcome these is to avoid

floating anything on a print style sheet. This is quite

easy to achieve if all floats are done using a class. For

instance, to float something right you might set up a

rule in the general style sheet

.floatr { float: right; margin-left: 4px;

}

while in the print style sheet you might have

.floatr { float: none; }

If you find this over restrictive you need to look at

the problem areas. These are mainly images and tables.

Images contained in block elements (e.g. para-

graphs or divisions) which are floated will behave, as

far as page breaks are concerned, in the same way as

if the blocks (and images) were not floated.

Images placed directly in the body or in non floated

block elements and then floated are liable to be split

across a page boundary or to be truncated depending

on the browser. The simple solution to this is to float

the block in which the image is located if necessary

creating one specifically to hold it.

Floated tables appear prone to a variety of prob-

lems including locking up browsers. Avoid if at all

possible.

Long columns, as used for instance in some layout

schemes, are to be avoided if they are likely to overflow

from one page to the next.

As usual the advice is avoid if possible otherwise

check, check and check again.

A7.3.4 Browsers

Pages and style sheets designed as suggested will

be rendered satisfactorily, though not perfectly, on

most browsers. At the time of writing (late 2007) all of

the major browsers have difficulty with some aspect of

print styles. Authors should not hope to be really

prescriptive about how the final output appears. Web

Devout [Ref 2]has a useful page detailing Web browser

CSS support. Coverage will undoubtedly improve with

time.

A7.3.5 Development aid

Readers will know that KompoZer masquerades as

a passable browser. This can be pressed into use when

developing print style sheets. For testing purposes,

once the style sheets have been linked in the correct

order it is simple to relink the print style sheet as an

'all' style sheet (reversing the process described in

A7.1.2.1). After closing and reloading the file the Nor-

mal view or Preview mode then become print view

modes. The style sheet can then be refined while

immediately seeing the result. Don't forget to change

back to 'print' before finalising!

A7.4 References

[1] CSS2 Specification http://www.w3.org/TR/CSS21/ introduces media in section 7 and covers paged

media in section 13

[2] Web Devout http://www.webdevout.net/browser-support-css has a useful page detailing CSS support

for several modern browsers.

[3] WestCiv http://www.westciv.com/style_master/academy/browser_support/index.html has summary

information about a wide range including older browsers .

A number of sites cover various aspects of printing though none are at all comprehensive.

[4] A List Apart http://www.alistapart.com/articles/alaprintstyles has an excellent article by Eric Meyer on

choosing styles for printing. Probably the best available.

[5] About http://webdesign.about.com/cs/css/a/aa042103a.htm gives a general introduction by Jennifer

Kyrnyn to considerations for printed pages.

[6] Opera offers some useful general information.

http://dev.opera.com/articles/view/making-small-devices-look-great/

[7] WestCiv offers more specific information about @page and page properties.

http://www.westciv.com/style_master/academy/css_tutorial/advanced/printing.html

[8] Rich in style has a fairly informative page about paged media.

http://www.richinstyle.com/guides/fontface2.html This will become more useful when @page is bet-

ter supported.

Missbrauch melden von Frage und/oder Antwort

Libble nimmt den Missbrauch seiner Dienste sehr ernst. Wir setzen uns dafür ein, derartige Missbrauchsfälle gemäß den Gesetzen Ihres Heimatlandes zu behandeln. Wenn Sie eine Meldung übermitteln, überprüfen wir Ihre Informationen und ergreifen entsprechende Maßnahmen. Wir melden uns nur dann wieder bei Ihnen, wenn wir weitere Einzelheiten wissen müssen oder weitere Informationen für Sie haben.

Kompozer 07 Seite 56

Brauchen Sie Hilfe? Stellen Sie Ihre Frage.

Missbrauch melden von Frage und/oder Antwort

Art des Missbrauchs:

Forenregeln

Neu registrieren

Andere Handbücher von Kompozer 07

Das Handbuch wird per E-Mail gesendet. Überprüfen Sie ihre E-Mail.

Ihre Frage wurde zu diesem Forum hinzugefügt

Info