httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Esselink" <>
Subject Re: localization of content/apache server
Date Tue, 05 Aug 1997 07:07:14 GMT
> .rc (resource) files for Win32.  The big question is : 1.3 or 2.0 ???
Please do NOT use resource files for server side components. They are great
for Gui tools, but not as usefull for NT services.
For my commercial products i'm using MS's MC  (MC= Message Compiler).
You simply create a text file and based on that compile and link it into
your exe of dll.
The MC tool is part of the DevStudio (VC) compiler.
I have had the localization division create 6 different localized version
of my Us English
.MC file. These where in Japanese, Chinese, french,german, spanish and
italian and I
could compile and link these translated files without any problem on my us

Since i'm writing anyway about the NT Apache, the exe and dll should also
version information so that the installer (which i'm building using
InstallShield5) knows
whether to replace or keep the already installed files.
I'll try to make a resource file that includes this version info and upload
it into the ftp

> From: Stanley Gambarin <>
> To:
> Subject: Re: localization of content/apache server
> Date: Monday, August 04, 1997 10:12 PM
> On Mon, 4 Aug 1997, Brian Behlendorf wrote:
> > but I think we could make it even easier; we could abstract all text
> > messages (default HTTP error responses, error log reporting, etc) to a
> > messages.c file, and use a #define to pre-configure a number of
> > languages.  Thoughts?
> > 
> > 	Brian
> > 
> 	I had already emailed about this to this list.  I have a working
> code prototype which i attached before, but can remail if someone is 
> interested.  The idea is to use either NLS catalogs for Un*x platforms
> .rc (resource) files for Win32.  The big question is : 1.3 or 2.0 ???
> The only small problem that i see is that there maybe some collision
> between external modules, which define the same number for different
> messages, but resolving this issue is very minor.
> 							Stanley.

View raw message