<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1458" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=Arial size=2>Franck,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>That's why I did not think it was a priority. But a
french or japanese translation of gdalinfo might interest. My thinking was to
have easier access to the literal stuff and put some translating macros in
strategic places. Error messages are never understandable by a regular user. But
info could be displayed in user language.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>If you, or anyone on the list, are curious of
that, you will find the Unicode macros and functions in MS compilers tchar.h
headers. Roughly it is something like </FONT></DIV>
<DIV><FONT face=Arial size=2><EM>#ifdef UNICODE </EM></FONT></DIV>
<DIV><FONT face=Arial size=2><EM>typedef wchar_t TCHAR; </EM></FONT></DIV>
<DIV><FONT face=Arial size=2><EM>#else </EM></FONT></DIV>
<DIV><FONT face=Arial size=2><EM>typedef char TCHAR;</EM></FONT></DIV>
<DIV><FONT face=Arial size=2><EM>#endif</EM></FONT></DIV>
<DIV><EM><FONT face=Arial size=2></FONT></EM> </DIV>
<DIV><FONT face=Arial size=2>Changing the char definitions in GDAL code to
TCHAR is a tedious but simple operation. You ask the real question: Who would
pay time or money for that ?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Regards</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>AR</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>----- Original Message ----- </FONT>
<DIV><FONT face=Arial size=2>From: "Frank Warmerdam" <</FONT><A
href="mailto:fwarmerdam@gmail.com"><FONT face=Arial
size=2>fwarmerdam@gmail.com</FONT></A><FONT face=Arial size=2>></FONT></DIV>
<DIV><FONT face=Arial size=2>To: "Alain Rist" <</FONT><A
href="mailto:ar@navpoch.com"><FONT face=Arial
size=2>ar@navpoch.com</FONT></A><FONT face=Arial size=2>></FONT></DIV>
<DIV><FONT face=Arial size=2>Cc: <</FONT><A
href="mailto:gdal-dev@xserve.flids.com"><FONT face=Arial
size=2>gdal-dev@xserve.flids.com</FONT></A><FONT face=Arial
size=2>></FONT></DIV>
<DIV><FONT face=Arial size=2>Sent: Wednesday, December 08, 2004 6:56
PM</FONT></DIV>
<DIV><FONT face=Arial size=2>Subject: Re: [Gdal-dev] GDAL on
WinCE?</FONT></DIV></DIV>
<DIV><FONT face=Arial><BR><FONT size=2></FONT></FONT></DIV><FONT face=Arial
size=2>> On Wed, 8 Dec 2004 18:43:55 +0100, Alain Rist <</FONT><A
href="mailto:ar@navpoch.com"><FONT face=Arial
size=2>ar@navpoch.com</FONT></A><FONT face=Arial size=2>> wrote:<BR>>
> <BR>> > Franck, <BR>> > <BR>> > WinCE
systems are Unicode only. <BR>> > <BR>> > You can
process char, char*, char& and char[] types as usual, but any string<BR>>
> transfer with the system ( file names, error messages etc..) is Unicode.
<BR>> ><BR>> > Many places in GDAL code embed such strings. All
these char* or char[]<BR>> > should be changed to TCHAR ( a macro that
expands to wchar_t if Unicode is<BR>> > enabled ) , without touching the
real char type used in the formats. <BR>> > <BR>> > By
the way, Unicode enabling GDAL is a very good idea : if coupled with<BR>>
> grouping of all message strings and hard-coded names in some
resource<BR>> > location, it would open the possibility for non english
speakers to use GDAL<BR>> > ! <BR>> > <BR>> > But
if it is on your TODO list, I am afraid it gets a very bad scoring. <BR>>
<BR>> Alain, <BR>> <BR>> I can't say unicode enabling GDAL has been
high on my priority list. <BR>> It is a sufficiently major job that I think I
would need a paying client<BR>> who needs the capability enough to foot the
bill. And I hate to think<BR>> what complexities it would pose for
"normal" applications using<BR>> the library the old way. I would
definately want to look at doing<BR>> such a conversion in a way not unduely
incompatible with what is<BR>> done now. <BR>> <BR>> I am also not keen
on translatability of messages. I just find it hard<BR>> to imagine
anyone wanting to get error messages from GDAL in<BR>> another language badly
enough to justify the effort of translating and<BR>> trying to maintain all
the error messages. I also don't like messages<BR>> getting "too far
away" from the code that issues them. Generally I<BR>> have seen this
be a recipe for "message rot" where it is too much <BR>> trouble to find the
messages and update them when the code changes. <BR>> Knowing my own laziness
in this regard I would need a strong <BR>> motivation to make such a
change. Likewise, I do a crappy job at<BR>> keeping the format
documentation up to date as it is now. Imagine<BR>> how much less
likely this would be done well in another language. <BR>> <BR>> I
guess my point is that I try hard to limit the amount of <BR>> documentation
work so as to prevent me and others from just<BR>> giving up on it. I
am leery of anything that complicates the effort. <BR>> <BR>> Best
regards,<BR>> -- <BR>>
---------------------------------------+--------------------------------------<BR>>
I set the clouds in motion - turn up | Frank Warmerdam, </FONT><A
href="mailto:warmerdam@pobox.com"><FONT face=Arial
size=2>warmerdam@pobox.com</FONT></A><BR><FONT face=Arial size=2>> light and
sound - activate the windows | </FONT><A
href="http://pobox.com/~warmerdam"><FONT face=Arial
size=2>http://pobox.com/~warmerdam</FONT></A><BR><FONT face=Arial size=2>>
and watch the world go round - Rush | Geospatial Programmer
for Rent<BR>> <BR>> </FONT></BODY></HTML>