[GeoNetwork-devel] RE : Proposal / multilingual editing

GeoNetwork GeoNetwork Developer
1

+1 from me… PSC members on holidays.
Francois

Le 15 juil. 2009, 3:01 PM, “Francois Prunayre” <fx.prunayre@anonymised.com…> a écrit :

Dear PSC members,

Following last presentations in Bolsena, I would like to propose
multilingual metadata editing to GeoNetwork trunk (for 2.5 release) as
described here [1].
This include changes to the editor and view mode (including CSW).
Translated string will be indexed in the full text search criteria
(ie. any). Google translation service has been added to the editor to
suggest translation to the editors (and could be turned on/off).
Schematron rules check for duplicate or missing languages declaration.

More work could be done in the indexing mechanism but this is part of
a second proposal [2] which is not yet ready.

For those of you who would like to test/review:

  • the patch is available here [3] based on trunk.
  • or have a look to this screencast for a quick overview of this new
    feature [4].

Thanks swisstopo for support on this development made by Camptocamp
(Jesse & me) in the geocat.ch sandbox.
Thanks Pierre for details on multilingual ISO mechanism.

For developers, I suggest the following general (small) changes:

  • for translation in javascript, creation of a global translations
    table containing all JS required strings which could be then be called
    from any js file using a translate function (like t(key);). This was
    suggested by Patrick in the geocat.ch sandbox. Using this approach, we
    could then easily remove part of JS from XSL and have it in separate
    JS files.
  • added a config-gui.xml file in order to define global GUI
    parameters to be used in different places in XSL in order to change
    layout parameters. editor-google-translate has been added to turn
    on/off Google translation service for example.

Looking forward to your votes, cheers,

Francois

[1] http://trac.osgeo.org/geonetwork/wiki/MultilingualMetadata
[2] http://trac.osgeo.org/geonetwork/wiki/MultilingualIndexMechanism
[3] http://trac.osgeo.org/geonetwork/ticket/126
[4] http://trac.osgeo.org/geonetwork/attachment/wiki/MultilingualMetadata/geonetwork-multilingual-editing.swf?format=raw

2

Nice, +1.

Sorry for the delay, I really missed the original proposal mail.

   Ciao,
   Emanuele

Alle 00:26:18 di domenica 19 luglio 2009, Francois Prunayre ha scritto:

+1 from me... PSC members on holidays.
Francois

Le 15 juil. 2009, 3:01 PM, "Francois Prunayre" <fx.prunayre@anonymised.com> a
écrit :

Dear PSC members,

Following last presentations in Bolsena, I would like to propose
multilingual metadata editing to GeoNetwork trunk (for 2.5 release) as
described here [1].
This include changes to the editor and view mode (including CSW).
Translated string will be indexed in the full text search criteria
(ie. any). Google translation service has been added to the editor to
suggest translation to the editors (and could be turned on/off).
Schematron rules check for duplicate or missing languages declaration.

More work could be done in the indexing mechanism but this is part of
a second proposal [2] which is not yet ready.

For those of you who would like to test/review:
* the patch is available here [3] based on trunk.
* or have a look to this screencast for a quick overview of this new
feature [4].

Thanks swisstopo for support on this development made by Camptocamp
(Jesse & me) in the geocat.ch sandbox.
Thanks Pierre for details on multilingual ISO mechanism.

For developers, I suggest the following general (small) changes:
* for translation in javascript, creation of a global translations
table containing all JS required strings which could be then be called
from any js file using a translate function (like t(key);). This was
suggested by Patrick in the geocat.ch sandbox. Using this approach, we
could then easily remove part of JS from XSL and have it in separate
JS files.
* added a config-gui.xml file in order to define global GUI
parameters to be used in different places in XSL in order to change
layout parameters. editor-google-translate has been added to turn
on/off Google translation service for example.

Looking forward to your votes, cheers,

Francois

[1] http://trac.osgeo.org/geonetwork/wiki/MultilingualMetadata
[2] http://trac.osgeo.org/geonetwork/wiki/MultilingualIndexMechanism
[3] http://trac.osgeo.org/geonetwork/ticket/126
[4]
http://trac.osgeo.org/geonetwork/attachment/wiki/MultilingualMetadata/geone
twork-multilingual-editing.swf?format=raw

3

+1, nice work!

Mathieu

On Tue, Jul 21, 2009 at 2:28 AM, Emanuele Tajariol <e_tajariol@anonymised.com…> wrote:

Nice, +1.

Sorry for the delay, I really missed the original proposal mail.

Ciao,
Emanuele

Alle 00:26:18 di domenica 19 luglio 2009, Francois Prunayre ha scritto:

+1 from me… PSC members on holidays.
Francois

Le 15 juil. 2009, 3:01 PM, “Francois Prunayre” <fx.prunayre@anonymised.com> a
écrit :

Dear PSC members,

Following last presentations in Bolsena, I would like to propose
multilingual metadata editing to GeoNetwork trunk (for 2.5 release) as
described here [1].
This include changes to the editor and view mode (including CSW).
Translated string will be indexed in the full text search criteria
(ie. any). Google translation service has been added to the editor to
suggest translation to the editors (and could be turned on/off).
Schematron rules check for duplicate or missing languages declaration.

More work could be done in the indexing mechanism but this is part of
a second proposal [2] which is not yet ready.

For those of you who would like to test/review:

  • the patch is available here [3] based on trunk.
  • or have a look to this screencast for a quick overview of this new
    feature [4].

Thanks swisstopo for support on this development made by Camptocamp
(Jesse & me) in the geocat.ch sandbox.
Thanks Pierre for details on multilingual ISO mechanism.

For developers, I suggest the following general (small) changes:

  • for translation in javascript, creation of a global translations
    table containing all JS required strings which could be then be called
    from any js file using a translate function (like t(key);). This was
    suggested by Patrick in the geocat.ch sandbox. Using this approach, we
    could then easily remove part of JS from XSL and have it in separate
    JS files.
  • added a config-gui.xml file in order to define global GUI
    parameters to be used in different places in XSL in order to change
    layout parameters. editor-google-translate has been added to turn
    on/off Google translation service for example.

Looking forward to your votes, cheers,

Francois

[1] http://trac.osgeo.org/geonetwork/wiki/MultilingualMetadata
[2] http://trac.osgeo.org/geonetwork/wiki/MultilingualIndexMechanism
[3] http://trac.osgeo.org/geonetwork/ticket/126
[4]
http://trac.osgeo.org/geonetwork/attachment/wiki/MultilingualMetadata/geone
twork-multilingual-editing.swf?format=raw

Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World™ will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork