Re: [Tracker] Updating .po files



Il giorno mar, 09/12/2008 alle 12.28 +0000, Martyn Russell ha scritto:
On 09/12/08 11:32, Luca Ferretti wrote:

There is no need to regenerate .po files. Translators should grab
automatically updated po files from http://l10n.gnome.org/ or manually
check out code and use `intltool-update` before translate it.

While this may be the case. They are actually not being updated.

I don't understand. Why do you think .po files are not updated? Or,
better, what do you mean for "updated"?

Check for example the Estonian translation. On svn you have this[1], on
l10n.gnome.org this[2].

The reference stings on [2] (msgid) are updated to latest tracker code,
see the  POT-Creation-Date value. Of course a lot of msgstr are not
"updated" (no 100%) 'cause the last translation update was about 1 years
ago.
PO files on l10n.gnome.org are "updated" from reference messages to
translate point of view.

About .po files in svn, run `make` in po directory, then run `msgunfmt
et.gmo`. GMO files only contains translated strings, as it should be.

If you mean "translations are not 100%", this depends on translators
works, not on wrong po files generated by gettext/intltool

[1] http://svn.gnome.org/viewvc/tracker/trunk/po/et.po?view=markup
[2] http://l10n.gnome.org/POT/tracker.HEAD/tracker.HEAD.et.po


         -l, --limit=LIMIT   Limit the results to LIMIT (default 512)

while now it's something like

         -l, --limit=512     Limit the results

I'm working on it, I'll provide an initial patch this week.

That's exactly what the limit=512 means. It means, that's the default. 

To be honest I never see this kind of convention. All GNU programs (for
exampel coreutil, tar) are using uppercase for options' arguments (i.e.
stuff that user will decide on) but don't propose a value. Try for
example `tar --help` and you'll see stuff like:

        --checkpoint[=NUMBER]  display progress messages every NUMBERth
                               record (default 10)
        --no-quote-chars=STRING   disable quoting for characters from
        STRING
        --quote-chars=STRING      additionally quote characters from
        STRING
        
And similar. Following GNU convention, limit=512 means that --limit can
only use 512 as argument :)

This is something which is defined in the GOption configuration. 

Of course, I know, the GOptionEntry->arg_destription, the API ref says
its a "placeholder to use for the extra argument parsed by the option in
--help output ". But it should be a "description" (LIMIT, or NUMBER, or
SERVICE), not a "value" (512, or 3, or EmailAttachments).

If you notice, other non-default command line switches don't have
anything set there. There is no need to patch this.

From my point of view, there are other stuff that needs to updated too.
So let me list here.

First of all the --offset option, like --limit I think it should appear
--offset=OFFSET, not --offset=0

Then I think --path and --service descriptions are wrong too. By now
running `tracker-xxx --help` they appears like

        -p, --path    Path to use in query
        -s, --service Search from a specific service
        
But you can't use them without an argument, so should be at least
patched as follow:

         static GOptionEntry   entries[] = {
                { "path", 'p', 0, G_OPTION_ARG_STRING, &path,
                  N_("Path to use in query"),
        -         NULL,
        +         N_("PATH"),
                },
                { "service", 's', 0, G_OPTION_ARG_STRING, &service,
                  N_("Search from a specific service"),
        -         NULL
        +         N_("SERVICE")
        







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