Jeremias Maerki writes:
The migration of the xml-fop CVS module to Subversion is completed. The
CVS module is now read-only. All commits need to happen on SVN from now
on.
Base SVN URL for FOP:
http://svn.apache.org/repos/asf/xmlgraphics/fop/
FOP's trunk is at:
Jeremias Maerki writes:
If anyone has any problems, just shout! Have fun and hack away!
HELP! (you did say to shout :) )
Louder!
_ _ _ _ _
| | | | | | | _ \| |
| |_| | _| | | | |_) | |
| _ | |___| |___| __/|_|
|_| |_|_|_|_| (_)
bash-2.05b$
Jeremias Maerki writes:
Looks like Christian is right. The proxy probably coughs at Subversion's
special request methods. I've found the FAQ entry in the official SVN
FAQ concerning proxies. Maybe this contains an additional idea how to
solve this. The first step is probably identifying
Hi Vincent
Yeah, sorry. Given the feedback, you can go forward with this. I'll try
to help where I can. The goal should simply be that we have a real
benefit from using FOray-Font at the end. For example, the ability to
get rid of the manual step of creating font metric files is a good
benefit,
While creating the check for the span attributes a few minutes ago, I
wondered if we shouldn't actually warn about explicit non-inherited
properties on FO they don't apply to. We currently don't do that AFAICS.
Am I right that this is a task that we shouldn't forget?
Jeremias Maerki
The recommendation allows any property to be on any FO (First sentence
of section 5 of 1.1[1], but also somewhere in 1.0), regardless of its
utility. So we don't need to mention this as a warning.
We *might* want to do this in a few areas though where newbies might
make very common mistakes
I think these type of checks would be useful if available as an option
(perhaps part of an extended 'debug' mode?). The default, of course,
would be OFF, but could be enabled so users could 'see' what's
happening.
Web Maestro Clay
On Jun 24, 2005, at 9:01 AM, Jeremias Maerki wrote:
Ah, ok.
[EMAIL PROTECTED] wrote:
Jeremias Maerki writes:
If anyone has any problems, just shout! Have fun and hack away!
HELP! (you did say to shout :) )
Louder!
_ _ _ _ _
| | | | | | | _ \| |
| |_| | _| | | | |_) | |
| _ | |___| |___| __/|_|
|_|
Vincent Hennebert wrote:
Sorry to insist, but what is your final decision? A quick summary of the
thread gives:
- Jeremias +1
- Simon +1
- Glen +0
The FOray+aXSL stuff would be used in the form of a jar file put in the
lib directory; FOray's avalon loggers would be wrapped into a JCL
adapter
Jeremias Maerki wrote:
Ah, ok. Thank you. Will shut up then. These checks would only have eaten
performance.
I don't think another table lookup would eat that much performance.
Ultimately there are so many good reasons for all kinds of warnings
that we'll probably end up with a configurable
Peter B. West wrote:
You can always get the sources using the official command-line client
that comes with Subversion:
http://subversion.tigris.org/
http://subversion.tigris.org/project_packages.html
Which is what I had to do with BitKeeper, for which no client existed in
NetBeans,
11 matches
Mail list logo
