Re: Java text geometry

2004-06-29 Thread Peter B. West
Christian,
Sorry it's taken me so long to get back to you on this.  What's UTA?
Peter
Christian Z. wrote:
Hi Peter,
I didn't have a look at your work yet. So perhaps there's no reason for
me to speak up at all.
I personally find the Java Text API hard to extend and not very modular.
So here's my request. Could you please provide some kind of hook in form
of an interface so that I can easily write a patch for UTA anytime?
You'll also need some kind of attributed string like Java provides in
its java.text package. Would be fine to have a place where I can grab
the input in a well defined format and pass the result back to FOP.
--
Peter B. West http://www.powerup.com.au/~pbwest/resume.html


RE: FOP site update

2004-06-29 Thread Victor Mote
Clay Leeds wrote: 

 Way ahead of you[1]! (I'm using the version re-created by 
 Victor--and 'improved' by me a little. I/we never got a 
 vector-based version of that one, even though I like the 
 'mirrors' version you linked to better. We need a 
 vector-based version so we can have resolution-independence).

I can see two vector-based versions in ViewCVS. The SVG version is here:
http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/resources/images
/logo2.svg
The Adobe Illustrator version is here:
http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/resources/images
/logo2.ai

Here is the concurrent mailing list discussion:
http://marc.theaimsgroup.com/?l=fop-devm=107091332015607w=2

Victor Mote



Re: FOP site update

2004-06-29 Thread Clay Leeds
On Jun 29, 2004, at 7:41 AM, Victor Mote wrote:
Clay Leeds wrote:
Way ahead of you[1]! (I'm using the version re-created by
Victor--and 'improved' by me a little. I/we never got a
vector-based version of that one, even though I like the
'mirrors' version you linked to better. We need a
vector-based version so we can have resolution-independence).
I can see two vector-based versions in ViewCVS. The SVG version is  
here:
http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/resources/ 
images
/logo2.svg
The Adobe Illustrator version is here:
http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/resources/ 
images
/logo2.ai

Here is the concurrent mailing list discussion:
http://marc.theaimsgroup.com/?l=fop-devm=107091332015607w=2
Victor Mote
Sorry... I should've been more clear. The version I have[1] *is* the  
vector-based version I believe you (Victor) re-created. It's is *very*  
close to the original (great job Victor!), except the original had a  
'3D' ink bottle and '?xml' in the upper left quadrant of the 'O' in  
'FOP' (which I added). (Lest we forget... I am the original, official  
FOP nitpicker[2]! ;-p).

In any case, I used the AI version to output JPG  GIF versions... but  
had some trouble getting a clean version with anything other than a  
white background. [OT] Exacerbating the problem is that I just switched  
to a new Powerbook G4, but my Fireworks install was clobbered. I'm  
still having trouble getting it to work, which isn't helping things.

Also, I've been working to implement a different Forrest 'skin', but I  
keep getting errors when I switch from the forrest-site skin to other  
skins. When that is resolved, things will fall into place.

Web Maestro Clay
[1]
http://homepage.mac.com/webmaestro/xml-fop/
[2]
http://xml.apache.org/fop/team.html#cl
(NOTE: [OT] some may have noticed, that I've added IDs for each person,  
so appending '#your_initials' to the team.html link brings you to your  
entry... :-)



Re: Java text geometry

2004-06-29 Thread Christian Z.
Hi Peter!

 Sorry it's taken me so long to get back to you on this.  What's UTA?

UTA (Unified Typesetting API) is my attempt to provide an API for
typesetting that can be used by all kinds of text processing
applications. The primary goals are
* the ability that support for new scripts can easily be added
* support for low and high quality implementations of the API

Currently UTA provides an API for line-breaking similar to TeX's
mechanism (also TeX's behavior should be a special case of my model)
which I think is quite stable and will change only little till the
Milestone 1 release anytime around 9/1/2004. It also provides an
implementation of the simple-fit line-breaking algorithm as proof of
concept. There's also a helper package to allow global optimizing
line-break algorithms using a BSD licensed graph theory package (only
found a forrest report about an apache graph library without further
information, Jeremias). This package may be irrelevant in future
releases and is not needed to use the API. Furthermore there's the API
of how I think multilingual text can be set. This is subject to change,
I'll have to refactor/cleanup a bit and add some ideas.

Note that the code currently reflects my knowledge and therefore is
subject to change and perhaps will not fulfill all future requirements
right now. Note also that my focus currently only lies on the task to
define an API on how to typeset multilingual glyphs and how to break a
paragraph into lines. I can't currently provide implementations for
typesetting nor for advanced line-breaking algorithms.

UTA addresses some of FOP's low priority tasks and I think the task
you're currently working on. I had to take a look into the problems of
multilingual typesetting, TeX, XSL, the Java API, Pango, ATSUI,... I do
not claim to know everything about all of this technologies but I think
I can be of use for you providing you with further reading or something
else. So, just ask, if there are questions. Furthermore I'm currently
talking to the ExTeX people. IMO ExTeX will be _very_ similar to FOP in
the end effect, but currently has different priorities. And of course it
will be based on TeX in some kind not XSL. Cause they want to eliminate
TeX's drawbacks (including multilingual text) it perhaps makes sense to
get in touch with them too. BTW: They would like to use the Batik code
for reading TTF-files. I think there are Batik members here too? Perhaps
one of you could drop them a line...

Congratulations to your marriage from me too,
Christian Z.



Problems with URL encoding in FOP docs

2004-06-29 Thread Peter B. West
Fops,
In http://xml.apache.org/fop/design/alt.design/index.html there occurs 
the following link:
a 
href=http://marc.theaimsgroup.com/%3Fl=fop-dev%26m=103890259919360%26w=2;

The question mark and ampersand are encoded as expected.  When I hover 
on this link in Mozilla, I get:
http://marc.theaimsgroup.com/?l=fop-devm=103890259919360w=2
as expected.

When I follow the link, I get the _encoded_ values in the location 
window, and the website tells me that URL with the _unencoded_ values is 
not available.  When I manually change the URL in the location window to 
contain the _encoded_ values, it works.

How do I fix this?
Peter
--
Peter B. West http://www.powerup.com.au/~pbwest/resume.html


Re: Javasrc, JXR and documentation

2004-06-29 Thread Peter B. West
Clay,
FYI, Java 1.4 javadoc tool supports a -linksource argument, which 
generates html of source files.  However, the process seems to have 
pretty much the same restrictions as the Maven JXR - the only references 
are to line numbers, which is just about the most useless form imaginable.

It might be of interest to someone at a later stage to look at extending 
the standard doclet to utilise Javasrc to perform that generation.

Peter
--
Peter B. West http://www.powerup.com.au/~pbwest/resume.html