Fw: [Apache Newsletter Draft] News from XML sub/projects in July, 2003

[Tetsuya Kitahata]

Dear Apache FOP Delelopment Team, 
(http://xml.apache.org/fop/)


Hello,

I am now in the process of preparing the first all-Apache-wide newsletter.
http://www.apache.org/newsletter/

Please feel free to write statement/comment etc. to
the Apache Newsletter (Issue 1) using ApacheWiki
or in this mailing list. Hope to hear from you.
http://nagoya.apache.org/wiki/apachewiki.cgi?ApacheNewsletterDrafts/Issue1

Sincerely,

-- Tetsuya Kitahata ([EMAIL PROTECTED])

P.S. Apache FOP Project's Wikipage is here:
http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectPages

Forwarded by Tetsuya Kitahata <[EMAIL PROTECTED]>
--- Original Message ---
From:Tetsuya Kitahata <[EMAIL PROTECTED]>
To:  [EMAIL PROTECTED]
Date:Fri, 01 Aug 2003 17:29:35 +0900
Subject: [Apache Newsletter Draft] News from XML sub/projects in July, 2003



Hello, All (Apache XML General Mailing List Subscribers)


I am now preparing the 'The Apache Newsletter Issue 1',
the first ASF-wide-newsletter of July 2003, which will be published
in the middle of August 2003.
--  http://www.apache.org/newsletter/  --

This "Apache Newsletter" will be published as a result of the outgrowth
of the previous "Jakarta Newsletter" and "Apache Newsletter" can now
cover all the projects under apache.org including infrastructure,
incubator, xml, webservice, PHP, et cetra.


== WHAT WAS JAKARTA NEWSLETTER?? - http://jakarta.apache.org/site/news/


'The Apache Newsletter Issue 1' will be appeared at
http://www.apache.org/newsletter/200307.html
and the editorial deadline will be 00:00 GMT, 9th August.

ApacheWiki (http://nagoya.apache.org/wiki/apachewiki.cgi) had
been already set up.
If you have anything to be added to the ApacheWiki, please go to
http://nagoya.apache.org/wiki/apachewiki.cgi?ApacheNewsletterDrafts/Issue1
and fill up what you want to append in.
If there's nothing news-worthy on your sub/projects, then please write
something you *hope* (e.g. XX project will release FINAL version of
XX product in the middle of August, etc etc).

If you have been voted in warmly as a new committer in ASF the
last month (July) please add your name to the list on ApacheWiki.

If your project really want some "ADVERTISEMENT" (to recruit
new comers, etc etc), please write nice and catchy blurb at the
"advertisement" section so that it will attract the readers'
attentions.

Probably, the former newsletter final draft and newsletter itself
(Jakarta Newsletter Issue 9)
will give you some hints in writing the articles.
cf.
http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaNewsletterDrafts/Issue9
http://jakarta.apache.org/site/news/200305.html

If you have any questions about this, please send your messages to
[EMAIL PROTECTED] or this mailing list.

This Newsletter will be published as webpage and be announced
at [EMAIL PROTECTED] (the ASF-wide announcement list)
To subscribe to [EMAIL PROTECTED],
please follow this instruction:
http://www.apache.org/foundation/mailinglists.html#foundation-announce


Hope to hear from many Apache-XML sub/projects!!
(If you feel hesitation in writing articles on ApacheWiki, please
write your memo in this [EMAIL PROTECTED] mailing list or give me a note).
http://nagoya.apache.org/wiki/apachewiki.cgi?ApacheNewsletterDrafts/Issue1

Sincerely,


-- Tetsuya Kitahata ([EMAIL PROTECTED])

P.S. Contributions from anyone are cordially invited!!


-
Tetsuya Kitahata --  Terra-International, Inc.
E-mail: [EMAIL PROTECTED]
http://www.terra-intl.com/
(Apache Jakarta Translation, Japanese)
http://jakarta.terra-intl.com/

- Original Message Ends 


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

cvs commit: xml-fop/src/java/org/apache/fop/apps Driver.java FOInputHandler.java InputHandler.java XSLTInputHandler.java

[gmazza]

gmazza  2003/08/01 18:15:20

  Modified:src/java/org/apache/fop/apps Driver.java FOInputHandler.java
InputHandler.java XSLTInputHandler.java
  Log:
  1.  Moved the XMLReader createParser() functionality from abstract class 
InputHandler to FOInputHandler.
  2.  Added the setting of the "namespace-prefix" SAX option directly into 
createParser(), and removed function setParserFeatures (where it was previously being 
set).
  3.  Removed the duplicate XMLReader creation code in Driver.run(), it now uses 
FOTreeBuilder.createParser().
  
  Revision  ChangesPath
  1.14  +2 -11 xml-fop/src/java/org/apache/fop/apps/Driver.java
  
  Index: Driver.java
  ===
  RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/apps/Driver.java,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- Driver.java   29 Jul 2003 19:08:22 -  1.13
  +++ Driver.java   2 Aug 2003 01:15:20 -   1.14
  @@ -579,7 +579,6 @@
   public synchronized void render(InputHandler inputHandler)
   throws FOPException {
   XMLReader parser = inputHandler.getParser();
  -inputHandler.setParserFeatures(parser);
   render(parser, inputHandler.getInputSource());
   }
   
  @@ -660,15 +659,8 @@
   
   if (reader == null) {
   if (!(source instanceof DocumentInputSource)) {
  -try {
  -SAXParserFactory spf = 
javax.xml.parsers.SAXParserFactory.newInstance();
  -spf.setNamespaceAware(true);
  -reader = spf.newSAXParser().getXMLReader();
  -} catch (SAXException e) {
  -throw new FOPException(e);
  -} catch (ParserConfigurationException e) {
  -throw new FOPException(e);
  -}
  +//TODO: (gm) rename to FOFileHandler or similar
  +reader = org.apache.fop.apps.FOInputHandler.createParser();
   }
   }
   
  @@ -678,6 +670,5 @@
   render(reader, source);
   }
   }
  -
   }
   
  
  
  
  1.5   +29 -1 xml-fop/src/java/org/apache/fop/apps/FOInputHandler.java
  
  Index: FOInputHandler.java
  ===
  RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/apps/FOInputHandler.java,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- FOInputHandler.java   17 Jun 2003 16:35:57 -  1.4
  +++ FOInputHandler.java   2 Aug 2003 01:15:20 -   1.5
  @@ -53,11 +53,16 @@
   // Imported SAX classes
   import org.xml.sax.InputSource;
   import org.xml.sax.XMLReader;
  +import org.xml.sax.SAXException;
  +import org.xml.sax.SAXNotSupportedException;
   
   // java
  +import javax.xml.parsers.SAXParserFactory;
  +import javax.xml.parsers.ParserConfigurationException;
   import java.io.File;
   import java.net.URL;
   
  +
   /**
* Manages input if it is an XSL-FO file.
*/
  @@ -97,7 +102,7 @@
* @see org.apache.fop.apps.InputHandler#getParser()
*/
   public XMLReader getParser() throws FOPException {
  -return super.createParser();
  +return createParser();
   }
   
   /**
  @@ -107,6 +112,29 @@
   throw new FOPException("not implemented: FOInputHandler.run(Driver)");
   }
   
  +/**
  + * Creates XMLReader object using default
  + * SAXParserFactory
  + * @return the created XMLReader
  + * @throws FOPException if the parser couldn't be created or configured for 
proper operation.
  + */
  +protected static XMLReader createParser() throws FOPException {
  +try {
  +SAXParserFactory factory = SAXParserFactory.newInstance();
  +factory.setNamespaceAware(true);
  +factory.setFeature(
  +"http://xml.org/sax/features/namespace-prefixes";, true);
  +return factory.newSAXParser().getXMLReader();
  +} catch (SAXNotSupportedException se) {
  +throw new FOPException("Error: You need a parser which allows the"
  +   + " http://xml.org/sax/features/namespace-prefixes";
  +   + " feature to be set to true to support namespaces", se);
  +} catch (SAXException se) {
  +throw new FOPException("Couldn't create XMLReader", se);
  +} catch (ParserConfigurationException pce) {
  +throw new FOPException("Couldn't create XMLReader", pce);
  +}
  +}
   
   }
   
  
  
  
  1.6   +0 -35 xml-fop/src/java/org/apache/fop/apps/InputHandler.java
  
  Index: InputHandler.java
  ===
  RCS file: /home/cvs/xml-fop/src/java/org/apache/fop/apps/InputHandler.java,v
  retrieving revision 1.5
  retrieving revision 

Re: default value of "force" param for FOP

[M. Sean Gilligan]

>
>(c) include force in 0.20, default it to "false", but
>have a message in the release notes warning about the
>change.
>
>Technically, even if most users forgot to read the
>warning in (c) they would still be OK, as they would
>be happy if no time was spent with unnecessary
>regnerations.  However, due to internal links to other
>files that might have changed, etc.--which force does
>not capture, either here or in --there could be
>a difference in functionality.

In those cases, the Ant  task can be used to capture those dependencies.  
(I believe that is the best way to handle this in Ant.)

>Thoughts?

Sorry for not responding sooner - I've been burning the midnight oil for a client this 
week and am behind on my email.

Although the patch I submitted was for (b), my preference would be for (c) for the 
reasons you state (conformance with  task and the most sensible long-term 
solution)

I would really like to see this in the 0.20 branch because I am using Ant +  + 
 for a DocBook publishing toolchain which I would like to post to SourceForge or 
perhaps someday an Apache sub-project.  The idea is that Ant buildfiles can be used to 
build a (potentially large) set of documents with common components.  The Ant build 
would only rebuild the necessary pieces.  Since  and  processing of large 
documents is measured in minutes eliminating unnecessary processing is a huge win.

The 1.0 release is at best several months away (right?) - so choice (c) provides a 
valuable feature to fop users in the meantime.  I am willing to help out by testing or 
responding to questions on the lists to help make (c) a reality.

Thanks, again, to the FOP group for this powerful tool.

Regards,

Sean


-- 
---
M. Sean Gilligan: mailto:[EMAIL PROTECTED]
Catalla Systems, Inc.   : 831-439-9568 x11
---

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

RE: FOP logo (+ a graphics question)

[Victor Mote]

Clay Leeds wrote:

> What is the status of the FOP logo? If we need it tweaked, I can help.

That would be great. The last word on the subject is here:
http://marc.theaimsgroup.com/?l=fop-dev&m=105593071722327&w=2

Here is what I suggest:

1. Find the SVG document for #30, which won the contest. It looks like Oleg
doesn't have it. Would you please contact Scott Hofman directly (see the
above link for a link to him) to obtain a copy of it, create a Bugzilla
issue with it attached, and we'll get it into the repository.

2. We need to decide 1) whether additional tweaking is necessary, and 2) how
to decide what tweaking needs to be done, 3) get the tweaking actually done
(in addition to your offer, I think Scott made a similar offer), and
committed to the repository. I propose that we take the logo as is, and
revisit the issue in the future if we think its important. I don't think we
can afford to spend any more bandwidth on it now.

Here is my +1.

3. Research where the logo is needed. I can't think of any place other than
our website. For each place it is needed, we need to consider making a jpg
scaled properly. The existing jpg may be fine.

4. We'll need to get our Forrest web build to pick up the svg and/or the
jpg. Probably the most efficient way to proceed is for me to see if it can
be done easily.

5. When this is all done & visible, we can remove the logocontest page.

Thanks for helping get this done. I think it is useful to get some of this
old stuff cleaned up, to "clear the decks".

Victor Mote


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

FOP logo (+ a graphics question)

[Clay Leeds]

What is the status of the FOP logo? If we need it tweaked, I can help.
--
Clay Leeds - [EMAIL PROTECTED]
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

DO NOT REPLY [Bug 22027] - FOP Status graphic needs update

[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=22027

FOP Status graphic needs update

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2003-08-01 15:16 ---
Committed to CVS, along with updates to the statistics. Thanks, Clay.

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

DO NOT REPLY [Bug 22053] New: - basic-link off by footer height in table

[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=22053

basic-link off by footer height in table

   Summary: basic-link off by footer height in table
   Product: Fop
   Version: 0.20.5
  Platform: PC
OS/Version: Windows XP
Status: NEW
  Severity: Normal
  Priority: Other
 Component: pdf renderer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When adding a table-footer the hotspot for a basic-length appears to be offset 
toward the bottom by the height of the footer. Is the position incorrectly 
taking into account the table rows in the footer?

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

DO NOT REPLY [Bug 22048] - PDF renderer and hyphenation break character order

[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=22048

PDF renderer and hyphenation break character order

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2003-08-01 12:40 ---
This has been fixed already. Get the latest release.

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

DO NOT REPLY [Bug 22048] New: - PDF renderer and hyphenation break character order

[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=22048

PDF renderer and hyphenation break character order

   Summary: PDF renderer and hyphenation break character order
   Product: Fop
   Version: 0.20.4
  Platform: PC
   URL: http://staff.csc.fi/aniemela/fopbug2.pdf
OS/Version: Linux
Status: NEW
  Severity: Major
  Priority: Other
 Component: page-master/layout
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The PDF renderer/page layout component/hyphenation break character order with
inline elements:
The following construct


  Otsakerivin vapaamuotoisuuden takia ainoat jarkevasti hyodynnettavat
  arvot ovat kentan nimi ( 
   
  ) ja DT-numero. 

Is rendered as
Otsakerivin [] hyodynnettavat arvot ovat kentan nimi ( mel-
 ) ja DT-numero.

Below is a cleaned-up version of Docbook-XSLT-produced FO data, which explains
the block-happiness. URL points to a FOP 0.20.4 rendered PDF which illustrates
the bug.

Full XSL-FO data follows:
 
  http://www.w3.org/1999/XSL/Format"; font-family="serif"
font-size="10pt" text-align="left" line-height="normal"
font-selection-strategy="character-by-character" language="en">


   



   


   


   


  
 
 
 
 
  

  
  http://www.antennahouse.com/names/XSL/Extensions";
hyphenate="true" master-reference="body" 
language="fi" format="1" initial-page-number="1"
hyphenation-character="-" 
hyphenation-push-character-count="2"
hyphenation-remain-character-count="2">

  

  

  

   1.1.1.
Datamerkinnan otsakerivi 

  

  
   


  Otsakerivin vapaamuotoisuuden takia ainoat jarkevasti hyodynnettavat
arvot ovat kentan nimi ( 
   
  ) ja DT-numero. 

  

  


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