umber citations lead to a line break (in a book index),
so adjusting the line area might not be enough.
J.Pietschmann
straightforward
to implement.
J.Pietschmann
Jeremias Maerki wrote:
(It's probably best to collapse "Development" and "Design" into one tab.
Too many tabs are not ideal.
I second that.
J.Pietschmann
of
identifier building rules, it is a subclass of IOException. This is
certainly convenient at places, and in some sense even justifiable
(if you want to see RTF generation as part of an output process, just
like encoding characters into bytes). However, I think this should be
redesigned.
In order to suggest further changes, a closer look at the places where
a FOPException is thrown, and, more important, where exceptions are
caught, is necessary.
== Final Word ==
Did I miss something important?
Regards
J.Pietschmann
way.
If page numbers can be resolved to strings early, it should be
done. All the hassle for space readjusting, and perhaps reflowing
content, should be reserved for forward references, if only for
performance reasons.
J.Pietschmann
plified
as an index is usually set in several narrow columns.
J.Pietschmann
Very interesting indeed ... as soon as I finish working on the
line-adjusting I'll spend some more thought on this ...
Sounds like we'll get more improvements soon...
J.Pietschmann
d IOException as necessary. Yes, this hurts.
- Do something about PDFFilterException.
- Should we use IllegalArgumentException for sanity checkings
in the public API classes (not FOTree, layout or anything deeper
down), e.g. for enumerations for renderers which aren't known?
I'm undecided. Some JRE packages do so.
That's all for today
J.Pietschmann
agent.
Provide a mechanism so that the user can turn recoverable errors and
warnings into fatal errors, preferably individually.
J.Pietschmann
each other) must be really really fun.
J.Pietschmann
object pooling, in particular network connection pooling
and multiplexing
- XML creation
- Java object persistence
The list isn't complete of course.
J.Pietschmann
your setup?
J.Pietschmann
like to nominate him for
committership in Apache FOP.
+1 from me.
J.Pietschmann
I'll probably move all jars to ~/.ant/lib and point
optional.lib.dir there. Grmbl.
J.Pietschmann
50 lines!
Next question: I used to have old (maintenance branch) jars
for FOP and Batik in the repository, which causes compilation
problems. Therefore it might be a good idea to include only
specific fles rather than *.jar in the classpath set. WDYT?
J.Pietschmann
siarom egrub wrote:
Could you please advise on how to get a table centered
on a page?
This is a FAQ, either
http://xmlgraphics.apache.org/fop/faq.html#fo-center
or
http://xmlgraphics.apache.org/fop/faq.html#fo-center-table-horizon
J.Pietschmann
s and number of generated pages.
I don't think that generously sprinkling log.stuff() statements all
over the place is the best solution to the problems above, even though
this seems to fit.
J.Pietschmann
ocompletion features of modern IDEs,
long identifiers shouldn't impair typing too much.
I'll probably expand randomly choosen names in the future, which
may include class names. Tell me now if you don't like this.
Regards
J.Pietschmann
may be people with JCE
providers other than bouncy castle.
J.Pietschmann
Manuel Mall wrote:
I noticed we don't have any hyphenation testcases in the layout engine test
suite.
I'm working on that, as well as on test case for TR14 compatible
line breaking (not yet implemented though...).
J.Pietschmann
hink there is a difference between leaders using the dot character
(for the "foo...page 19" style) and a leader which is a dotted line
(rule-style=dotted). THe rule-thickness only applies to the second
leader style.
J.Pietschmann
errytech.com/xsl/xsl-list/
J.Pietschmann
Hi all,
fresh on freshmeat:
http://freshmeat.net/releases/207188/
Can this be used to provide tests for the PDF renderer?
J.Pietschmann
if this sounds suboptimal.
J.Pietschmann
ther this got into
0.20.5, and I can't currently test it. Does someone else have
a 0.20.5 installation ready to run to do a quick test?
J.Pietschmann
ewhat blank
now...
J.Pietschmann
umLen
- offDocumentItems
- paddingPt
- pgNbField
- pixSzMM
- propEx
- relbase (but relativebase used elsewhere)
- resSpace: reserved? resolved? reset? randomly enhanced space?
- rightPadStr
- rslt
- setDW
- setDoOutput
- sPM
- spMaker
- trIter
- transFactory
- uniMap
- xRefFormats
HTH
J.Pietschmann
me sort of Jakarta commons
Unicode file component, but the guys there weren't all that
enthusiastic about this, and I've not enough time to get
the ball rolling all of my own.
J.Pietschmann
Manuel Mall wrote:
What we also need for proper script support is a mapping from Unicode
code point to script.
On a second thought: isn't this what Class Character.UnicodeBlock
does?
J.Pietschmann
isn't easily
understandable from the spec or the errata, IIRC Peter made
an inquiry on a w3c list and got a clarification.
J.Pietschmann
Manuel Mall wrote:
It doesn't quite solve all issues though I think:
Correct.
May be a wrapper around this class to provide that functionality?
Given that we must get data from Unicode files anyway, we
could as well have our own implementation for everything.
J.Pietschmann
rapper.
I still wonder: creating no line breaks at all should be
significantly easier than creating breaks...
J.Pietschmann
tput must be an OutputStream, so this is not character compatible
but byte only compatible, it seems unicode cannot be processed correctly ?
PDF isn't text, it is a binary format. For details, check the PDF spec.
J.Pietschmann
yphenation) in a single pass is
unwieldy if BreakIterator is used, that's why I tried to implement it
differently some time ago
http://people.apache.org/~pietsch/linebreak.tar.gz
J.Pietschmann
eaking property SY, it is actually quite
complex as it does not allow a break within a sequence of digits, e.g.
26/10/2005 and discourages breaking things like "w/o" or "A/S".
Oops! I should have read further.
J.Pietschmann
l that the hyphenation code collects words across LM
boundaries.
As it should. Word boundaries and FO boundaries are different things:
A word
J.Pietschmann
using a
BreakIterator or something, or looking up the line break Unicode
properties and looking up whether a break may occur in the
line-break matrix. Hyphenation points are generated elsewhere and
remain unaffected.
J.Pietschmann
operties
- paragraph separator U+2029
- bidi control characters 200E-200F, 202A-202E
- deprecated controls 206A-206F
J.Pietschmann
erwise
the string including the trailing spaces will overflow the line area.
The trailing whitespace may also influence text justification.
J.Pietschmann
at finding line break opportunities and handling white
space are different things, and can be handled nearly independently.
Note that white space removal around line breaks happend after a break
opportunity has been actually "promoted" to a real line break.
J.Pietschmann
e.g. Soft Hyphen (its either
suppressed or replaced by the proper hyphen), zero-width joiners, ...
In case of the hypothetical HTML renderer, you *want* to pass all these
characters to the renderer.
Is that a sensible grouping?
Dunno.
What about character composition/decomposition?
J.Pietschmann
normalization.
J.Pietschmann
ously,
putting the precomposed character U+00E4 into the output is
a smart move. Where should this transformation occur: output
generation, renderer, layout stage? A slight problem is that
the width of U+00E4 may be different from U+0061.
J.Pietschmann
nds b).
J.Pietschmann
Manuel Mall wrote:
Ooops, that wasn't very efficient as I did more or less the same thing.
Oops, sorry. After several weeks of inactivity I thought
I could polish up the old sketch and commit. There's still
enough work to do though, see the separate post.
J.Pietschmann
cruft from
the Java source and the build.xml soon.
BTW. Ant 1.6.1 complains: build.xml:808: The type doesn't
support the nested "condition" element.
Do we really need a bleeding edge ant? (although the Ant people could
be a bit less aggressive with adding features in minor releases too).
J.Pietschmann
The references have been generated too, and there are two
invalid references now. I was unable to locate the specific bugs
(dind't try hard though), can somebody please correct them?
J.Pietschmann
rc_url testcase
Suggestions? Should we just remove it?
I've disabled it. People without restrictions could reenable the
testcase for themselves. Alternatively, we could add FOP extensions
allowing for proxy authentification.
J.Pietschmann
to create another category of tests, "tests unsafe for people without
internet connection" or so.
J.Pietschmann
ding other authorization and session problems.
J.Pietschmann
Parker, Les wrote:
I am looking for a java class to web-enable PDF files.
Does anyone know of such an animal that is Open Source?
Check SourceForge. IIRC iText and PDFBox both can be configured
to generate linearized PDF.
J.Pietschmann
s
the expected page number in case the static content is used
on more than one page?
J.Pietschmann
=== Remaining in FOUserAgent ===
...
* PDF!EncryptionParams
I'd like to fold these into a more generic Properties object holding
stuff to be passed to the renderers (i.e. the character encoding for
the text renderer). Does this sound sensible?
J.Pietschmann
to pass command line values to the
renderer.
BTW: encryption options like noprint should as well be configurable,
and there are arguments that even the user password for encryption
could benefit from being read from the XML configuration data.
J.Pietschmann
e existing renderer
options Map this is possible.
No problem. I just had a vague memory that properties can automatically
convert strings into boolean values.
J.Pietschmann
r to build the FO tree including metadata and embedded foreign
data?
J.Pietschmann
Jeremias Maerki wrote:
I'm considering removing the "character" area tree object and instead
map an fo:character to a normal text area with one word child.
Looks ok: +1
J.Pietschmann
Jeremias Maerki wrote:
Yep, that's exactly what I need. But hey, adding a 3MB library just for
this method, that is a little much.
If all else fails, do the same as for the line breaking properties.
J.Pietschmann
roposed
several times for various purposes. Algorithms based on ICU presence
could be preferred, while falling back to a more crude implementation
if ICU is not presend.
BTW ICU has lots of other interesting features relevant for I18N,
look for example at the calender section or the number formatting.
J.Pietschmann
Jeremias Maerki wrote:
On 28.02.2006 21:48:27 J.Pietschmann wrote:
If all else fails, do the same as for the line breaking properties.
Sorry, but I don't understand what you mean.
Generate the necessary data tables directly from the Unicode
source, automatically or manually. Yes
advantage over using the Java
BreakIterator (other than the latter not being available in Java 1.3).
I'd prefer to have a more "pull style" interface to the line break
finder though.
J.Pietschmann
Jeremias Maerki wrote:
1. I'd like to propose merging back the Temp_API_Finalization branch
back into Trunk.
+1
2. ...
+1 from me for deprecating all Fop constructors,
+1
J.Pietschmann
Jeremias Maerki wrote:
[snip]
+1 to a new beta release, even if the whitespace still isn't
resolved completely.
J.Pietschmann
lt or in a fo:declarations (extension element). PIs are
also an option, they may enhance portability (ignored by other
software than the target processor) but may confuse users about
the scope where they apply and may provide surprises if read
too late in a streaming processing mode.
J.Pietschmann
[EMAIL PROTECTED] wrote:
Added: .../fop/render/afp/exceptions/NestedRuntimeException.java
^^
Ow. Don't we have that already somewhere else in the code?
J.Pietschmann
control should be
done on the page master level. I'm still somewhat uneasy with
the chain of indirections/mappings necessary, these things tend
to break unexpectedly. But I don't have a better solution either.
J.Pietschmann
(e.g. class
names like FOPException vs. FopFactory).
J.Pietschmann
to ease the
transition. If the API is really declared "stable", the beta tag can
be dropped from the release number even for a pre 1.0 release.
Should we hold a formal vote on the API style issue? Either way, I'd
even volunteer to do the changes (it's easy enough :-).
J.Pietschmann
rther progress. I brought this
topic up only because this seems to be the very last chance for
changes. If everybody is ok with as is, then just go forward.
J.Pietschmann
Jeremias Maerki wrote:
Anyone else?
No way. Sorry, family and the day job take all the time.
J.Pietschmann
d that little detail that the weak reference is on the key, not
the value.
Oops, my fault.
J.Pietschmann
Jeremias Maerki wrote:
+1 for PCL
+0 for AFP (I didn't have time for even a quick glance at it).
J.Pietschmann
ofessional
tool) is better.
J.Pietschmann
Vincent Hennebert wrote:
A line-area is a block-area
I doubt this. Last time I read the spec, I got the impression
that lines are not explicit block areas.
J.Pietschmann
ing anyway.
J.Pietschmann
Andreas L Delmelle wrote:
Yeah, and taking into account that quite a lot of people forget to
remove the indent attribute from xsl:output once they know the FO to be
generated correctly...
I don't think it's all that bad. The indent attribute has no effect
unless the output of the XSLT is seria
issue... :-)
J.Pietschmann
rule base approaches
This concerns probably mainly the base* settings
- Provide a GUI application for changing commonly changed settings
- Get commonly changed settings from a file with an easier format,
like Java properties
Did I get the problem right?
J.Pietschmann
Simon Pepping wrote:
No UML diagrams for FOP available. Would be nice though.
As soon as I get some spare time, I'll try
http://sourceforge.net/projects/umldot
I suspect the diagrams to be somewhat unwieldy.
J.Pietschmann
for wide tables/images" problem. The difference
to explicitely switching page masters is that some other content
before/after the wide FO may flow onto the page, thereby avoiding
unpleasant white areas on the page before and on the last page of the
wide element.
Please tell me if you need clarifications on any of the points.
J.Pietschmann
tes the FO processor implementation. :-P
J.Pietschmann
the renderer
has to undo some of the mirroring done while constructing the FO tree.
J.Pietschmann
Vincent Hennebert wrote:
Comments are welcome, of course.
I'm quite impressed. The layout improvements are very exciting.
J.Pietschmann
Jeremias Maerki wrote:
Just be prepared that they may wrinkle their noses.
I'd expect them to do exactly this. How should tabs mix with, say,
centered text, or BIDI stuff? I'm not convinced it's worth the
additional complexity of the spec.
J.Pietschmann
Jeremias Maerki wrote:
If nobody objects I'm going to remove the deprecated elements in the
apps package later this week.
Umm, couldn't this wait until after the 0.93 release? Well, that's
a question, not a veto. If you think it's a good idea, go ahead.
J.Pietschmann
don't see why the latter should have disabled it.
J.Pietschmann
the line-height or font-size to 0. (if you put
text in such lines, they will look "glued" together)
J.Pietschmann
.
J.Pietschmann
three variants (normal, bold, italic), the normal
variant in 4 sizes, for a total of 7 different font property
bundles). BorderAndPadding might be another case, for example by
using a static immutable instance for the "empty" case.
J.Pietschmann
n in most cases).
Also, 0.20.5 is no longer maintained. Please try a more recent
release.
J.Pietschmann
background-position-vertical
as supported.
J.Pietschmann
ng the FOP servlet
(properly customized) there, and either link or delegate from the ASP
pages to the servlet.
J.Pietschmann
then to prepare metrics file for this font as well
in the same way as for let say Arial?
You can try to use the "-enc ansi" switch and see if it helps.
J.Pietschmann
instead
of a data file.
Links:
http://www.unicode.org/reports/tr14/
http://www.unicode.org/Public/UNIDATA/LineBreak.txt
J.Pietschmann
Simon Pepping wrote:
Herewith I start a vote on this release. The vote will end in 72
hours, that is, on Saturday 30 December 2006 at noon UTC.
+1 from me.
J.Pietschmann
whitespace handling was implemented then.
Unfortunately I lost track how whitespace normalization and
collapsing is handled now. Perhaps setting break marks can be
folded into the whitespace handling loop.
J.Pietschmann
Inline LM the
last and first character of the their preceeding/following LM when
constructing the LM from the FO is also worth a look.
Certainly, but it looks somewhat odd to modify semi-high level
APIs to cater for a much more low level algorithm. I find access
methods more attractive.
J.Pietschmann
Manuel Mall wrote:
However, what about markers. Their content is only known at layout time
isn't it?
That's an "OOPS" factor. However, wouldn't this also be a problem
for the current whitespace handling?
J.Pietschmann
erlined. I
text-decoration were inherited, the decoration of the inner
wrapper would already override underlining.
In order to turn off underlining, one should use
text1
text2
J.Pietschmann
Simon Pepping wrote:
[EMAIL PROTECTED]
I took care of that.
We might need to annotate the lists announcements are sent to by
subscribed team members :-)
Oh, and the Mulberry XSL list seems to have been left out.
J.Pietschmann
1 - 100 of 221 matches
Mail list logo
