Jeremias Maerki wrote:
snip/
I understand that IBM is quite big in the document business. It would be
very interesting if IBM committed to supporting FOP like they do for
other open source projects here at the Apache Software Foundation. As
far as I know IBM even has its own implementation of
Jeremias Maerki wrote:
Hi Jeremias,
I finally have Knuth's Digital Typography and let myself enlighten by
his well-written words. In [1] Simon outlined different strategies for
page-breaking, obviously closely following the different approaches
defined by Knuth. At first glance, I'd say that
Glen Mazza wrote:
Hi Glen,
OH!!! lightBulb state=on wattage=25/
Yes, you're right, Chris--now I see the issue. I
implemented validation for about 80% of the FOs, but
80% is not 100%. fo:table-body never had any
validation implemented, hence the NPE's that were
occurring.
I'm glad this issue
Jeremias Maerki wrote:
On 25.02.2005 07:21:25 Glen Mazza wrote:
snip/
For the moment I'm not going to answer the veto itself. Your veto makes
this situation a one against one. I have presented my reasons for the
change and therefore, I request feedback from the rest of the committers
on this
Jeremias Maerki wrote:
snip/
So here are the proposed changes:
- Package org.apache.fop.render.awt becomes org.apache.fop.render.java2d
- AWTRenderer.java becomes Java2DRenderer.java (AWT*.java -
Java2D*.java)
I think the viewer subpackage can stay as is under the renamed package.
Any objections?
m r dantuluri wrote:
Hi,
I am using FOP 0.15 Version. The PDF files rendered by FOP gives junk
charecters for double-byte languages like korea, japan etc.
FOP 0.15 is ancient. I am fairly confident that I can go as far to say it is
unsupported. Please upgrade to 0.20.5.
When I search in the net
Jeremias Maerki wrote:
Just to be clear. This ArrayOutOfBoundsException is not the same problem
I've described in my earlier post. I just happened to run into both
problems at the same time. Running normal-breaking2.xml with the current
code (without my patch) will result in a document with 1 page
Jeremias Maerki wrote:
Luca (and maybe Finn),
Not forgetting Simon :-)
snip/
Is there some reason why my patch below would make anything worse? It
seems to fix my problem here and all my test cases still pass (at least
the ones that passed before).
I dont know the answer to your question. However,
Jeremias Maerki wrote:
There seems to have been some discussion about this in the CR phase:
http://www.w3.org/2001/08/28-XSL-PR-DOC.html (see comment 20)
It would seem that in the case of reference-area generating FOs
start-indent should simply be inherited (comment 20, item 3). In my
example the
Glen Mazza wrote:
They're coming very close (I suspect in a few weeks at
the latest) to having a Last Call version--would it
be acceptable for you at that stage? I don't mind
waiting a little longer.
Second edition of working Draft was released today :-)
snip/
Chris
Christian Geisert wrote:
Bertrand Delacretaz wrote:
Hi FOP people,
I have the great pleasure to announce that Jeremias Maerki has been
elected as an ASF member at the last member's meeting during ApacheCon.
This is good news indeed for both Jeremias and the FOP project!
Chris
Andreas L. Delmelle wrote:
snip/
Hi fellas,
Well... (sigh)... well ('nutha sigh)
What *does* Finn think, in that case? So far, I've yet to hear a single
*solid* argument pleading against the proposed change. Of course, something
like LM Makers can be added later on --the proposed AreaFactory
Glen Mazza wrote:
snip/
Personally speaking, I am much more amenable to adding
some complexity (LM Makers, for example, or opening up
our validation) if it helps out Finn's work, because
of the sheer weight of contributions he adds to Fop.
(We slow him down, we slow down Fop.) Making these
Clay Leeds wrote:
On Oct 31, 2004, at 7:17 AM, Florian Hecht wrote:
I' ve developed a form extension for XSL-FO for an university project.
It's an extension to FO like the fox extensions. With it you can
declare and define the usual form elements like edit fields, radio
buttons, check boxes,
Clay Leeds wrote:
snip/
When I look at the FOP Compliance page, I see a couple of items which
are implemented (I assume this page is in reference to the
0_20_2-maintain CVS branch--I am I correct in this assumption?).
Hi Clay - yes compliance page does refer to 0.20.5 functionality.
snip/
Chris
Schmitt, Christian (ext.) wrote:
Hi,
while updating our project I found this one bug where the
color for SVG text elements wasn't set correctly.
The patch below should fix that.
Hi Christian,
thanks for submitting your patch. I have created a bugzilla entry and attached
your patch to it. You
Glen Mazza wrote:
OK -- PDF 1.4 it is. I agree with supporting Acrobat
V5. However, I don't see backwards compatibility
concerns as much of an issue here, given the Acrobat
Reader is free and pretty easy to download.
Glen,
you are right that AR is free and easily available. However, large
Townsend, Pete wrote:
Dear fop-dev,
The AFP renderer has now been added to sourceforge
http://afp-renderer.sourceforge.net and a release is available for download
compatible with FOP 0.20.5, please could you close the patch on bugzilla
31213 (or direct them to the above link) so that people don't
Simon Pepping wrote:
snip/
My interest in FOP's layout is mostly theoretical. I cannot get
enthousiastic about todo lists, time schedules and time estimates.
Thats understandable.
I would like to see keep and break properties implemented. They are
the raison d'être of the new design. I do not
J.Pietschmann wrote:
Simon Pepping wrote:
I propose that we make Luca Furini a member of the FOP team.
+1 for me too.
Chris
Jeremias Maerki wrote:
Looks like we don't get any more votes. Let's see:
+1 from:
Simon Pepping, Clay Leeds, Jeremias Maerki, Oleg Tkachenko, Finn Bock,
Glen Mazza, Christian Geisert, Joerg Pietschmann, Bertrand Delacrétaz.
(9 votes)
cough, cough. I did vote too. Sorry to be picky, but I want to
Jeremias Maerki wrote:
Sorry, Chris, I don't have your vote on my radar [1]. Must have gone
lost somewhere.
Thats Ok, I cant find it in the archives either, but it is in my sent items -
odd really.
Chris
Team,
I have been trying to work out what is left to do be done before we can do an
initial release of HEAD, 0.3, say. I know some of you will prefer to aim for a
1.0 and get everything right first time, but please bear with me.
I have consolidated the layout issues from [1] and [2] The
Anton Tagunov wrote:
Hi, gang!
I'm Anton Tagunov, a committer with Avalon and Excalibur
apache projects. I'm afraid I have not been much active
withing these projects lately, but I've still got the commit
priviliges and an active apache account.
Welcome.
I have a full understanding of current
Anton Tagunov wrote:
amendment:
It really is not such a nonsense as it may seem, Tomcat
3.x.y piecfully co-exist with 4 and 4 coexists with 5.
The trouble is everyone always focuses on 0.20.x to the detriment of 1.0
development. Going for the low hanging fruit in 0.20.x may help fix a few
minor
Glen Mazza wrote:
Team,
With the recent removal (who did that? ;) of the
unused layout.AreaClass and layout.TextState classes,
the fop.layout package is now empty save for its
hyphenation subpackage.
I'd like to drop the layout package and make
hyphenation a top-level package (i.e.,
Victor Mote wrote:
FOP Devs:
I checked in with Chris Bowditch recently to see how his foray work was
coming, and he indicated that he has not had, and probably will not have in
the near future, enough time to complete the evaluation and make a
recommendation to you.
Victor is right, I dont have
--- Additional Comments From [EMAIL PROTECTED] 2004-08-31 18:44 ---
Thanks for the new patch. I could apply it without problems, and
testing it goes well.
You mention that you have not implemented the Knuth algorithm for
ContentLM. Would it be difficult to do that?
FOP team,
If I would
Glen Mazza wrote:
There are already other AFP Renderers for FOP
0.20.5--actually Hansuli has it in our resources page:
http://xml.apache.org/fop/resources.html
I agree with Pete here - this AFP renderer is too disjointed and has a few
limitations which make it too unpractical.
And--amazing what
Jeremias Maerki wrote:
Hehe, and then there was the one by UBS which I asked them to make OSS
and they declined even after killing the project.
I don't think there's a big legal problem around AFP, it's probably more
the technology itself that has the attribute may cost a bit more on it.
:-) While
Glen Mazza wrote:
My primary goal is not to get this committed. But
if you have code you wish to donate to the ASF, just
do so via Bugzilla. It doesn't matter which
format--it is the logic in the code that is being
sought. No guarantees, however, as to it ever getting
committed into FOP,
Townsend, Pete wrote:
Glen,
I'll get this added as a patch (via Bugzilla as Chris suggested). The
developer forum can then decide if this is something you wish to take
forward (perhaps someone can get feedback from the user community as to
whether it would be desirable). It has saved us a huge
Keiron Liddle wrote:
Well I did it for an internal project and was never allowed to release
the code so it has remained unchanged and closed for some time now. I
still believe that all is needed is for someone to start put the code
into the public. The basic format (although binary and a bit
Nuno Lopes wrote:
Hello,
I was trying to make some PDFs of the PHP manual when I got some problems.
The manual is written in docbook and then I have a XSL sheet. I can generate
the manual in english, portuguese, french,... but not in russian.
Firstly, please post user related questions to the user
Glen Mazza wrote:
I'll take care of it by this weekend, if not much
sooner.
Thanks Glen, where would we be without you!
Chris
Clay Leeds wrote:
On Aug 2, 2004, at 1:48 AM, Chris Bowditch wrote:
Clay Leeds wrote:
snip/
Just to be sure, are these amongst the changes you're looking for:
Hi Clay, yes these are the changes I was looking for. If you could
apply the changes manually I would be most grateful. Thanks,
Chris
Glen Mazza wrote:
Well, the number of patches and enhancements made to
layout/rendering has only been about 2-3 per month in
the 12 months that we've had AddLMVisitor. FOP won't
finish at that rate, and that *will* affect the users.
I agree that FOP wont finish at its current rate of development!
Clay Leeds wrote:
snip/
Just to be sure, are these amongst the changes you're looking for:
Hi Clay, yes these are the changes I was looking for. If you could apply the
changes manually I would be most grateful. Thanks,
Chris
Justified Text
High
This has been completed, thanks largely to
Victor Mote wrote:
J.Pietschmann wrote:
Well, the real stakeholders (aka users) are probably more
interested in working footnotes, or multi-column layout.
I don't understand. More interested in working footnotes or multi-column
layout than what? Is removing AddLMVisitor an advancement in
Andrej Czapszys wrote:
Please excuse my ignorance, but what is the current status of the
redesign, and how might I help out? The website explanation wasn't very
clear.
The website is great for the maintenance versions of FOP 0.20.x, but is a
little unclear with regards to the redesign (sorry
Victor Mote wrote:
FOP Devs:
I am pleased to announce the release of FOray 0.1 alpha 1. This release is
only useful to FOP developers. Some useful information about the release can
be found in these places:
http://foray.sourceforge.net/module/font/index.html
Peter B. West wrote:
Hi Peter - did you have a good honeymoon?
Fopsters,
I notice that Glen has been progressively adding validity checking to FO
elements. I'll take this opportunity to draw the attention of recent
foppers to an earlier discussion of the relative merits of push vs. pull
Glen Mazza wrote:
Reconsidered. OK, I'll join, and reinstate my first
proposal, that of you joining the PMC and (yes) being
its head.
Hi Glen,
glad that you reconsidered, I agree with Jeremias, the PMC needs you. It also
needs Jeremias, so I second your proposal to have Jeremias on the PMC.
Jeremias Maerki wrote:
Chris, please check the settings of your IDE not to allow tab characters.
Thanks!
Hi Jeremias,
I cant simply turn off Tabs as I need them for my paid work! I would like to
be able to run checkstyle to check for this sort of mistake, but have run into
some problems with it.
Peter B. West wrote:
Fopfellows,
I will be offline for the next week. I'm marrying Jenni tomorrow, and
honeymooning in the frozen south of the South Island of New Zealand for
a week. I'll post some photos to my web site when I get back.
Peter - congratulations! Enjoy your well deserved break.
Glen Mazza wrote:
Noted. My instinct would be for us to wait about 6-9
months after several other projects move over. If no
problems with them, or at least no major problems,
then I think it would be fine for us to switch
products if other committers would like.
However, this will still require
Simon Pepping wrote:
Inline area generating LMs and Inline area containing LMs
and their corresponding FO nodes
=
In the listings below the LMs are followed by the FO nodes that
generate them.
Thanks for the summary Simon.
snip/
Note that
A.M. wrote:
Replying off-list:
huh?
I'm not sure I really have a choice concerning the fop version.
Considering I needed column balancing yesterday, I'll take the route
that gives me balanced columns ASAP. I haven't looked at the PDF
rendering code yet, so (neglecting your desire for the dev
[EMAIL PROTECTED] wrote:
A.M. [EMAIL PROTECTED] wrote 27.05.2004 16:27:29:
Excuse me for being annoying with the column balancing issue (from
fop-user), but it's something that we crucially need. I would like to
offer my time to implement this- however it's not clear to me which
block
Simon Pepping wrote:
snip/
No exceptions. I ran Luca's test fo files successfully.
Strange how you and I always get such different results. It doesnt run with
any file despite changing the language to en. I always get NPE on LLM:249.
Looking at the code it would appear to be a mistake as NPE
Peter B. West wrote:
snip/
Simon, yes! That's what branching is there for. People seem to be
afraid of it, but it is an enormously useful tool for just such
situations. I think it's always a good idea to tag the tree immediately
before a branch.
Hi Peter,
its not that I am afraid of
Luca Furini wrote:
JThe method startParagraphs dereferences only knuthParagraphs and
textIndent, so maybe there is a missing line concerning their initialization.
I have proved that textIndent is definitely null when it is not specified on
the block.
snip/
While textIndent is initialized in the
Luca Furini wrote:
You are completely right; by the way, what other child LMs could the LLM
have?
I'm just guessing, but I think anything that can appear inline, i.e.
hyperlinks, leaders, etc. Block level stuff like Tables and graphics can not
be children of the LLM.
I do not believe that the
Team,
thanks to everyone who agreed to hold off commits until the fate of Luca's
patch had been decided. I think everyone is in agreement that this first patch
needs more work, so I will re-sync with CVS. Therefore, it is safe to make
commits to HEAD once more.
Thanks,
Chris
Clay Leeds wrote:
BTW, Anyone else seeing sporadic mail issues? I didn't actually
*receive* Andreas' message. (I noticed in MARC, and am responding before
I go home).
Hi Clay - I noticed that the mailing lists were very slow yesterday, with
responses appearing in MARC well before I received
Andreas L. Delmelle wrote:
Hi Andreas,
its great to have you trying to help with layout.
Adding the necessary activation code to the FObjs to pass these properties
to Layout is easy enough, but I'm still having a bit of difficulty in
'seeing' what needs to be done to handle this in the respective
Andreas L. Delmelle wrote:
Just gathering my thoughts here...
Thanks for your feedback. I need all the help I can get!
If I interpret the related code in BLM correctly, then the childLMs are all
created (and call their addAreas() ) after the first marker has been added
( line 265:
Victor Mote wrote:
FOP Devs:
I apologize for intruding again. After thrashing around for a bit, I
No need to apologize, your input is welcome.
concluded that there were an overwhelming number of good reasons for me to
import the entire FOP maintenance branch into the FOray repository, then
delete
Hi Luca,
May I start by thanking you for your hard work in submitting the patch for
Knuth's Line breaking algorithm.
I'm just starting to look at your patch now. First thing that strikes me, and
this was pointed out to me before I became a committer. Please try to avoid
commenting out large
FOP Devs,
I'm trying to apply Luca's patch and running into problems. The hunks in the
first 9/10 files get applied okay, but when the patch program gets to
LineLayoutManager, it only reconises 6 hunks, the seventh is very big and for
some reason the patch program thinks it has found the start
Jeremias Maerki wrote:
Chris,
I've just upgraded my sources and tried to apply the same patch within
Eclipse to see what happens. I get two parts of the patch that Eclipse
claims to be unable to apply correctly. But this only makes up a few
lines in all. Maybe if Luca would send you the whole
Simon Pepping wrote:
That was basic work. The basis of the property subsystem is good,
and shorthands all work, I think. But it is another question which
properties are really implemented w.r.t. their effect on the layout. I
do not think we have a good overview. See Glen's experimental
approach:
Peter B. West wrote:
My understanding is that thanks to the property work earlier this year
by Glen, Finn and Simon, that properties are 95% there, including
shorthands. Admittely I didnt follow their work very closely, so could
be wrong about this. Im sure Glen will interject and correct me on
Jeremias Maerki wrote:
Guys,
my comment on this is: Commit it if you think it's an improvement. It
may be a bit different if it concerned design questions, but with small
fixed and improvements I'd rather you guys just did it. If it turns
out to be a mistake it can easily be corrected. That's why
Tibor Vyletel wrote:
Hi guys,
In previous versions (builds) of FOP areas have had set ID_AREA trait in
order to allow identification of original FONodes (and XML elements)
they had been created from. Why is this feature missing in recent builds
(1.0DEV)? Is there any other possibility how to
FOP Devs,
I'm currently trying to get Markers working. The problem I have is that the
first marker on page 2 is actually being added to the markers on Page 1.
the markers are added to pageViewport in the BLM.addAreas method. Now my
understanding is that addAreas are called once the BPs have
Victor Mote wrote:
Simon Pepping wrote:
I sympathize with this goal as well. I realize that that is
not quite in line with my reaction to Glen's recent patch. I
agree with Chris and Glen that it is not currently a key goal
for FOP. And since we do not have a strong proponent and
architect of
Luca Furini wrote:
I am still thinking about justification and the more general problem of
line-breaking, and I have come to think that it's quite strange that the
LineLayoutManager should make choices about breaking points using only the
information provided by the TextLayoutManagers, while it
Clay Leeds wrote:
Be warned that the RenderX testsuite files require a relatively high
degree of spec compliance. Shorthands are used everywhere, all table
examples require auto-layout, and so on. I confess that I learned a
few more things about FO when testing with these files...
Sounds like a
Victor Mote wrote:
Dear FOP Developers:
Hi Victor - welcome back. I was saddened by your decision to leave FOP.
After considering a return to FOP development, and briefly discussing the
pros and cons with those whom I consider to be the FOP development leaders,
I have decided to partially fork FOP
Andreas L. Delmelle wrote:
Hmm.. Yes, but... these properties are not specifically meant for the rows
themselves. They are meant to be propagated to/combined with those defined
on the table-cells contained by it.
Good point.
( IIC, resolving the possible conflicts WRT backgrounds/borders can be
Andreas L. Delmelle wrote:
comments below:
Posting this as a follow-up to my earlier ponderings. If we don't get it
implemented, or postpone this one indefinitely, at least we'll have it
nicely summed up for possible future use... (Who knows, maybe parts of these
remarks can be used to implement
[EMAIL PROTECTED] wrote:
Some elaborations on this from my side. Please feel free to ignore it
entirely.
Thanks for speaking up. Just because you are not a committer, doesnt mean your
opinion doesnt matter. This is open source way. The project is owned by everyone.
snip/
5. Time goes on, A' and
FOP Devs,
I would appreciate some advice. I have noticed that top/bottom borders dont
work on regular blocks. This is because the PDF Renderer uses block.getWidth()
to determine the length of the border lines. Here is a sinnper of Area Tree
output:
block width=138897 ipd=0
Chris Bowditch wrote:
FOP Devs,
I would appreciate some advice. I have noticed that top/bottom borders
dont work on regular blocks. This is because the PDF Renderer uses
block.getWidth() to determine the length of the border lines. Here is a
sinnper of Area Tree output:
block width
[EMAIL PROTECTED] wrote:
Chris Bowditch [EMAIL PROTECTED] wrote on 18.05.2004 12:03:33:
This is very true, I also have the same concerns, which is why I have
set out
some simple objectives that must be met before the redesign is ready for
an initial release. See here:
http://xml.apache.org/fop
Baron Moenghausen wrote:
Hello!
What wrong with pdf made with cyrillic KOI8-r?
Hello,
sorry but I dont understand your question. Could you rephrase it and maybe
elaborate.
Thanks,
Chris
Andreas L. Delmelle wrote:
snip/
Now, I'm wondering, since the spec states that an fo:table-row doesn't
generate any reference areas and since it can contain only TableCells,
whether it wouldn't be more interesting (heap-wise :) ) to create just one
TableRow object per TableBody, use it to process
J.Pietschmann wrote:
Simon Pepping wrote:
Summarizing, you mean that
1. the layout system should calculate the justification and add
corresponding word and space areas to the area tree;
Eh, not quite. The problem is that the actual justification can
only be done after page number citations
Team,
just to let you know that I will be off line until Monday 19th April.
Best regards,
Chris
Simon Pepping wrote:
I believe the reason why justification still doesnt work after correcting the
issues you've found is because TextLM.addAreas doesnt create separate areas
for each word - it creates one big area in some cases for whole line, so there
is no opportunity to add space adjust
Comments most welcome.
Glen,
In general I like your solution. However, I did a bit of testing with inlines
and the effects are very serious. Valid non-whitespace characters from the
enclosing block are simply deleted if there is whitespace at the start of the
fo:inline.
Chris
Chris Bowditch wrote:
Simon Pepping wrote:
I believe the reason why justification still doesnt work after
correcting the issues you've found is because TextLM.addAreas doesnt
create separate areas for each word - it creates one big area in some
cases for whole line, so there is no opportunity
Team,
sorry but another newbie committer question:
I downloaded a patch program from the internet. Not sure if there is a
specific one I need, or whether they all conform to a standard. When I try to
run the patch program with unified patch file in the xml-fop directory, it
cant figure out
Jeremias Maerki wrote:
Hi Chris,
I'm applying the patches directly in Eclipse which provides graphical
helpers to resolve problems like this. Patches can even be copy/pasted.
I've had problem with the patch.exe myself in the past, but since I'm
using Eclipse I've had almost no problems anymore.
Glen Mazza wrote:
Chris Bowditch wrote:
snip/
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
We would need to add this to FOP.sh or FOP.bat in CVS
It might be more efficient to store this information in the Ant build
file instead--I believe the .sh/.bat files just
Glen Mazza wrote:
I use this tool (I couldn't find a patch program in WinCVS):
http://marc.theaimsgroup.com/?l=fop-devm=105874140111833w=2
Two other notes to read:
http://marc.theaimsgroup.com/?l=fop-devm=106961785412734w=2
http://marc.theaimsgroup.com/?l=fop-devm=106962776820285w=2
to apply the
Christian Geisert wrote:
cbowditch (at) apache.org wrote:
cbowditch2004/04/02 05:50:52
Modified:src/java/org/apache/fop/fo/flow Block.java
Log:
Applied Luca Furini's patch from bugzilla entry 28021.
Corrections to behaviour of whitespace-treatment property
Revision Changes
Glen Mazza wrote:
Here's my +1.
Simon has certainly shown a great understanding of the redesigned layout and
has helped me improve my understanding at times. I think committership is long
overdue, and if Glen hadnt proposed this Vote, I would have done.
+1
Chris
Glen Mazza wrote:
snip/
Accordingly, I think it's time now for us to do the
same for FOP. I'd like us to drop the Avalon library
for 1.0, and switch to Jakarta Commons-Logging [4] as
a replacement for Avalon's logging component. For
1.0, I propose having FOP join Batik, Xalan, Xerces,
Luca Furini wrote:
Hi all!
I am an italian student of the University of Bologna.
I have tried to solve a few problems concerning hyphenation, in
particular:
- show the '-' at the end of the hyphenated lines
- use the fo:hyphenate property to enable hyphenation, instead of the
alignment
-
Glen Mazza wrote:
Team,
I'll be taking a few weeks off the project, there's some things I want
to study and get out of the way right now. I'll be back to coding soon!
Thanks for letting us know Glen. I just want to thank you for all your
work to date on FOP. It takes FOP another step closer
Naveen M V wrote:
Hi All,
I need to generate PDF files using XSL-FO transformation and embed
CMYK -jpeg for printing. I am using fop-0.20.5. Can any body help.
When you say printing are you using the Postscript renderer? Everything
that is currently known about JPEG graphics is on the website,
Peter B. West wrote:
Thanks again, Jeremias, for all of the licensing housekeeping. I'm
sorry I didn't get around to giving you a hand with this. Does anything
(apart from the hyphenation mess) remain to be done?
Peter
I would also like to thank Jeremias for sorting out the licensing, not
Glen Mazza wrote:
They're currently voting on the Cocoon side[1] to set
1.4 as the minimum JDK for their next 2.2 release. So
far it looks good for approval.
I'm not so sure it does, look at the 3rd mail in the thread:
http://marc.theaimsgroup.com/?l=xml-cocoon-devm=107813002510299w=2
and this
Glen Mazza wrote:
snip/
The updates and issues he has brought up to us this
week, I'm sure he would be happy to take care of for
us, just as soon as we provide him write access. I
also hope he develops a psychological concept of
ownership of our website over time, resulting in it
looking
I know this subject has come up before, but I still cant quite get
things working after trawling through the archives.
I'm using WinCVS 1.3 and Putty to connect to the cvs.apache.org. My
understanding was that using SSH keys was optional but strongly
encouraged. So I had a go at creating the
Jeremias Maerki wrote:
I've had my problems with using SSH2. I finally tried SSH1 and it worked.
I suggest you create a SSH1 key pair and retry with this.
Thanks for the fast response Jeremias. I have managed to get SSH1 working.
There are two ways you can work with putty. Either you create a
Glen Mazza wrote:
Team,
To simplify the Area Tree--Renderer interaction somewhat, making this
section of the code easier to follow, I'd like to make two changes to
the code:
1.) Remove the serveVisitor() methods in AbstractRenderer.java [1], and
return to what we were using last year, that
Andreas L. Delmelle wrote:
snip/
The related class in Xalan: org.apache.xalan.lib.Redirect
It contains a HashMap, m_outputStreams, which is, unfortunately, protected,
so can't be queried from outside the xalan.lib package...
Whats wrong with sub-classing, e.g. FopRedirect extends Redirect.
1 - 100 of 175 matches
Mail list logo
