drupal - translation overview module

[Anne Ghisla-2]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

the Portal Translation Status is definitely hard to mantain (sic).
For translation status overview, there's a Drupal module [0] that nicely
does the job, and furthermore marks trasnlated page as outdated when the
original version is modified.
Is it possible to integrate with current translation module(s), and see
if it can substitute the coordination page on the wiki?

HTH,
Anne

[0] http://drupal.org/project/translation_overview
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpZ6u4ACgkQzZ3g4YwFFgYdbwCfbhdK+cb3TmFQKTmeapZGMSUm
NgIAmwRxOirnLTfvfUrHNWcB4syxgzuz
=h9YL
-----END PGP SIGNATURE-----
_______________________________________________
Webcom mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/webcom

[Wolf Bergenheim]

Hi Anne,

Unfortunately that module only works with Drupal 6.x, and we are still
running 5.x. I have planned an upgrade, and this module will be added
at that time. Thanks for pointing it out.

Dear Webcom,
The dreaded upgrade will take place sometime after SoC. I haven't gone
through the list of modules yet, but Drupal 6 has been out for over a
year now, so most modules should be out by now. I think we should do
the upgrade like we did it the last time. Freeze the main site, and
then work on a test site, and then transfer it over. Also there has
been a lot of fixes ind improvements in Drupal 6, so on that note
upgrading to 6 is also a good idea.

--Wolf

On Sun, Jul 12, 2009 at 16:53, Anne Ghisla<[hidden email]> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
>
> the Portal Translation Status is definitely hard to mantain (sic).
> For translation status overview, there's a Drupal module [0] that nicely
> does the job, and furthermore marks trasnlated page as outdated when the
> original version is modified.
> Is it possible to integrate with current translation module(s), and see
> if it can substitute the coordination page on the wiki?
>
> HTH,
> Anne
>
> [0] http://drupal.org/project/translation_overview
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkpZ6u4ACgkQzZ3g4YwFFgYdbwCfbhdK+cb3TmFQKTmeapZGMSUm
> NgIAmwRxOirnLTfvfUrHNWcB4syxgzuz
> =h9YL
> -----END PGP SIGNATURE-----
> _______________________________________________
> Webcom mailing list
> [hidden email]
> http://lists.osgeo.org/mailman/listinfo/webcom
>

--

<:3 )---- Wolf Bergenheim ----( 8:>
_______________________________________________
Webcom mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/webcom

[Tyler Mitchell (OSGeo)]

Anne Ghisla wrote:
> the Portal Translation Status is definitely hard to mantain (sic).
> For translation status overview, there's a Drupal module [0] that nicely
> does the job, and furthermore marks trasnlated page as outdated when the
> original version is modified.
> Is it possible to integrate with current translation module(s), and see
> if it can substitute the coordination page on the wiki?

Before we get to the v6 upgrade, I thought I'd mention that some
translators simply monitor the recent changes RSS feed from the website.
  Then I follow a simple method of labeling my changes to the site with
a language code prefix, eg.:  "en: adding more text" - then you can see
new pages, as well as modified changes to english content.

Hmm, but now that I look at it, I think the recent changes page may be
easier to use than the RSS feed.  The RSS feed shows a diff but the web
page shows a summary log comment:

The recent changes page:
http://www.osgeo.org/recent_changes

And the RSS feed:
http://www.osgeo.org/recent_changes/feed

Anyone doing anything different?

Tyler
_______________________________________________
Webcom mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/webcom

[Marie Silvestre]

I'm indeed using the "recent changes page" to keep an eye on... well... changes and having the "en:" prefix helps a lot, thanks for keeping doing that!
That's a shame I haven't done anything on the website since last year but right now I'm trying to update pages and resume translation of other non-translated pages.

I thought of something that could really help translators:a page showing all english nodes with the date of the last revision in every other languages.
Something like that :
node ; en ; fr ; it ; etc.
http://www.osgeo.org/content/faq/getting_started.html ; 2009-09-15 22:16 ; 2009-10-03 12:04 ; 2009-07-11 18:36 ; etc.
(it could have the time difference instead and no value for non translated nodes)

It will help spotting non translated pages and pages that really need an update.
Of course event and news nodes should be left aside because imho it would just be confusing and mess things up too much.


If it's a problem to have this kind of page online it could be queried every month or week and sent as a text file to this list.

I haven't yet analysed why I 've stopped working on translation on the website for a year but I think the clumsiness of the current system may be part of the explanation...

So it would really really really help!

Marie


----- Message d'origine ----
De : Tyler Mitchell (OSGeo) <[hidden email]>
À : Web committee discussions <[hidden email]>
Envoyé le : Mardi, 14 Juillet 2009, 18h32mn 05s
Objet : Re: [Webcom] drupal - translation overview module

Anne Ghisla wrote:
> the Portal Translation Status is definitely hard to mantain (sic).
> For translation status overview, there's a Drupal module [0] that nicely
> does the job, and furthermore marks trasnlated page as outdated when the
> original version is modified.
> Is it possible to integrate with current translation module(s), and see
> if it can substitute the coordination page on the wiki?

Before we get to the v6 upgrade, I thought I'd mention that some translators simply monitor the recent changes RSS feed from the website.  Then I follow a simple method of labeling my changes to the site with a language code prefix, eg.:  "en: adding more text" - then you can see new pages, as well as modified changes to english content.

Hmm, but now that I look at it, I think the recent changes page may be easier to use than the RSS feed.  The RSS feed shows a diff but the web page shows a summary log comment:

The recent changes page:
http://www.osgeo.org/recent_changes

And the RSS feed:
http://www.osgeo.org/recent_changes/feed

Anyone doing anything different?

Tyler
_______________________________________________
Webcom mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/webcom




_______________________________________________
Webcom mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/webcom