Re: [Fwd: xml.apache.org refactoring #1]
Christian Geisert wrote: From: Ted Leung [EMAIL PROTECTED] We ask each subproject to nominate 1 (or 2) people from that project to be a part of the XML PMC. From my experience, I think that it will be better to have 2 people rather than one in order to share workload, etc. So, they want 2 people, I believe it's not a problem for us to elect them, let's start - candidates? -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Fop able to run without Batik?
[EMAIL PROTECTED] wrote: Batik is only necessary to generate SVG output, right? Nope, you forgot about svg images. -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Named Destinations
Hi all. Reading the mailing list archives (developer and user) I found that the topic of named destinations was raised several times and it seems that many people would like / need this feature. Studiying the changes list I even found the entry # Linking to a specific page and a named destinations of an external PDF file. (see www.adobe.com/products/acrobat/pdfs/c01acrotip.pdf) (CG) Thanks to Bernd Brandstetter. # update Unfortunately the corresponding patch (submitted on the user-list) seems not to be integrated in the next release 0.20.5. However, I could patch FOP myself. In addition, in November 2001, Lloyd McKenzie submitted a patch in the developer list that allowed the definition of named destinations (i.e. targets one can link to). His patch is not integrated either and I fruitlessly tried to apply it manually on the current version. Now my kind plea is that some of the FOP gurus could take a look on it and integrate this functionality. I am sure that many users would appreciate it much. --Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: duplicated sax classes
Jeremias Maerki wrote: I think we could just remove the SAX classes from batik.jar. batik.jar was compiled by us manually and Keiron (for trunk) and I (for branch) both haven't realized that the SAX classes slipped in, I guess. I'll check the way we generate that jar again tomorrow. It might simply be a matter of sending the Batik team a little patch for their build.xml so we get an Ant target for creating a big batik.jar like we need/like it for FOP. You'll hear from me again. Great, thanks! -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: duplicated sax classes
Keiron Liddle wrote: Current cvs batik has been fixed so that it uses the xml-apis.jar instead of having its own version. So if this is what is causing the problem you can make a build from current cvs. Fine. I would be nice to have such batik.jar in 0.20.5 release. -- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16257] New: - Problems with adding true type fonts to FOP
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16257. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16257 Problems with adding true type fonts to FOP Summary: Problems with adding true type fonts to FOP Product: Fop Version: 0.20.4 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The adding of true type fonts seems to work randomly. With some fonts the adding works fine and the fonts in pdf document look like they should, but with some fonts there are problems. When I tried to add the font Batang FOP created an empty xml file containing just one line: ?xml version=1.0 encoding=UTF-8?. The adding of font FF Meta Normal LF Roman seemed to work fine, except that the line breaks are missing. I tried the same piece of text in simple fo-document with many fonts, but the FF Meta Normal LF Roman was the only one which caused the text lines to be on top of one another, all in the same row. I am almost sure, that the congiguration file is ok, except that for the embed- option I used the ttf-files and not pfb-files. Is there something I could do to make the line breaks work? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16257] - Problems with adding true type fonts to FOP
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16257. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16257 Problems with adding true type fonts to FOP --- Additional Comments From [EMAIL PROTECTED] 2003-01-20 13:45 --- Created an attachment (id=4495) The ttf-file of font FF Meta Normal LF Roman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Fop able to run without Batik?
Batik is only necessary to generate SVG output, right? I guess, a lot of people are using Fop to generate PDF only, but Fop needs batik.jar in any case because the driver initializes an SVG element mapping: org.apache.fop.apps.Driver.setupDefaultMappings() : addElementMapping(org.apache.fop.svg.SVGElementMapping); That is to handle svg input which could be used in a PDF (or any other) output document. This method will throw a ClassNotFoundException when batik.jar is not in the classpath There are a number of other areas that require batik in the classpath. Maybe the initialization of the element mapping could somehow be moved to SVG specific code. Ideally it would be included only when the output format requires Batik This has been dealt with in the redesign. The code that handles the element mapping, external XML and image loading is separated so that if batik is not in the classpath it will continue to operate. Eckard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/design/alt.design/properties PropertyConsts.html
pbwest 2003/01/20 06:42:40 Modified:src/documentation/content/design/alt.design/properties PropertyConsts.html Log: Trivial change Revision ChangesPath 1.2 +0 -0 xml-fop/src/documentation/content/design/alt.design/properties/PropertyConsts.html Index: PropertyConsts.html === RCS file: /home/cvs/xml-fop/src/documentation/content/design/alt.design/properties/PropertyConsts.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/design/alt.design/properties AbstractPropertyValue.html PropertyValue.html PropertyValueList.html
pbwest 2003/01/20 06:45:18
Added: src/documentation/content/design/alt.design/properties
AbstractPropertyValue.html PropertyValue.html
PropertyValueList.html
Log:
Code documentation
Revision ChangesPath
1.1
xml-fop/src/documentation/content/design/alt.design/properties/AbstractPropertyValue.html
Index: AbstractPropertyValue.html
===
!DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01//EN
!-- Created by htmlize-0.67 in css mode. --
html
head
titleAbstractPropertyValue.java/title
style type=text/css
!--
body {
color: #00;
background-color: #faf0e6;
} /* default */
.jde-java-font-lock-package {
color: #cd;
background-color: #faf0e6;
} /* jde-java-font-lock-package-face */
.jde-java-font-lock-constant {
color: #5f9ea0;
background-color: #faf0e6;
} /* jde-java-font-lock-constant-face */
.keyword {
color: #8b;
background-color: #faf0e6;
} /* font-lock-keyword-face */
.jde-java-font-lock-doc-tag {
color: #008b00;
background-color: #faf0e6;
} /* jde-java-font-lock-doc-tag-face */
.jde-java-font-lock-number {
color: #bc8f8f;
background-color: #faf0e6;
} /* jde-java-font-lock-number-face */
.jde-java-font-lock-italic {
background-color: #faf0e6;
font-style: italic;
} /* jde-java-font-lock-italic-face */
.string {
color: #008b00;
background-color: #faf0e6;
} /* font-lock-string-face */
.variable-name {
color: #8b008b;
background-color: #faf0e6;
} /* font-lock-variable-name-face */
.jde-java-font-lock-modifier {
color: #da70d6;
background-color: #faf0e6;
} /* jde-java-font-lock-modifier-face */
.type {
color: #4682b4;
background-color: #faf0e6;
} /* font-lock-type-face */
.comment {
color: #8b;
background-color: #faf0e6;
} /* font-lock-comment-face */
.function-name {
color: #8b2323;
background-color: #faf0e6;
} /* font-lock-function-name-face */
a {
color: inherit;
background-color: inherit;
font: inherit;
text-decoration: inherit;
}
a:hover {
text-decoration: underline;
}
--
/style
/head
body
pre
span class=keywordpackage/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagedatatypes/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagefo/span.span class=typePropertyConsts/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagefo/span.span class=typePropNames/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagefo/span.span
class=jde-java-font-lock-packageproperties/span.span
class=jde-java-font-lock-number*/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagefo/span.span class=typeFONode/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagefo/span.span
class=jde-java-font-lock-packageexpr/span.span
class=typePropertyException/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagedatatypes/span.span
class=typePropertyValue/span;
span class=comment/*
* AbstractPropertyValue.java
* $Id: AbstractPropertyValue.html,v 1.1 2003/01/20 14:45:18 pbwest Exp $
*
* Copyright (C) 2001 The Apache Software Foundation. All rights reserved.
* For details on use and redistribution please refer to the
* LICENSE file included with these sources.
* @author lt;a href=quot;mailto:[EMAIL PROTECTED]quot;gt;Peter B.
Westlt;/agt;
cvs commit: xml-fop/src/documentation/content/design/alt.design/properties FOAttributes.html
pbwest 2003/01/20 06:46:51
Added: src/documentation/content/design/alt.design/properties
FOAttributes.html
Log:
Code documentation
Revision ChangesPath
1.1
xml-fop/src/documentation/content/design/alt.design/properties/FOAttributes.html
Index: FOAttributes.html
===
!DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01//EN
!-- Created by htmlize-0.67 in css mode. --
html
head
titleFOAttributes.java/title
style type=text/css
!--
body {
color: #00;
background-color: #faf0e6;
} /* default */
.jde-java-font-lock-number {
color: #bc8f8f;
background-color: #faf0e6;
} /* jde-java-font-lock-number-face */
.function-name {
color: #8b2323;
background-color: #faf0e6;
} /* font-lock-function-name-face */
.jde-java-font-lock-italic {
background-color: #faf0e6;
font-style: italic;
} /* jde-java-font-lock-italic-face */
.jde-java-font-lock-modifier {
color: #da70d6;
background-color: #faf0e6;
} /* jde-java-font-lock-modifier-face */
.keyword {
color: #8b;
background-color: #faf0e6;
} /* font-lock-keyword-face */
.variable-name {
color: #8b008b;
background-color: #faf0e6;
} /* font-lock-variable-name-face */
.string {
color: #008b00;
background-color: #faf0e6;
} /* font-lock-string-face */
.jde-java-font-lock-package {
color: #cd;
background-color: #faf0e6;
} /* jde-java-font-lock-package-face */
.jde-java-font-lock-constant {
color: #5f9ea0;
background-color: #faf0e6;
} /* jde-java-font-lock-constant-face */
.type {
color: #4682b4;
background-color: #faf0e6;
} /* font-lock-type-face */
.jde-java-font-lock-doc-tag {
color: #008b00;
background-color: #faf0e6;
} /* jde-java-font-lock-doc-tag-face */
.comment {
color: #8b;
background-color: #faf0e6;
} /* font-lock-comment-face */
.reference {
color: #cd;
background-color: #faf0e6;
} /* font-lock-reference-face */
a {
color: inherit;
background-color: inherit;
font: inherit;
text-decoration: inherit;
}
a:hover {
text-decoration: underline;
}
--
/style
/head
body
pre
span class=keywordpackage/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagefo/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packageapps/span.span class=typeFOPException/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagefo/span.span
class=jde-java-font-lock-packageexpr/span.span
class=typePropertyException/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagefo/span.span class=typePropertyConsts/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagefo/span.span class=typeFObjectNames/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagedatatypes/span.span class=typeInts/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagemessaging/span.span
class=typeMessageHandler/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
class=jde-java-font-lock-packagexml/span.span class=typeFoXMLEvent/span;
span class=keywordimport/span span
class=jde-java-font-lock-packageorg/span.span
class=jde-java-font-lock-packageapache/span.span
class=jde-java-font-lock-packagefop/span.span
cvs commit: xml-fop/src/documentation/content/design/alt.design/properties PropertyConsts-class.html
pbwest 2003/01/20 06:51:12
Added: src/documentation/content/design/alt.design/properties
PropertyConsts-class.html
Log:
Code documentation
Revision ChangesPath
1.1
xml-fop/src/documentation/content/design/alt.design/properties/PropertyConsts-class.html
Index: PropertyConsts-class.html
===
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
html
head
META http-equiv=Content-Type content=text/html; charset=ISO-8859-1
titlePropertyConsts Description/title
style type= text/css
span.codeDisplay {font:italic bold}
body {
font-family: Verdana, Helvetica, sans-serif;
}
.note { border: solid 1px #7099C5; background-color: #f0f0ff; }
.note .label { background-color: #7099C5; color: #ff; }
.content {
padding: 5px 5px 5px 10px;
font : Verdana, Helvetica, sans-serif; font-size : 90%;
}
/style
/head
body marginheight=0 marginwidth=0 topmargin=0 leftmargin=0
text=#00 bgcolor=#FF
div class=content
h1PropertyConsts Description/h1
p
font size=-2bynbsp;Peter B. West/font
/p
ul class=minitoc
li
a href=#N10014Introduction/a
/li
/ul
a name=N10014/a
h3Introduction/h3
p
a href=javascript:parent.displayCode(
'PropertyConsts.html#PropertyConstsClass'
)This class/a, and the singleton object which is a
href=javascript:parent.displayCode(
'PropertyConsts.html#pconsts' )generated by the static
initializer/a, is essentially a repository of
lt;propertygt; class instances and the static data from
those classes of span
class=codefragorg.apache.fop.fo.property/span.
The heart of this class is the method a href=
javascript:parent.displayCode(
'PropertyConsts.html#setupProperty' )span class=codefrag
setupProperty/span /a. Whenever access to the data or
methods of a property class is required, this method in the
singleton must be called to ensure that an instance of the
property exists and that the static data from that instance
has been extracted.
/p
div class=frame note
div class=labelNote/div
div class=content
An alternative to this requirement would be to pre-load all
of the individual property classes during the system
initialization phase. This is not done currently because of
the start-up expense of the required class loading for over
three hundred classes, and the relatively low added expense
of checking for the existence of a property instance before
every access. Given that FOP is increasingly used in a
server environment, it may prove acceptable in the long run
to change to pre-loading.
/div
/div
p
The class name is generated and stored in the a
href=javascript:parent.displayCode(
'PropertyConsts.html#classNames' )span class=codefrag
classNames/span /a array; a class instance is generated
from the name and stored in the a
href=javascript:parent.displayCode(
'PropertyConsts.html#classes' )span class=codefrag
classes/span /a array; and an instance of the class is
generated from the class object and stored in the a
href=javascript:parent.displayCode(
'PropertyConsts.html#properties' )span class=codefrag
properties/span /a array.
/p
p
The other data gathering facilities and access methods of this
class will be examined in conjunction with the various types
of property classes.
/p
p
strongPrevious:/strong a href = classes-overview.html
Property classes overview/a
/p
p
strongNext:/strong a href= simple-properties.html
Simple property classes/a
/p
/div
table summary=footer cellspacing=0 cellpadding=0
width=100% height=20 border=0
tr
td colspan=2 height=1 bgcolor=#4C6C8Fimg height=1 width=1
alt= src=../../skin/images/spacer.gifa href=../../skin/images/label.gif/aa
href=../../skin/images/page.gif/aa href=../../skin/images/chapter.gif/aa
href=../../skin/images/chapter_open.gif/aa
href=../../skin/images/current.gif/aa href=../..//favicon.ico/a/td
/tr
tr
td colspan=2 bgcolor=#CFDCED class=copyright align=centerfont
size=2 face=Arial, Helvetica, Sans-SerifCopyright copy;
1999-2002nbsp;The Apache
cvs commit: xml-fop/src/documentation/content/design/alt.design/properties introduction.html
pbwest 2003/01/20 06:52:06
Added: src/documentation/content/design/alt.design/properties
introduction.html
Log:
Code documentation
Revision ChangesPath
1.1
xml-fop/src/documentation/content/design/alt.design/properties/introduction.html
Index: introduction.html
===
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
html
head
META http-equiv=Content-Type content=text/html; charset=ISO-8859-1
titleImplementing Properties/title
style type= text/css
body {
font-family: Verdana, Helvetica, sans-serif;
}
.note { border: solid 1px #7099C5; background-color: #f0f0ff; }
.note .label { background-color: #7099C5; color: #ff; }
.content {
padding: 5px 5px 5px 10px;
font : Verdana, Helvetica, sans-serif; font-size : 90%;
}
/style
/head
body marginheight=0 marginwidth=0 topmargin=0 leftmargin=0 text=#00
bgcolor=#FF
div class=content
h1Implementing Properties/h1
p
font size=-2bynbsp;Peter B. West/font
/p
ul class=minitoc
li
a href=#N10014An alternative properties implementation/a
ul class=minitoc
li
a href=#N10043The history problem/a
/li
li
a href=#N10061The construction hierarchy/a
/li
li
a href=#N10082Representing properties: lt;propertygt; classes/a
/li
/ul
/li
/ul
a name=N10014/a
h3An alternative properties implementation/h3
div class=frame note
div class=labelNote/div
div class=content
The following discussion focusses on the relationship between
Flow Objects in the Flow Object tree, and properties. There
is no (or only passing) discussion of the relationship between
properties and traits, and by extension, between properties
and the Area tree.
/div
/div
p
Property handling is complex and expensive. Varying numbers of
properties strongapply/strong to individual Flow Objects
strong(FOs)/strong in the strongFO tree /strong but
any property may effectively be assigned a value on any
element of the tree. If that property is inheritable, its
defined value will then be available to any children of the
defining FO.
/p
div class=frame note
div class=labelNote/div
div class=content
em(XSL 1.0 Rec)/em strong5.1.4 Inheritance/strong
...The inheritable properties can be placed on any formatting
object.
/div
/div
p
Even if the value is not inheritable, it may be accessed by
its children through the span class=codefraginherit/span
keyword or the span class=codefragfrom-parent()/span
core function, and potentially by any of its descendents
through the span
class=codefragfrom-nearest-specified-value()/span core
function.
/p
p
In addition to the assigned values of properties, almost every
property has an stronginitial value/strong which is used
when no value has been assigned.
/p
a name=N10043/a
h4The history problem/h4
p
The difficulty and expense of handling properties comes from
this univeral inheritance possibility. The list of properties
which are assigned values on any particular emFO/em
element will not generally be large, but a current value is
required for each property which applies to the emFO/em
being processed.
/p
p
The environment from which these values may be selected
includes, for each emFO/em, strongfor each applicable
property/strong, the value assigned on this emFO/em,
the value which applied to the parent of this emFO/em,
the nearest value specified on an ancestor of this element,
and the initial value of the property.
/p
a name=N10061/a
h4The construction hierarchy/h4
p
Properties are resoved in the strongFO tree/strong in a
strictly hierarchical manner. Nodes are detected in the
input in a strongpre-order/strong traversal, and are
built in the same order. This imples that there are two
phases, or states, of property resolution and construction.
Any particular FO node is either in a state of constructing
its own subtree, or in a stable state where the subtree
construction
cvs commit: xml-fop/src/documentation/content/design/alt.design/properties classes-overview.html
pbwest 2003/01/20 06:52:44
Added: src/documentation/content/design/alt.design/properties
classes-overview.html
Log:
Code documentation
Revision ChangesPath
1.1
xml-fop/src/documentation/content/design/alt.design/properties/classes-overview.html
Index: classes-overview.html
===
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
html
head
META http-equiv= Content-Type content= text/html; charset=ISO-8859-1
titleProperty classes overview/title
style type= text/css
body {
font-family: Verdana, Helvetica, sans-serif;
}
.note { border: solid 1px #7099C5; background-color: #f0f0ff; }
.note .label { background-color: #7099C5; color: #ff; }
.content {
padding: 5px 5px 5px 10px;
font : Verdana, Helvetica, sans-serif; font-size : 90%;
}
/style
/head
body marginheight= 0 marginwidth= 0 topmargin= 0 leftmargin= 0 text=
#00 bgcolor= #FF
div class= content
h1Property classes overview/h1
p
font size= -2 bynbsp;Peter B. West/font
/p
ul class= minitoc
li
a href = #N10014 Properties: packages/a
ul class= minitoc
li
a href = #N10019 org.apache.fop.fo/a
/li
li
a href = #N100AC org.apache.fop.fo.properties/a
/li
li
a href = #N100EE org.apache.fop.fo.expr/a
/li
li
a href = #N10134 org.apache.fop.datatypes/a
/li
li
a href = #N101A2
org.apache.fop.datatypes.indirect/a
/li
/ul
/li
/ul
a name= N10014 /a h3Properties: packages/h3 a name=
N10019 /a h4org.apache.fop.fo/h4
dl
dt
a href = javascript:parent.displayCode(
'PropNames.html#PropNamesClass'
) emPropNames/em/a
/dt
dd
This class maintains an array of a href=
javascript:parent.displayCode(
'PropNames.html#propertyNames' ) property names/a,
synchronized to a complete set of property name a href =
javascript:parent.displayCode( 'PropNames.html#NO_PROPERTY'
) constants/a for indexing property-based arrays. It
includes methods to a href =
javascript:parent.displayCode(
'PropNames.html#getPropertyName' ) convert an index to a
name/a and to a href = javascript:parent.displayCode(
'PropNames.html#getPropertyIndex' ) convert a property
name to an index/a.
/dd
dt
a href = PropertyConsts-class.html emPropertyConsts/em/a
/dt
dd
A singleton instance of span class= codefrag
PropertyConsts/span is created by the static initializer
of the a href = javascript:parent.displayCode(
'PropertyConsts.html#pconsts' ) pconsts/a field.
Working from the property indices defined in PropNames, the
methods in this class collect and supply the values of
fields defined in property objects into arrays.br The
heart of this class in the method a href =
javascript:parent.displayCode(
'PropertyConsts.html#setupProperty' ) setupProperty/a,
which constructs the property name from the index,
instantiates a singleton of the appropriate class, and
extracts static fields by reflection from that instance into
the arrays of field values.
/dd
dt
a href = javascript:parent.displayCode(
'PropertySets.html#PropertySetsClass' ) emPropertySets/em/a
/dt
dd
This class provides a number of span class= codefrag
ROBitSet/spans representing many of the sets of
properties defined in emSection 7/em of the
specification. Note that the a
href=javascript:parent.displayCode(
'PropertySets.html#borderProps' )emBorder/em/a, a
href=javascript:parent.displayCode(
'PropertySets.html#paddingProps' )emPadding/em/a and
a href=javascript:parent.displayCode(
'PropertySets.html#backgroundProps'
)emBackground/em/a sets are defined separately.
/dd
dt
a href = javascript:parent.displayCode(
'../FOPropertySets.html#FOPropertySetsClass' )
emFOPropertySets/em/a
/dt
dd
This class provides a number of span class= codefrag
ROBitSet/spans representing sets of properties which are
cvs commit: xml-fop/src/documentation/content/design/alt.design/properties enumerated-values.html
pbwest 2003/01/20 06:54:22
Added: src/documentation/content/design/alt.design/properties
enumerated-values.html
Log:
Code documentation
Revision ChangesPath
1.1
xml-fop/src/documentation/content/design/alt.design/properties/enumerated-values.html
Index: enumerated-values.html
===
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
html
head
META http-equiv=Content-Type content=text/html; charset=ISO-8859-1
titleEnumerated Data Values/title
style type= text/css
body {
font-family: Verdana, Helvetica, sans-serif;
}
.note { border: solid 1px #7099C5; background-color: #f0f0ff; }
.note .label { background-color: #7099C5; color: #ff; }
.content {
padding: 5px 5px 5px 10px;
font : Verdana, Helvetica, sans-serif; font-size : 90%;
}
/style
/head
body marginheight=0 marginwidth=0 topmargin=0 leftmargin=0 text=#00
bgcolor=#FF
div class=content
h1Enumerated Data Values/h1
ul class=minitoc
li
a href=#N1000CEnumerated Data Values/a
ul class=minitoc
li
a href=#N10020Array representation/a
/li
li
a href=#N1005CHashMap representation/a
/li
li
a href=#N1009D
Factoring Out Common Enumeration Values
/a
/li
li
a href=#N100DDMapped Numeric Values/a
/li
/ul
/li
/ul
a name=N1000C/a
h3Enumerated Data Values/h3
p
Property classes which allow enumerated data types must encode
integer constants representing the enumeration tokens, and
must provide a way of translating between the tokens and the
integers, and emvice versa/em. Depending on the number of
tokens in an enumeration set, the mapping from token to
integer is maintained in an array or a span
class=codefragHashMap/span. The switch-over point from
array to span class=codefragHashMap/span was determined
by some highly implementation-dependent testing to be in the
region of four to five elements.
/p
p
Many properties share common sets of enumeration tokens,
e.g. those which allow color values, and those applying to
borders and padding. A special case of enumerated value is
the mapped numeric enumeration, in which a token maps to a
Numeric value. These situations are discussed below.
/p
a name=N10020/a
h4Array representation/h4
p
a href= javascript:parent.displayCode(
'Direction.html#DirectionClass' ) span
class=codefragorg.apache.fop.fo.properties.Direction/span/a
is an example of a class which supports an enumerated value
with a small set of tokens. The a href=
javascript:parent.displayCode( 'Direction.html#dataTypes' )
span class=codefragdataTypes/span/a field contains
the a href= javascript:parent.displayCode(
'Property.html#NOTYPE' ) span class=codefragENUM/span
data type constant, defined in span
class=codefragProperty/span/a. The enumeration integer
constants are defined as span class=codefragpublic static
final int/span values, a href=
javascript:parent.displayCode( 'Direction.html#LTR') span
class=codefrag' ) LTR/span and span
class=codefragRTL/span/a. Associating enumeration
tokens with these integer constants occurs in the array a
href= javascript:parent.displayCode( 'Direction.html#rwEnums'
) span class=codefragString[] rwEnums/span/a, which
is initialized with the token strings. By convention, zero is
never used to represent a valid enumeration constant, anywhere
in this code. It is, of course, critical that synchronization
between span class=codefragrwEnums/span and the
enumeration constants be maintained.
/p
p
The publicly accessible mapping from enumeration token to
enumeration constant is achieved through the method a href=
javascript:parent.displayCode( 'Direction.html#getEnumIndex'
) span class=codefragint
getEnumIndex(String)/span/a. The corresponding mapping
from enumeration constant to enumeration token is achieved
through the method a href= javascript:parent.displayCode(
'Direction.html#getEnumText' ) span class=codefragString
getEnumText(int)/span/a.
/p
a name=N1005C/a
h4HashMap
cvs commit: xml-fop/src/documentation/content/design/alt.design/properties getInitialValue.html
pbwest 2003/01/20 06:55:02
Added: src/documentation/content/design/alt.design/properties
getInitialValue.html
Log:
Code documentation
Revision ChangesPath
1.1
xml-fop/src/documentation/content/design/alt.design/properties/getInitialValue.html
Index: getInitialValue.html
===
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
html
head
META http-equiv=Content-Type content=text/html; charset=ISO-8859-1
titleGenerating Initial Values/title
style type= text/css
span.codeDisplay {font:italic bold}
body {
font-family: Verdana, Helvetica, sans-serif;
}
.note { border: solid 1px #7099C5; background-color: #f0f0ff; }
.note .label { background-color: #7099C5; color: #ff; }
.content {
padding: 5px 5px 5px 10px;
font : Verdana, Helvetica, sans-serif; font-size : 90%;
}
/style
/head
body marginheight=0 marginwidth=0 topmargin=0 leftmargin=0 text=#00
bgcolor=#FF
div class=content
h1Generating Initial Values/h1
p
font size=-2bynbsp;Peter B. West/font
/p
ul class=minitoc
li
a href=#N10014Introduction/a
/li
li
a href=#N10021
Generating amp; Accessing Initial Values
/a
ul class=minitoc
li
a href=#N10062Properties without
getInitialValue()/a
/li
/ul
/li
/ul
a name=N10014/a
h3Introduction/h3
p
The a href=simple-properties.htmlprevious section/a
discussed the common data elements in the simplest examples of
property classes. This section discusses more complex classes
whose facilities are accessed only through various methods.
/p
a name=N10021/a
h3
Generating amp; Accessing Initial Values
/h3
p
a href= javascript:parent.displayCode( 'AutoRestore.html' )
span class=codefrag
org.apache.fop.fo.properties.AutoRestore/span/a is an
example of the next most complex property class. In
addition to all of the common static fields, these classes
have initial data value types which require the dynamic
generation of a PropertyValue instance.
/p
p
The method a href= javascript:parent.displayCode(
'AutoRestore.html#getInitialValue' ) span
class=codefragPropertyValue getInitialValue(int)/span/a
returns an instance of PropertyValue of the appropriate
subclass containing the initial value for this property. Like
the static data fields, this value is, in turn, stored in the
array of initial values maintained in the a href=
javascript:parent.displayCode(
'PropertyConsts.html#PropertyConstsClass' ) span
class=codefragPropertyConsts/span/a singleton a href=
javascript:parent.displayCode( 'PropertyConsts.html#pconsts'
) span class=codefragpconsts/span/a.` As with the
fields, the first invocation of the method a href=
javascript:parent.displayCode(
'PropertyConsts.html#setupProperty' ) span
class=codefragsetupProperty/span/a on the property
instantiates the singleton instance of the class, and stores
that instance in the in the a href=
javascript:parent.displayCode(
'PropertyConsts.html#properties' ) span
class=codefragProperty[] properties/span/a array of a
href= javascript:parent.displayCode(
'PropertyConsts.html#pconsts' ) span
class=codefragpconsts/span/a.
/p
p
Unlike the static data fields, however, the initial value is
not immediately generated. It is generated by a call to a
href= javascript:parent.displayCode(
'PropertyConsts.html#getInitialValue' ) span
class=codefragPropertyValue getInitialValue(int)/span/a
in a href= javascript:parent.displayCode(
'PropertyConsts.html#pconsts' ) span
class=codefragpconsts/span/a. This call, in turn,
locates the relevant instance of the particular property class
in the a href= javascript:parent.displayCode(
'PropertyConsts.html#properties' ) span class= codefrag
properties/span array of span class= codefrag
PropertyConsts/span/a, and invokes the span class=
codefrag getInitialValue()/span of that instance. A
side-effect of this call is to store the initial value in a
href= javascript:parent.displayCode(
'PropertyConsts.html#initialValues' ) span
cvs commit: xml-fop/src/documentation/content/design/alt.design/properties propertyExpressions.html simple-properties.html
pbwest 2003/01/20 06:56:34
Added: src/documentation/content/design/alt.design/properties
propertyExpressions.html simple-properties.html
Log:
Code documentation
Revision ChangesPath
1.1
xml-fop/src/documentation/content/design/alt.design/properties/propertyExpressions.html
Index: propertyExpressions.html
===
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
html
head
META http-equiv=Content-Type content=text/html; charset=ISO-8859-1
titleProperty Expression Parsing/title
style type= text/css
body {
font-family: Verdana, Helvetica, sans-serif;
}
.note { border: solid 1px #7099C5; background-color: #f0f0ff; }
.note .label { background-color: #7099C5; color: #ff; }
.content {
padding: 5px 5px 5px 10px;
font : Verdana, Helvetica, sans-serif; font-size : 90%;
}
/style
/head
body marginheight=0 marginwidth=0 topmargin=0 leftmargin=0 text=#00
bgcolor=#FF
div class=content
h1Property Expression Parsing/h1
p
font size=-2bynbsp;Peter B. West/font
/p
ul class=minitoc
li
a href=#N10014Property expression parsing/a
ul class=minitoc
li
a href=#N10044Data types/a
/li
li
a href=#N10252Tokenizer/a
/li
li
a href=#N1029CParser/a
/li
/ul
/li
/ul
a name=N10014/a
h3Property expression parsing/h3
p
The parsing of property value expressions is handled by two
closely related classes: a href=
javascript:parent.displayCode(
'PropertyTokenizer.html#PropertyTokenizerClass' ) span
class=codefragorg.apache.fop.fo.expr.PropertyTokenizer/span/a
and its subclass, a href= javascript:parent.displayCode(
'PropertyParser.html#PropertyParserClass' ) span
class=codefragorg.apache.fop.fo.expr.PropertyParser/span/a,
and by span class= codefrag refineParsing(int, FONode,
PropertyValue)/span methods in the individual property
classes. span class=codefragPropertyTokenizer/span, as
the name suggests, handles the tokenizing of the expression,
handing a href= javascript:parent.displayCode(
'PropertyTokenizer.html#EOF' ) emtokens/em/a back to
its subclass, span
class=codefragPropertyParser/span. span
class=codefragPropertyParser/span, in turn, returns a a
href= javascript:parent.displayCode(
'PropertyValueList.html#PropertyValueListClass' ) span
class= codefragPropertyValueList/span/a, a list of a
href= javascript:parent.displayCode(
'PropertyValue.html#PropertyValueInterface' ) span class=
codefragPropertyValue/span/as.
/p
p
The tokenizer and parser rely in turn on the datatype
definitions from the span
class=codefragorg.apache.fop.datatypes/span package,
which include the a href= javascript:parent.displayCode(
'PropertyValue.html#NO_TYPE' ) span class= codefrag
PropertyValue/span datatype constant definitions/a.
/p
a name=N10044/a
h4Data types/h4
p
The data types currently defined in
span class=codefragorg.apache.fop.datatypes/span include:
/p
table class=ForrestTable cellspacing=1 cellpadding=4
tr
th colspan=2 rowspan=1Numbers and lengths/th
/tr
tr
th colspan=1 rowspan=1Numeric/th
td colspan=3 rowspan=1
The fundamental length data type. emNumerics/em of
various types are constructed by the classes listed
below.
/td
/tr
tr
td colspan=1 rowspan=1/td
th colspan=3
rowspan=1Constructor classes for emNumeric/em/th
/tr
tr
td colspan=1 rowspan=1/td
td colspan=1 rowspan=1Ems/td
td colspan=2 rowspan=1Relative length in emems/em/td
/tr
tr
td colspan=1 rowspan=1/td
td colspan=1 rowspan=1IntegerType/td
td colspan=1 rowspan=1/td
/tr
tr
td colspan=1 rowspan=1/td
td colspan=1 rowspan=1Length/td
td colspan=2 rowspan=1In centimetres(cm), millimetres(mm),
inches(in), points(pt), picas(pc) or pixels(px)/td
/tr
tr
cvs commit: xml-fop/src/documentation/content/design/alt.design alt-design-frameset.html codeframe.html logo.html
pbwest 2003/01/20 06:59:18
Added: src/documentation/content/design/alt.design
alt-design-frameset.html codeframe.html logo.html
Log:
Code documentation
Revision ChangesPath
1.1
xml-fop/src/documentation/content/design/alt.design/alt-design-frameset.html
Index: alt-design-frameset.html
===
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Frameset//EN
html
head
titleAlt Design Frameset/title
META http-equiv=Content-Type content=text/html; charset=ISO-8859-1
style
body {
font-family: Verdana, Helvetica, sans-serif;
}
frame.logo {align=right;}
.note { border: solid 1px #7099C5; background-color: #f0f0ff; }
.note .label { background-color: #7099C5; color: #ff; }
.content {
padding: 5px 5px 5px 10px;
font : Verdana, Helvetica, sans-serif; font-size : 90%;
}
/style
script type=application/x-javascript
!--
var isWide = false;
var isHigh = true;
function widenCol() {
if (isWide) { return; }
fset = document.getElementById(altDesignFramesetCols);
fset.setAttribute(cols, 60%,*);
logowin = top.frames[0];
logodoc = logowin.document;
wbutton = logodoc.getElementById(widenButton);
//tnode = document.createTextNode();
//tchild = wbutton.firstChild;
wbutton.setAttribute(value, );
isWide = true;
}
function narrowCol() {
if ( ! isWide) { return; }
fset = document.getElementById(altDesignFramesetCols);
fset.setAttribute(cols, 200,*);
logowin = top.frames[0];
logodoc = logowin.document;
wbutton = logodoc.getElementById(widenButton);
//tnode = document.createTextNode();
//tchild = wbutton.firstChild;
//wbutton.replaceChild(tnode, tchild);
wbutton.setAttribute(value, );
isWide = false;
}
function toggleColWidths() {
if (isWide) {
narrowCol();
} else {
widenCol()
}
}
function lengthenCol() {
if (isHigh) { return; }
fset = document.getElementById(altDesignFramesetRows);
fset.setAttribute(rows, 75%,*);
logowin = top.frames[0];
logodoc = logowin.document;
lbutton = logodoc.getElementById(lengthenButton);
//tnode = document.createTextNode(^);
//tchild = lbutton.firstChild;
//lbutton.replaceChild(tnode, tchild);
lbutton.setAttribute(value, ^);
isHigh = true;
}
function shortenCol() {
if ( ! isHigh) { return; }
fset = document.getElementById(altDesignFramesetRows);
fset.setAttribute(rows, 100,*);
logowin = top.frames[0];
logodoc = logowin.document;
lbutton = logodoc.getElementById(lengthenButton);
//tnode = document.createTextNode(v);
//tchild = lbutton.firstChild;
//lbutton.replaceChild(tnode, tchild);
lbutton.setAttribute(value, v);
isHigh = false;
}
function toggleColHeights() {
if (isHigh) {
shortenCol();
} else {
lengthenCol()
}
}
function displayCode(src) {
top.frames[1].location = src;
widenCol();
shortenCol();
}
function displayHtml(src) {
top.frames[2].location = src;
narrowCol();
lengthenCol();
}
--
/script
/head
frameset id=altDesignFramesetCols cols=200,*
frameset id=altDesignFramesetRows rows=75%,*
frame id=logoFrame class=logo style=padding: 0px; margin: 0px:
border: 0px; src=logo.html scrolling=no
frame id= codeDisplayFrame
class= codeDisplay
src= codeframe.html
/frameset
frame id=contents src=properties/introduction.html
/frameset
/html
1.1
xml-fop/src/documentation/content/design/alt.design/codeframe.html
Index: codeframe.html
===
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
html
head
titleFrame for Code Display/title
style type=text/css
!--
p { text-align:center }
--
/style
/head
body
pFrame for code display./p
/body
/html
1.1 xml-fop/src/documentation/content/design/alt.design/logo.html
Index: logo.html
===
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01
Re: Named Destinations
[EMAIL PROTECTED] wrote: Hi all. Reading the mailing list archives (developer and user) I found that the topic of named destinations was raised several times and it seems that many people would like / need this feature. Studiying the changes list I even found the entry # Linking to a specific page and a named destinations of an external PDF file. (see www.adobe.com/products/acrobat/pdfs/c01acrotip.pdf) (CG) Thanks to Bernd Brandstetter. # update Unfortunately the corresponding patch (submitted on the user-list) seems not to be integrated in the next release 0.20.5. However, I could patch FOP myself. The patch from Bernd should work with the maintenance branch http://marc.theaimsgroup.com/?l=fop-cvsm=103478902410381w=2 [..] Now my kind plea is that some of the FOP gurus could take a look on it and integrate this functionality. I am sure that many users would appreciate it much. Sorry, to late for 0.20.5 Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 16237] - superscripts and subscipts are placed too high / too low
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16237. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16237 superscripts and subscipts are placed too high / too low --- Additional Comments From [EMAIL PROTECTED] 2003-01-20 15:21 --- Thanks for your contribution but I would rather not apply it to the maintenance branch because there are quite a few stylesheets out there which use vertical-align and this patch would probably make the documents look wrong (even if it corrects vertical-align) Of course we will consider this for the redesign. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Release
Ok, we should finally finish 0.20.5 Open issues: Remove xml-apis from Batik (Jeremias?) Joerg has mentioned bug #15936 as showstopper to me. (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15936) Should we try to fix this? If yes any volunteer? Anything else? Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/lib batik.jar
jeremias2003/01/20 08:11:13 Modified:lib Tag: fop-0_20_2-maintain batik.jar Log: Removed the classes also found in xml-apis.jar to fix problems in Eclipse, for example. The batik.jar is still 1.5beta4. Revision ChangesPath No revision No revision 1.5.2.5 +7 -203xml-fop/lib/batik.jar Binary file - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release
On 20.01.2003 16:33:28 Christian Geisert wrote: Ok, we should finally finish 0.20.5 Open issues: Remove xml-apis from Batik (Jeremias?) done (in branch). Joerg has mentioned bug #15936 as showstopper to me. (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15936) Should we try to fix this? If yes any volunteer? I probably could do it but not before Wednesday if nobody else wants it. Anything else? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [Fwd: xml.apache.org refactoring #1]
I'd volunteer if nobody else wants the job. On 20.01.2003 11:48:31 Oleg Tkachenko wrote: Christian Geisert wrote: From: Ted Leung [EMAIL PROTECTED] We ask each subproject to nominate 1 (or 2) people from that project to be a part of the XML PMC. From my experience, I think that it will be better to have 2 people rather than one in order to share workload, etc. So, they want 2 people, I believe it's not a problem for us to elect them, let's start - candidates? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Ready for 0.20.5 from my side
Can't we do it in a way that the history gets copied? That way, people downloading an old revision will have both src/org and src/java/org locally, so it uses a bit more storage capacity but still build. Is that doable? On 15.01.2003 19:41:51 Oleg Tkachenko wrote: Jeremias Maerki wrote: I'll continue to do the directory moves in the redesign and I'm still hoping for a volunteer to do the server side move/copy of the src/org directory to src/java/org. It's easy, but we'll loose ability to build old revisions then (didn't we yet?). If it's not an issue, all we have to do is to move the directory within the repository and massage CVSROOT/history, that's it, isn't it? Well, I'm going to try on local cvs first with xml-fop module. Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Release
Christian Geisert wrote: Joerg has mentioned bug #15936 as showstopper to me. (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15936) Actually, I can't reproduce it right now. I'll give it another try tomorrow. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [Fwd: xml.apache.org refactoring #1]
Jeremias Maerki wrote: I'd volunteer if nobody else wants the job. On 20.01.2003 11:48:31 Oleg Tkachenko wrote: Christian Geisert wrote: From: Ted Leung [EMAIL PROTECTED] We ask each subproject to nominate 1 (or 2) people from that project to be a part of the XML PMC. From my experience, I think that it will be better to have 2 people rather than one in order to share workload, etc. So, they want 2 people, I believe it's not a problem for us to elect them, let's start - candidates? Jeremias, +1 Next question: should we go with 1 or get another nomination? Peter -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Ready for 0.20.5 from my side
Jeremias Maerki wrote: Can't we do it in a way that the history gets copied? That way, people downloading an old revision will have both src/org and src/java/org locally, so it uses a bit more storage capacity but still build. Is that doable? On 15.01.2003 19:41:51 Oleg Tkachenko wrote: Jeremias Maerki wrote: I'll continue to do the directory moves in the redesign and I'm still hoping for a volunteer to do the server side move/copy of the src/org directory to src/java/org. It's easy, but we'll loose ability to build old revisions then (didn't we yet?). If it's not an issue, all we have to do is to move the directory within the repository and massage CVSROOT/history, that's it, isn't it? Well, I'm going to try on local cvs first with xml-fop module. I already have three trees - HEAD, maint and alt. The main thing is that particular distributions be reproduced. Make sure the complete tree is tagged just before the move. Then, when things are moved, you take the trouble to add a Moved from ... tag TAG comment to the cvs add phase, the trail can always be followed back from the cvs log. I don't know whether the same can be said of cvs remove. I've never tried it. Peter -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
