Re: duplicated sax classes

2003-01-19 Thread Keiron Liddle 

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.

On Sunday, January 19, 2003, at 06:41  PM, 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.

On 19.01.2003 12:05:53 Oleg Tkachenko wrote:
We've got SAX classes both in xml-apis.jar and batik.jar. I don't care 
about
superfluous 10-20 Kb, but unfortunately it causes problems in some
environments, for instance in eclipse. One fellow has developed FOP 
plugin for
eclipse and he's got "Duplicate class definition" problem because of 
it, but
when he replaces batik.jar for a bunch of batik jars except of 
batik-ext.jar
it works ok.
Anybody has any ideas?


Jeremias Maerki



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Re: duplicated sax classes

2003-01-19 Thread Jeremias Maerki 
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.

On 19.01.2003 12:05:53 Oleg Tkachenko wrote:
> We've got SAX classes both in xml-apis.jar and batik.jar. I don't care about 
> superfluous 10-20 Kb, but unfortunately it causes problems in some 
> environments, for instance in eclipse. One fellow has developed FOP plugin for 
> eclipse and he's got "Duplicate class definition" problem because of it, but 
> when he replaces batik.jar for a bunch of batik jars except of batik-ext.jar 
> it works ok.
> Anybody has any ideas?


Jeremias Maerki


-
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

2003-01-19 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
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-19 13:37 ---
Created an attachment (id=4488)
diff file which corrects this bug

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

DO NOT REPLY [Bug 16237] New: - superscripts and subscipts are placed too high / too low

2003-01-19 Thread bugzilla 
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
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

   Summary: superscripts and subscipts are placed too high / too low
   Product: Fop
   Version: 0.20.4
  Platform: All
OS/Version: All
Status: NEW
  Severity: Minor
  Priority: Other
 Component: page-master/layout
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Using "super" / "sub" in property vertical-align will place the characters
too high / too low. This is due to a minor mistake in class LineArea.
In method verticalAlign() the offset of the super/subscript is computed by
taking 2/3 of ascender for the choosen font. The value which should be used
must be 1/3 because you want to get a 2/3 overlap with the text before/after.


/**
 * Balance (vertically) the inline areas within this line.
 */
public void verticalAlign() {
int superHeight = -this.placementOffset;
int maxHeight = this.allocationHeight;
Enumeration e = children.elements();
while (e.hasMoreElements()) {
Box b = (Box)e.nextElement();
if (b instanceof InlineArea) {
InlineArea ia = (InlineArea)b;
if (ia instanceof WordArea) {
ia.setYOffset(placementOffset);
}
if (ia.getHeight() > maxHeight) {
maxHeight = ia.getHeight();
}
int vert = ia.getVerticalAlign();
if (vert == VerticalAlign.SUPER) {
int fh = fontState.getAscender();
// was: ia.setYOffset((int)(placementOffset - (2.0 * fh / 
3.0)));
ia.setYOffset((int)(placementOffset - (fh / 3.0)));
} else if (vert == VerticalAlign.SUB) {
int fh = fontState.getAscender();
// was: ia.setYOffset((int)(placementOffset + (2.0 * fh / 
3.0)));
ia.setYOffset((int)(placementOffset + (fh / 3.0)));
}

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

duplicated sax classes

2003-01-19 Thread Oleg Tkachenko 
Hello!

We've got SAX classes both in xml-apis.jar and batik.jar. I don't care about 
superfluous 10-20 Kb, but unfortunately it causes problems in some 
environments, for instance in eclipse. One fellow has developed FOP plugin for 
eclipse and he's got "Duplicate class definition" problem because of it, but 
when he replaces batik.jar for a bunch of batik jars except of batik-ext.jar 
it works ok.
Anybody has any ideas?

--
Oleg Tkachenko
eXperanto team
Multiconn Technologies, Israel


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]