Re: Is there a decent way of using different PDF fonts for different parts of a Forrest site?

2012-02-01 Thread Tim Williams
For the archives, it looks like this is the commit [
http://svn.apache.org/viewvc?view=revision&revision=1239111 ].  If
this is a common need, perhaps a candidate to just get rolled into
Forrest itself, I dunno.

FWIW, I'm pretty sure the output.xmap is unnecessary and you could
have used a project-specific locationmap to point to your custom
document-to-fo.xsl but maybe I'm missing something...

--tim

On Wed, Feb 1, 2012 at 8:02 AM, Karl Wright  wrote:
> FWIW, the $path has just what I hoped in it and works well.
>
> Thanks!
> Karl
>
> On Tue, Jan 31, 2012 at 9:23 PM, Karl Wright  wrote:
>>> Then, inside your own document-to-fo.xsl you should have access
>>> to a "path" parameter.  You may add an additional condition to the
>>> font of interest (e.g. rootFontFamily) that uses XSL string functions
>>> against your $path parameter.
>>>
>>
>> I've set things up so that my document path includes the language code
>> (e.g. 'en_US') as the first part of the path under
>> src/documentation/content/xdocs.  For example,
>> src/documentation/content/xdocs/en_US/mydocument.xml would be the
>> starting point.  The question is what the $path variable will contain
>> - if it's just "en_US/mydocument.xml" my job is easy.  If it could be
>> "en_US\mydocument.xml" on Windows and "en_US/mydocument.xml" on Unix
>> it's a bit harder.   But if it is the absolute path xsl expressions
>> aren't going to help me and I'd better find a better solution.
>>
>> What I'd do (and this might even make a decent general patch) is look
>> for the property with the language specifier first.  For example,
>> instead of looking for "output.pdf.fontFamily.sansSerif" first, I'd
>> look for "output.pdf.fontFamily.sansSerif.en_US" first, and only look
>> for the other if that property is not found.
>>
>> So, what can I expect to see for the $path parameter?
>>
>> Thanks again for your help!
>> Karl


Re: Is there a decent way of using different PDF fonts for different parts of a Forrest site?

2012-02-01 Thread Tim Williams
On Wed, Feb 1, 2012 at 8:02 AM, Karl Wright  wrote:
> FWIW, the $path has just what I hoped in it and works well.

My apologies Karl, I got busy last night and didn't have a chance to
get back to this:(  I haven't confirmed but path should be the request
path (of the URL) - so the same on both systems.

--tim

> Thanks!
> Karl
>
> On Tue, Jan 31, 2012 at 9:23 PM, Karl Wright  wrote:
>>> Then, inside your own document-to-fo.xsl you should have access
>>> to a "path" parameter.  You may add an additional condition to the
>>> font of interest (e.g. rootFontFamily) that uses XSL string functions
>>> against your $path parameter.
>>>
>>
>> I've set things up so that my document path includes the language code
>> (e.g. 'en_US') as the first part of the path under
>> src/documentation/content/xdocs.  For example,
>> src/documentation/content/xdocs/en_US/mydocument.xml would be the
>> starting point.  The question is what the $path variable will contain
>> - if it's just "en_US/mydocument.xml" my job is easy.  If it could be
>> "en_US\mydocument.xml" on Windows and "en_US/mydocument.xml" on Unix
>> it's a bit harder.   But if it is the absolute path xsl expressions
>> aren't going to help me and I'd better find a better solution.
>>
>> What I'd do (and this might even make a decent general patch) is look
>> for the property with the language specifier first.  For example,
>> instead of looking for "output.pdf.fontFamily.sansSerif" first, I'd
>> look for "output.pdf.fontFamily.sansSerif.en_US" first, and only look
>> for the other if that property is not found.
>>
>> So, what can I expect to see for the $path parameter?
>>
>> Thanks again for your help!
>> Karl


Re: Is there a decent way of using different PDF fonts for different parts of a Forrest site?

2012-01-31 Thread Tim Williams
On Tue, Jan 31, 2012 at 3:16 AM, Karl Wright  wrote:
> Hi Hitoshi,
>
> plugins/org.apache.forrest.plugin.output.pdf/resources/stylesheets/document-to-fo.xsl
> does seem like the right place to conditionalize things, but I'm
> unclear in your example where the language specifier comes from?  In
> other words, I'd like the path to the current file to determine the
> language, not the system settings.  Do you (or does anyone else) know
> how to construct a conditional within the document-to-fo.xsl file that
> would (say) base a decision for a font choice on whether a file had a
> name that matched a particular regular expression?  That's the kind of
> logic I'm looking for here.

Hi Karl,
Know?  Unfortunately not - this is a guess.  Create a copy of
document-to-fo.xsl - using the project-specific locationmap to find
it.  Then, inside your own document-to-fo.xsl you should have access
to a "path" parameter.  You may add an additional condition to the
font of interest (e.g. rootFontFamily) that uses XSL string functions
against your $path parameter. Unfortunately, I can't verify any of
this until tonight.

Thanks,
--tim


Re: Adding site documentation to project

2011-09-23 Thread Tim Williams
On Fri, Sep 23, 2011 at 4:05 PM, lewis john mcgibbney
 wrote:
> Hi again,
>
> I'm back working on this and could do with some pointers. Please see below
> for some of the keys areas.
>
> I've looked closely at your references and read both the forrestbot "svn"
> workstage and forrestbot automated build and deploying documentation. I
> understand completely how I want this to work and your suggestion for the
> process of editing sourc, updating the Nutch site, then an additional
> forrestbot task would update the new /docs directory within our SVN
> nutch/branches/branch-1.4/docs diretcory. This would then enable devs to
> simply svn update and any documentation changes would be updated. It would
> also provide an excellent way of shipping the generated docs with our next
> release. The parts I am struggling to understand are below:
>
>
> On Mon, Sep 19, 2011 at 3:27 AM, David Crossley  wrote:
>>
>> lewis john mcgibbney wrote:
>> > Hi all,
>> >
>> > As a project, we are wanting to ship core documentation with the
>> > software
>> > distribution. Currently the Nutch site documentation can be found here
>> > [1],
>> > however we would like to start shipping it with our branch-1.4 [2] under
>> > a
>> > new /docs directory.
>> >
>> > I know this is rather trivial and that there must be documentation on it
>> > somewhere but I have not been able to get my hands on it from the
>> > Forrest
>> > site yet!
>> >
>> > Thanks for any pointers.
>> >
>> > [1] https://svn.apache.org/repos/asf/nutch/site/
>> > [2] https://svn.apache.org/repos/asf/nutch/branches/branch-1.4/
>>
>> I gather that you mean the "generated" relevant docs for that version.
>>
>> You could use the "Forrestbot" as we do for our Forrest project docs.
>>
>> http://forrest.apache.org/howto-forrestbot-svn.html
>> How to deploy documentation with the Forrestbot "svn" workstage
>>
>> In our case we deploy our generated documentation to SVN forrest/site
>> which gets 'svn up' on people.apache.org to publish our website.
>
> I 'think' this is already done. I am waiting for a reply from the more
> experienced dev's to give me insight into how committed changes to the site
> source are actually fed through to nutch.apache.org. As I know of no other
> method for doing this other than the one your specified, I am going on the
> assumption that this is already in place.
>
>>
>> The Nutch project could do that too for your website docs.
>
> Excellent, this is now my intention :0)
>
>>
>> Then have another "Forrestbot buildfile" which deploys the relevant
>> docs to SVN nutch/branches/branch-1.4
>
> How does this task get executed? If my comments as above are correct, this
> appears to be the main task at hand, therefore I am trying to find out where
> the additional buildfile is located and if this process can be triggered
> should there be any update to the site documentation e.g. a commit from the
> dev's.

There's another build file, typically "publish.xml"[see our example 1]
that contains the details of where to publish it.  You might find it
easier to start with a condensed version of our own publishing
instructions[2] or slightly more verbose[3] and expand your reading as
necessary from there...  There's no "trigger" to update them, but
they're periodically pulled - it looks like your latest footer change,
for example, was already pulled - sorry, I don't know the detailed
mechanics of that arrangement.

You've done plenty of research, ask away:)
--tim

[1] - http://svn.apache.org/repos/asf/forrest/trunk/site-author/publish.xml
[2] - http://svn.apache.org/repos/asf/forrest/trunk/etc/publishing_our_site.txt
[3] - http://forrest.apache.org/procedures/How_to_publish_docs.html


Re: 2.1 in FAQ typo

2011-06-29 Thread Tim Williams
Thanks Tomo, fixed at revision 1140926.  It'll be live next time the
site is published.  Next time, would you mind adding an issue in JIRA
for us so that it doesn't get lost?

https://issues.apache.org/jira/browse/FOR

Thanks,
--tim

2011/6/23  :
> Hi,
>
> I found a typo.
>
> 2.1 in FAQ
> http://forrest.apache.org/docs_0_100/faq.html#edit-content
>
> ... ensure that the document stucture is consistent. ...
>                         
>
>                      -> structure
>
> Regards,
> --
> Tomo
>


Re: timed out only for several files

2010-12-21 Thread Tim Williams
On Tue, Dec 21, 2010 at 8:26 AM, Szabo, Patrick (LNG-VIE)
 wrote:
> Can you tell me where that file is located ?!

http://forrest.apache.org/howto-dev.html#debug-logfiles

http://forrest.apache.org/docs_0_90/faq.html#logs



> . . . . . . . . . . . . . . . . . . . . . . . . . .
> Patrick Szabo
>  XSLT-Entwickler
> LexisNexis
> Marxergasse 25, 1030 Wien
>
> mailto:patrick.sz...@lexisnexis.at
> Tel.: +43 (1) 534 52 - 1573
> Fax: +43 (1) 534 52 - 146
>
>
> -Ursprüngliche Nachricht-
>
> Von: Tim Williams [mailto:william...@gmail.com]
> Gesendet: Dienstag, 21. Dezember 2010 14:23
> An: user@forrest.apache.org
> Betreff: Re: timed out only for several files
>
> I was thinking the actual log file itself, not stdout.
>
> --tim
>
> On Tue, Dec 21, 2010 at 8:14 AM, Szabo, Patrick (LNG-VIE)
>  wrote:
>> I started forrest with forrest run -l log.txt and i do get the txt-file but 
>> if i browse to a page nothing is written into the file.
>>
>> Still there is an error in the log file:
>>
>> 14:08:10.857 EVENT  Checking Resource aliases
>> 14:08:10.982 EVENT  Starting Jetty/4.2.19
>> 14:08:11.045 EVENT  Started WebApplicationContext[/,Apache Forrest]
>> 14:08:11.076 WARN!! Delete existing temp dir C:\WINDOWS\TEMP\Jetty____ 
>> for WebApplicationContext[/,Apache Forrest]
>> Lazy mode: false
>> 14:08:11.638 WARN!! Failed to start: socketliste...@0.0.0.0:
>> 14:08:11.638 WARN!!
>> org.mortbay.util.MultiException[java.net.BindExceLazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> Lazy mode: false
>> va:359)
>>        at java.net.ServerSocket.bind(ServerSocket.java:319)
>>        at java.net.ServerSocket.(ServerSocket.java:185)
>>        at 
>> org.mortbay.util.ThreadedServer.newServerSocket(ThreadedServer.java:317)
>>        at org.mortbay.util.ThreadedServer.open(ThreadedServer.java:390)
>>        at org.mortbay.util.ThreadedServer.start(ThreadedServer.java:419)
>>        at org.mortbay.http.SocketListener.start(SocketListener.java:154)
>>        at org.mortbay.http.HttpServer.start(HttpServer.java:671)
>>        at org.mortbay.jetty.Server.main(Server.java:429)
>>
>> Kind regards
>>
>>
>> . . . . . . . . . . . . . . . . . . . . . . . . . .
>> Patrick Szabo
>>  XSLT-Entwickler
>> LexisNexis
>> Marxergasse 25, 1030 Wien
>>
>> mailto:patrick.sz...@lexisnexis.at
>> Tel.: +43 (1) 534 52 - 1573
>> Fax: +43 (1) 534 52 - 146
>>
>>
>> -Ursprüngliche Nachricht-
>>
>> Von: Tim Williams [mailto:william...@gmail.com]
>> Gesendet: Dienstag, 21. Dezember 2010 14:02
>> An: user@forrest.apache.org
>> Betreff: Re: timed out only for several files
>>
>> Not much to go on here, can you post relevant sections of your log
>> file after you make a request? If you've not already, put log-level to
>> debug.
>>
>> --tim
>>
>>
>> On Tue, Dec 21, 2010 at 7:51 AM, Szabo, Patrick (LNG-VIE)
>>  wrote:
>>> Hi,
>>>
>>> It seems to have something todo with the doctype.
>>> We are using 2 of them : topic and task.
>>>
>>> All of the topic-files work, the task-files don't.
>>>
>>> Does that telly ou anything ?!
>>>
>>> Kind regards
>>>
>>>
>>> . . . . . . . . . . . . . . . . . . . . . . . . . .
>>> Patrick Szabo
>>>  XSLT-Entwickler
>>> LexisNexis
>>> Marxergasse 25, 1030 Wien
>>>
>>> mailto:patrick.sz...@lexisnexis.at
>>> Tel.: +43 (1) 534 52 - 1573
>>> Fax: +43 (1) 534 52 - 146
>>>
>>>
>>> -Ursprüngliche Nachricht-
>>>
>>> Von: Szabo, Patrick (LNG-VIE) [mailto:patrick.sz...@lexisnexis.at]
>>> Gesendet: Montag, 20. Dezember 2010 15:30
>>> An: user@forrest.apache.org
>>> Betreff: timed out only for several files
>>>
>>> hi,
>>>
>>> I'm running an 0.7 forrest server and i have a problem with a couple of
>>> files.
>>> For the most part everything is working fine but i can't acces all
>>> files.
>>> A hand full of files deliver that error:
>>>
>>> Message: null
>>>
>>> Description: No details available.
>>>
>>> Sender: org.apache.cocoon.servlet.CocoonServlet
>>>
>>> Source: Cocoon Servlet
>>>
>>> cause
>>>
>>> Connection timed out: connect
>>>
>>> Request URI
>>>
>>> cpf/newsletter/pvp.html
>>>
>>> request-uri
>>>
>>> /cpf/newsletter/pvp.html
>>>
>>> The files exist, and are accessbile through the filesystem.
>>>
>>> Any ideas ?!
>>>
>>> Thanks in advance...
>>>
>>> Kind regards
>>>
>>> . . . . . . . . . . . . . . . . . . . . . . . . . .
>>> Patrick Szabo
>>>  XSLT-Entwickler
>>> LexisNexis
>>> Marxergasse 25, 1030 Wien
>>>
>>> mailto:patrick.sz...@lexisnexis.at
>>> Tel.: +43 (1) 534 52 - 1573
>>> Fax: +43 (1) 534 52 - 146
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>


Re: timed out only for several files

2010-12-21 Thread Tim Williams
I was thinking the actual log file itself, not stdout.

--tim

On Tue, Dec 21, 2010 at 8:14 AM, Szabo, Patrick (LNG-VIE)
 wrote:
> I started forrest with forrest run -l log.txt and i do get the txt-file but 
> if i browse to a page nothing is written into the file.
>
> Still there is an error in the log file:
>
> 14:08:10.857 EVENT  Checking Resource aliases
> 14:08:10.982 EVENT  Starting Jetty/4.2.19
> 14:08:11.045 EVENT  Started WebApplicationContext[/,Apache Forrest]
> 14:08:11.076 WARN!! Delete existing temp dir C:\WINDOWS\TEMP\Jetty____ 
> for WebApplicationContext[/,Apache Forrest]
> Lazy mode: false
> 14:08:11.638 WARN!! Failed to start: socketliste...@0.0.0.0:
> 14:08:11.638 WARN!!
> org.mortbay.util.MultiException[java.net.BindExceLazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> Lazy mode: false
> va:359)
>        at java.net.ServerSocket.bind(ServerSocket.java:319)
>        at java.net.ServerSocket.(ServerSocket.java:185)
>        at 
> org.mortbay.util.ThreadedServer.newServerSocket(ThreadedServer.java:317)
>        at org.mortbay.util.ThreadedServer.open(ThreadedServer.java:390)
>        at org.mortbay.util.ThreadedServer.start(ThreadedServer.java:419)
>        at org.mortbay.http.SocketListener.start(SocketListener.java:154)
>        at org.mortbay.http.HttpServer.start(HttpServer.java:671)
>        at org.mortbay.jetty.Server.main(Server.java:429)
>
> Kind regards
>
>
> . . . . . . . . . . . . . . . . . . . . . . . . . .
> Patrick Szabo
>  XSLT-Entwickler
> LexisNexis
> Marxergasse 25, 1030 Wien
>
> mailto:patrick.sz...@lexisnexis.at
> Tel.: +43 (1) 534 52 - 1573
> Fax: +43 (1) 534 52 - 146
>
>
> -Ursprüngliche Nachricht-
>
> Von: Tim Williams [mailto:william...@gmail.com]
> Gesendet: Dienstag, 21. Dezember 2010 14:02
> An: user@forrest.apache.org
> Betreff: Re: timed out only for several files
>
> Not much to go on here, can you post relevant sections of your log
> file after you make a request? If you've not already, put log-level to
> debug.
>
> --tim
>
>
> On Tue, Dec 21, 2010 at 7:51 AM, Szabo, Patrick (LNG-VIE)
>  wrote:
>> Hi,
>>
>> It seems to have something todo with the doctype.
>> We are using 2 of them : topic and task.
>>
>> All of the topic-files work, the task-files don't.
>>
>> Does that telly ou anything ?!
>>
>> Kind regards
>>
>>
>> . . . . . . . . . . . . . . . . . . . . . . . . . .
>> Patrick Szabo
>>  XSLT-Entwickler
>> LexisNexis
>> Marxergasse 25, 1030 Wien
>>
>> mailto:patrick.sz...@lexisnexis.at
>> Tel.: +43 (1) 534 52 - 1573
>> Fax: +43 (1) 534 52 - 146
>>
>>
>> -Ursprüngliche Nachricht-
>>
>> Von: Szabo, Patrick (LNG-VIE) [mailto:patrick.sz...@lexisnexis.at]
>> Gesendet: Montag, 20. Dezember 2010 15:30
>> An: user@forrest.apache.org
>> Betreff: timed out only for several files
>>
>> hi,
>>
>> I'm running an 0.7 forrest server and i have a problem with a couple of
>> files.
>> For the most part everything is working fine but i can't acces all
>> files.
>> A hand full of files deliver that error:
>>
>> Message: null
>>
>> Description: No details available.
>>
>> Sender: org.apache.cocoon.servlet.CocoonServlet
>>
>> Source: Cocoon Servlet
>>
>> cause
>>
>> Connection timed out: connect
>>
>> Request URI
>>
>> cpf/newsletter/pvp.html
>>
>> request-uri
>>
>> /cpf/newsletter/pvp.html
>>
>> The files exist, and are accessbile through the filesystem.
>>
>> Any ideas ?!
>>
>> Thanks in advance...
>>
>> Kind regards
>>
>> . . . . . . . . . . . . . . . . . . . . . . . . . .
>> Patrick Szabo
>>  XSLT-Entwickler
>> LexisNexis
>> Marxergasse 25, 1030 Wien
>>
>> mailto:patrick.sz...@lexisnexis.at
>> Tel.: +43 (1) 534 52 - 1573
>> Fax: +43 (1) 534 52 - 146
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>


Re: timed out only for several files

2010-12-21 Thread Tim Williams
Not much to go on here, can you post relevant sections of your log
file after you make a request? If you've not already, put log-level to
debug.

--tim


On Tue, Dec 21, 2010 at 7:51 AM, Szabo, Patrick (LNG-VIE)
 wrote:
> Hi,
>
> It seems to have something todo with the doctype.
> We are using 2 of them : topic and task.
>
> All of the topic-files work, the task-files don't.
>
> Does that telly ou anything ?!
>
> Kind regards
>
>
> . . . . . . . . . . . . . . . . . . . . . . . . . .
> Patrick Szabo
>  XSLT-Entwickler
> LexisNexis
> Marxergasse 25, 1030 Wien
>
> mailto:patrick.sz...@lexisnexis.at
> Tel.: +43 (1) 534 52 - 1573
> Fax: +43 (1) 534 52 - 146
>
>
> -Ursprüngliche Nachricht-
>
> Von: Szabo, Patrick (LNG-VIE) [mailto:patrick.sz...@lexisnexis.at]
> Gesendet: Montag, 20. Dezember 2010 15:30
> An: user@forrest.apache.org
> Betreff: timed out only for several files
>
> hi,
>
> I'm running an 0.7 forrest server and i have a problem with a couple of
> files.
> For the most part everything is working fine but i can't acces all
> files.
> A hand full of files deliver that error:
>
> Message: null
>
> Description: No details available.
>
> Sender: org.apache.cocoon.servlet.CocoonServlet
>
> Source: Cocoon Servlet
>
> cause
>
> Connection timed out: connect
>
> Request URI
>
> cpf/newsletter/pvp.html
>
> request-uri
>
> /cpf/newsletter/pvp.html
>
> The files exist, and are accessbile through the filesystem.
>
> Any ideas ?!
>
> Thanks in advance...
>
> Kind regards
>
> . . . . . . . . . . . . . . . . . . . . . . . . . .
> Patrick Szabo
>  XSLT-Entwickler
> LexisNexis
> Marxergasse 25, 1030 Wien
>
> mailto:patrick.sz...@lexisnexis.at
> Tel.: +43 (1) 534 52 - 1573
> Fax: +43 (1) 534 52 - 146
>
>
>
>
>
>
>
>


Re: moving to different hardware

2010-12-15 Thread Tim Williams
On Wed, Dec 15, 2010 at 1:54 AM, Szabo, Patrick (LNG-VIE)
 wrote:
> Thank you for all of your answers !
>
> The move is sheduled for Thursday so i might be able to tell you if it workes 
> then.
> Anothers thing i was wondering in which directory do i have to be to run
> 'forrest commands' or is that an "systemwide" command once i set the 
> variables ?!

After you set up your environment[1], the forrest command will be on
your "path" - allowing you to run it from anywhere.  Generally, you'd
run it from a project directory or a directory where you want a
project created.

--tim

[1] - 
http://forrest.apache.org/docs_0_90/your-project.html#Setting+up+the+Environment


Re: moving to different hardware

2010-12-14 Thread Tim Williams
On Mon, Dec 13, 2010 at 9:46 AM, Szabo, Patrick (LNG-VIE)
 wrote:
> Hi,
>
> I have to move our forrest installation to a different hardware. Since i
> didn't install and configure it myself i'm wondering how to do that.
>
> Is it possible to just copy the directories, set the Enviroment Variables?!
>
> Would that work ?! If not...why not ?!

Hi Patrick,
Assuming you have Java installed on the new machine, simply copying
everything (Forrest + Your Project) should work just fine. Good luck!

--tim


Re: Lucene Search

2010-11-08 Thread Tim Williams
On Mon, Nov 8, 2010 at 7:25 AM, Szabo, Patrick (LNG-VIE)
 wrote:
> Hi,
>
> I'm new to Forrest and my boss in all it's wisdom decided that i have to
> administrate our forrest installation now.
> I wasn't involved in our installation until now.
>
> I've already read the forrest documentation and it did help me, but
> there are quite a few question that i couldn't answer.

Yeah, in trying to answer your question I realize that the
documentation in this area is weak.  After you understand this stuff,
it'd be great if you could contribute to them.

> I understand that i can use fields to search with lucene. Is there a
> list somewhere where i can see which fields are available ?!

For any given document, you can add a .lucene extension and the
element names are the searchable field names.  These are mostly title,
subtitle, abstract, version, author, and content.

> Can i somehow add fields ?!

I don't think there's a way to add per-project fields, but for you
Forrest implementation, you can try to add it into
$FORREST_HOME/main/webapp/resources/stylesheets/xdoc-to-lucene.xsl

> We have an element  in our source xml
> and i would like to be able to serch for the date. E.g. i want to see
> all the documents that where modified last week.

Hmm... I'm not sure, I reckon you'd have to index it based on its xdoc
equivalent.

> I've got a few more questions but i don't want to pack them all in just
> one mail.

Yeah, one per thread is always preferred - mail threads are cheap though:)

I'm not sure what version of Forrest you are on but I had to do some
hacking just to get the indexing to work - I reckon it's been a
long-standing bug.  I'll take that up on the dev@ list though.  Good
luck!

--tim


Re: Feeder. Use Example

2010-10-07 Thread Tim Williams
On Wed, Oct 6, 2010 at 11:38 PM, Bryce Alcock  wrote:
>
> I was looking at the Forrest Feeder Pluggin (which is at 0.2 -Unreleased?).
>
> The feature sounds very cool...  (I cannot say that it looks very cool
> because the demo did not work)
> Demo Link:
> http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.feeder/samples/singleFeed.html
>
> CURRENT How to use docs (not clear enough for me.):
> http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.feeder/changes.html
>
> I would like to know if there is a better example of:
> 1.  HOW TO USE.

Maybe look at the source for the demo.  It seems as simple as dropping
a "feedDescriptor" file in with your sources.  Have you tried that?

http://svn.apache.org/repos/asf/forrest/trunk/plugins/org.apache.forrest.plugin.input.feeder/src/documentation/content/xdocs/samples/

> 2.  WHAT IT LOOKS LIKE in forrest.

Did you follow the links under "Usable Features"?  That seems to be a
working example to me:
http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.feeder/index.html#Usable+Features

Thanks,
--tim


Re: relative links in site.xml

2010-07-07 Thread Tim Williams
On Tue, Jul 6, 2010 at 2:53 AM, Wipf Markus  wrote:
> Hi,
>
> There are external links because we have several sites on the same webserver. 
> So each
>site is completely independent during generation time but not during runtime. 
>That's why I
> try to use relative links to be able to deploy the pages on another location 
> (for another
> customer for example).

I wonder if you might have an XY problem[1] here?  Why don't you
include the links as normal and use cli-conf[2] to ignore them?

> But as I mentioned below Forrest treats link generation for html
> and pdf not in the same manner. That's my problem.

It would appear that Forrest behaves inconsistently only when this
feature is used in a way that's inconsistent with its intent.

--tim

[1] - http://people.apache.org/~hossman/#xyproblem
[2] - http://forrest.apache.org/docs_0_80/faq.html#cli-xconf


Re: relative links in site.xml

2010-07-01 Thread Tim Williams
On Wed, Jun 30, 2010 at 8:36 AM, Wipf Markus  wrote:
> Hi,
>
>
>
> Can anybody help me please to fix this problem.
>
> I'm trying to make the things more flexible by using relative links to
> external sites in site.xml:
>
>     
>
>    
>
>    
>
>     href="services/training/workshops/as/as_knowhow.pdf"/>
>
>    
>
>    
>
> The reference to it looks like:
>
> as_knowhow.pdf
>
>
>
> Running the site ant-task I get the following error:
>
>  [java] * [40/9]    [3/31]    0.728s 37.8Kb  kt/training.html
>
>  [java] * [41/8]    [0/0] 1.64s  52.3Kb  kt/training.pdf
>
>  [java] X [0]
> ../services/training/workshops/as/as_knowhow.pdf BROKEN: No flow in
> page-sequence
>
>
>
> The linkmap.xmap file defines for the 'linkmap' pipeline:  A linkmap is a
> map from abstract ('site:index') to
>
> physical ('../index.html') links for the current page.
>
>
>
> The compilation to html works fine, because the pipeline assumes another
> ../, which points exactly to the right place. But the pdf pipeline doesn't
> behave the same way. I don't understand this behavior.
>
> Is there any solution? Best regards. Markus

Hi Markus,
Is it really an *external* reference?  I haven't looked at this in a
while, but I can't recall seeing an example like yours where it's a
local (e.g. "../") and not building up on some full base url.
Hopefully someone else comes along soon, what version of forrest are
you using?  I'm not familiar with that particular fop error either
unfortunately.

--tim


[Travel Assistance] - Applications Open for ApacheCon NA 2010

2010-05-16 Thread Tim Williams
FYI Forrest community...


-- Forwarded message --

The Travel Assistance Committee is now taking in applications for those
wanting to attend ApacheCon North America (NA) 2010, which is taking place
between the 1st and 5th November in Atlanta.

The Travel Assistance Committee is looking for people who would like to be
able to attend ApacheCon, but who need some financial support in order to be
able to get there. There are limited places available, and all applications
will be scored on their individual merit.

Financial assistance is available to cover travel to the event, either in
part or in full, depending on circumstances. However, the support available
for those attending only the barcamp is smaller than that for people
attending the whole event. The Travel Assistance Committee aims to support
all ApacheCons, and cross-project events, and so it may be prudent for those
in Asia and the EU to wait for an event closer to them.

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 are now being accepted, and
will close on the 7th July 2010.

Good luck to all those that will apply.

You are welcome to tweet, blog as appropriate.

Regards,

The Travel Assistance Committee.


Re: For input string: ":0"

2010-04-30 Thread Tim Williams
On Thu, Apr 29, 2010 at 11:46 PM, Richard Suematsu
 wrote:
> On Tue, Apr 20, 2010 at 2:46 AM, Tim Williams  wrote:
>> On Mon, Apr 19, 2010 at 11:20 PM, Richard Suematsu
>>  wrote:
>>> Hi,
>>>
>>> Using Forrest (trunk), I've been getting a 'BROKEN: For input string:
>>> ":0"' error message when Forrest tried to generate pdfs of my pages.
>>> My site probably has 50 pages and none of them generate.  On another
>>> machine with a older Forrest, everything still works fine.  Any ideas?
>>
>> Hi Richard,
>> I honestly have no clue what's going on but maybe telling us a bit
>> more about your environment might help us help you.  JDK version,
>> dispatcher or not, etc.  Logs surrounding the error?  Does it work in
>> dynamic mode?
>> Thanks,
>> --tim
>>
>
> Hi Tim,
>
> Thank you for the help.  A little more info:
>
> JDK 1.6.0_19 on a Windows 7 64-bit with 64-bit Java.
> I don't think I'm using dispatcher.  I don't know what it is.  It
> doesn't work in dynamic mode either.  I brought over a copy of my
> "apache-forrest-0.8" from another machine that works and it works on
> this machine also.  So it's just the version I check out of
> subversion.
>
> As a test, I created a new project (forrest seed), and I have them
> same problem.  Here's is a run of the compile:

I just did this test on my mac with now problems, I wonder if it's a
windows thing?  Unfortunately, I don't have a machine to test it with.
 Hopefully, someone else on this list will have a windows machine to
confirm.  Have you checked your logs/do they give any more hint? (e.g.
build/webapp/WEB-INF/logs)

Thanks,
--tim


Re: For input string: ":0"

2010-04-20 Thread Tim Williams
On Mon, Apr 19, 2010 at 11:20 PM, Richard Suematsu
 wrote:
> Hi,
>
> Using Forrest (trunk), I've been getting a 'BROKEN: For input string:
> ":0"' error message when Forrest tried to generate pdfs of my pages.
> My site probably has 50 pages and none of them generate.  On another
> machine with a older Forrest, everything still works fine.  Any ideas?

Hi Richard,
I honestly have no clue what's going on but maybe telling us a bit
more about your environment might help us help you.  JDK version,
dispatcher or not, etc.  Logs surrounding the error?  Does it work in
dynamic mode?
Thanks,
--tim


Re: validate error when I run the forrest command

2010-04-15 Thread Tim Williams
On Thu, Apr 15, 2010 at 5:39 AM, Trasca Virgil  wrote:
> Hi,
>
>  I tried forrest seed and I generated the initial project.
>
> When I run forrest I get a BUILD FAILED - validate.xml:158: Validation
> failed, messages should have been provided.
>
> What is this?

It's the task that checks the validity of your source content, maybe
you made some invalid changes to an xdoc or something?  Can you give
some more of the output?
Thanks,
--tim


Forrest JIRA users please read...

2010-04-13 Thread Tim Williams
>From the incident report[1]:

"If you are a user of the Apache hosted JIRA, Bugzilla, or Confluence,
a hashed copy of your password has been compromised."

Thanks,
--tim

[1] - https://blogs.apache.org/infra/entry/apache_org_04_09_2010


Re: problem with incorrect tab selection

2010-02-11 Thread Tim Williams
On Thu, Feb 11, 2010 at 8:36 AM, Ionut Scutaru  wrote:
> Hi,
> Our project has it's documentation site generated with Apache Forrest
> (v0.6). The site is up and running and in general everything is working
> fine. However.. there is a slight problem that was noticed and I don't know
> if this is a bug or something that we configured wrong in the xml files.
>
> The issue is that, for some links, the currently selected tab is moved back
> to the first one but the contents of the page remains correct. Practically,
> the Design page is shown correctly, but not under the "Architecture" tab, as
> it should, but under the "Release Notes" tab.
>
> I tried to figure out what's different for those links compared with the
> ones that work correctly and I noticed something:
>
> 
> http://apache.org/forrest/linkmap/1.0"; label="Proj" href=""
> tab="releasenotes">
>
>      href="project/release_documentation/" tab="releasenotes">
>     
>     
>
>      tab="architecture">
>     
>     
>     
>
>     
>
> 
>
> The structure of the folders is as follows:
>     
>         project\release_documentation\
>         project\architecture\
>         general\documentation\
>
> When I click on the "Design Patterns" link I'm taken to the right page, but
> the Architecture tab do not remain selected, but instead the "Release Notes"
> tab gets active.
>
> It seems to me there is a problem with the indirect linking, but I can't
> pinpoint it..

Can you share your tabs definition?  I seem to remember some problems
with loosing context in 0.6 - have you had a chance to search JIRA for
old issues?

--tim


Re: Skinned Sites: Please remove the Link to www.krabbelkaefer.de

2009-10-17 Thread Tim Williams
Done in the source at r826262.
Thanks,
--tim

On Sat, Oct 17, 2009 at 10:23 AM, Monika Schaefer
 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
>


Re: about internationalization

2009-07-30 Thread Tim Williams
On Wed, Jul 29, 2009 at 2:51 PM, Joao
Ferreira 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


Re: how to source a global document-to-fo.xsl from my local one?

2009-02-26 Thread Tim Williams
On Thu, Feb 26, 2009 at 7:37 AM, EMMEL Thomas  wrote:
> Ross,
>
> finally I managed what I liked to do:
> I added
>
> 
>
> to my local document-to-fo.xsl
> and
>
> 
>src="{forrest:forrest.plugins}/org.apache.forrest.plugin.output.pdf/resources/stylesheets/{1}-to-{2}.xsl"/>
> 
>
> to my locationmap
>
> So, how can I add patches to the documentation? Should I send that to the
> list, to you or submit it by svn???

http://forrest.apache.org/contrib.html#patch

--tim


Re: how to use photogallery plugin?

2008-07-14 Thread Tim Williams
On Mon, Jul 14, 2008 at 11:06 AM, gulfiz ergin <[EMAIL PROTECTED]> wrote:
>
>>Can you copy your site to a simple path (e.g. C:\temp) and try to
>>build from there?  I'm wondering if the spaces in the directory path
>>aren't the issue.
>>--tim
> as you said I change the path...both nothing has changed...when I check
> error.log,it is empty..

Can you run the Photogallery sample site?  Does it work properly?

--tim


Re: how to use photogallery plugin?

2008-07-14 Thread Tim Williams
On Mon, Jul 14, 2008 at 5:42 AM, gulfiz ergin <[EMAIL PROTECTED]> wrote:
>>Are you using *nix platform?  If so, you might have to open up write
>>permissions on those directories.  Can you look into your logs and see
>>if there's any useful information?
>
>>--tim
>
> I am using windows xp. I checked error.log and I have "Internal Cocoon
> Problem"
> I pasted whole error here:
>
> "ERROR   (2008-07-14) 23:29.36:593   [access] (/gallery/ge/b.thumb.jpg)
> PoolThread-3/CocoonServlet: Internal Cocoon Problem
> org.apache.cocoon.ProcessingException: Error creating persistent file for
> transformed version of file:/C:/Documents and
> Settings/gulfizer/Desktop/son/src/documentation/content/xdocs/images/gallery/ge/b.thumb.jpg
> at  -

... snipped stack trace...

> Well, I confused more than ever...:S

Can you copy your site to a simple path (e.g. C:\temp) and try to
build from there?  I'm wondering if the spaces in the directory path
aren't the issue.
--tim


Re: how to use photogallery plugin?

2008-07-14 Thread Tim Williams
On Mon, Jul 14, 2008 at 3:32 AM, gulfiz ergin <[EMAIL PROTECTED]> wrote:
> Hi again...
> There is something strange in my site..(may be this issue is discussed
> before
> I did not search for it.)Any kind of photo I put to my site (logo etc.) does
> not
> appear on Mozilla Firefox but in internet explorer!I don't know what is
> wrong here...
>
> On the other hand,I can say that photo gallery is working but I can see the
> images
> when I click on "view the largest picture".It is written in the document
> that
> "The thumbnail and small sized images will be automatically generated" but
> in my site
> I couldn't see the thumbnails and small sized images.
> thanks for your responses! have a nice day...

Are you using *nix platform?  If so, you might have to open up write
permissions on those directories.  Can you look into your logs and see
if there's any useful information?

--tim


Re: how to use photogallery plugin?

2008-07-10 Thread Tim Williams
On Thu, Jul 10, 2008 at 9:56 AM, gulfiz ergin <[EMAIL PROTECTED]> wrote:
>  <--tim
> Tim as you said it is generated! now I have two different photo galleries
>  that  have its own album.xml file and photos. But I couldn't see my photos.
> I wrote the code in album.xml like this :
>
> 
>
> but still any photo appears on the site, what is more my
> album's name disappears!
> how this code should be?any help?

Please go back to the plugin page[1] and carefully follow all the
instructions.  The album.xml file should look like this[2].

--tim
[1] - 
http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.PhotoGallery/index.html
[2] - 
http://svn.apache.org/viewvc/forrest/trunk/plugins/org.apache.forrest.plugin.input.PhotoGallery/src/documentation/content/xdocs/images/gallery/demo/album.xml?revision=410189&content-type=text%2Fplain


Re: how to use photogallery plugin?

2008-07-10 Thread Tim Williams
On Thu, Jul 10, 2008 at 7:28 AM, gulfiz ergin <[EMAIL PROTECTED]> wrote:
>  <{properties:content.xdocs}/images/gallery/ then you should be able to
><--tim
> I am so sorry about my dumb questions.Should I create this index.html or
> plugin will do it for me?
> I created it by myself and actually i don't know which codes I should write
> in it?Is there any example
> .xml file (for gallery) that I can see what should I have and then I can
> change it for my site?

It's generated - just point your browser at it.
--tim


Re: how to use photogallery plugin?

2008-07-10 Thread Tim Williams
On Thu, Jul 10, 2008 at 7:02 AM, gulfiz ergin <[EMAIL PROTECTED]> wrote:
> hey all;
> I want to use photo gallery plugin but i am not able to do it. I look at
> mail archive and couldn't find something which is helpful. I check
> "http://forrest.apache.org/pluginDocs/plugins_0_80/org.apache.forrest.plugin.input.PhotoGallery/index.html
> "also...
> I created  my directories and  I have  album.xml in it. but i dont know what
> i should do now? I will appreciate if somebody will explain the steps of
> using this plugin...
> have a nice day!

If you've followed the docs and put your images in
{properties:content.xdocs}/images/gallery/ then you should be able to
navigate to /gallery/index.html and see them. Maybe you could explain
exactly how far you are getting and report any errors you've
encountered?
--tim


Re: Want to use javascript

2008-06-17 Thread Tim Williams
The link works fine for me - it's to an archived email exchange
addressing your issue.  Here's the markmail version:

http://markmail.org/message/x6mgagystmh3rlvq

--tim

On Tue, Jun 17, 2008 at 8:04 AM, Dr. Bhatia Praveen
<[EMAIL PROTECTED]> wrote:
> Hi Thorsten,
>  The link that you have given is not a valid link (the html page is
> missing.) Please direct me to the right link.
> Praveen
>
> -Original Message-
> From: Thorsten Scherler [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 17, 2008 8:28 PM
> To: user@forrest.apache.org
> Subject: Re: Want to use javascript  in generated html pages
>
> On Sat, 2008-06-14 at 00:24 +0900, Dr. Bhatia Praveen wrote:
>> Hi,
>>   I want to embed javascript code in the final html pages generated by
>> forrest ie it should have