I18n Module maintenance
mmassonnet at gmail.com
mmassonnet at gmail.com
Mon Nov 19 10:02:38 CET 2007
On Mon, Nov 19, 2007 at 09:35:53AM +0100, mike wrote:
> On Mon, Nov 19, 2007 at 09:07:31AM +0100, Stephan Arts wrote:
> > Hi,
> > I noticed the following projects are missing po template files (.pot)
> > xfce4-cellmodem-plugin
> > xfmedia-remote-plugin
> > xfce4-places-plugin
> > And the following projects have .pot file issues:
> > xfce4-teatime-plugin - it's called teatime-plugin.pot (instead of
> > xfce4-teatime-plugin.pot)
> > xfce4-timer-plugin - it's called xfce4-timer.pot (instead of
> > xfce4-timer-plugin.pot)
> > libxfce4menu - it's called libxfce4menu-1.0.pot (instead of libxfce4menu.pot)
> > libexo - it's called libexo-0.3.pot (instead of libexo.pot)
> > thunar - it's called Thunar.pot (lovely... the germans camelcasing)
> Lovely <3 it even gives a distinction between compiled files and source
> files when you /bin/ls the source directory.
> > xfcalendar - it's called orage.pot (obviously)
> Just my 2 cents:
> The pot file is automatically generated when you 1) delete it and 2) run
> make update-po. It gets also deleted by make clean.
> So basically what would be needed is to run an update-po target and add
> those fresh pot files in svn. It fixes the issue with wrong names,
> hence it takes it wrong the project name (configure.in.in). In the case
> of orage, the xfcalendar dir name is "wrong".
> I often forget to refresh the pot file in the notes plugin :( Maybe it
> should just not be there, but then you can't run msginit for new
> > The .pot files obviously need to be imported to svn.
> > But what to do with the inconsistencies with the other 6 projects?
> > In the new stats page, 6 out of 71 projects fail to generate new
> > .po files because the .pot filename does not match the project name.
> > Now I could asume that my approach is wrong, which it probably is when
> > you look at Thunar and orage.
> > But the .pot files for the other 4 projects are just named weird.
> > What do you think?
> Except my 2 cents not much, sorry.
Actually, all the work around the po/ directory should to be done
automatically, and not by the dev — except the POTFILES telling from
where to pull the translatable strings. Add a svn hook maybe?
On another topic, Mişu arised a problem where new translated strings
for the most recent branch aren't merged to trunk, while there could be
As example, I can take the recent commit in trunk I have done for
Muhammad. While he had everything translated for trunk, it had be a
perfect candidate for a merge inside the 4.4 branch, since all the files
are new translations. If I knew about a way to do the merge, I had done
it, but in fact I don't know much about the po stuff.
> > Regards,
> > Stephan
> >  http://mocha.foo-projects.org/~stephan/stats.php
More information about the Xfce4-dev