Using language name instead of national flags to provide language options

[kbraak]

Given the fact that the nationality doesn't necessarily reflect the language of choice
of our users, for example, Spanish user may want to use English for the interface,
or Costa Rican may need to pick Spanish flag for Spanish, I suggest we use language
name for options instead of flags.

Original issue reported on code.google.com by burkeker.gbif on 2011-07-05 14:47:10

[kbraak]

In my opinion, I would like to continue using the flag icons to select the idiom. In
fact, the icons allow an intuitive handling for the ipt.

From my side, every time I see an option with a Spain flag I understand that is something
related to Spanish language; I think it because in many places uses that standard.

Original issue reported on code.google.com by htobon on 2011-07-06 20:04:14

[kbraak]

We have to think long term, when we add traditional Chinese there's no 1 country flag
that would work. Where some languages are spoken in multiple countries, it isn't always
apparent which country is directly associated with the language. 

Ideal, is something like seen here: http://www.google.com/analytics/

The name of the language is written in that language so that people looking for it
can quickly identify it.

When other high priority issues are finished, and the translation of French and Spanish
is complete, I'd suggest we make this small UI change.

Original issue reported on code.google.com by kyle.braak on 2011-08-02 12:16:04

• Labels added: Component-UI

[kbraak]

(No text was entered with this change)

Original issue reported on code.google.com by htobon on 2011-08-02 12:49:46

[kbraak]

I agree: language names are better than flags + provide name of language in that language.

A dropdown list like http://www.google.com/analytics/ is the most flexible option,
as it allows to add languages without affecting the UI. But most IPT installations
will only have one or two languages, for which a simple link approach (like http://www.canadensys.net/)
is the most intuitive.

I think a happy medium would be to implement the dropdown, but also provide a language
variable in the ftl (e.g. "?lang=en) pages, so admins can customize the language selection
as they want. This is currently more or less the case in menu.ftl:

<a href="?request_locale=${lang}">

The problem with this simple approach is the "?": how is this going to behave for a
url which already has variables, like http://data.canadensys.net/ipt/resource.do?r=vascan.
To be correct, the language should be added with "&".

Original issue reported on code.google.com by peter.desmet.cubc on 2011-08-11 14:36:38

[kbraak]

See also issue 754

Original issue reported on code.google.com by peter.desmet.cubc on 2011-08-11 14:39:49

[kbraak]

Thanks for your comment Peter. We need to ensure that we are properly constructing the
URL, with the ? being used for the first parameter, and the & used for each subsequent
parameter. This obviously applies to the lang (request_locale) parameter and I noticed
a bug, see Issue 756. When this is working properly, we can change it to lang as you
suggested in Issue 754. Thanks.

Original issue reported on code.google.com by kyle.braak on 2011-08-12 09:56:59

[kbraak]

(No text was entered with this change)

Original issue reported on code.google.com by kyle.braak on 2011-11-04 10:09:43

[kbraak]

This issue is coming back as we are getting closer to getting IPT used in some new countries
without raising concerns on identity and nationality. We may want to assign this issue
a version to ensure it's in the pipeline.

Original issue reported on code.google.com by bko@gbif.org on 2013-04-16 08:42:42

[kbraak]

(No text was entered with this change)

Original issue reported on code.google.com by kyle.braak on 2013-04-22 14:07:50

• Labels added: Milestone-Release2.0.5, UserManual

[kbraak]

Change made in r4289 - see screenshots. Portuguese image missing, although we might
consider updating all images to have a different color. Tested in Safari, Firefox,
Chrome, and Opera. 

Original issue reported on code.google.com by kyle.braak on 2013-04-27 10:00:59

---

• Attachment: Screen Shot 2013-04-27 at 11.50.25 AM.png
  
• Attachment: Screen Shot 2013-04-27 at 11.38.38 AM.png
  
• Attachment: Screen Shot 2013-04-27 at 12.00.00 PM.png
  

[kbraak]

Thanks Daniel! I would like to suggest that we use "繁體中文" instead of just "中文" so it's
clear to users that it is Traditional Chinese in the current IPT.

Original issue reported on code.google.com by bko@gbif.org on 2013-04-29 13:57:55

[kbraak]

This issue was updated by revision r4305.

Original issue reported on code.google.com by kyle.braak on 2013-05-03 06:35:44

[kbraak]

This issue was updated by revision r4349.

Original issue reported on code.google.com by kyle.braak on 2013-05-14 10:01:15

[kbraak]

This issue was updated by revision r4350.

Original issue reported on code.google.com by kyle.braak on 2013-05-14 10:02:47

[kbraak]

This issue was updated by revision r4373.

Original issue reported on code.google.com by kyle.braak on 2013-05-14 16:35:42

[kbraak]

All languages now added, please see screenshot. 

Original issue reported on code.google.com by kyle.braak on 2013-05-14 16:40:39

---

• Attachment: Screen Shot 2013-05-14 at 6.40.25 PM.png
  

[kbraak]

This issue was updated by revision r4374.

Original issue reported on code.google.com by kyle.braak on 2013-05-14 16:46:16

[kbraak]

This issue was updated by revision r4380.

Original issue reported on code.google.com by kyle.braak on 2013-05-15 14:16:32

[kbraak]

Verified working. Fix will be included in 2.0.5 release. Changes to User Manual complete.

Original issue reported on code.google.com by kyle.braak on 2013-05-16 12:54:10