OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [Fwd: Re: [docbook-apps] Text going out of margins in PDF]

-------- Message original --------
Sujet: Re: [docbook-apps] Text going out of margins in PDF
Date: Tue, 03 Jul 2007 17:39:00 +0000
De: Bob Saggot
Pour: Vincent Hennebert


See the bottom of pages 2 and 3.  Thanks for taking a look at this.


>From: Vincent Hennebert
>To: caporale
>Subject: Re: [docbook-apps] Text going out of margins in PDF
>Date: Tue, 03 Jul 2007 09:54:14 +0200
>Hi Joseph,
>caporale a écrit :
> > I'm using FOP 0.93, xsltproc, and DocBook 4.5.
> >
> > Sometimes text appears to almost overlap DocBook's footer line.  I've
> > noticed the problem more when I'm doing lists and especially lists
> > lists. Is there any better way to control this so that text never goes
> > of the margins and into the footer?
>Can you provide a small example showing the problem? Please attach the
>sample DocBook file and the resulting PDF, and state the version of the
>XSLT stylesheets you're using.
>I'd say this is because keep-together is specified on lists, but a quick
>look at the stylesheets didn't confirm that.

<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "file:///c:/db/docbookx.dtd">

<title>SCCGOV Web Style Guide</title>
<publishername>Information Services Department</publishername>
<street>1555 Berger Drive</street>
<city>San Jose</city>, <state>CA</state> <postcode>95112</postcode>
<corpauthor>Information Services Department</corpauthor>
<pubdate>June 5, 2007</pubdate>
<mediaobject id="logo1">
<imagedata scalefit="1" width="1.0in" fileref="logo.png"/>

<mediaobject id="logo2">
<imagedata scalefit="1" width="1.0in" fileref="isd.png"/>
<para>This document is an introduction to the basic functionality of CMA.</para>
<para>Use, duplication, modification, and distribution of the Datawatch User Guide and its accompanying documentation for any purpose is strictly prohibited without express, written permission from ISD.</para>
<para><literallayout>Board of Supervisors: Donald F. Gage, Blanca Alvarado, Pete McHugh, Ken Yeager, Liz Kniss
County Executive: Peter Kutras Jr.</literallayout></para>

<revision id="latest">
<date>June 29, 2007</date>
<revremark>Converted to DocBook</revremark>

<date>June 9, 2006</date>
<revremark>Initial version</revremark>

<para>The purpose of this style guide is to offer basic design principles that you can use to make your web content as easy to understand as possible. We explain how to use design as a tool, not as an objective. We give pointers on how to create a user interface that will allow visitors to your site to navigate your content with ease. We offer suggestions on how to write Web documents. All the guidance we offer shares a single purpose: to make your message clear to your readers.</para>

<para>This is not an HTML manual, nor is it a book on graphic design. It is a practical guide to help you design Web sites for the long run.</para>

<para>Please direct technical questions to:</para>

<para><literallayout>ISD Tech Link Center
<para>and comments and suggestions on the Style Guide to:</para>

<para><literallayout>Elizabeth Gorgue

<title>The Web Design Process</title>
<para><xref linkend="sitedevelopmentprocess"/> shows the six steps of the site development process.</para>

<figure id="sitedevelopmentprocess">
<title>Site Development Process</title><mediaobject><imageobject><imagedata fileref="cma1.png" scalefit="1" width="100%" contentdepth="100%"/></imageobject></mediaobject>

    <para>Site Definition and Planning</para>
    <para>The planning process involves defining the site's goals &amp; objectives, production schedule, and staffing.</para>
    <listitem><para>Goals and strategies</para>
        <listitem><para>What is the mission of your organization?</para></listitem>
        <listitem><para>How will creating a Web site support your organization's mission?</para></listitem>
        <listitem><para>What are your two or three most important goals for the site?</para></listitem>
        <listitem><para>Who is the primary audience for the Web site?</para></listitem>
        <listitem><para>What do you want the audience to think or do after having visited your site?</para></listitem>
        <listitem><para>What Web-related strategies will you use to achieve those goals?</para></listitem>
        <listitem><para>How will you measure the success of your site?</para></listitem>
        <listitem><para>How will you adequately maintain the finished site?</para></listitem>
  <listitem><para>Production issues</para>
        <listitem><para>How many pages will the site contain?</para></listitem>
        <listitem><para>What special technical or functional requirements are needed?</para></listitem>
        <listitem><para>What is the budget for the site?</para></listitem>
        <listitem><para>What is the production schedule for the site?</para></listitem>
        <listitem><para>Who is on the development team and what are the roles &amp; responsibilities?</para></listitem>
  <listitem><para>Operations &amp; Maintenance</para>
        <listitem><para>Who is responsible for the content of each page in the site?</para></listitem>
        <listitem><para>How will you ensure consistent editorial, graphic design, and compliance with policies?</para></listitem>
  <listitem><para>Information Architecture</para>
<para>The Information Architecture phase involves building navigation hierarchies and relationships between content items.</para>


  <listitem><para>Site organization</para><para>Detail the organizational structure of the site - ie, the major categories of information used by customers to navigate the site.</para></listitem>
  <listitem><para>Content inventory</para>

    <listitem><para>Inventory existing content - from online and offline sources</para></listitem>
    <listitem><para>Identify content gaps</para></listitem>

  <listitem><para>Web site prototype</para><itemizedlist><listitem><para>Build site prototype</para></listitem>
  <listitem><para>Test site navigation and develop the user interface - include enough pages to assess accurately what it's like to move from menus to content pages.</para></listitem>
  <listitem><para>The prototype allows graphic designers to develop relations between how the site looks and how the navigation interface supports the information design.</para></listitem></itemizedlist></listitem>

<listitem><para>Site design</para>
<para>The goal of the Site Design phase is to produce all the content components and functional programming and have them ready for the final production stage: the construction of the actual Web site pages.</para>
    <listitem><para>Site look &amp; feel elements</para><para>Page grid, page design, and overall graphic design      standards are created and approved.</para></listitem>
    <listitem><para>Site creative</para>
    <para>Illustrations, photography, and other graphic or audiovisual content for the site are commissioned and created.</para></listitem>
    <listitem><para>Content development</para><para>Research, writing, organizing, assembling, and editing the site's text   content is performed.</para></listitem>
    <listitem><para>Technical design</para>
    <para>Any programming, database design and data entry, and search engine design should be well under way by now. </para>
  <para>Typical products at the end of the Site Design stage could include:</para>
  <listitem><para>Content components, detailed organization and assembly</para>
<listitem><para>Text, edited and proofread</para></listitem>
<listitem><para>Graphic design specifications for all page types</para></listitem>
<listitem><para>Finished interface graphics for page templates</para></listitem>
<listitem><para>Header and footer graphics, logos, buttons, backgrounds</para></listitem>
<listitem><para>Detailed page comps or finished examples of key pages</para></listitem>
<listitem><para>Site graphic standards manual for large, complex sites</para></listitem>
<listitem><para>Interface design and master page grid templates completed</para></listitem>
<listitem><para>Finished HTML template pages</para></listitem>


<listitem><para>Functional and logic components</para>

<listitem><para>JavaScript scripts, Java applets designed</para></listitem>
<listitem><para>Database tables and programming, interaction prototypes completed</para></listitem>
<listitem><para>Search engine designed and tested</para></listitem>




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]