db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (DERBY-2628) WARNING involving LineLayoutManager$LineBreakingAlgorithm
Date Wed, 10 Sep 2014 18:53:33 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128777#comment-14128777

Kim Haase edited comment on DERBY-2628 at 9/10/14 6:52 PM:

The number of occurrences at present is as follows.

adminguide 44
devguide 12
getstart 0
ref 251
tools 13
tuning 1
security 17

Problem seems not to be solvable with current tools.

was (Author: chaase3):
There are now 44 occurrences of this warning in the Admin Guide; I haven't checked elsewhere.

Problem seems not to be solvable with current tools.

> WARNING involving LineLayoutManager$LineBreakingAlgorithm 
> ----------------------------------------------------------
>                 Key: DERBY-2628
>                 URL: https://issues.apache.org/jira/browse/DERBY-2628
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kim Haase
>            Priority: Minor
>              Labels: derby_triage10_5_2
> A warning like the following appears during the PDF generation of most of the manuals:
>       [fop] May 8, 2007 9:48:41 AM org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm
>       [fop] WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location:
> It appears the following number of times for each manual. The only part of the message
that varies is the location information:
> adminguide: 16
> devguide: 16
> getstart: 0
> ref: 125
> tools: 4
> tuning: 0
> Most of the warnings appear near the end of the PDF generation process, except for two
of the Reference Manual warnings, which appear at the beginning.
> Although the warning does not seem to affect the correctness of the generated output,
it would be helpful to know how to get rid of it, either by correcting the DITA source or
by fixing the toolkit in some way. The number of errors is a particular nuisance for the Reference

This message was sent by Atlassian JIRA

View raw message