v.to.db help messages missing po templates

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

v.to.db help messages missing po templates

Marco Curreli
Hi all,

I was searching the help messages of v.to.db module in pofiles, but
I can't find most of them in any pofile.

Also, I'm wondering why some strings of help messages come from
grasslibs, instead of grassmods.

Best regards,
        Marco

_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations
Reply | Threaded
Open this post in threaded view
|

Re: v.to.db help messages missing po templates

Markus Neteler
Hi Marco,

On Fri, Mar 9, 2012 at 7:20 PM, Marco Curreli <[hidden email]> wrote:
> Hi all,
>
> I was searching the help messages of v.to.db module in pofiles, but
> I can't find most of them in any pofile.

I get it partically translated:

v.to.db help

Descrizione:
 Popola i valori del database da features vettoriali

Parole chiave:
 vettoriale, database, tabella degli attributi

Uso:
 v.to.db [-psc] map=name [type=string[,string,...]] [layer=value]
   [qlayer=value] option=string [units=string]
[columns=name[,name,...]]
   [qcolumn=name] [--verbose] [--quiet]

Flags:
  -p   Stampa solo
  -s   Stampa solo le istruzioni SQL
  -c   In print mode prints totals for options: length,area,count
 --v   Output verboso del modulo
 --q   Output quieto del modulo

Parametri:
      map   Nome del vettoriale in input
     type   Tipo di elemento
             Per coor sono validi point/centroid, per length sono
validi line/boundary
            opzioni: point,line,boundary,centroid
            predefinito: point,line,boundary,centroid
    layer   Numero del layer (su cui scrivere)
             Un singolo vettoriale pu� essere connessa a database
multiple. Questo numero determina quale tabella viene usata.
            predefinito: 1
   qlayer   Numero del layer da interrogare (da cui leggere)
             Un singolo vettoriale pu� essere connessa a database
multiple. Questo numero determina quale tabella viene usata.
            predefinito: 1
   option   Valore da aggiornare
            opzioni: cat,area,compact,fd,perimeter,length,count,coor,start,
                     end,sides,query,slope,sinuous,azimuth
             cat: insert new row for each category if doesn't exist yet
             area: area size
             compact: compactness of an area, calculated as
              compactness = perimeter / (2 * sqrt(PI * area))
             fd: fractal dimension of boundary defining a polygon,
calculated as
              fd = 2 * (log(perimeter) / log(area))
             perimeter: perimeter length of an area
             length: line length
             count: number of features for each category
             coor: point coordinates, X,Y or X,Y,Z
             start: line/boundary starting point coordinates, X,Y or X,Y,Z
             end: line/boundary end point coordinates, X,Y or X,Y,Z
             sides: categories of areas on the left and right side of
the boundary, 'qlayer' is used for area category
             query: result of a database query for all records of the
geometry(or geometries) from table specified by 'qlayer' option
             slope: slope steepness of vector line or boundary
             sinuous: line sinuousity, calculated as line length /
distance between end points
             azimuth: line azimuth, calculated as angle between North
direction and endnode direction at startnode
    units   Unit�
             mi(les),f(eet),me(ters),k(ilometers),a(cres),h(ectares),r(adians),d(egrees)
(miglia, piedi, metri, chilometri, acri, ettari, radianti, gradi)
            opzioni: mi,miles,f,feet,me,meters,k,kilometers,a,acres,h,
                     hectares,r,radians,d,degrees
  columns   Nome della colonna(e) dell'attributo
  qcolumn   Nome colonna degli attributi da usare per l'opzione 'query'
             E.g. 'cat', 'count(*)', 'sum(val)'

I realize that the large block explaining the options in not tagged
for translation in
vector/v.to.db/parse.c

I wonder why... it should! ( @Devs: why not? )

Markus
_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations
Reply | Threaded
Open this post in threaded view
|

Re: v.to.db help messages missing po templates

Marco Curreli
On 17:55 Sat 10 Mar     , Markus Neteler wrote:
> I realize that the large block explaining the options in not tagged
> for translation in
> vector/v.to.db/parse.c
>
Thanks.

In parse.c, are the strings tagget for translation those in round
brackets?

regards,
Marco

_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations
Reply | Threaded
Open this post in threaded view
|

Re: v.to.db help messages missing po templates

Markus Neteler
On Sat, Mar 10, 2012 at 10:28 PM, Marco Curreli <[hidden email]> wrote:
> On 17:55 Sat 10 Mar     , Markus Neteler wrote:
>> I realize that the large block explaining the options in not tagged
>> for translation in
>> vector/v.to.db/parse.c
>>
> Thanks.
>
> In parse.c, are the strings tagget for translation those in round
> brackets?

Yes. For some technical details, see
http://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/locale/README

Note that also v.to.rast (and maybe others) are affected.

Best
Markus
_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations
Reply | Threaded
Open this post in threaded view
|

Re: v.to.db help messages missing po templates

Marco Curreli
On 10:20 Sun 11 Mar     , Markus Neteler wrote:
>
> Yes. For some technical details, see
> http://svn.osgeo.org/grass/grass/branches/releasebranch_6_4/locale/README
>
thanks

_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations