X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=F7SqXH4jncRQVPW2sqcWIevBkM4yTx0gjQG8IhhsWuI=; b=ftrNRNqxavY4A5MWGMz86LsJVwX4UyiMFzV9KEGeInkRQuiqTa+HrsF4MxwfNnzPu0 jdK/NbsKW5flHW2NsRP3cOhXYtQs9WtU/DyDPn+a/ldovHmUsfWzj/xRwwMWb4/mfn4I xPS1JOUo2AeSTJyix4Ohh1M0rBaDRG/jwgu6k3JvnrUPpqfJzhxDiVm1yXcyxcHlHMOk TT4lH5kHAMqEBPE1fvxInIFSyOA2bcxWadAFHbwGBoT+a4+V/hZcZQlTq1LQjrMCEjAS czErAcV30r0harttWAuLOQddZGvL9OzPPhUqcnmvccTi0CYWjfJFet6WJIZZ0fkpW3lt 3/Ew== MIME-Version: 1.0 X-Received: by 10.60.81.202 with SMTP id c10mr16300578oey.61.1450891303509; Wed, 23 Dec 2015 09:21:43 -0800 (PST) In-Reply-To: <8FC1AF9D-22A6-4EBB-A3AE-A2C8D01F8E75@sbcglobal.net> References: <2F985E82-4EA8-42C9-9C50-99816BCE0BB4 AT sbcglobal DOT net> <14F365D1-6794-427D-893B-BD972E81771E AT sbcglobal DOT net> <8FC1AF9D-22A6-4EBB-A3AE-A2C8D01F8E75 AT sbcglobal DOT net> Date: Wed, 23 Dec 2015 17:21:43 +0000 Message-ID: Subject: Re: [geda-user] Missing PO Files From: "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" To: gEDA User Mailing List Content-Type: multipart/alternative; boundary=047d7b417c3dc0e300052793f471 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 --047d7b417c3dc0e300052793f471 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable It would probably work, but my gut feel is go with Vladimir's suggestion and keep it the way it is. Translators can maintain their translations far more readily than the developers, so do as we used to.... Develop away, prior to release freeze, get the po files into launchpad, let the Translators do their thing, and pull back the updated .po files. You can copy+paste translations in 'n' languages, but I'd suggest just focusing on the code. Peter On 23 Dec 2015 17:03, "Edward Hennessy (ehennes AT sbcglobal DOT net) [via geda-user AT delorie DOT com]" wrote: > Thanks for the response, Peter. > > > On Dec 22, 2015, at 8:55 AM, Peter Clifton ( > petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com] < > geda-user AT delorie DOT com> wrote: > > > > The only implication I can think might crop up is distro-packaging of > > the installed translation files. By sharing them between programs > > (which still for most distros, have separate build and install > > processes), you create the necessity to split out a common dependency > > package with the translation files (or tie it into libgeda, since most > > use this). > > Do you think that having a single PO folder under (associated with) one > configure.ac would work with the distos? I=E2=80=99m not familiar enough = with the > downstream process. > > Ed > --047d7b417c3dc0e300052793f471 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It would probably work, but my gut feel is go with Vladimir&= #39;s suggestion and keep it the way it is.

Translators can maintain their translations far more readily= than the developers, so do as we used to....

Develop away, prior to release freeze, get the po files into= launchpad, let the Translators do their thing, and pull back the updated .= po files.

You can copy+paste translations in 'n' languages, bu= t I'd suggest just focusing on the code.

Peter

On 23 Dec 2015 17:03, "Edward Hennessy (ehennes AT sbcglobal DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:=
Thanks for the resp= onse, Peter.

> On Dec 22, 2015, at 8:55 AM, Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>
> The only implication I can think might crop up is distro-packaging of<= br> > the installed translation files. By sharing them between programs
> (which still for most distros, have separate build and install
> processes), you create the necessity to split out a common dependency<= br> > package with the translation files (or tie it into libgeda, since most=
> use this).

Do you think that having a single PO folder under (associated with) one configure= .ac would work with the distos? I=E2=80=99m not familiar enough with th= e downstream process.

Ed
--047d7b417c3dc0e300052793f471--