X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=XCXqObFGaemw4rj/CjqUNl8UwSnPGtQ8N7YknuYDjnw=; b=g/e4yCJWrycyhQJ0lP77GuVUndlPNLL+mieEhyhS+O7+f7HBbbIEH2JHtYXD6wPn6z LhrIdgUmNvyUPHbfk0+uHh9zWuKmhGenTlLfMfvezfO5dC5QEP68fVYWXZVxz+BS4tTn kOw8E2yxiS5l5MPYCHJdijDu6wqSVxE6t/VQxBh8sLDL96MHCE+raF6DJsPH/kjbAXoU bSbauv1uFpXPfmd2UfJZWH8j8YbfeJWL+aLL2EKgR1bzmzUHLQrZ1e2EBc/4TpwfMgOr fnqcwZGeUMP4F0J2M3ZBjRKa95MJxs5Y4BIxXtqZ/bOYh3v5CzXG4IrV8aaifYN6XiP+ XICA== MIME-Version: 1.0 In-Reply-To: <20121113211401.20747813A49B@turkos.aspodata.se> References: <20121113211401 DOT 20747813A49B AT turkos DOT aspodata DOT se> Date: Wed, 14 Nov 2012 09:57:46 -0500 Message-ID: Subject: Re: [geda-user] Bug #903129 Translations don't work on Windows From: Bob Paddock To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=20cf307cfe02f1c51504ce75c168 Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --20cf307cfe02f1c51504ce75c168 Content-Type: text/plain; charset=ISO-8859-1 > a, Tell the user he must install the binary in if he wants locale > support, or just install it there without user intervention Corporate IT policy's in the IT world make that non-workable. For example IT allows nothing to be installed on drive C:\ to make *their* jobs easier. Some other places only allow user code to be installed in IT specified locations. > b, binary patch the lib at install time That will run afoul of the day when signed binaries are forced on Windows users. Might not be far away in Windows-8. > c, replace LOCALEDIR with value from a config file, e.g. ~/.gEDA/locale > > d, since libgeda isn't really a freestanding lib, and the caller could > possible also need some language files, push the problem to caller. > E.g. by a parameter: libgeda_int(char *localedir); d. is the most Windows viable solution. Something to watch-out for when, if, we get there, is that there is a C locale and a C++ stream locale, and currently in MinGW setting the C++ stream locale slows the code down by orders of magnatudes. Hopefully that is fixed in the MinGW end someday. --20cf307cfe02f1c51504ce75c168 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

> a, Tell the user he must install the binary in <dir> if = he wants locale
> =A0 =A0support, or just install it there without us= er intervention

Corporate=A0IT=A0policy's=A0in the IT world make= that non-workable.
For example IT allows nothing to be installed on drive C:\
to make *thei= r* jobs easier. =A0
Some other places only allow user code to be instal= led in IT=A0specified=A0locations.

> b, binary patch the lib at i= nstall time

That will run afoul of the day when signed binaries are forced on Windo= ws users.
Might not be far away in Windows-8.

> c, replace LO= CALEDIR with value from a config file, e.g. ~/.gEDA/locale
>
> = d, since libgeda isn't really a freestanding lib, and the caller could<= br> > =A0 =A0possible also need some language files, push the problem to cal= ler.
> =A0 =A0E.g. by a parameter: libgeda_int(char *localedir);
<= br>d. is the most Windows viable solution.

Somethi= ng to=A0watch-out=A0for when, if, we get there, is that there is a C locale= and a C++ stream locale,
and currently in MinGW setting the C++ stream locale slows the code do= wn by orders of=A0magnatudes.
Hopefully that is fixed in the MinG= W end someday.

=A0
--20cf307cfe02f1c51504ce75c168--