xboard-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [XBoard-devel] Internationalization proposition


From: Daniel Mehrmann
Subject: Re: [XBoard-devel] Internationalization proposition
Date: Thu, 19 Feb 2004 19:11:26 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040124

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tim Mann wrote:


| On Thu, 19 Feb 2004 07:28:56 +0100, Daniel Mehrmann
<address@hidden> wrote:
|
|>No, sorry. I think you don't understand how windows language support
|>really works. We don't need gettext. Gettext is unix. I don't wanna unix
|>~   stuff into a real native WIN32 application.
|
|
| Daniel, how do you propose to internationalize backend.c and the other
| shared code using Windows language support without breaking their use in
| xboard?
|
I see no problems. Windows supports this for printf stuff too. We could
use #define calls. I don't see many lines that we must change. The
importent file for winboard is winboard.c. All the rest are only 3% or
less text lines.

But Alper remember me, not friendly but i don't want a flame or other
stuff, that you said we're using gettext. I don't like it, but its okay
for me. We're working as team and the team said gettext :)


| I don't know if gettext is as portable across Windows and Unix as we'd
| like, but the Windows language support is not portable at all -- it is
| Windows-only.
|
| A quick web search for [gettext windows] finds several pages about using
| gettext with Win32:

Importent is that we _not_ changing any internal dll stuff of windows if
we used gettext for windows. I think i don't remember you what happend
with other windows applications if we change %system%\*.dll stuff ;)



- --
Daniel Mehrmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)

iD8DBQFANPxOPt1V5Pj1nvYRApR5AJ95WfRBbThgfLvvdT/YE+V29VilZgCfU9Gp
DbDUyxuQ/Gn5xRmYZDni1aY=
=CEnQ
-----END PGP SIGNATURE-----

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]