2009/10/19 Sander W G van der Waal <sander.vanderwaal@oucs.ox.ac.uk>: > Hello, > > I am a new user of Forrest and downloaded and installed the 0.8 > release of Forrest last Friday. I want to run Forrest locally on > an existing Forrest-website, so after installation I executed > 'forrest run' from the basedir of my website. The following error > appeared : > > C:\java\apache-forrest-0.8\main\targets\plugins.xml:359: STOP GENERATION ! > WARNING - Cannot find the plugin description > ============================================ > > Unable to find the description of org.apache.forrest.plugin.output.inputModule in the different descriptor files. ... > I could not find anything on my problem in the documentation / list / issue > tracker. Did I overlook something? Is there a better way to handle this? This occurs when a site is using dispatcher based site. Dispatcher is in the whiteboard still and has been under heavy development since version 0.8. I suspect the site you are trying to build requires Forrest 0.9-dev - which is the version in SVN Ross
Hello,
I am a new user of Forrest and downloaded and installed the 0.8
release of Forrest last Friday. I want to run Forrest locally on
an existing Forrest-website, so after installation I executed
'forrest run' from the basedir of my website. The following error
appeared :
C:\java\apache-forrest-0.8\main\targets\plugins.xml:359: STOP GENERATION !
WARNING - Cannot find the plugin description
============================================
Unable to find the description of org.apache.forrest.plugin.output.inputModule in the
different descriptor files.
The output.inputModule was indeed present in my project.required.plugins
list in forrest.properties, which seems mandatory following FOR-926 [1].
The local plugin list in plugins/plugins.xml of release 0.8 contains a
reference to output.inputModule, but this file is overridden with the
public plugins.xml [2] which does not contain the reference to
output.inputModule (because of FOR-1103 [3]?).
Since the public plugin list is not version specific I suspect it would
still need older plugins listed there, but I am only new here so I am
not sure I understand the mechanism correctly.
I got it up-and-running by changing the ant file main/targets/plugins.xml,
task fetch-plugins-descriptors. Changing the var plugin-counter to 3 on
line 293 kept the local plugins.xml files and added the remote ones instead
of overriding them. This worked for me but it may not be the way Forrest
should be used.
I could not find anything on my problem in the documentation / list / issue
tracker. Did I overlook something? Is there a better way to handle this?
Best regards,
Sander van der Waal
[1] http://issues.apache.org/jira/browse/FOR-926
[2] http://forrest.apache.org/plugins/plugins.xml
[3] http://issues.apache.org/jira/browse/FOR-1103
Done in the source at r826262. Thanks, --tim On Sat, Oct 17, 2009 at 10:23 AM, Monika Schaefer <monika@schaefer-wilhelmsdorf.de> wrote: > Hello > > Im sorry but I have to inform you that www.krabbelkaefer.de is no longer > using forrest as it it's content has been removed. > Would you please remove the link from your Live Sites List. > > I want to thank you all, forrest ist a great project. > > Bye > Monika Schäfer >
Hello Im sorry but I have to inform you that www.krabbelkaefer.de is no longer using forrest as it it's content has been removed. Would you please remove the link from your Live Sites List. I want to thank you all, forrest ist a great project. Bye Monika Schäfer
VTD-XML 2.7 (http://vtd-xml.sf.net) is released and can be downloaded at http://sourceforge.net/projects/vtd-xml/files/. Below is a summary of what are the new features and enhancements. Expanded VTD-XML's Core API a.. VTDNav: toStringUpperCase, toStringLowerCase, contains(), endsWith(), startsWith() b.. Extended VTD added in-memory buffer support Improved Xpath a.. Added the following XPath 2.0 functions: abs(), ends-with(), upper-case(), lower-case() b.. Added support for variable reference * significantly enhanced XPath syntax, checking error reporting (Special thanks to Mark Swanson) c.. Internal performance tuning Bug fixes and Code Enhancement a.. C version significantly removed warning message, fix memory leak during Xpath expression parsing, b.. Various bug fies (Special thanks to Jon Roberts, John Zhu, Matej Spiller, Steve Polson, and Romain La Tellier)
----- Forwarded message from Sally Khudairi ----- Sign up for ApacheCon US by 14 August and save up to $500! This year's ApacheCon US promises to deliver our most extensive program to date, and largest anticipated gathering of the global Apache community to celebrate the ASF's milestone 10th Anniversary. The San Francisco Bay Area is where the very first ASF official user conference was held, and we hope that you will join us in celebrating the ASF's success! Apache members, code contributors, users, developers, system administrators, business managers, service providers, and vendors will convene 2-6 November in Oakland, California, for a week of training, presentations, sharing and hacking. ApacheCon US 2009 features new content tracks, MeetUps, and GetTogethers, as well as a number of events open to the public free of charge, such as the Hackathon and 2-day BarCampApache, in appreciation of their support over the past decade. Be sure to register by 14 August to save up to $500! To sign up, visit http://www.us.apachecon.com/ Those wishing to attend ApacheCon, but may be unable to do so due to financial reasons are encouraged to apply for Travel Assistance by completing the form at http://www.apache.org/travel/ Financial support for flights, accommodation, subsistence, and conference fees are availablAnyone involved in Open Source is welcome to apply for financial support for flights, accommodation, subsistence and Conference fees. Hurry, applications close on 17 August. Conference sponsor, exhibitor, and community partnerships are also available: please contact Delia Frees at delia@apachecon.com for details. # # # ----- End forwarded message -----
On Wed, Jul 29, 2009 at 2:51 PM, Joao Ferreira<jmcferreira@critical-links.com> wrote: > Hello all, > > is i18n supported in any form by Forrest ? could anyone point me to some > docs or best practices on Internationalizing a document written with > Forrest ? > > at my company we are on the verge on starting translating our documents > and I'dd like to get my hands on the biggest issues and understand > exactlly how Forrest would help us on this... > > I'm realy a beginner in this issue, but I need to get into this matter > to understandf just how we will do this... it seems a big and complex > task. > > THX for any pointers. Have you tried playing around with the sample[1]? It might give you a good idea of how things work.. I also found this issue[2] that led to that page's creation. I'm not sure why it was decided to put it only as a sample and not with the real docs. We should probably change that. --tim [1] - http://forrest.zones.apache.org/ft/build/forrest-seed/samples-c/i18n.html [2] - https://issues.apache.org/jira/browse/FOR-707
Hello all, is i18n supported in any form by Forrest ? could anyone point me to some docs or best practices on Internationalizing a document written with Forrest ? at my company we are on the verge on starting translating our documents and I'dd like to get my hands on the biggest issues and understand exactlly how Forrest would help us on this... I'm realy a beginner in this issue, but I need to get into this matter to understandf just how we will do this... it seems a big and complex task. THX for any pointers. Joao
Forwarded from Travel Assistance Committee: The Travel Assistance Committee is taking in applications for those wanting to attend ApacheCon US 2009 (Oakland) which takes place between the 2nd and 6th November 2009. The Travel Assistance Committee is looking for people who would like to be able to attend ApacheCon US 2009 who may need some financial support in order to get there. There are limited places available, and all applications will be scored on their individual merit. Applications are open to all open source developers who feel that their attendance would benefit themselves, their project(s), the ASF and open source in general. Financial assistance is available for flights, accommodation, subsistence and Conference fees either in full or in part, depending on circumstances. It is intended that all our ApacheCon events are covered, so it may be prudent for those in Europe and/or Asia to wait until an event closer to them comes up - you are all welcome to apply for ApacheCon US of course, but there should be compelling reasons for you to attend an event further away that your home location for your application to be considered above those closer to the event location. More information can be found on the main Apache website at http://www.apache.org/travel/index.html - where you will also find a link to the online application and details for submitting. Applications for applying for travel assistance will open on 27th July 2009 and close of the 17th August 2009. Good luck to all those that will apply. Regards, The Travel Assistance Committee --------------------
On Mon, Jun 22, 2009 at 10:52:26AM +0200, Cyriaque Dupoirieux wrote: > le 10/06/2009 09:57 Derek Baum a écrit : >> Hi, >> >> We've been successfully using forrest 0.8 for over a year now and we >> like the ability to build content from openoffice .odt documents. >> (http://newton.codecauldron.org) >> >> We largely have this working, but we still find that it is sensitive >> to what type of images are embedded in the .odt file: .png and .jpg >> images render fine, but .tiff images do not. >> >> Is this just because the file extension in the OO file is .tif rather >> than .tiff, or something else? >> >> $ unzip -l InstallationGuide.odt >> Archive: InstallationGuide.odt >> Length Date Time Name >> -------- ---- ---- ---- >> 39 06-05-09 16:49 mimetype >> 0 06-05-09 16:49 Configurations2/images/Bitmaps/ >> 127620 06-05-09 16:49 Pictures/1000000000000280000001E02A9E9828.tif >> 59894 06-05-09 16:49 Pictures/1000000000000280000001E0E2C50ACF.tif >> 7160 06-05-09 16:49 Pictures/1000000000000196000001142835D184.jpg >> >> Up until now, we have just been replacing embedded .tiff images with >> .png or .jpg, but this is a pain. >> >> Can anyone suggest how to fix this properly? >> >> Thanks, >> >> Derek >> >> > Hi, > > I am going to work a little on forrest on friday, > I will see what's the problem with tif files. I'm sorry, I forgot to report that I did some troubleshooting on this. I tried David's suggestion with raw.xmap, but I didn't notice any change. When I called the full URL of the graphic that wasn't displaying as it should have done, the image was fetched but the mime-type was not what I specified in raw.xmap. Brian > Did you create an issue for this in Jira ? > > -- > Salutations, > Cyriaque >
Hi, No I didn't create a Jira issue. I have not yet tried David's suggestion of looking in raw.xmap, as I'm currently travelling, but I hope to try it next week. Derek 2009/6/22 Cyriaque Dupoirieux <cyriaque.dupoirieux@pco-innovation.com> > le 10/06/2009 09:57 Derek Baum a écrit : > > Hi, >> >> We've been successfully using forrest 0.8 for over a year now and we like >> the ability to build content from openoffice .odt documents. ( >> http://newton.codecauldron.org) >> >> We largely have this working, but we still find that it is sensitive to >> what type of images are embedded in the .odt file: .png and .jpg images >> render fine, but .tiff images do not. >> >> Is this just because the file extension in the OO file is .tif rather than >> .tiff, or something else? >> >> $ unzip -l InstallationGuide.odt >> Archive: InstallationGuide.odt >> Length Date Time Name >> -------- ---- ---- ---- >> 39 06-05-09 16:49 mimetype >> 0 06-05-09 16:49 Configurations2/images/Bitmaps/ >> 127620 06-05-09 16:49 Pictures/1000000000000280000001E02A9E9828.tif >> 59894 06-05-09 16:49 Pictures/1000000000000280000001E0E2C50ACF.tif >> 7160 06-05-09 16:49 Pictures/1000000000000196000001142835D184.jpg >> >> Up until now, we have just been replacing embedded .tiff images with .png >> or .jpg, but this is a pain. >> >> Can anyone suggest how to fix this properly? >> >> Thanks, >> >> Derek >> >> >> Hi, > > I am going to work a little on forrest on friday, > I will see what's the problem with tif files. > Did you create an issue for this in Jira ? > > -- > Salutations, > Cyriaque > >
le 10/06/2009 09:57 Derek Baum a écrit : > Hi, > > We've been successfully using forrest 0.8 for over a year now and we > like the ability to build content from openoffice .odt documents. > (http://newton.codecauldron.org) > > We largely have this working, but we still find that it is sensitive > to what type of images are embedded in the .odt file: .png and .jpg > images render fine, but .tiff images do not. > > Is this just because the file extension in the OO file is .tif rather > than .tiff, or something else? > > $ unzip -l InstallationGuide.odt > Archive: InstallationGuide.odt > Length Date Time Name > -------- ---- ---- ---- > 39 06-05-09 16:49 mimetype > 0 06-05-09 16:49 Configurations2/images/Bitmaps/ > 127620 06-05-09 16:49 Pictures/1000000000000280000001E02A9E9828.tif > 59894 06-05-09 16:49 Pictures/1000000000000280000001E0E2C50ACF.tif > 7160 06-05-09 16:49 Pictures/1000000000000196000001142835D184.jpg > > Up until now, we have just been replacing embedded .tiff images with > .png or .jpg, but this is a pain. > > Can anyone suggest how to fix this properly? > > Thanks, > > Derek > > Hi, I am going to work a little on forrest on friday, I will see what's the problem with tif files. Did you create an issue for this in Jira ? -- Salutations, Cyriaque
Derek Baum wrote: > > We've been successfully using forrest 0.8 for over a year now and we like > the ability to build content from openoffice .odt documents. ( > http://newton.codecauldron.org) > > We largely have this working, but we still find that it is sensitive to what > type of images are embedded in the .odt file: .png and .jpg images render > fine, but .tiff images do not. > > Is this just because the file extension in the OO file is .tif rather than > .tiff, or something else? > > $ unzip -l InstallationGuide.odt > Archive: InstallationGuide.odt > Length Date Time Name > -------- ---- ---- ---- > 39 06-05-09 16:49 mimetype > 0 06-05-09 16:49 Configurations2/images/Bitmaps/ > 127620 06-05-09 16:49 Pictures/1000000000000280000001E02A9E9828.tif > 59894 06-05-09 16:49 Pictures/1000000000000280000001E0E2C50ACF.tif > 7160 06-05-09 16:49 Pictures/1000000000000196000001142835D184.jpg > > Up until now, we have just been replacing embedded .tiff images with .png or > .jpg, but this is a pain. > > Can anyone suggest how to fix this properly? See $FORREST_HOME/main/webapp/raw.xmap and search in file for "jpg" and "jpeg". Add similar handling to read other raw formats, such as TIFF. Please add a patch to our issue tracker: http://forrest.apache.org/issues.html -David
Hi,
We've been successfully using forrest 0.8 for over a year now and we like
the ability to build content from openoffice .odt documents. (
http://newton.codecauldron.org)
We largely have this working, but we still find that it is sensitive to what
type of images are embedded in the .odt file: .png and .jpg images render
fine, but .tiff images do not.
Is this just because the file extension in the OO file is .tif rather than
.tiff, or something else?
$ unzip -l InstallationGuide.odt
Archive: InstallationGuide.odt
Length Date Time Name
-------- ---- ---- ----
39 06-05-09 16:49 mimetype
0 06-05-09 16:49 Configurations2/images/Bitmaps/
127620 06-05-09 16:49 Pictures/1000000000000280000001E02A9E9828.tif
59894 06-05-09 16:49 Pictures/1000000000000280000001E0E2C50ACF.tif
7160 06-05-09 16:49 Pictures/1000000000000196000001142835D184.jpg
Up until now, we have just been replacing embedded .tiff images with .png or
.jpg, but this is a pain.
Can anyone suggest how to fix this properly?
Thanks,
Derek
hi,
I'm using forrest 0.8. in the document-to-fo.xsl, there's following code:
<!-- resources image dir -->
<xsl:when test="starts-with(string(@src),'images/')">
<xsl:value-of
select="concat($imagesdir,substring-after(@src,'images'))"/>
</xsl:when>
<xsl:when test="contains(string(@src),'/images/')">
<xsl:value-of
select="concat($imagesdir,substring-after(@src,'/images'))"/>
</xsl:when>
<!-- already absolute -->
<xsl:when test="contains(string(@src),':') or
starts-with(string(@src),'/')">
<xsl:value-of select="@src"/>
</xsl:when>
<!-- relative to document -->
<xsl:otherwise>
<xsl:value-of select="concat($xmlbasedir,@src)"/>
</xsl:otherwise>
</xsl:choose>
</xsl:variable>
<fo:external-graphic src="{$imgpath}">
<xsl:if test="@height">
<xsl:attribute name="height">
<xsl:value-of select="@height"/>
</xsl:attribute>
</xsl:if>
<xsl:if test="@width">
<xsl:attribute name="width">
<xsl:value-of select="@width"/>
</xsl:attribute>
</xsl:if>
</fo:external-graphic>
the first part causes trouble when the images happen not to be in the
resource folder, but in an "images" folder (e.g. in
/content/xdocs/images), i.e. "fo:external-graphic" gets a wrong src value.
commenting out this part did the trick for me - but I do wonder
1/ what is the rationale behind having images in the resource/ folder?
2/ if I wanted to have all my images in resource/images rather than in
content/xdocs/images, (how) would I still be able to include the images
in the site?
3/ are there any plans to simplify the default forrest folder structure
a bit? right now, it looks quite complex. I recognize that many folders
are necessary to allow for customization, yet I believe those do not
necessarily need to be created by a "forrest seed" from a user point of
view (to name a few: translations, resources, conf and classes do not
seem to give much added value on the first sight)
thanks,
Manuel
On Sat, May 30, 2009 at 08:48:47PM +0200, Bacchella Fabrice wrote: > http://jrds.sourceforge.net/ > > jrds is a cacti like tools written in java. > > I choose dispatcher because of the Google Analytics contract. Thanks. This site has been added to the list and will appear on the Forrest site shortly. Brian
http://jrds.sourceforge.net/ jrds is a cacti like tools written in java. I choose dispatcher because of the Google Analytics contract.
From: Heather Phipps Sent: Thursday, 7 May 2009 3:52 AM To: user@forrest.apache.org Subject: Re: build fails when I attempt "forrest site" after "forrest seed-business" > Sure, please see https://issues.apache.org/jira/browse/FOR-1162. Great, thanks. It would be good if other users/devs could maybe try this out and see what happens for them. It fails for me in both Windows and Linux. 1. create new directory 'for-1162' 2. cd for-1162 3. forrest seedTestBusiness 4. forrest run Do you see the same errors or is all ok? Not being involved in this seed target before can someone confirm/deny that Resume plugin is/isn't involved - I couldn't see any evidence in the target seed that it is, but the output suggests otherwise. The blogsJane.xml and blogsJoe.xml in the /resume/ directory are seemingly ignored and I can not see any .xsl that should be processing those files (other than including the currently broken Resume plugin) Gav...
(Sorry, I meant "to 1 GB," not "by 1 GB) Also, to clarify, when I do "forrest run" the PDFs are in fact generated, but they use the default fonts, so the Japanese once again displays as ########
As stated previously in this thread, the out of memory issue was resolved by increasing the memory to Java by 1 GB. The outstanding issue is that the font is properly embedded when I use "forrest site" to pre-generate content but not when I use "forrest-run" and the PDFs are (apparently) created on-the-fly as they are requested...
On 08.05.2009 03:29:20 David Crossley wrote: > Heather Phipps wrote: > > Actually, with my little hack, the font is properly embedded in the PDF only > > when pre-generated, i.e., when you do "forrest site," but not when the PDFs > > are generated on the fly, i.e., when you do "forrest run." Not sure exactly > > what accounts for the difference. If anyone has a better understanding of > > the cause of this discrepency, please let me know... > > > > Otherwise, I may look into this more at some later point and will update > > this thread if I have any further insight. > > Perhaps the FOP project will be able help with that > and with the memory issue: > http://xmlgraphics.apache.org/fop/ When it is working in one case inside Forrest but not another? I doubt it. That rather sounds like an integration problem (and I'm no Cocoon expert). I don't know what the difference is between the two cases and how the JVM gets the memory settings for them (I assume we're talking about an OutOfMemoryError). What you'll get from FOP support is questions like: does it work from the command-line? Generally, FOP can deal with Japanese characters (left-to-right only). At any rate, loading TrueType font currently takes a lot of memory (i.e. it's programmed rather inefficiently). I'm sure that can be improved but so far nobody cared enough to do the work. Sorry, but I don't have any good suggestions other than (somehow) making sure the JVM has enough memory. Jeremias Maerki
Heather Phipps wrote: > Actually, with my little hack, the font is properly embedded in the PDF only > when pre-generated, i.e., when you do "forrest site," but not when the PDFs > are generated on the fly, i.e., when you do "forrest run." Not sure exactly > what accounts for the difference. If anyone has a better understanding of > the cause of this discrepency, please let me know... > > Otherwise, I may look into this more at some later point and will update > this thread if I have any further insight. Perhaps the FOP project will be able help with that and with the memory issue: http://xmlgraphics.apache.org/fop/ -David
Actually, with my little hack, the font is properly embedded in the PDF only when pre-generated, i.e., when you do "forrest site," but not when the PDFs are generated on the fly, i.e., when you do "forrest run." Not sure exactly what accounts for the difference. If anyone has a better understanding of the cause of this discrepency, please let me know... Otherwise, I may look into this more at some later point and will update this thread if I have any further insight.
FYI, other 1.1 files generate a PDF successfully, so it appears that the problem is something more specific, which I have yet to identify...
Sure, please see https://issues.apache.org/jira/browse/FOR-1162.
Hi Heather, Haven't found a cause or anything yet, but am confirming it also happens for me (in trunk) running forrest seed-business or forrest seedTestBusiness (in forrrest run or site mode). So something's missing. Whether it depends on the Resume plug-in that doesn't work at the moment or something else I don't know, need to investigate further. Can you open an issue? (issues.apache.org/jira/browse/forrest) I noticed on the issue tracker last year someone submitting a minor bug fix (spelling) so I guess it was working for them at that stage. Thanks Gav. _____ From: Heather Phipps [mailto:hmphipps@gmail.com] Sent: Monday, 4 May 2009 3:24 PM To: user@forrest.apache.org Subject: build fails when I attempt "forrest site" after "forrest seed-business" Hi, It appears that the source files necessary to run the command "forrest site" are not generated properly when I do "forrest seed-business." This is what the errors look like: X [0] team/allBySkill.html BROKEN: /Users/Heather/usg/src/documentation/content/xdocs/team/allBySkill.xml (No such file or directory) X [0] team/all.html BROKEN: /Users/Heather/usg/src/documentation/content/xdocs/team/all.xml (No such file or directory) I'm confused why it's looking for files that weren't automatically produced by "forrest seed-business." Anyone else experience this? I have no problem with running "forrest site" in a directory populated with "forrest seed." Obviously I can add the xml files that it is looking for, or modify the site.xml file so that they aren't needed, but I'm curious why it's behaving this way... Other info: Mac OS 10.5.6 Java 1.5.0_16 Forrest 0.8 Thanks, Heather
Hi, It appears that the source files necessary to run the command "forrest site" are not generated properly when I do "forrest seed-business." This is what the errors look like: X [0] team/allBySkill.html BROKEN: /Users/Heather/usg/src/documentation/content/xdocs/team/allBySkill.xml (No such file or directory) X [0] team/all.html BROKEN: /Users/Heather/usg/src/documentation/content/xdocs/team/all.xml (No such file or directory) I'm confused why it's looking for files that weren't automatically produced by "forrest seed-business." Anyone else experience this? I have no problem with running "forrest site" in a directory populated with "forrest seed." Obviously I can add the xml files that it is looking for, or modify the site.xml file so that they aren't needed, but I'm curious why it's behaving this way... Other info: Mac OS 10.5.6 Java 1.5.0_16 Forrest 0.8 Thanks, Heather
Heather Phipps wrote: > My own file is version 1.1, whereas the sample file is version 1.0. Is this > a problem? Does the plugin not handle v 1.1? I do not know anything about those "office" type plugins. The docs show that the "odt" plugin is in the whiteboard so is still in development. http://forrest.apache.org/pluginDocs/ So the dev mail list is more appropriate. You might grab the attention there of its developers. -David
My own file is version 1.1, whereas the sample file is version 1.0. Is this a problem? Does the plugin not handle v 1.1?
I believe that the process I'm using is correct, because when I add the sample file "opendocument-writer.odt" to my site in the same way, both the html and PDF are generated correctly. So, there must be some problematic difference between my .odt file and this .odt file. Perhaps the version of OO that was used to create it differs...or...maybe my file contains some problematic elements? Any ideas? The file appears relatively simple, with no hyperlinks or images.
Hello, I am having trouble generating a PDF from an ODT file using the org.apache.forrest.plugin.input.odt plugin. I added "Abstracts-10.odt" to my source and the following corresponding entry to site.xml: <abstracts label="abstracts" href="Abstracts-10.html"/> The html is generated properly, but I get the following error with regard to the PDF: * [98/2] [1/36] 0.535s 29.9Kb samples/Abstracts-10.html X [0] samples/Abstracts-10.pdf BROKEN: internal-destination or external-destination must be specified in basic-link Am I missing something obvious? Other info: Mac OS 10.5.6 Java 1.5.0_16 Forrest 0.8 Thanks! -Heather
I increased the memory to Java by editing maxmemory property in the site's forrest.properties file: # Max memory to allocate to Java forrest.maxmemory=1024m Japanese displays correctly now in PDF from DocBook source! (Turns out there was no need to update the FOP jar file.)
I have an update and some further questions.
The Japanese font display issue is only occurring with my DocBook XML source
files. These are not handled by document2fo.xsl, but rather by the DocBook
4.4 stylesheets, which I downloaded and included on my own. Here is an
excerpt from my project sitemap showing how I did this:
<map:match pattern="**.pdf">
<map:act type="sourcetype" src="{properties:content.xdocs}{1}.xml">
<map:select type="parameter">
<map:parameter name="parameter-selector-test" value="{sourcetype}"/>
<map:when test="docbook-v4.4">
<map:generate src="{properties:content.xdocs}{../1}.xml"/>
<map:transform
src="{properties:resources.stylesheets}/docbook-xsl-1.74.3-pre
2/fo/docbook.xsl"/>
<map:serialize type="fo2pdf"/>
</map:when>
</map:select>
</map:act>
</map:match>
I didn't feel like messing around in the the DocBook stylesheets just yet,
so I hacked the font config file to see if I could get other (non-Japanese)
fonts to display properly in my PDFs generated from DocBook. Here is the
hacked font config file:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<fonts>
<font
metrics-file="/Users/Heather/apache-forrest-0.8/main/webapp/resources/fonts/Brush_Script.xml"
embed-file="/Users/Heather/apache-forrest-0.8/main/webapp/resources/fonts/Brush_Script.ttf"
kerning="yes">
<font-triplet name="serif" style="normal" weight="normal"/>
<font-triplet name="serif" style="normal" weight="bold"/>
<font-triplet name="serif" style="italic" weight="normal"/>
<font-triplet name="serif" style="italic" weight="bold"/>
<font-triplet name="sans-serif" style="normal" weight="normal"/>
<font-triplet name="sans-serif" style="normal" weight="bold"/>
<font-triplet name="sans-serif" style="italic" weight="normal"/>
<font-triplet name="sans-serif" style="italic" weight="bold"/>
<font-triplet name="sans" style="normal" weight="normal"/>
<font-triplet name="sans" style="normal" weight="bold"/>
<font-triplet name="sans" style="italic" weight="normal"/>
<font-triplet name="sans" style="italic" weight="bold"/>
<font-triplet name="monospace" style="normal" weight="normal"/>
<font-triplet name="monospace" style="normal" weight="bold"/>
<font-triplet name="monospace" style="italic" weight="normal"/>
<font-triplet name="monospace" style="italic" weight="bold"/>
</font>
</fonts>
</configuration>
This works...it causes the PDFs created from both sample XML files included
in the demo site and my DocBook XML files to use the "Brush Script" font.
However, when I attempt the same thing with a Japanese font, it works
properly for the sample XML files (even when I add some Japanese text) but
not for my DocBook XML files...I get the following out of memory error:
* [54/14] [0/0] 9.776s 0b samples/dotnet.pdf
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:95)
at org.apache.fop.tools.IOUtil.copyStream(IOUtil.java:77)
at org.apache.fop.tools.IOUtil.toByteArray(IOUtil.java:95)
at org.apache.fop.fonts.FontFileReader.init(FontFileReader.java:76)
at org.apache.fop.fonts.FontFileReader.<init>(FontFileReader.java:105)
at
org.apache.fop.render.pdf.fonts.MultiByteFont.getFontFile(MultiByteFont.java:237)
at
org.apache.fop.render.pdf.fonts.LazyFont.getFontFile(LazyFont.java:218)
at
org.apache.fop.pdf.PDFDocument.makeFontDescriptor(PDFDocument.java:974)
at org.apache.fop.pdf.PDFDocument.makeFont(PDFDocument.java:875)
at
org.apache.fop.render.pdf.FontSetup.addToResources(FontSetup.java:250)
at
org.apache.fop.render.pdf.PDFRenderer.stopRenderer(PDFRenderer.java:249)
at
org.apache.fop.apps.StreamRenderer.stopRenderer(StreamRenderer.java:204)
at org.apache.fop.fo.FOTreeBuilder.endDocument(FOTreeBuilder.java:246)
at
org.apache.cocoon.xml.AbstractXMLPipe.endDocument(AbstractXMLPipe.java:55)
at
org.apache.cocoon.xml.AbstractXMLPipe.endDocument(AbstractXMLPipe.java:55)
at sun.reflect.GeneratedMethodAccessor37.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.cocoon.core.container.handler.PoolableComponentHandler$ProxyHandler.invoke(PoolableComponentHandler.java:147)
at $Proxy6.endDocument(Unknown Source)
at
org.apache.cocoon.components.sax.XMLTeePipe.endDocument(XMLTeePipe.java:67)
at
org.apache.xml.serializer.ToXMLSAXHandler.endDocument(ToXMLSAXHandler.java:181)
at
org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1378)
at
org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:3458)
at
org.apache.xalan.transformer.TransformerHandlerImpl.endDocument(TransformerHandlerImpl.java:406)
at
org.apache.cocoon.xml.AbstractXMLPipe.endDocument(AbstractXMLPipe.java:55)
at
org.apache.cocoon.transformation.TraxTransformer.endDocument(TraxTransformer.java:585)
at org.apache.xerces.parsers.AbstractSAXParser.endDocument(Unknown
Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.endDocument(Unknown
Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl.endEntity(Unknown
Source)
at org.apache.xerces.impl.XMLEntityManager.endEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source)
Anyone seen this before? Thoughts/suggestions? I'm first going to try to
change the heap memory applied to Forrest, hoping that this will change the
heap memory applied to FOP...and also maybe try updating the FOP jar that is
included with Forrest.
2009/4/23 Heather Phipps <hmphipps@gmail.com>: > Hello, > What is the difference between these two plugins? How do I choose > which one to use for an ODT input file? *.odt has it in the name so it's a safe bet. The plugin description says "Use OpenDocument Writer files (*.odt) as input sources. " so it's a safe bet. Ross -- Ross Gardler OSS Watch - supporting open source in education and research http://www.oss-watch.ac.uk
2009/4/24 Heather Phipps <hmphipps@gmail.com>: > Hello, > > The documentation > (http://forrest.apache.org/pluginDocs/plugins_0_80/usingPlugins.html) > states: "Clashes between plugins can occur. For example, the > simplified-docbook and full docbook plugins may try and process the > same files." However, I do not see a full docbook plugin in the list > of available plugins, and the FAQ states that in order to fully > utilize DocBook files as input you need to use the full DocBook > stylesheets directly, rather than a plugin. This seems conflicting. > Is there a full Docbook plugin? There is no full docbook plugin - there would be a conflict *if* there were one. I agree it's not very clear in the text quoted. Ross -- Ross Gardler OSS Watch - supporting open source in education and research http://www.oss-watch.ac.uk
Hi David,
Thank you for pointing that out. I am new to using the plugins and
didn't realize this. So, I attempted to follow your advice:
heather-phipps-computer:org.apache.forrest.plugin.output.pdf Heather$
/Users/Heather/apache-forrest-0.8/tools/ant/bin/ant local-deploy
Buildfile: build.xml
init-build-compiler:
echo-init:
[echo]
[echo] --------------------------------------------------------------
[echo]
[echo] Using Apache Ant version 1.6.5 compiled on May 16 2006
[echo] Build file
/Users/Heather/apache-forrest-0.8/plugins/org.apache.forrest.plugin.output.pdf/build.xml
[echo] Use 'build.[sh|bat] -projecthelp' to see other options.
[echo] Build system home /Users/Heather/apache-forrest-0.8/tools/ant
[echo] Build number 0
[echo] Project Name Forrest plugin build file
[echo] Java Version 1.5
[echo] Timestamp 200904241808
[echo]
[echo] --------------------------------------------------------------
[echo]
init:
compile:
jar:
local-deploy:
[echo] Locally deploying org.apache.forrest.plugin.output.pdf
build:
BUILD SUCCESSFUL
Total time: 0 seconds
But then I did "forrest" again, and the PDF is still generated with
##### instead of Japanese text, so I guess I am still missing
something else...
-Heather
Hello, The documentation (http://forrest.apache.org/pluginDocs/plugins_0_80/usingPlugins.html) states: "Clashes between plugins can occur. For example, the simplified-docbook and full docbook plugins may try and process the same files." However, I do not see a full docbook plugin in the list of available plugins, and the FAQ states that in order to fully utilize DocBook files as input you need to use the full DocBook stylesheets directly, rather than a plugin. This seems conflicting. Is there a full Docbook plugin? -Heather
Heather Phipps wrote: > > Unfortunately, even after editing > $FORREST/apache-forrest-0.8/plugins/org.apache.forrest.plugin.output.pdf/output.xmap, > I am unable to get the font to display correctly in the PDF file. Whenever a local plugin's resources (e.g. sitemaps or stylesheets, etc.) are edited then you need to "local-deploy" the plugin. See: http://forrest.apache.org/pluginDocs/plugins_0_80/usingPlugins.html#local-deploy http://forrest.apache.org/docs_0_80/howto/howto-buildPlugin.html#ant http://forrest.apache.org/docs_0_80/howto/howto-buildPlugin.html#Testing+During+Development -David
Hi Heather,
Thanks.
Yes the output.xmap needs to be used because the Forrest 0.8 now uses
plugins for fo2pdf generation.
The step 5 which you mentioned is correct as the skins are not ready for
Japanese, so MS gothic needs to inserted.
I will look into your files, and what I had done, to see if I can help
you further. Will get back to you later on that.
best wishes
Praveen
----- Original Message -----
From: "Heather Phipps" <hmphipps@gmail.com>
To: <user@forrest.apache.org>; "Dr. Bhatia Praveen"
<praveen.bhatia@sumpurn.com>
Sent: Thursday, April 23, 2009 3:19 PM
Subject: Re: Japanese PDF rendering
> Hi Praveen,
>
> I very much appreciate your prompt response, as I have been struggling
> with this issue for quite some time now.
>
> Unfortunately, even after editing
> $FORREST/apache-forrest-0.8/plugins/org.apache.forrest.plugin.output.pdf/output.xmap,
> I am unable to get the font to display correctly in the PDF file.
>
> I have a few questions. First...how did you know that Forrest is
> using output.xmap instead of sitemap.xmap for this step? Second, do
> you know if step number 5 in the instructions from
> http://www.terra-intl.com/agel/2005/11/forrest_japanese.html is
> correct for Forrest 0.8?
>
> Here is an excerpt from my output.xmap file:
>
> ...
> <map:serializers default="fo2pdf">
> <map:serializer name="fo2pdf"
> src="org.apache.cocoon.serialization.FOPSerializer"
> mime-type="application/pdf">
> <user-config
> src="/Users/Heather/apache-forrest-0.8/main/webapp/resources/fonts/config.xml"
> />
> </map:serializer>
> ...
>
> (Currently, this is in both my sitemap.xmap file and output.xmap)
>
> I downloaded the .ttf and corresponding font-metric xml files from
> http://www.terra-intl.com/agel/2005/11/forrest_japanese.html and
> placed them in
> /Users/Heather/apache-forrest-0.8/main/webapp/resources/fonts/,
> alongside config.xml, which contains the following:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <configuration>
> <fonts>
> <font
> metrics-file="/Users/Heather/apache-forrest-0.8/main/webapp/resources/fonts/sazanami-gothic.xml"
> embed-file="/Users/Heather/apache-forrest-0.8/main/webapp/resources/fonts/sazanami-gothic.ttf"
> kerning="yes">
> <font-triplet name="Gothic" style="normal" weight="normal"/>
> <font-triplet name="Gothic" style="normal" weight="bold"/>
> <font-triplet name="Gothic" style="italic" weight="normal"/>
> <font-triplet name="Gothic" style="italic" weight="bold"/>
> </font>
> <font
> metrics-file="/Users/Heather/apache-forrest-0.8/main/webapp/resources/fonts/sazanami-mincho.xml"
> embed-file="/Users/Heather/apache-forrest-0.8/main/webapp/resources/fonts/sazanami-mincho.ttf"
> kerning="yes">
> <font-triplet name="Mincho" style="normal" weight="normal"/>
> <font-triplet name="Mincho" style="normal" weight="bold"/>
> <font-triplet name="Mincho" style="italic" weight="normal"/>
> <font-triplet name="Mincho" style="italic" weight="bold"/>
> </font>
> </fonts>
> </configuration>
>
> I also tried using different .ttf files and generating the font-metric
> files myself, and it appeared that the font-metric files were
> generated properly, but the PDF still did not display the Japanese
> text correctly.
>
> Any further thoughts?
>
> -Heather
>
--------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.238 / Virus Database: 270.12.3/2075 - Release Date: 04/22/09
17:25:00
Hello, What is the difference between these two plugins? How do I choose which one to use for an ODT input file? Thank you, Heather