[GRASS translations] Re: translations digest, Vol 1 #93 - 1 msg
neteler at itc.it
Thu Feb 2 08:41:52 EST 2006
On Thu, Feb 02, 2006 at 02:14:14PM +0100, Otto Dassau wrote:
> Am Donnerstag, 2. Februar 2006 14:06 schrieb Markus Neteler:
> > On Thu, Feb 02, 2006 at 12:36:15PM +0100, Otto Dassau wrote:
> > > Hi,
> > >
> > > > Message: 1
> > > > Date: Wed, 01 Feb 2006 22:33:36 +0100
> > > > From: "Laurent C." <lrntct at gmail.com>
> > > > To: Markus Neteler <neteler at itc.it>, translations at grass.itc.it
> > > > Subject: Re: [GRASS translations] GRASS translations to
> > > > Slovene/French/Spanish
> > > >
> > > > Hi,
> > > > I'm interested for such a glossary. I've read Eve's translation of
> > > > grass in a nutshell.
> > > > Some words haven't the same translation between grasslib, grassmod and
> > > > nutshell.
> > > >
> > > > I'm ok to use nutshell version (because this is the only complete
> > > > translation) in all the files if every translators agree.
> > >
> > > I agree, we should try to harmonize although it seems to be difficult.
> > > Since we currently work in two repositories cvs (grass.itc) and svn
> > > (GDF), we probably need to find a solution, to develope and keep a
> > > glossary uptodate and make it easy for everybody to contribute and change
> > > entries.
> > We could use the WIKI. It's very simple to make a table in
> > TWIKI. Later it could become something fancy (e.g. PostGRESQL with
> > pgpPGadmin)
> > > Best solution for translators would be to have one glossary file for all
> > > currently available languages included once in each repository, I guess.
> > > This is difficult to achive - I don't have a clue for that.
> > Why not a simple table as first approach?
> > english | french | german | spanish | ...
> > ---------+--------+--------+---------+----
> > location | .... | ...
> > ...
> > Maybe I am missing something.
> no, as a first step it is fine I guess :-). I just thought, people are lazy
> and don't want to get their nessesary translation stuff from different URLs
> or Repositories, but the wiki is great and easy to edit!
sure but for fetching the static version we could, instead of cloning
the glossary everywhere, simply add a "fetch_glossary.sh" script
which used wget to download the page from the WIKI.
> maybe a new page called translation_glossary here?:
> if all agree; i would start a table...
Let's go :-)
More information about the grass-translations