Mail Archives: geda-user/2015/12/23/12:21:54
--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]" <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
<p dir=3D"ltr">It would probably work, but my gut feel is go with Vladimir&=
#39;s suggestion and keep it the way it is.</p>
<p dir=3D"ltr">Translators can maintain their translations far more readily=
than the developers, so do as we used to....</p>
<p dir=3D"ltr">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.</p>
<p dir=3D"ltr">You can copy+paste translations in 'n' languages, bu=
t I'd suggest just focusing on the code.</p>
<p dir=3D"ltr">Peter</p>
<div class=3D"gmail_quote">On 23 Dec 2015 17:03, "Edward Hennessy (<a =
href=3D"mailto:ehennes AT sbcglobal DOT net">ehennes AT sbcglobal DOT net</a>) [via <a hr=
ef=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>]" <<a=
href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>> wrote:=
<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks for the resp=
onse, Peter.<br>
<br>
> On Dec 22, 2015, at 8:55 AM, Peter Clifton (<a href=3D"mailto:petercjc=
lifton AT googlemail DOT com">petercjclifton AT googlemail DOT com</a>) [via <a href=3D"m=
ailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] <<a href=3D"mail=
to:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>> wrote:<br>
><br>
> The only implication I can think might crop up is distro-packaging of<=
br>
> the installed translation files. By sharing them between programs<br>
> (which still for most distros, have separate build and install<br>
> processes), you create the necessity to split out a common dependency<=
br>
> package with the translation files (or tie it into libgeda, since most=
<br>
> use this).<br>
<br>
Do you think that having a single PO folder under (associated with) one <a =
href=3D"http://configure.ac" rel=3D"noreferrer" target=3D"_blank">configure=
.ac</a> would work with the distos? I=E2=80=99m not familiar enough with th=
e downstream process.<br>
<br>
Ed<br>
</blockquote></div>
--047d7b417c3dc0e300052793f471--
- Raw text -