denemo-devel
[Top][All Lists]
Advanced

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

Re: [Denemo-devel] POTFILES.in out of the repository


From: Richard Shann
Subject: Re: [Denemo-devel] POTFILES.in out of the repository
Date: Tue, 11 Jun 2013 14:11:40 +0100

On Tue, 2013-06-11 at 14:07 +0200, Éloi Rivard wrote:
> I just saw that cgit generates snapshots at each commit :
> http://git.savannah.gnu.org/cgit/denemo.git/snapshot/denemo-master.tar.gz
> 

???? this is the url I gave in the email you are replying to (see
below).

Richard

> 
> 
> 2013/5/31 Richard Shann <address@hidden>
>         On Fri, 2013-05-31 at 15:52 +0200, Éloi Rivard wrote:
>         > Le vendredi 31 mai 2013 à 14:38 +0100, Richard Shann a
>         écrit :
>         > > Ah, I see, you are trying to email a file denemo-xxx.pot
>         as an
>         > > attachment. I can't quite make out if you are trying to
>         email the
>         > > location of the tarball which they want for translators to
>         consult in
>         > > case of ambiguity.
>         > Both tarball and denemo.pot are sended.
>         > > The mailx command didn't work with my version of
>         > > mailx because of an unrecognized option -r.
>         > You are right, -r is kept for compatibility -S
>         address@hidden
>         > seems to be the right way to do this.
>         > > What I don't understand is that after doing
>         > > git pull
>         > > ./autogen.sh && ./configure
>         > > make send-pot
>         > > I do not have an up-to-date denemo.pot file (I checked for
>         the strings
>         > > recently included in changes to the tooltip to the command
>         > > d-StagedDelete). In fact denemo.pot is unchanged ...
>         > Actually for the moment, scheme code is node translated
>         until you
>         > extract scheme from xml, with tools/extract_scheme.
>         
>         
>         so I should do
>         
>         cd tools
>         gcc extract_scheme.c -o extract_scheme
>         cd ..
>         ./extract_all.sh
>         
>         and then what?
>         
>         
>         >  This is quite dirty.
>         > I think the best way would be to store the scheme code
>         nearby its xml
>         > file. So we could fully automate translation, and we would
>         not mix data
>         > and metadata.
>         > >
>         > > Although it is a little sloppy we can just email the git
>         snapshot url
>         > > once we have updated denemo.pot for a new release;
>         something better
>         > > would be good of course, but tricky, as it should really
>         involve putting
>         > > a tarball up on the internet somewhere (with all that
>         implies in terms
>         > > of storage space etc).
>         > How many space is free on the denemo website server ?
>         
>         Jeremiah mentioned it was a little tight, so we can have the
>         current
>         release up there but not a chain of them.
>         > If it is a
>         > dedicated server, maybe we can set a hook that would launch
>         "make dist"
>         > on each commit on master, and rename the tarball
>         denemo-lastest.tgz.
>         
>         
>         This is obviated by the git server on savannah, I just send an
>         email
>         with subject
>         New version  denemo-1.0.0~rc7<n>.pot.
>         and body
>         
> 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
>         Denemo has an updated pot file available the tar ball is at
>         
> http://git.savannah.gnu.org/cgit/denemo.git/snapshot/denemo-master.tar.gz
>         
>         
> 8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><8><
>         
>         That is, the above URL gets the needed tarball, generated on
>         the fly.
>         The reason I call this sloppy is that I am not sure that the
>         translation
>         project copies the tarball away somewhere, so that, if not,
>         the snapshot
>         could have moved on by the time a translator looks at it to
>         check for an
>         ambiguity. But in practice I think this is ok. We would not
>         commit any
>         new denemo.pot to git master after sending the email until the
>         translation project has responded, but that is ok, we wouldn't
>         do that.
>         
>         Richard
>         
>         
> 
> 
> 
> -- 
> Éloi Rivard - address@hidden
>         
> « On perd plus à être indécis qu'à se tromper. »
> 





reply via email to

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