Re: solr home page

2006-01-31 Thread Otis Gospodnetic
Wow, thanks for taking the time to figure this out, Yonik.  The c renders 
correctly for me, but even if it doesn't, don't worry about it, unless you 
really want to fix the Forrest/httpd conf encodings...

Otis

- Original Message 
From: Yonik Seeley [EMAIL PROTECTED]
To: solr-dev@lucene.apache.org
Sent: Tue 31 Jan 2006 12:00:23 AM EST
Subject: Re: solr home page

I'm surprised no one noticed the mismatch of encodings before.
Let's see what the forrest folks have to say...
http://www.mail-archive.com/user@forrest.apache.org/msg01652.html

-Yonik

On 1/30/06, Yonik Seeley [EMAIL PROTECTED] wrote:
 Hmmm, the c in Gospodnetic got messed up somewhere in the chain of things...

 I put it in the source xdoc as #263; and that worked in the local preview.
 That turned into C487 in the generated XML (which still looks fine
 if I point by browser at the local file).
 When it's served up by apache though, it doesn't work.

 Ideas?

 -Yonik


 On 1/30/06, Yonik Seeley [EMAIL PROTECTED] wrote:
  Basic web site is up.
 
  http://incubator.apache.org/solr/
 
  Built with Forrest 0.7, it grew on me after I got over the stumbling blocks.
  I discovered that forrest run also allows you to change the source
  documents and just hit reload in the browser... no need to rebuild to
  see the changes.
 
  -Yonik
 






Re: solr home page

2006-01-31 Thread Yonik Seeley
I set the default encoding to everything under solr for UTF-8 via .htaccess

AddDefaultCharset UTF-8

I see it correctly after clearing my browser cache (reload alone doesn't do it).

It's still a hack IMO, since it doesn't really allow documents with
different charsets to coexist.

May want to add that to lucene.apache.org if we ever want anything
outside ASCII on those sites.

-Yonik

On 1/31/06, Otis Gospodnetic [EMAIL PROTECTED] wrote:
 Wow, thanks for taking the time to figure this out, Yonik.  The c renders 
 correctly for me, but even if it doesn't, don't worry about it, unless you 
 really want to fix the Forrest/httpd conf encodings...

 Otis

 - Original Message 
 From: Yonik Seeley [EMAIL PROTECTED]
 To: solr-dev@lucene.apache.org
 Sent: Tue 31 Jan 2006 12:00:23 AM EST
 Subject: Re: solr home page

 I'm surprised no one noticed the mismatch of encodings before.
 Let's see what the forrest folks have to say...
 http://www.mail-archive.com/user@forrest.apache.org/msg01652.html

 -Yonik

 On 1/30/06, Yonik Seeley [EMAIL PROTECTED] wrote:
  Hmmm, the c in Gospodnetic got messed up somewhere in the chain of things...
 
  I put it in the source xdoc as ć and that worked in the local preview.
  That turned into C487 in the generated XML (which still looks fine
  if I point by browser at the local file).
  When it's served up by apache though, it doesn't work.
 
  Ideas?
 
  -Yonik
 
 
  On 1/30/06, Yonik Seeley [EMAIL PROTECTED] wrote:
   Basic web site is up.
  
   http://incubator.apache.org/solr/
  
   Built with Forrest 0.7, it grew on me after I got over the stumbling 
   blocks.
   I discovered that forrest run also allows you to change the source
   documents and just hit reload in the browser... no need to rebuild to
   see the changes.
  
   -Yonik
  
 






Re: solr home page

2006-01-31 Thread Paul Querna

Yonik Seeley wrote:

I set the default encoding to everything under solr for UTF-8 via .htaccess

AddDefaultCharset UTF-8


You shouldn't need any Default Charset anyways.

Just set it to AddDefaultCharset off, and let the browser guess.

This will allow documents of different charsets to exist.

-Paul


I see it correctly after clearing my browser cache (reload alone doesn't do it).

It's still a hack IMO, since it doesn't really allow documents with
different charsets to coexist.

May want to add that to lucene.apache.org if we ever want anything
outside ASCII on those sites.

-Yonik

On 1/31/06, Otis Gospodnetic [EMAIL PROTECTED] wrote:

Wow, thanks for taking the time to figure this out, Yonik.  The c renders 
correctly for me, but even if it doesn't, don't worry about it, unless you really want to 
fix the Forrest/httpd conf encodings...

Otis

- Original Message 
From: Yonik Seeley [EMAIL PROTECTED]
To: solr-dev@lucene.apache.org
Sent: Tue 31 Jan 2006 12:00:23 AM EST
Subject: Re: solr home page

I'm surprised no one noticed the mismatch of encodings before.
Let's see what the forrest folks have to say...
http://www.mail-archive.com/user@forrest.apache.org/msg01652.html

-Yonik

On 1/30/06, Yonik Seeley [EMAIL PROTECTED] wrote:

Hmmm, the c in Gospodnetic got messed up somewhere in the chain of things...

I put it in the source xdoc as ć and that worked in the local preview.
That turned into C487 in the generated XML (which still looks fine
if I point by browser at the local file).
When it's served up by apache though, it doesn't work.

Ideas?

-Yonik


On 1/30/06, Yonik Seeley [EMAIL PROTECTED] wrote:

Basic web site is up.

http://incubator.apache.org/solr/

Built with Forrest 0.7, it grew on me after I got over the stumbling blocks.
I discovered that forrest run also allows you to change the source
documents and just hit reload in the browser... no need to rebuild to
see the changes.

-Yonik









Re: solr home page

2006-01-30 Thread Yonik Seeley
Hmmm, the c in Gospodnetic got messed up somewhere in the chain of things...

I put it in the source xdoc as #263; and that worked in the local preview.
That turned into C487 in the generated XML (which still looks fine
if I point by browser at the local file).
When it's served up by apache though, it doesn't work.

Ideas?

-Yonik


On 1/30/06, Yonik Seeley [EMAIL PROTECTED] wrote:
 Basic web site is up.

 http://incubator.apache.org/solr/

 Built with Forrest 0.7, it grew on me after I got over the stumbling blocks.
 I discovered that forrest run also allows you to change the source
 documents and just hit reload in the browser... no need to rebuild to
 see the changes.

 -Yonik