You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@roller.apache.org by Anil Gangolli <an...@busybuddha.org> on 2005/12/06 17:08:03 UTC
localization guide and question
I'm adding a localization guide to the wiki.
In documenting current Roller i18n support, it appears that we use the
server JVM's default locale rather than the user browser's locale for
selection of the resources in all of the JSP-based views. Is this
intended? Is it a regression? or have I got it wrong?
--a.
RE: Optionally indexing comments
Posted by Matthew Schmidt <ma...@javalobby.org>.
Seems the file did not get attached.
-----Original Message-----
From: Matthew Schmidt [mailto:matt@javalobby.org]
Sent: Wednesday, December 14, 2005 10:39 AM
To: roller-dev@incubator.apache.org
Subject: RE: Optionally indexing comments
Here's the adjustment to IndexOperation. It's listed as a class called
DZIndexOperation. Lines 62-67 are new as are 97-119. There's also a new
property in roller.properties listed as search.index.comments=true. It goes
just under the search.index.dir property.
-Matt
-----Original Message-----
From: Anil Gangolli [mailto:anil@busybuddha.org]
Sent: Wednesday, December 14, 2005 10:24 AM
To: roller-dev@incubator.apache.org
Subject: Re: Optionally indexing comments
These both sound good to me.
+1
I also volunteer to do the integration work if you send me the patches.
--a.
Matthew Schmidt wrote:
>Hi guys. During my work to migrate cleanly to Roller 2.x, I've come across
>an interesting problem. I'm currently trying to use the custom directory
to
>prevent myself from changing core files. The problem is that I need to
>change IndexOperation to not index comments (causes indexing to slag the
>machine when rebuilding the index). Would it be possible to have another
>roller property for optionally indexing comments? It seems like a trivial
>change and helps performance for large sites. It would also keep me from
>having to change a core class :)
>
>Another proposal I have is to add in user-agent checking to RefererFilter.
>We do this at JROller to exclude google and other spiders from the dayhits
>(when google hits you 80k times a day, its definitely needed). I have a
>small patch for this if you guys would like to add it to the core.
>Alternatively, is there a way I can override RefererFilter with my own
>version without causing duplicate class errors? Perhaps a way to remove it
>from the generated filter list and replace it with my own? All without
>tweaking the core code? :)
>
>Thanks,
>Matt
>
>-----Original Message-----
>From: Anil Gangolli [mailto:anil@busybuddha.org]
>Sent: Tuesday, December 06, 2005 11:08 AM
>To: roller-dev@incubator.apache.org
>Subject: localization guide and question
>
>
>I'm adding a localization guide to the wiki.
>
>In documenting current Roller i18n support, it appears that we use the
>server JVM's default locale rather than the user browser's locale for
>selection of the resources in all of the JSP-based views. Is this
>intended? Is it a regression? or have I got it wrong?
>
>--a.
>
>
>
>
>
RE: Optionally indexing comments
Posted by Matthew Schmidt <ma...@javalobby.org>.
Here's the adjustment to IndexOperation. It's listed as a class called
DZIndexOperation. Lines 62-67 are new as are 97-119. There's also a new
property in roller.properties listed as search.index.comments=true. It goes
just under the search.index.dir property.
-Matt
-----Original Message-----
From: Anil Gangolli [mailto:anil@busybuddha.org]
Sent: Wednesday, December 14, 2005 10:24 AM
To: roller-dev@incubator.apache.org
Subject: Re: Optionally indexing comments
These both sound good to me.
+1
I also volunteer to do the integration work if you send me the patches.
--a.
Matthew Schmidt wrote:
>Hi guys. During my work to migrate cleanly to Roller 2.x, I've come across
>an interesting problem. I'm currently trying to use the custom directory
to
>prevent myself from changing core files. The problem is that I need to
>change IndexOperation to not index comments (causes indexing to slag the
>machine when rebuilding the index). Would it be possible to have another
>roller property for optionally indexing comments? It seems like a trivial
>change and helps performance for large sites. It would also keep me from
>having to change a core class :)
>
>Another proposal I have is to add in user-agent checking to RefererFilter.
>We do this at JROller to exclude google and other spiders from the dayhits
>(when google hits you 80k times a day, its definitely needed). I have a
>small patch for this if you guys would like to add it to the core.
>Alternatively, is there a way I can override RefererFilter with my own
>version without causing duplicate class errors? Perhaps a way to remove it
>from the generated filter list and replace it with my own? All without
>tweaking the core code? :)
>
>Thanks,
>Matt
>
>-----Original Message-----
>From: Anil Gangolli [mailto:anil@busybuddha.org]
>Sent: Tuesday, December 06, 2005 11:08 AM
>To: roller-dev@incubator.apache.org
>Subject: localization guide and question
>
>
>I'm adding a localization guide to the wiki.
>
>In documenting current Roller i18n support, it appears that we use the
>server JVM's default locale rather than the user browser's locale for
>selection of the resources in all of the JSP-based views. Is this
>intended? Is it a regression? or have I got it wrong?
>
>--a.
>
>
>
>
>
Re: Optionally indexing comments
Posted by Anil Gangolli <an...@busybuddha.org>.
These both sound good to me.
+1
I also volunteer to do the integration work if you send me the patches.
--a.
Matthew Schmidt wrote:
>Hi guys. During my work to migrate cleanly to Roller 2.x, I've come across
>an interesting problem. I'm currently trying to use the custom directory to
>prevent myself from changing core files. The problem is that I need to
>change IndexOperation to not index comments (causes indexing to slag the
>machine when rebuilding the index). Would it be possible to have another
>roller property for optionally indexing comments? It seems like a trivial
>change and helps performance for large sites. It would also keep me from
>having to change a core class :)
>
>Another proposal I have is to add in user-agent checking to RefererFilter.
>We do this at JROller to exclude google and other spiders from the dayhits
>(when google hits you 80k times a day, its definitely needed). I have a
>small patch for this if you guys would like to add it to the core.
>Alternatively, is there a way I can override RefererFilter with my own
>version without causing duplicate class errors? Perhaps a way to remove it
>from the generated filter list and replace it with my own? All without
>tweaking the core code? :)
>
>Thanks,
>Matt
>
>-----Original Message-----
>From: Anil Gangolli [mailto:anil@busybuddha.org]
>Sent: Tuesday, December 06, 2005 11:08 AM
>To: roller-dev@incubator.apache.org
>Subject: localization guide and question
>
>
>I'm adding a localization guide to the wiki.
>
>In documenting current Roller i18n support, it appears that we use the
>server JVM's default locale rather than the user browser's locale for
>selection of the resources in all of the JSP-based views. Is this
>intended? Is it a regression? or have I got it wrong?
>
>--a.
>
>
>
>
>
Optionally indexing comments
Posted by Matthew Schmidt <ma...@javalobby.org>.
Hi guys. During my work to migrate cleanly to Roller 2.x, I've come across
an interesting problem. I'm currently trying to use the custom directory to
prevent myself from changing core files. The problem is that I need to
change IndexOperation to not index comments (causes indexing to slag the
machine when rebuilding the index). Would it be possible to have another
roller property for optionally indexing comments? It seems like a trivial
change and helps performance for large sites. It would also keep me from
having to change a core class :)
Another proposal I have is to add in user-agent checking to RefererFilter.
We do this at JROller to exclude google and other spiders from the dayhits
(when google hits you 80k times a day, its definitely needed). I have a
small patch for this if you guys would like to add it to the core.
Alternatively, is there a way I can override RefererFilter with my own
version without causing duplicate class errors? Perhaps a way to remove it
from the generated filter list and replace it with my own? All without
tweaking the core code? :)
Thanks,
Matt
-----Original Message-----
From: Anil Gangolli [mailto:anil@busybuddha.org]
Sent: Tuesday, December 06, 2005 11:08 AM
To: roller-dev@incubator.apache.org
Subject: localization guide and question
I'm adding a localization guide to the wiki.
In documenting current Roller i18n support, it appears that we use the
server JVM's default locale rather than the user browser's locale for
selection of the resources in all of the JSP-based views. Is this
intended? Is it a regression? or have I got it wrong?
--a.