[SAC] Language issues on web site

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

Folks,
the translation in our current version of Drupal is not only confusing
but also seems to not work quite right.

Somebody translated the Charter Members [1] page to Greek (in general
a good idea) but instead of creating a "New Translation" overwrote the
English version. I reverted the edit and then tried to copy the Greek
version into the Greek node but Greek does not show up in the
translation tab?! But it does show up on the main languages list in
the left border.

TO see the results it also makes a difference if you are logged in or
not and what language settings are selected in the profile (if logged
in).

User interface and content language switch:
* When switching user interface language, switch also the content language
* Keep separated user interface and content language
* Use global options

Never quite got what these options are supposed to do either.

I have been struggling with all these "feature" since we have them and
never really got satisfying results. Probably I am too dumb to use
this correctly but if I am not significantly dumber than the rest of
the crew then statistically at least half of the potential
contributors will fail in the same way (after getting frustrated for
some time). This is inefficient. Ideas what we can do to change this?

Cheers,
Arnulf

[1] https://www.osgeo.org/charter_members

- --
Exploring Space, Time and Mind
http://arnulf.us
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEUEARECAAYFAk/YqI4ACgkQXmFKW+BJ1b1DoQCYqnhsqt4pL7VUBuvJq3lGfExh
VwCfYabkL0t8DYI21GhPdw3PG7JkjJk=
=vGR+
-----END PGP SIGNATURE-----

I ran into the same issue yesterday and figured out how to straighten
out the mess. Once the main page knows it's English again the Greek
option shows up in the Translation list.

In terms of long term solutions, the migration to a newer version of
Drupal is likely necessary before an solution other than training can be
done. Maybe a 30 second video showing the right way to start a
translation will help.

Thanks,
Alex

On 06/13/2012 07:49 AM, Seven (aka Arnulf) wrote:

Folks,
the translation in our current version of Drupal is not only confusing
but also seems to not work quite right.

Somebody translated the Charter Members [1] page to Greek (in general
a good idea) but instead of creating a "New Translation" overwrote the
English version. I reverted the edit and then tried to copy the Greek
version into the Greek node but Greek does not show up in the
translation tab?! But it does show up on the main languages list in
the left border.

TO see the results it also makes a difference if you are logged in or
not and what language settings are selected in the profile (if logged
in).

User interface and content language switch:
* When switching user interface language, switch also the content language
* Keep separated user interface and content language
* Use global options

Never quite got what these options are supposed to do either.

I have been struggling with all these "feature" since we have them and
never really got satisfying results. Probably I am too dumb to use
this correctly but if I am not significantly dumber than the rest of
the crew then statistically at least half of the potential
contributors will fail in the same way (after getting frustrated for
some time). This is inefficient. Ideas what we can do to change this?

Cheers,
Arnulf

[1] https://www.osgeo.org/charter_members

Fixed, by the way I emailed the translator of those Greek pages to make
sure he knew what was going on.

Here's some more info:
The translation list will not show the language you are currently
browsing in. So one must be in English browsing, go to the page they
want to translate, Select the Translate tab and then create translation
next to the correct language. When in the Edit box then they must select
the right language from the drop down too before saving.

In order to fix the current Greek pages, go to the page in English
browse. Edit, Select English in the drop down, sumbit. Go to the
Translation page, create Greek - it will copy the current page to start.
Now select Greek from the drop down and submit. Once done (you'll notice
it's different node number) go back to the English version and revert to
before the greek got added.

Thanks,
Alex

On 06/13/2012 09:00 AM, Alex Mandel wrote:

I ran into the same issue yesterday and figured out how to straighten
out the mess. Once the main page knows it's English again the Greek
option shows up in the Translation list.

In terms of long term solutions, the migration to a newer version of
Drupal is likely necessary before an solution other than training can be
done. Maybe a 30 second video showing the right way to start a
translation will help.

Thanks,
Alex

On 06/13/2012 07:49 AM, Seven (aka Arnulf) wrote:

Folks,
the translation in our current version of Drupal is not only confusing
but also seems to not work quite right.

Somebody translated the Charter Members [1] page to Greek (in general
a good idea) but instead of creating a "New Translation" overwrote the
English version. I reverted the edit and then tried to copy the Greek
version into the Greek node but Greek does not show up in the
translation tab?! But it does show up on the main languages list in
the left border.

TO see the results it also makes a difference if you are logged in or
not and what language settings are selected in the profile (if logged
in).

User interface and content language switch:
* When switching user interface language, switch also the content language
* Keep separated user interface and content language
* Use global options

Never quite got what these options are supposed to do either.

I have been struggling with all these "feature" since we have them and
never really got satisfying results. Probably I am too dumb to use
this correctly but if I am not significantly dumber than the rest of
the crew then statistically at least half of the potential
contributors will fail in the same way (after getting frustrated for
some time). This is inefficient. Ideas what we can do to change this?

Cheers,
Arnulf

[1] https://www.osgeo.org/charter_members

_______________________________________________
Sac mailing list
Sac@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/sac

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

On 13.06.2012 18:36, Alex Mandel wrote:

Here's some more info: The translation list will not show the
language you are currently browsing in. So one must be in English
browsing, go to the page they want to translate, Select the
Translate tab and then create translation next to the correct
language. When in the Edit box then they must select the right
language from the drop down too before saving.

In order to fix the current Greek pages, go to the page in English
browse. Edit, Select English in the drop down, sumbit. Go to the
Translation page, create Greek - it will copy the current page to
start. Now select Greek from the drop down and submit. Once done
(you'll notice it's different node number) go back to the English
version and revert to before the greek got added.

...OK, understood.

Another comment/question: If you are on a Drupal page which has a
translation (e.g. in Greek language mode for the charter page [1]) and
then switch to a language that does not have a translation (e.g.
German) then the last version will be displayed, in this case the
Greek version. Would it be possible (low priority) to default to the
English page regardless of the prior used language version?

Cheers,
Arnulf

[1] https://www.osgeo.org/charter_members

- --
Exploring Space, Time and Mind
http://arnulf.us
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk/ZrFQACgkQXmFKW+BJ1b3rCwCfSWimbYNBcmOp+2hnersuUKkO
/FUAn28qAyqAM9tdrDyiJvAI1IDy3dz0
=+KxB
-----END PGP SIGNATURE-----

On 06/14/2012 02:18 AM, Seven (aka Arnulf) wrote:

On 13.06.2012 18:36, Alex Mandel wrote:

Here's some more info: The translation list will not show the
language you are currently browsing in. So one must be in English
browsing, go to the page they want to translate, Select the
Translate tab and then create translation next to the correct
language. When in the Edit box then they must select the right
language from the drop down too before saving.

In order to fix the current Greek pages, go to the page in English
browse. Edit, Select English in the drop down, sumbit. Go to the
Translation page, create Greek - it will copy the current page to
start. Now select Greek from the drop down and submit. Once done
(you'll notice it's different node number) go back to the English
version and revert to before the greek got added.

...OK, understood.

Another comment/question: If you are on a Drupal page which has a
translation (e.g. in Greek language mode for the charter page [1]) and
then switch to a language that does not have a translation (e.g.
German) then the last version will be displayed, in this case the
Greek version. Would it be possible (low priority) to default to the
English page regardless of the prior used language version?

Cheers,
Arnulf

[1] https://www.osgeo.org/charter_members

I have absolutely no idea. I was under the impression when no language
was found it should default to English, or at least what it thought was
the English version. Will check the localizer module settings to see if
that's possible. Yet another thing that is handled better in newer
versions of Drupal.

I fixed 4 pages that had this issue yesterday.

Thanks,
Alex