arved 01/07/07 22:03:49
Added: src/org/apache/fop/fo/pagination PageNumberGenerator.java
Log:
Supports page-number formatting
Revision ChangesPath
1.1
xml-fop/src/org/apache/fop/fo/pagination/PageNumberGenerator.java
Index
arved 01/07/07 22:04:11
Modified:src/org/apache/fop/fo/pagination PageSequence.java
Log:
Supports page-number formatting
Revision ChangesPath
1.30 +14 -3 xml-fop/src/org/apache/fop/fo/pagination/PageSequence.java
Index: PageSequence.java
arved 01/07/07 22:04:57
Modified:src/org/apache/fop/layout Page.java
Log:
Supports page-number formatting
Revision ChangesPath
1.12 +11 -2 xml-fop/src/org/apache/fop/layout/Page.java
Index: Page.java
arved 01/07/08 13:58:27
Modified:src/codegen foproperties.xml
Log:
Support 'format' property on fo:page-sequence
Revision ChangesPath
1.17 +44 -0 xml-fop/src/codegen/foproperties.xml
Index: foproperties.xml
arved 01/07/08 20:01:15
Modified:src/org/apache/fop/fo/pagination PageSequence.java
Log:
AHS: support 'force-page-count'
Revision ChangesPath
1.31 +97 -6 xml-fop/src/org/apache/fop/fo/pagination/PageSequence.java
Index: PageSequence.java
arved 01/07/08 20:02:43
Modified:src/org/apache/fop/fo/pagination
RepeatablePageMasterAlternatives.java
Log:
AHS: restore ability to do blank pages
Revision ChangesPath
1.5 +2 -2
xml-fop/src/org/apache/fop/fo/pagination
arved 01/07/12 19:30:37
Modified:src/org/apache/fop/fo/flow Block.java
Log:
AHS: addressing break boundary conditions
Revision ChangesPath
1.34 +21 -73xml-fop/src/org/apache/fop/fo/flow/Block.java
Index: Block.java
arved 01/07/12 19:31:16
Modified:src/org/apache/fop/layout Area.java
Log:
AHS: addressing break boundary conditions
Revision ChangesPath
1.20 +5 -1 xml-fop/src/org/apache/fop/layout/Area.java
Index: Area.java
arved 01/07/16 03:35:47
Modified:src/codegen foproperties.xml
Log:
AHS: initial marker support
Revision ChangesPath
1.21 +15 -4 xml-fop/src/codegen/foproperties.xml
Index: foproperties.xml
arved 01/07/16 03:36:48
Modified:src/org/apache/fop/fo FONode.java FObj.java
Log:
AHS: initial marker support
Revision ChangesPath
1.16 +36 -2 xml-fop/src/org/apache/fop/fo/FONode.java
Index: FONode.java
arved 01/07/16 03:37:58
Modified:src/org/apache/fop/fo/flow Block.java
Log:
AHS: initial marker support
Revision ChangesPath
1.35 +13 -1 xml-fop/src/org/apache/fop/fo/flow/Block.java
Index: Block.java
arved 01/07/16 03:43:40
Modified:src/org/apache/fop/fo/flow Marker.java
Log:
AHS: initial marker support
Revision ChangesPath
1.2 +68 -23xml-fop/src/org/apache/fop/fo/flow/Marker.java
Index: Marker.java
arved 01/07/16 03:43:51
Modified:src/org/apache/fop/fo/flow RetrieveMarker.java
Log:
AHS: initial marker support
Revision ChangesPath
1.2 +103 -22 xml-fop/src/org/apache/fop/fo/flow/RetrieveMarker.java
Index: RetrieveMarker.java
arved 01/07/16 03:45:08
Modified:src/org/apache/fop/fo/pagination Root.java PageSequence.java
Log:
AHS: initial marker support
Revision ChangesPath
1.12 +2 -1 xml-fop/src/org/apache/fop/fo/pagination/Root.java
Index: Root.java
arved 01/07/16 03:45:43
Modified:src/org/apache/fop/layout Page.java Area.java
Log:
AHS: initial marker support
Revision ChangesPath
1.13 +12 -1 xml-fop/src/org/apache/fop/layout/Page.java
Index: Page.java
arved 01/07/16 03:46:15
Added: src/org/apache/fop/layout AreaClass.java
Log:
AHS: initial marker support
Revision ChangesPath
1.1 xml-fop/src/org/apache/fop/layout/AreaClass.java
Index: AreaClass.java
arved 01/07/16 20:15:57
Modified:src/org/apache/fop/layout Area.java AreaContainer.java
BodyAreaContainer.java ColumnArea.java
Log:
AHS: improving area information
Revision ChangesPath
1.22 +9 -1 xml-fop/src/org/apache/fop/layout
arved 01/07/16 20:16:29
Modified:src/org/apache/fop/render/xml XMLRenderer.java
Log:
AHS: improving area information
Revision ChangesPath
1.19 +32 -6 xml-fop/src/org/apache/fop/render/xml/XMLRenderer.java
Index: XMLRenderer.java
arved 01/07/22 18:58:56
Modified:src/org/apache/fop/fo/flow RetrieveMarker.java
Log:
AHS: continued work on fo:marker support
Revision ChangesPath
1.3 +54 -19xml-fop/src/org/apache/fop/fo/flow/RetrieveMarker.java
Index: RetrieveMarker.java
arved 01/07/22 18:59:38
Modified:src/org/apache/fop/fo/pagination PageSequence.java
Log:
AHS: continued work on fo:marker support
Revision ChangesPath
1.33 +5 -2 xml-fop/src/org/apache/fop/fo/pagination/PageSequence.java
Index: PageSequence.java
arved 01/07/22 19:00:37
Modified:src/org/apache/fop/layout Page.java
Log:
AHS: continued work on fo:marker support
Revision ChangesPath
1.14 +16 -1 xml-fop/src/org/apache/fop/layout/Page.java
Index: Page.java
arved 01/07/23 17:57:32
Modified:src/org/apache/fop/fo/flow ListBlock.java
Log:
AHS: adding support for 'returned-by'
Revision ChangesPath
1.17 +20 -52xml-fop/src/org/apache/fop/fo/flow/ListBlock.java
Index: ListBlock.java
arved 01/07/23 17:57:57
Modified:src/org/apache/fop/fo/flow ListItem.java
Log:
AHS: adding support for 'returned-by'
Revision ChangesPath
1.13 +27 -60xml-fop/src/org/apache/fop/fo/flow/ListItem.java
Index: ListItem.java
arved 01/07/23 17:58:22
Modified:src/org/apache/fop/fo/flow ListItemBody.java
Log:
AHS: adding support for 'returned-by'; placeholder
Revision ChangesPath
1.9 +9 -49 xml-fop/src/org/apache/fop/fo/flow/ListItemBody.java
Index: ListItemBody.java
arved 01/07/23 17:58:34
Modified:src/org/apache/fop/fo/flow ListItemLabel.java
Log:
AHS: adding support for 'returned-by'; placeholder
Revision ChangesPath
1.9 +18 -58xml-fop/src/org/apache/fop/fo/flow/ListItemLabel.java
Index: ListItemLabel.java
arved 01/07/26 17:18:27
Modified:src/org/apache/fop/render/xml XMLRenderer.java
Log:
AHS: changed signatures
Revision ChangesPath
1.20 +43 -6 xml-fop/src/org/apache/fop/render/xml/XMLRenderer.java
Index: XMLRenderer.java
arved 01/07/26 19:13:24
Added: docs/examples/markers glossary.xml glossary.xsl
Log:
AHS: fo:marker examples
Revision ChangesPath
1.1 xml-fop/docs/examples/markers/glossary.xml
Index: glossary.xml
arved 01/08/09 19:07:05
Modified:.CHANGES
Log:
Changes from 0.18 to 0.19
Revision ChangesPath
1.7 +185 -0xml-fop/CHANGES
Index: CHANGES
===
RCS file: /home/cvs/xml-fop/CHANGES,v
arved 01/08/13 17:16:20
Modified:.build.xml
Log:
AHS: build improvements; version change
Revision ChangesPath
1.39 +3 -5 xml-fop/build.xml
Index: build.xml
===
RCS file: /home
arved 01/08/13 17:17:16
Modified:lib buildtools.jar
Log:
AHS: updated buildtools
Revision ChangesPath
1.9 +189 -204 xml-fop/lib/buildtools.jar
Binary file
arved 01/08/13 17:52:43
Modified:.build.xml
Log:
AHS: need to specifically delete tarfiles after all
Revision ChangesPath
1.40 +1 -0 xml-fop/build.xml
Index: build.xml
===
RCS
arved 02/02/09 17:51:22
Removed: lib Tag: fop-0_20_2-maintain jimi-1.0.jar
Log:
Remove for license reasons
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
arved 02/02/09 17:51:50
Removed: lib Tag: fop-0_20_2-maintain jimi-License.txt
Log:
Remove for license reasons
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
arved 02/02/09 17:52:35
Added: lib Tag: fop-0_20_2-maintain BSF.license.txt
Log:
Proper license for BSF
Revision ChangesPath
No revision
No revision
1.1.2.1 +171 -0xml-fop/lib/Attic/BSF.license.txt
arved 02/02/09 18:01:15
Modified:lib Tag: fop-0_20_2-maintain readme
Log:
Indicated changes wrt Jimi
Revision ChangesPath
No revision
No revision
1.4.2.1 +7 -0 xml-fop/lib/readme
Index: readme
arved 02/03/17 09:21:14
xml-fop/docs/design/understanding - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
arved 02/03/17 09:21:53
Added: docs/design/understanding area_tree.xml book.xml fo_tree.xml
handling_attributes.xml images.xml
layout_managers.xml layout_process.xml
pdf_library.xml properties.xml renderers.xml
arved 02/03/17 09:22:16
xml-fop/docs/design/alt.design - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
arved 02/04/23 15:22:53
Modified:src/codegen Tag: fop-0_20_2-maintain foproperties.xml
Log:
support for background-image (all renderers)
author: Michael Gratton
Revision ChangesPath
No revision
No revision
1.25.2.3
arved 02/04/23 15:23:39
Modified:src/org/apache/fop/fo Tag: fop-0_20_2-maintain
PropertyManager.java
Log:
support for background-image (all renderers)
author: Michael Gratton
Revision ChangesPath
No revision
arved 02/04/23 15:24:45
Modified:src/org/apache/fop/fo/flow Tag: fop-0_20_2-maintain
Block.java BlockContainer.java ListBlock.java
Table.java TableBody.java TableCell.java
TableColumn.java TableRow.java
Log
arved 02/04/23 15:25:25
Modified:src/org/apache/fop/fo/pagination Tag: fop-0_20_2-maintain
RegionAfter.java RegionBefore.java RegionBody.java
RegionEnd.java RegionStart.java
Log:
support for background-image (all renderers)
author
arved 02/04/23 15:33:40
Modified:src/org/apache/fop/render/awt Tag: fop-0_20_2-maintain
AWTRenderer.java
src/org/apache/fop/render/mif Tag: fop-0_20_2-maintain
MIFRenderer.java
src/org/apache/fop/render/pcl
the PDFs to disk.
Netscape (4.08, even, I might add, which I use) very cleanly displays the
PDF document in the browser, and also saves perfectly well. No refreshing
needed.
This is with the latest Acrobat Reader (standalone and browser plugins): 5.0.
Regards,
Arved Sandstrom
P.S. How is it that lots
At 11:31 AM 6/8/01 +0200, Bertrand Delacretaz wrote:
On Friday 08 June 2001 11:02, Alex McLintock wrote:
I think the best way to pay for open source development of FOP is if
development takes place in response to real life business requirements.
Quoting Arved, ...trying not to waste time
checking out if you
haven't. I have to grudgingly admit that this is darned handy, and I'm sure
that a lot of users would like this kind of graphical interface to FOP.
So this is something maybe to interest you.
Regards,
Arved
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless
the approach required to handle
reference-orientation and writing-mode.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
-
To unsubscribe
At 12:08 AM 6/28/01 -0300, Arved Sandstrom wrote:
A side-float becomes a child of the nearest ancestor reference area (I still
need to figure out what the hell the spec means by reference area chain,
so this may change). This will usually (but not always) be a column area
within a span area
a last patch
of his to commit, which is causing me some aggro at the moment); it may be
that your use of FOP can take some advantage of that.
Regards,
Arved Sandstrom
--
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Halifax, Nova Scotia
Wireless * B2B * J2EE * XML
over the next few days.
We also have a number of FT (or nearly FT) developers at the moment - I
think their input on this is critical.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
At 06:40 AM 6/29/01 -0500, Weiqi Gao wrote:
On 29 Jun 2001 06:37:00 -0300, Arved Sandstrom wrote:
FOP2 is the term for a completely new layout engine, and so maybe
we don't really want to call the thing FOP2. Suggestions? I'll
call it FOP1+ for now.
Please spare us of the confusion
one set of contiguous N characters
to another contiguous set also of length N. The best way to edit PDF, in
general, is to edit the source and re-generate.
Regards,
Arved Sandstrom
At 05:53 PM 7/2/01 +0800, Art Simcoe wrote:
Thanks Alex,
I have been doing just that, sifting through hundreds
have
put in there already to some degree); someone may not be interested in
levels below regions, someone else might want down to blocks, someone else
may want everything right down to inlines in agonizing detail.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e
with WinZip just as easy as if it was ZIP, and
they wouldn't even know the difference. Because I'll guarantee this is a
person on Windows.
Regards,
Arved Sandstrom
At 06:40 PM 7/10/01 -0500, Weiqi Gao wrote:
On 10 Jul 2001 23:11:30 +0200, Petr Andrs wrote:
Why? tar.gz is much smaller and does
, and let's say that you use sections, and
you put a break-before=page on every section title; if a section leads off
a page-sequence, which is pretty likely, then you would get an extra unwanted
blank page. This should now be fixed.
Regards,
Arved Sandstrom
--
Fairly Senior Software Type
e-plicity
to jump through right now to answer
basic questions...it would be nice to obviate the necessity for that.
Any insight you can bring to bear on this would be appreciated. I'd
personally be happy to assist with integrating your tree stuff into FOP.
Regards,
Arved
--
Fairly Senior Software Type
e
to get his stuff into CVS. How about
we see what develops over the next week, and no matter what, do a release
next weekend? That is the 21st-22nd.
Arved
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
on [EMAIL PROTECTED], it was due to many, many
people trying to do what you were doing.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
to consider is stopping the process after refinement, but before
layout, if there are any content-model errors. Or maybe all of this can be
subject to user control?
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax
responsible for changing the checkBreakBefore() signature, so I'll
apply the patch. Odd that it didn't show up as an error during my builds
(Ant/javac dependency checking is a bit spotty). Thank you.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless
before you render page-sequence N. All that's going on there is,
if the force-page-count property on page-sequence N is auto, it needs to
know about the initial-page-number property on page-sequence N+1. This
doesn't require any formatting to take place at all.
Regards,
Arved Sandstrom
Fairly
) are
properly set on all areas we generate/return is much more of a task, but we
have to start somewhere.
As I say, everything should build, and existing stuff shouldn't notice any of
this. Please let me know if that is not the case.
Regards,
Arved Sandstrom
--
Fairly Senior Software Type
e
is an oversight, more often than not.
We should also comment qualifier choices if they don't make obvious sense
within the context of their own class.
Regards,
Arved Sandstrom
At 09:38 PM 7/16/01 +1000, Mark wrote:
Hey there foptologists
I was just wondering if there has been any discussion about
a style tool to the whole
codebase, strip out all tabs, and re-commit the whole thing. :-)
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
at BlockArea level; leave it out and
you'll see everything.
Regards,
Arved Sandstrom
--
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Halifax, Nova Scotia
Wireless * B2B * J2EE * XML
-
To unsubscribe, e-mail: [EMAIL
will appear?
As an aside, we are clearly not talking about extensions. Separate issue. I
think those are fine.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
to adhere to code conventions.
It would be useful if you can work in license long-form - short-form
translation also.
A tag is a good idea, I agree. Who knows what might happen?
Thanks in advance for doing this.
Regards,
Arved
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com
...still
no joy?
Can you run your current Ant on other build files?
What version of Ant are you using? Try Ant 1.3 if all else fails.
Just some starter ideas. I'm sure we'll get to the solution sooner or later.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e
is the lack of design documentation - docs
diagrams. Another real problem is that we are operating sort of at a CMM
Level 1 - the project is succeeding because of individuals and not because
of process. All stuff we need to talk about, definitely.
Regards,
Arved
Fairly Senior Software Type
e-plicity
Ant 1.3 if all else fails.
I just installed the 1.3-2 RPMs for Ant from jakarta.apache.org,
but it seems to me from build.sh that a private version of ant.jar is
used...
Hmmm, we're talking about UNIX and strange lack of evidence...permissions on
directories?
Regards,
Arved
Fairly Senior
] stuff) to another
email address of your choice. You will then find out about these kinds of
things right away.
I didn't do this until recently myself. :-)
Regards,
Arved
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
, at
this point in time I would avoid doing stuff like this, and if it happens to
turn out to your satisfaction, enjoy it while it lasts, because it could
change.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova
the
corresponding scaled content-width and content-height, and overflow is
'hidden' or 'scroll'.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
. :-)
This is interesting and I'll see what I can find out further.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
-
To unsubscribe, e-mail: [EMAIL
,
incidentally.
Assuming that you are using the very latest CVS, would it be too much to ask
if you could post an FO example that does not work for you? At the very
least I could explain why, and how I intend to fix it (and when).
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity
At 01:46 AM 7/28/01 +1000, Peter B. West wrote:
Arved Karen,
On the surface of it, this re-parenting issue looks like a tree
operation. The point of definition of the marker remains in its context
at the point of definition. When a retrieve-marker is found, the marker
sub-tree is attached
-produced doc using _Reader_? As
soon as FOP produced it?
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
-
To unsubscribe, e-mail
the rest of the patch to Block, AreaTree, Page, and TestConverter,
right? Just trying to get my head straight. :-)
Regards,
Arved
P.S. Thanks for the yeoman effort.
--
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Halifax, Nova Scotia
Wireless * B2B * J2EE * XML
of page-numbering is to already do what you want to
do (the default behaviour of 'initial-page-number'). The aforementioned
properties happen to give you extra flexibility.
Also check out the 'format' property...
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e
to
alpha. All points you made yourself. Thanks.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
-
To unsubscribe, e-mail: [EMAIL
come close to the
equivalent of one (1) FT resource, current circumstances excepted. Writing an
XSL formatter is a big deal, and if I was estimating such a project from
scratch I'd give it 2 person-years of _effort_ easy (maybe more). So it's no
surprise that we are where we are.
Regards,
Arved
-sequence could have different
page-masters and different headers, footers and sidebars.
There should be some examples in FOP already, under docs/examples.
Regards,
Arved Sandstrom
--
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Halifax, Nova Scotia
Wireless * B2B * J2EE * XML
for docs?
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email
mean are we interested in well-known, stable interfaces for invoking FOP,
configuring FOP, and plugging in different renderers, yes, we already pretty
much have an API. Although it's always open for improvement.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e
a bit. Sorry.
Regards,
Arved Sandstrom
At 01:30 AM 8/2/01 -0500, Runar Bjarnason wrote:
Ok, I admit I haven't been looking at the source code very long, but I've
been somewhat frustrated with some of the things I'm trying to accomplish
with FOP. For instance, the Driver class only has void methods
a lot of familiar editing features in a package that is much smaller
and appreciably faster.
The other features are on a par with other leading text editors.
Regards,
Arved Sandstrom
--
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Halifax, Nova Scotia
Wireless * B2B * J2EE
I can build the
release itself. But for anyone wrapping up loose ends, you can certainly
assume next weekend and no earlier.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
it is better to duplicate and add classes to support
this rather than to modify any existing classes, like FOText, because they
are too central. But one could make the argument that FOText itself maybe
needs work, so why _not_ modify it for the general case?
Regards,
Arved Sandstrom
Fairly Senior
be in there.
Regards,
Arved
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
can be of great assistance here.
Thanks,
Arved
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
that they are supposed to) that is rather more of an obstacle. I
have some ideas in regard to how you might want to tackle the problem you
describe and will elaborate this evening.
Regards,
Arved Sandstrom
At 09:38 AM 8/7/01 +0200, Keiron Liddle wrote:
Your help is very welcome.
Unfortunately
on the XML PMC...it would be nice to hear constructive suggestions
rather than snide comments.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
to the suitability and serviceability of the distributions?
I am still (and have been for quite a while) very undecided about whether to
include Javadoc (size considerations). Perhaps in the source distro only?
Comments?
Regards,
Arved Sandstrom
--
Fairly Senior Software Type
e-plicity (http://www.e
(I would
think) is a consideration.
Regards,
Arved
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
features and
limittaions, and that's it.
Arved wrote
I look at OS projects like Subversion and I'm green with envy.
Well on theirs site, they has a section devoted to well define specific
task that need to be done.
Thats something we should do for fop site as well.
For instance, it could be nice
on this.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email
At 09:59 AM 8/13/01 +0200, Keiron Liddle wrote:
On Mon, 13 Aug 2001 03:27:37 Arved Sandstrom wrote:
Confirmed, on all counts:
1) NPE running your 'dsrb2' example, something to do with the lazy font
code
it looks like;
2) 500 K file for 17 pages with your 'emp' example. I'm not familiar
be the default). I think that for a
number of reasons it is useful to keep the debugging capability available.
In any case, it would be nice to have a configurable xml diff utility that
can be set up to ignore certain attributes.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http
Thank you, I'll get this up into CVS soonest. My fault in the first place.
Regards,
Arved Sandstrom
At 09:27 AM 8/15/01 +1200, Struan Judd wrote:
Specifically if you have any of ampersand, greater-than or less-than symbols
in text they will not be escaped as per the XML spec.
Correcting diff
that is not far off.
4. Just for curiosity, why isn't there a HTMLRenderer?
Lack of interest? I wouldn't recommend production of HTML from FO myself.
Regards,
Arved Sandstrom
Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia
1 - 100 of 279 matches
Mail list logo