What's a project in GRASS?

[Roberto Antolin]

Hi all,
In the spanish translation group we have an interesting debate about the
definition of project in GRASS. So I've decided to post it here.

The first time I translated 'location' into spanish, I used 'proyecto'
(that is, project), since in a single location are defined the
coordinates type, the region bounds and resolution, the projection
information and the datum, and also because the location folders contain
mapsets (users, subregions, etc...).

Another translator thinks that 'location' may be translated as
'ubicacion' (that is, place), and he also considers that projects in
GRASS are the mapsets into a location.

May be, we are both wrong, and a project in grass is 'workspace'. An
italian user gave me this possibility. But there is still another
possibility: no translating terms like 'location' or 'mapset'.

At this point, I'm totally confused about it. So, what do you think?

Regards,
Roberto.

--
Roberto Antolín Sánchez
Politecnico di Milano – Polo Regionale di Como
(Laboratorio di Geomatica V2.8)
Via Valleggio, 11 – 22100 Como, Italy
tel: [phone] || fax: [phone]
email: [hidden email]

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Otto Dassau]

Hi,

I think a location is more than a 'ubicacion' and definitely not a workspace.
Workspace in GRASS is used to save definitions about the current status of a
GRASS session in a .grc, .dm or .dmrc file.

German translations often keep the name location or use sth. like:

- Project location (currently official in the startup gui)
- Project environment
- or simply call it a Project

Mapset usually is translated as Mapset, I think

hope this helps

  Otto
 

On Wed, 17 Jan 2007 12:58:25 +0100
Roberto Antolin <[hidden email]> wrote:

> Hi all,
> In the spanish translation group we have an interesting debate about the
> definition of project in GRASS. So I've decided to post it here.
>
> The first time I translated 'location' into spanish, I used 'proyecto'
> (that is, project), since in a single location are defined the
> coordinates type, the region bounds and resolution, the projection
> information and the datum, and also because the location folders contain
> mapsets (users, subregions, etc...).
>
> Another translator thinks that 'location' may be translated as
> 'ubicacion' (that is, place), and he also considers that projects in
> GRASS are the mapsets into a location.
>
> May be, we are both wrong, and a project in grass is 'workspace'. An
> italian user gave me this possibility. But there is still another
> possibility: no translating terms like 'location' or 'mapset'.
>
> At this point, I'm totally confused about it. So, what do you think?
>
> Regards,
> Roberto.
>

--

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Roberto Antolin]

Otto Dassau ha scritto:

>Hi,
>
>I think a location is more than a 'ubicacion' and definitely not a workspace.
>Workspace in GRASS is used to save definitions about the current status of a
>GRASS session in a .grc, .dm or .dmrc file.
>  
>
That's why I didn't use 'ubicacion' for 'location'.
I'm sorry if I did some confusion with terminology. I didn't want to say
that a location is a 'workspace', but that a 'workspace' is a kind of
project.

>German translations often keep the name location or use sth. like:
>
>- Project location (currently official in the startup gui)
>- Project environment
>- or simply call it a Project
>
>Mapset usually is translated as Mapset, I think
>  
>
The same as I did. In fact, I translated location as 'proyecto' and keep
the term 'mapset' with quotation marks to remark that it is not a
spanish term.

>hope this helps
>
>  Otto
>
You helped me a lot (thank you!), but I don't know if you did so with
the other spanish translators :)

Any other suggestions?

Thanks,
Roberto.


--
Roberto Antolín Sánchez
Politecnico di Milano – Polo Regionale di Como
(Laboratorio di Geomatica V2.8)
Via Valleggio, 11 – 22100 Como, Italy
tel: [phone] || fax: [phone]
email: [hidden email]

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Eve Rousseau]

Hi,
If you're not sure (or can't agree) on what the adequate Spanish word should be,
keeping the English terms might be the best option... But, doesn't Spanish
usually integrate words directly or just changes the original spelling to match
Spanish pronunciation..?
Otherwise, just in case it might help, French translators agreed on "Secteur"
for "Location" (maybe "Sector" or "Sector de proyecto" could be convenient), and
"Jeu de données" for "Mapset (literaly "juego de datos" or maybe something close
to "surtido" or "surtido de mapas")...
Hope this helps,
Eve

> Otto Dassau ha scritto:
>
> >Hi,
> >
> >I think a location is more than a 'ubicacion' and definitely not a workspace.
> >Workspace in GRASS is used to save definitions about the current status of a
> >GRASS session in a .grc, .dm or .dmrc file.
> >  
> >
> That's why I didn't use 'ubicacion' for 'location'.
> I'm sorry if I did some confusion with terminology. I didn't want to say
> that a location is a 'workspace', but that a 'workspace' is a kind of
> project.
>
> >German translations often keep the name location or use sth. like:
> >
> >- Project location (currently official in the startup gui)
> >- Project environment
> >- or simply call it a Project
> >
> >Mapset usually is translated as Mapset, I think
> >  
> >
> The same as I did. In fact, I translated location as 'proyecto' and keep
> the term 'mapset' with quotation marks to remark that it is not a
> spanish term.
>
> >hope this helps
> >
> >  Otto
> >
> You helped me a lot (thank you!), but I don't know if you did so with
> the other spanish translators :)
>
> Any other suggestions?
>
> Thanks,
> Roberto.
>
>
> --
> Roberto Antolín Sánchez
> Politecnico di Milano – Polo Regionale di Como
> (Laboratorio di Geomatica V2.8)
> Via Valleggio, 11 – 22100 Como, Italy
> tel: [phone] || fax: [phone]
> email: [hidden email]
>
> _______________________________________________
> translations mailing list
> [hidden email]
> http://grass.itc.it/mailman/listinfo/translations
>

        --------------------------------
        Interface WebMail / Magic OnLine
              http://www.magic.fr


_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Daniel Calvelo]

Is "zona" already used? I'd search among words describing a piece of
space such as "sector", "ubicación", "localización" (awful),
"zona",... "área", "perímetro" and other geometrical terms will
probably be misconstrued or ambiguous.

HTH, DCA

On 1/17/07, Eve Rousseau <[hidden email]> wrote:

> Hi,
> If you're not sure (or can't agree) on what the adequate Spanish word should be,
> keeping the English terms might be the best option... But, doesn't Spanish
> usually integrate words directly or just changes the original spelling to match
> Spanish pronunciation..?
> Otherwise, just in case it might help, French translators agreed on "Secteur"
> for "Location" (maybe "Sector" or "Sector de proyecto" could be convenient), and
> "Jeu de données" for "Mapset (literaly "juego de datos" or maybe something close
> to "surtido" or "surtido de mapas")...
> Hope this helps,
> Eve
>
> > Otto Dassau ha scritto:
> >
> > >Hi,
> > >
> > >I think a location is more than a 'ubicacion' and definitely not a workspace.
> > >Workspace in GRASS is used to save definitions about the current status of a
> > >GRASS session in a .grc, .dm or .dmrc file.
> > >
> > >
> > That's why I didn't use 'ubicacion' for 'location'.
> > I'm sorry if I did some confusion with terminology. I didn't want to say
> > that a location is a 'workspace', but that a 'workspace' is a kind of
> > project.
> >
> > >German translations often keep the name location or use sth. like:
> > >
> > >- Project location (currently official in the startup gui)
> > >- Project environment
> > >- or simply call it a Project
> > >
> > >Mapset usually is translated as Mapset, I think
> > >
> > >
> > The same as I did. In fact, I translated location as 'proyecto' and keep
> > the term 'mapset' with quotation marks to remark that it is not a
> > spanish term.
> >
> > >hope this helps
> > >
> > >  Otto
> > >
> > You helped me a lot (thank you!), but I don't know if you did so with
> > the other spanish translators :)
> >
> > Any other suggestions?
> >
> > Thanks,
> > Roberto.
> >
> >
> > --
> > Roberto Antolín Sánchez
> > Politecnico di Milano – Polo Regionale di Como
> > (Laboratorio di Geomatica V2.8)
> > Via Valleggio, 11 – 22100 Como, Italy
> > tel: [phone] || fax: [phone]
> > email: [hidden email]
> >
> > _______________________________________________
> > translations mailing list
> > [hidden email]
> > http://grass.itc.it/mailman/listinfo/translations
> >
>
>
>
>
>
>         --------------------------------
>         Interface WebMail / Magic OnLine
>               http://www.magic.fr
>
>
> _______________________________________________
> translations mailing list
> [hidden email]
> http://grass.itc.it/mailman/listinfo/translations
>

--
-- Daniel Calvelo Aros

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Roberto Antolin]

Eve Rousseau ha scritto:

>Hi,
>If you're not sure (or can't agree) on what the adequate Spanish word should be,
>keeping the English terms might be the best option... But, doesn't Spanish
>usually integrate words directly or just changes the original spelling to match
>Spanish pronunciation..?
>  
>
Yes, we commonly adapt some terms into spanish but it is slang, not
official. For example:
- To click (the button); Slang: "Clicar" (el boton); The correct form:
Pulsar (el boton).

Only after some years and after that everybody uses these kind of terms,
the RAE (Spanish Royal Academy) accept them.

>Otherwise, just in case it might help, French translators agreed on "Secteur"
>for "Location" (maybe "Sector" or "Sector de proyecto" could be convenient), and
>"Jeu de données" for "Mapset (literaly "juego de datos" or maybe something close
>to "surtido" or "surtido de mapas")...
>Hope this helps,
>Eve
>  
>
Thank you, Eve! I appreciate your help and you give me some idea to
translate 'mapset'. Maybe not 'surtido' because in spanish it seems that
you have to choose between maps, but something like that would be ok.

Talking about keeping the english terms, I wouldn't like to do it. But
thinking about it, maybe it is the best solution. I mean, if I've
developed a software gis called GRASS, do I rename it into HIERBA in the
spanish translation (or ERBA into italian)? Surely not. So, if I have
two 'key' folders in the GRASS architecture called 'Location' and
'mapset', should I try to translate them? I don't know. What do you think?

Regards,
Roberto.

--
Roberto Antolín Sánchez
Politecnico di Milano – Polo Regionale di Como
(Laboratorio di Geomatica V2.8)
Via Valleggio, 11 – 22100 Como, Italy
tel: [phone] || fax: [phone]
email: [hidden email]

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Roberto Antolin]

Daniel Calvelo ha scritto:

> Is "zona" already used? I'd search among words describing a piece of
> space such as "sector", "ubicación", "localización" (awful),
> "zona",... "área", "perímetro" and other geometrical terms will
> probably be misconstrued or ambiguous.


What do you mean with "already use"? Of course it is used, but not for
the translation of a GRASS object, I think. And why is "localización" so
awful? I don't like it either, but it is no awful. I prefer it instead
of "ubicación", for example.

Roberto.

--
Roberto Antolín Sánchez
Politecnico di Milano – Polo Regionale di Como
(Laboratorio di Geomatica V2.8)
Via Valleggio, 11 – 22100 Como, Italy
tel: [phone] || fax: [phone]
email: [hidden email]

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Eve Rousseau]

Hi,

What Daniel Calvelo meant with 'already in use' must be about the words you've
chosen to translate concepts like 'region' or 'areas'(as geometric objects)...
Maybe you could update the glossary here to make the other Spanish translators
aware of your choices?
http://grass.gdf-hannover.de/wiki/GRASS_Translation_Glossary
 
> Talking about keeping the english terms, I wouldn't like to do it. But
> thinking about it, maybe it is the best solution. I mean, if I've
> developed a software gis called GRASS, do I rename it into HIERBA in the
> spanish translation (or ERBA into italian)? Surely not. So, if I have
> two 'key' folders in the GRASS architecture called 'Location' and
> 'mapset', should I try to translate them? I don't know. What do you think?

Keeping English is fine because anyway when we come down to the name of
environment variables, we stick with English - but there's always some
peculiarities... In French for instance, we can't use 'Location' because it has
a totally different meaning and it would be a bit confusing. There's always the
"Frenglish" word 'localisation' but it's awful too (and non-sensical).
It's up to Spanish native speakers to tell which Spanish word could be the more
intuitive for this concept, and does it really matters if it ends up to be an
English word..? I really don't know, maybe native Spanish speakers like Daniel
should know better than I...
Atentamente,
Eve


        --------------------------------
        Interface WebMail / Magic OnLine
              http://www.magic.fr


_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Glynn Clements]

Roberto Antolin wrote:

> In the spanish translation group we have an interesting debate about the
> definition of project in GRASS. So I've decided to post it here.
>
> The first time I translated 'location' into spanish, I used 'proyecto'
> (that is, project), since in a single location are defined the
> coordinates type, the region bounds and resolution, the projection
> information and the datum, and also because the location folders contain
> mapsets (users, subregions, etc...).
>
> Another translator thinks that 'location' may be translated as
> 'ubicacion' (that is, place), and he also considers that projects in
> GRASS are the mapsets into a location.
>
> May be, we are both wrong, and a project in grass is 'workspace'. An
> italian user gave me this possibility. But there is still another
> possibility: no translating terms like 'location' or 'mapset'.
>
> At this point, I'm totally confused about it. So, what do you think?

AFAICT, GRASS doesn't use the term "project".

The term "location" (in the sense of database,location,mapset) refers
to a geographical location, i.e. a "place" on the earth's surface.

Google's translator gives "localización". Is that appropriate? It
sounds like the English localisation, which means something different
("localise" (verb) = assign to a location, "localisation" (noun) = the
process of doing so).

--
Glynn Clements <[hidden email]>

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Roberto Antolin]

On Wed, 17 Jan 2007, Eve Rousseau wrote:

> Hi,
>
> What Daniel Calvelo meant with 'already in use' must be about the words you've
> chosen to translate concepts like 'region' or 'areas'(as geometric objects)...
> Maybe you could update the glossary here to make the other Spanish translators
> aware of your choices?
> http://grass.gdf-hannover.de/wiki/GRASS_Translation_Glossary
>
Yes, I translated part of that glossary and I say to news translators to
have a look to it first.

> Keeping English is fine because anyway when we come down to the name of
> environment variables, we stick with English - but there's always some
> peculiarities... In French for instance, we can't use 'Location' because it has
> a totally different meaning and it would be a bit confusing. There's always the
> "Frenglish" word 'localisation' but it's awful too (and non-sensical).

In spanish, 'localizacion' is no so bad because it has a sense of place.
In fact, it's commonly use as a sinonim of village.

I'm begining to think that translating some kind of GRASS terms is no so
bad. It avoid some problems :)

> It's up to Spanish native speakers to tell which Spanish word could be the more
> intuitive for this concept, and does it really matters if it ends up to be an
> English word..? I really don't know, maybe native Spanish speakers like Daniel
> should know better than I...

Daniel, are you a spanish speaker? Would you like to join us? ;)

Eve, you are totally right, we should know which is the best word in
every case. The problem is that we don't agree in the word nor in the
concept. And I see that GRASS community doesn't agree in the concept. So,
I do the next question:

For you and considering the whole concept of 'location' in GRASS, is it
closer to 'project' or to 'place'?

German people have translated it just as 'Project' or 'Location Project'
as Otto said. French people have translated as 'Secteur' that is, closer
to place. We, spaniards, don't know, although I strongly prefer the concept
of project. The "rest of the world"?

While I wrote this message, I was looking for something and I found it. I
want to show to everybody (also to myself) how wiki defines the concepts
of 'location' an 'mapset' :)
http://grass.gdf-hannover.de/wiki/Gis_Concepts#How_a_GRASS_project_is_organized

> Atentamente,
> Eve

Saludos,
Roberto.

>
>
> --------------------------------
> Interface WebMail / Magic OnLine
>      http://www.magic.fr
>
>

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Roberto Antolin]

> I'm begining to think that translating some kind of GRASS terms is no so bad.
> It avoid some problems :)
>
Sorry, I wanted to say that keeping some english terms is no so bad :P

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Glynn Clements]

dottorando wrote:

> For you and considering the whole concept of 'location' in GRASS, is it
> closer to 'project' or to 'place'?

Place.

> German people have translated it just as 'Project' or 'Location Project'
> as Otto said.

"Project" amounts to a change in terminology, not a translation.

While you could argue that a "location" corresponds to a "project", if
we had wanted to use the term "project", we would have done.

> French people have translated as 'Secteur' that is, closer
> to place. We, spaniards, don't know, although I strongly prefer the concept
> of project. The "rest of the world"?

It depends upon whether you feel that a translation should simply be a
translation, or whether it's appropriate to change any English terms
which you disagree with, then translate the changed terms.

> While I wrote this message, I was looking for something and I found it. I
> want to show to everybody (also to myself) how wiki defines the concepts
> of 'location' an 'mapset' :)
> http://grass.gdf-hannover.de/wiki/Gis_Concepts#How_a_GRASS_project_is_organized

Regarding the sentence:

        A location is a GRASS project consisting of an area,
        projection definition (or unprojected), a grouping of mapsets,
        all with the same projection settings. A location is a
        subdirectory of the GRASS database.

I wouldn't have used the term "project" here, but simply written:

        A location consists of an area, projection definition (or
        unprojected), a grouping of mapsets, all with the same
        projection settings. A location is a subdirectory of the GRASS
        database.

A user could just as easily have a separate database directory for
each project. In fact, if a project is likely to consist of data in
multiple projections, it would probably better to have a separate
database directory for the project.

The only significant difference between having two locations in the
same database or in separate databases is that there are a small
number of commands (e.g. r.proj, v.proj, i.rectify) which can access
data from a different location directory within the same database
directory, but commands never access data from outside the current
database directory.

IOW, although any given project usually involves data from a single
location, it can use data from more than one location. In that sense,
it isn't accurate to consider a project as equivalent to a location.
OTOH, if you rarely use data from outside the current location
directory, it's common to have a single database directory containing
all of your location directories, so it isn't accurate to consider a
project as equivalent to a database directory either.

In summary, GRASS itself has no notion of a project, it's purely a
matter of the user's perception.

--
Glynn Clements <[hidden email]>

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Otto Dassau]

Hi,

On Thu, 18 Jan 2007 19:43:56 +0000
Glynn Clements <[hidden email]> wrote:

>
> dottorando wrote:
>
> > For you and considering the whole concept of 'location' in GRASS, is it
> > closer to 'project' or to 'place'?
>
> Place.
>
> > German people have translated it just as 'Project' or 'Location Project'
> > as Otto said.
>
> "Project" amounts to a change in terminology, not a translation.
>
> While you could argue that a "location" corresponds to a "project", if
> we had wanted to use the term "project", we would have done.
>
> > French people have translated as 'Secteur' that is, closer
> > to place. We, spaniards, don't know, although I strongly prefer the concept
> > of project. The "rest of the world"?
>
> It depends upon whether you feel that a translation should simply be a
> translation, or whether it's appropriate to change any English terms
> which you disagree with, then translate the changed terms.

>From my point of view "location" and "mapset" are proper names for sth.
(area, projection definition,group of mapsets etc.) as Glynn described below.
That's maybe the problem and makes it impossible to simply translate it.

Maybe a solution would be to keep the english terms (location and mapset)
as proper names and add a paragraph in documents, where you try to define
exactly in your language what a location and a mapset is. This could be
translated then.
 
BTW: It might be useful to find an agreement on how to use
location and mapset in documents, thinking that almost every tutorial and its
translation try to describe locations and mapsets in a different way again.

just another idea... :-)

regards,
 Otto

> > While I wrote this message, I was looking for something and I found it. I
> > want to show to everybody (also to myself) how wiki defines the concepts
> > of 'location' an 'mapset' :)
> >
http://grass.gdf-hannover.de/wiki/Gis_Concepts#How_a_GRASS_project_is_organized

>
> Regarding the sentence:
>
> A location is a GRASS project consisting of an area,
> projection definition (or unprojected), a grouping of mapsets,
> all with the same projection settings. A location is a
> subdirectory of the GRASS database.
>
> I wouldn't have used the term "project" here, but simply written:
>
> A location consists of an area, projection definition (or
> unprojected), a grouping of mapsets, all with the same
> projection settings. A location is a subdirectory of the GRASS
> database.
>
> A user could just as easily have a separate database directory for
> each project. In fact, if a project is likely to consist of data in
> multiple projections, it would probably better to have a separate
> database directory for the project.
>
> The only significant difference between having two locations in the
> same database or in separate databases is that there are a small
> number of commands (e.g. r.proj, v.proj, i.rectify) which can access
> data from a different location directory within the same database
> directory, but commands never access data from outside the current
> database directory.
>
> IOW, although any given project usually involves data from a single
> location, it can use data from more than one location. In that sense,
> it isn't accurate to consider a project as equivalent to a location.
> OTOH, if you rarely use data from outside the current location
> directory, it's common to have a single database directory containing
> all of your location directories, so it isn't accurate to consider a
> project as equivalent to a database directory either.
>
> In summary, GRASS itself has no notion of a project, it's purely a
> matter of the user's perception.
>

--


_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Roberto Antolin]

Hi all,

>While you could argue that a "location" corresponds to a "project", if
>we had wanted to use the term "project", we would have done.
>  
>
That's a very good argument :)

>It depends upon whether you feel that a translation should simply be a
>translation, or whether it's appropriate to change any English terms
>which you disagree with, then translate the changed terms.
>  
>
If the aim is only translation, a 'word by word' translation should be
ok. The fact is that we don't want to do just a translation but also an
interpretation ot the terms. This is very important for the spanish
speakers community since a lot of them don't understand english. And
interpretation is also important because there aren't any exactly
spanish words for some kind of terms.

On the other hand, I don't disagree with the english term of 'location',
I disagree with the literaly translation into spanish of it.

>In summary, GRASS itself has no notion of a project, it's purely a
>matter of the user's perception.
>  
>
Yes, I realized of that. As I said, for me a 'location' is a project,
for other spanish translators 'mapset' could be considered as projects.
Anyway, thank you very much for you comments, Glynn.

About keeping the english terms, it could be a good idea since these
problems would disappear. Also because 'location' and 'mapset' could be
considered as proper nouns (like Roberto, Peter or GRASS) But, spanish
is a very 'strong' language and the community ask for spanish terms. It
isn't nice to keep not spanish words, although it happens sometimes :)

Cheers,
Roberto.

--
Roberto Antolín Sánchez
Politecnico di Milano – Polo Regionale di Como
(Laboratorio di Geomatica V2.8)
Via Valleggio, 11 – 22100 Como, Italy
tel: [phone] || fax: [phone]
email: [hidden email]

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Roberto Antolin]

Hi everybody again,

>From my point of view "location" and "mapset" are proper names for sth.
>(area, projection definition,group of mapsets etc.) as Glynn described below.
>That's maybe the problem and makes it impossible to simply translate it.
>  
>
I just talk about it in my last post :)

>Maybe a solution would be to keep the english terms (location and mapset)
>as proper names and add a paragraph in documents, where you try to define
>exactly in your language what a location and a mapset is. This could be
>translated then.
>  
>
This could be a solution, yes.

>
>BTW: It might be useful to find an agreement on how to use
>location and mapset in documents, thinking that almost every tutorial and its
>translation try to describe locations and mapsets in a different way again.
>
>just another idea... :-)
>  
>
Exactly! That's why I asked for the closer "definition" of 'location'. I
think this should be standardized.

>regards,
> Otto
>
Roberto.


--
Roberto Antolín Sánchez
Politecnico di Milano – Polo Regionale di Como
(Laboratorio di Geomatica V2.8)
Via Valleggio, 11 – 22100 Como, Italy
tel: [phone] || fax: [phone]
email: [hidden email]

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Markus Neteler-3]

On Fri, Jan 19, 2007 at 11:30:47AM +0100, Roberto Antolin wrote:
...
> Exactly! That's why I asked for the closer "definition" of 'location'. I
> think this should be standardized.

Please use this as material
http://grass.itc.it/grass63/manuals/html63_user/helptext.html
and update it there. The manual should be the "gold standard".

ciao
Markus

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations

[Daniel Calvelo]

On 1/17/07, dottorando <[hidden email]> wrote:
>
> On Wed, 17 Jan 2007, Eve Rousseau wrote:
>
> > Hi,
> >
> > What Daniel Calvelo meant with 'already in use' must be about the words you've
> > chosen to translate concepts like 'region' or 'areas'(as geometric objects)...

Merci Eve, that's what I meant. Sorry for being unclear.

> In spanish, 'localizacion' is no so bad because it has a sense of place.
> In fact, it's commonly use as a sinonim of village.

In Spain? We use 'lugar' here in Peru, which could be a nice translation too.

> I'm begining to think that translating some kind of GRASS terms is no so
> bad. It avoid some problems :)

Indeed, we did not translate very technical terms such as "buffer"
("zona de amortiguamiento" actually), "plug-in", "raster". Very often
the spanish equivalents are not nouns but phrases.

> > It's up to Spanish native speakers to tell which Spanish word could be the more
> > intuitive for this concept, and does it really matters if it ends up to be an
> > English word..? I really don't know, maybe native Spanish speakers like Daniel
> > should know better than I...

Eve is right. In common use most technical english terms are roughly
spanicized or used as spanishly pronounced english. In writing
however, we have very often a hard time because the correct
translations are usually awkward (longer, scarcely single words) and
mixed with the spoken english terms.

> Daniel, are you a spanish speaker? Would you like to join us? ;)

I have :) Couldn't help much lately, though. In the versions I
translated, two or three terms were candidates for plain english
(unquoted in my case): raster, buffer and mapset are those I can think
of now.

[...]
> For you and considering the whole concept of 'location' in GRASS, is it
> closer to 'project' or to 'place'?

Place, definitely. At least it is intended to behave like one. But
since in geography, projects often are about a given location, there
is some ambiguity.

[snip]

Auguri,

Daniel.

--
-- Daniel Calvelo Aros

_______________________________________________
translations mailing list
[hidden email]
http://grass.itc.it/mailman/listinfo/translations