[ 
https://issues.apache.org/jira/browse/ROL-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719466#comment-13719466
 ] 

Glen Mazza commented on ROL-1964:
---------------------------------

Hi, thanks for the patch.  Could you better clarify what the problem is, why 
this change is helpful/important?  Is it that people who are using the (say) 
German version of Roller don't get a results page back in English (although the 
results page doesn't seem to show any static text, so I don't know why it would 
matter.) Or is it not the results page but the search page itself that isn't 
being placed into German?  (Sorry, I'm new to i18n and in English-only America 
so I'm not sure how to test this.)

I don't know if this is a related issue, but the older Roller 3.1 unfortunately 
provides two URLs for every blog entry, one with the locale, one without: 
http://www.jroller.com/gmazza/entry/apache_roller_blogging and 
http://www.jroller.com/gmazza/en/entry/apache_roller_blogging.  That messes up 
people's Google Analytics statistics, because Google chooses either URL when 
people search for blog entries and then the G.A. divides the blog entry 
statistics between two URLs even though the article is the same.  I'd like to 
avoid returning to that in 5.1 if possible (although I'm not sure this search 
page matter is related to it.)   
                
> SearchServlet does not preserve locale
> --------------------------------------
>
>                 Key: ROL-1964
>                 URL: https://issues.apache.org/jira/browse/ROL-1964
>             Project: Roller
>          Issue Type: Improvement
>          Components: Page Rendering & Management
>            Reporter: Maciej Rumianowski
>            Assignee: Roller Unassigned
>            Priority: Minor
>         Attachments: search.patch
>
>
> Search page is not localized:
> http://localhost/roller/test/de/search?q=test
> http://localhost/roller/test/en/search?q=test

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to