-
Notifications
You must be signed in to change notification settings - Fork 0
/
known-issues.xml
91 lines (89 loc) · 3.66 KB
/
known-issues.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
<?xml version="1.0" encoding="UTF-8" ?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- $Id$ -->
<known-issues>
<known-issue>
MIF and SVG output support have not been restored, yet.
</known-issue>
<known-issue>
RTF output is inferior to other output formats supported by FOP.
For details, please see the "Output Targets" page of the release
you're using.
</known-issue>
<known-issue>
Auto table layout is not implemented, yet.
</known-issue>
<known-issue>
Footnotes may overlap with text of the region-body in multi-column
documents.
</known-issue>
<known-issue>
Space resolution does not work between footnote regions.
</known-issue>
<known-issue>
There's a problem involving nested block-containers and
reference-orientation 180/-180 (<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=36391">Bugzilla #36391</a>)
</known-issue>
<known-issue>
block-containers with no height currently don't create a fence for
spaces as they should (they behave like a normal block).
</known-issue>
<known-issue>
Preserved linefeeds in fo:character are not handled correctly.
</known-issue>
<known-issue>
An empty block currently produces a fence for stacking constraints
which it shouldn't.
</known-issue>
<known-issue>
There are several small problems around white space handling.
</known-issue>
<known-issue>
Images currently don't shrink so they fit on a page when they are
too big and shrinking is allowed to happen.
</known-issue>
<known-issue>
inline-container may not work as expected.
</known-issue>
<known-issue>
letter-spacing and word-spacing properties may not work as expected.
</known-issue>
<known-issue>
leaders with leader-pattern="use-content" may not work as expected.
</known-issue>
<known-issue>
keep-with-previous doesn't work inside tables and lists, yet.
</known-issue>
<known-issue>
If two consecutive pages don't have the same available width, the
content currently isn't properly fit into the available space on
the new page.
</known-issue>
<known-issue>
background-images on page-number-citations are not placed correctly.
</known-issue>
<known-issue>
Not all FO elements can be referenced by their "id", most notably:
table-body, table-header, table-footer and table-row.
</known-issue>
<known-issue>
Border and padding conditionality are not supported on table-cells, yet.
</known-issue>
<known-issue>
Column balancing in multi-column documents may not work as expected
(<a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=36356">Bugzilla #36356</a>)
</known-issue>
</known-issues>