kicad-developers team mailing list archive

[Marco Ciampa <ciampix@xxxxxxxxx>]

Sorry I erroneously sent this to Nick and not to the list...

----- Forwarded message from Marco Ciampa <ciampix@xxxxxxxxx> -----

Date: Fri, 13 Mar 2015 18:23:13 +0100
From: Marco Ciampa <ciampix@xxxxxxxxx>
To: Nick Østergaard <oe.nick@xxxxxxxxx>
Subject: Re: [Kicad-developers] Announcing work on providing windows nightlies
User-Agent: Mutt/1.5.21 (2010-09-15)

On Fri, Mar 13, 2015 at 05:21:05PM +0100, Nick Østergaard wrote:
> 2015-03-13 16:29 GMT+01:00 Marco Ciampa <ciampix@xxxxxxxxx>:
> > On Fri, Mar 13, 2015 at 01:06:16PM +0100, Nick Østergaard wrote:
> > [...]
> >> Also, I wonder why the compiled po files are in the repo also (the .mo
> >> files). Is there a reason for this? Why not just do this as a build
> >> step?
> >
> > Looking at the i18n procedure it rely on poedit reading the headers of
> > the .po file just to update and collect the strings from sources.
> >
> > Since this is done by means of a manual procedure started by humans and
> > not updated automatically, it is necessary to save with the sources even
> > the .mo files that are binary compiled from .po files that are the real
> > source files.
> >
> > I already said that IMNSHO I consider this done badly if not totally
> > wrong.
> 
> Marco, I don't quite understand your point here. The po files are the
> sources, the mo files are the binaries.

so far so good

> For any source it should only
> be nessesary to keep the sources (po files) versioned, whilst the
> binaries should be compiled.

that is exactly my point

> I don't see what you think is done manually.

I mean:

 - where is the catalog file, the file that contains list of sources from 
   which the translatable strings are extracted? Actually there is no such 
   file (IIRC) but a list of reference in the .po files headers
 - usually there is a file, usually named POTFILES that contains the 
   references to such source files
 - usually compilation scripts use such POTFILES file to create a .pot 
   catalog file that is then used to automatically update the .po
   files
 - usually compilation script (make/cmake and such) keeps .mo files 
   compiled into .mo files
 - having such mechanism in-place there is no use to commit binary files
   with source .po files

> What I really ask is; is there a use for the mo files to be precompiled?

normally not. But our workflow depends on poedit .mo compilation, update 
and and catalog handling. .mo files are not automatically compiled by 
any cmake script (if I am not totally wrong) nor .po files are automatically
updated/merged by the gettext tools.
Usually such task is handled by intltool-update script that is not part of
cmake or kicad. If we want to automate the .po file generation/update/handling
we should create such a mechanism or adopt some ready made tool such GNU 
intltool.

bye

--


Marco Ciampa

I know a joke about UDP, but you might not get it.

+------------------------+
| GNU/Linux User  #78271 |
| FSFE fellow       #364 |
+------------------------+


----- End forwarded message -----

-- 


Marco Ciampa

I know a joke about UDP, but you might not get it.

+------------------------+
| GNU/Linux User  #78271 |
| FSFE fellow       #364 |
+------------------------+