Re: tlug: Forward from [Mustiantono <simus@example.com>]

[Ian Barwick <ianb@example.com>]

On Sat, 15 Apr 2000, Jonathan Q wrote:

> 
> Forwarded Message
> -----------------
> 
> Hi  ...
> I am setting up a webserver customised to Japanese environment.  I was
> wondering whether I should install Japanese Apache or ordinary English
> Apache.  I tried to use ordinary english Apaache and tried if it could
> display some html with kanji in it.  And it worked.  So I was wondering
> whether Japanese Apache is just ordinary Apache with japanese
> documentation or it has some features which are required in order to run
> some web applications which contains Japanese characters.  The web
> applications I will develop will be based heavily on perl, MySQL and
> PHP.

The web-server's job is basically to deliver the documents specified by an
HTTP request, regardless of what language or format they're in. Apache
will never need to address coding issues and in that sense is completely
"language transparent".

Where language does play a role is in the messages displayed by Apache
("The requested URL was not found on this server" etc) and the user
documentation. I presume this is what the "Japanese Apache" covers.
You can of course provide your own message handling in a language of your
choice.

It'll be with your application software itself where the real fun with
Japanese encoding starts ;-)

Yours
(delurking for the first time, promise I'll introduce myself properly)


Ian Barwick
ianb@example.com and sometimes in Tokyo



--------------------------------------------------------------------
Next Nomikai Meeting: April 20 (Thu) Linux Conference 2000 Spring Ed.
Next Technical Meeting: May 13 (Sat) 13:30 Temple University Japan
* Topic: TBD
--------------------------------------------------------------------
more info: http://www.tlug.gr.jp        Sponsor: Global Online Japan