New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out multilanguage sites #898

Closed
patrickmj opened this Issue May 1, 2017 · 35 comments

Comments

Projects
None yet
8 participants
@patrickmj
Copy link
Member

patrickmj commented May 1, 2017

We have a way to tag language for values, but don't yet have a system for using them, other than the signal about what language a value has set. Seems like some way to 1) set a language, or languages to display and 2) filter based on that setting might be in order. Alternatively, people have suggested a way to have multiple sites that use different languages (which sounds like a site setting). Either of those approaches sound like having the theme be able to know what language(s) to display and filter values accordingly.

One feature we know people want is on-the-fly language switching, without being logged in and without changing browser setting. However, a system that can work with browser settings also makes sense for the filtering.

See convo on the forums https://forum.omeka.org/t/internationalized-omeka-s/3154

@patrickmj patrickmj self-assigned this May 1, 2017

@patrickmj patrickmj added the question label May 1, 2017

@zerocrates zerocrates modified the milestone: May 15 May 1, 2017

@elrossco22

This comment has been minimized.

Copy link

elrossco22 commented May 4, 2017

one to follow @stephenwf @euanfergusson

@patrickmj

This comment has been minimized.

Copy link
Member Author

patrickmj commented May 8, 2017

If I remember right from our conversation, it sounded like we'd look at the approach you need for your deadline and go from there?

@Daniel-KM

This comment has been minimized.

Copy link
Contributor

Daniel-KM commented May 8, 2017

An example of Omeka S project in multilanguage (French, English, Turkish), where the language code is the site: http://ifeaistanbul.net/omeka-s/.

@patrickmj

This comment has been minimized.

Copy link
Member Author

patrickmj commented May 8, 2017

@Daniel-KM Interesting. Is this items with metadata in the three languages, then the theme decides which to display? Or is it distinct items for each language?

@euanfergusson

This comment has been minimized.

Copy link
Contributor

euanfergusson commented May 8, 2017

looks like 3 omeka sites, where the site slug is also set to the language code?

@Daniel-KM

This comment has been minimized.

Copy link
Contributor

Daniel-KM commented May 8, 2017

They are the same items. Each metadata is translated in three languages and the user chooses the main language, that is related to the interface, then it displays only the good language for metadata.

@zerocrates

This comment has been minimized.

Copy link
Member

zerocrates commented May 8, 2017

One option I've been thinking about is to have a language setting in the site settings, which would go along well with a pattern of having a site-per-language type setup.

@euanfergusson

This comment has been minimized.

Copy link
Contributor

euanfergusson commented May 8, 2017

its an interesting approach and may work for some, but isnt multilingual , its multisite

@zerocrates

This comment has been minimized.

Copy link
Member

zerocrates commented May 8, 2017

Well I'd say it's a bit of both, but no need to quibble over the wording.

Having this (choosing language for a site in its settings) wouldn't preclude other ways of dealing with multilingual content (like separating values from different languages and allowing users to interactively select the content/UI language they want). Where "multisite" and "multilingual" start to cross over though, is in "site" content: static pages and so on. as those aren't stored in parallel or language-tagged like resource values are. That's where tying the default language support to a site starts to make a good deal of sense.

@patrickmj

This comment has been minimized.

Copy link
Member Author

patrickmj commented May 8, 2017

Yes, the two different approaches will appealing to different projects as different design choices. Both, though, need the theme work to figure out what to display, so that might be a common system to think through.

@euanfergusson

This comment has been minimized.

Copy link
Contributor

euanfergusson commented May 9, 2017

@zerocrates that could prove problematic re static pages, ideally we dont want to build multiple pages. Perhaps adding something to the pages db table (or other means to identify a page language) is the first step we need to take.

@patrickmj

This comment has been minimized.

Copy link
Member Author

patrickmj commented May 10, 2017

Interesting -- while we have the language tag for metadata values, it doesn't look like there's a good way to tag all of the aspects of display. That would go beyond site_pages down to site_page_blocks, and continue over to media attached to items (e.g., HTML media). That could lead into a pretty heavy lift.

@zerocrates zerocrates modified the milestones: May 15, May 30 May 15, 2017

@hajoki

This comment has been minimized.

Copy link

hajoki commented May 26, 2017

Hello, I confirm http://ifeaistanbul.net/omeka-s/ is a multisite approach.
How are things going about the general approach Omeka S want to adopt for multilingual sites?
Good luck everyone!

@euanfergusson

This comment has been minimized.

Copy link
Contributor

euanfergusson commented May 26, 2017

@hajoki , we have started developing a module for it. Not sure what is happening re this from Omeka's end.

@patrickmj

This comment has been minimized.

Copy link
Member Author

patrickmj commented May 26, 2017

Thanks @hajoki and @euanfergusson ! It's good to see what people building sites want and need, per the above discussion. Debates are continuing here at RRCHNM about what will be most helpful. Links to code -- both themes and modules -- for us to look in-depth at the approaches will be helpful to us.

@euanfergusson

This comment has been minimized.

Copy link
Contributor

euanfergusson commented May 26, 2017

will keep you in the loop

@euanfergusson

This comment has been minimized.

Copy link
Contributor

euanfergusson commented May 26, 2017

@patrickmj @zerocrates - has any of the discussions so far focused on how pages and/or interaction with the api will be handled ?

@hajoki

This comment has been minimized.

Copy link

hajoki commented May 26, 2017

Sure, I uploaded the theme I use: https://github.com/hajoki/istanbul

@patrickmj

This comment has been minimized.

Copy link
Member Author

patrickmj commented May 26, 2017

@euanfergusson not a lot on those fronts, though I suspect that API considerations will just pass along all data available with the language codes where they exist.

@zerocrates zerocrates removed this from the May 30 milestone May 30, 2017

@euanfergusson

This comment has been minimized.

Copy link
Contributor

euanfergusson commented Jun 5, 2017

@patrickmj @zerocrates

quick request for the multilingual elements. Can we include the name of the language in the mo/po files. Looking at the Omeka files , the word "Deutsch" doesnt appear in the file anyway - meaning we need to manually translate the actual name of the Language.

Would be a lot easier if the file could effectively translate itself, this would make the creation of a language switching UI easier

@zerocrates

This comment has been minimized.

Copy link
Member

zerocrates commented Jun 5, 2017

The trick there is that for our translation platform, everything needs to be translating from the same English strings, so unless we want to have an ever-growing translation in each language of the name of every other language, we can't easily accomplish this (unless we cheat and make a "fake" source string which each language translates as its own name).

However, we have the same problem solved in Classic by just using an external source for the language strings. In Classic we have to use Zend's Locale component which is based on ICU data. The equivalent in S would be using PHP's intl support, so something like http://php.net/manual/en/locale.getdisplayname.php I'd imagine.

@euanfergusson

This comment has been minimized.

Copy link
Contributor

euanfergusson commented Jun 6, 2017

@patrickmj @zerocrates - shall look into that

Can we also get a en_GB translation set up at transfix ? (need to deal with your countries obsession with 'z' and inability to spell colour ;) )

@zerocrates zerocrates modified the milestones: June 12, June 26 Jun 12, 2017

@hajoki

This comment has been minimized.

Copy link

hajoki commented Jun 19, 2017

Hello everyone,
Can we have a bit of visibility about what is going on about Omeka S' way of dealing with multilanguage sites? @euanfergusson, do you have any idea of when your module could be ready?

At the moment, even with a multisite approach, I cannot have a clean multilanguage site because:

  • the strings enclosed in translate(); ?> display invariably in English
  • tags in all languages display all together.

Can we open the Transifex project to start translating the strings in translate()?
As for tags, I know @Daniel-KM is waiting to see the coming choices of Omeka S team to make changes in Folksonomy.

Thanks for your work and news!

@Daniel-KM

This comment has been minimized.

Copy link
Contributor

Daniel-KM commented Jun 19, 2017

On this subject: in fact, any content or module content may have a language (tags, comments, etc.). And the visitor should be able to switch from one language for the interface or for the metadata, independantly.

So it is rather a theme related question, but the value of the language may be saved as a specific value, or as a value managed widely in all Omeka.

@zerocrates

This comment has been minimized.

Copy link
Member

zerocrates commented Jun 19, 2017

The Transifex project for S is already open: https://www.transifex.com/omeka/omeka-s/

@zerocrates zerocrates modified the milestones: June 26, July 10 2017 Jun 26, 2017

@hajoki

This comment has been minimized.

Copy link

hajoki commented Jul 7, 2017

Thank you for the link, I requested the creation of Turkish and French and asked to join the team but I still cannot access to any translation, is there something I miss?

@zerocrates

This comment has been minimized.

Copy link
Member

zerocrates commented Jul 7, 2017

I'll see if there's something we need to fix over on the Transifex side, but at least some translations have been coming through

@zerocrates

This comment has been minimized.

Copy link
Member

zerocrates commented Jul 7, 2017

Let's try this: there are older preexisting "teams" for "French" and "Turkish (Turkey)". Can you try asking to join those instead?

@hajoki

This comment has been minimized.

Copy link

hajoki commented Jul 8, 2017

Of course I would love that, but I cannot find the access...
When going there https://www.transifex.com/omeka/omeka-s/, signing in, in the long list of languages first there was no French nor Turkish, that's why I tried "Request the language".
Now there are appearing but I could not enter in them, that's why I tried "Join the team"
but I did not change anything yet, do I miss something about the functioning of the site?

@zerocrates

This comment has been minimized.

Copy link
Member

zerocrates commented Jul 8, 2017

@hajoki I've manually added you to those two teams

@hajoki

This comment has been minimized.

Copy link

hajoki commented Jul 8, 2017

Perfect, now I can enter!

@zerocrates zerocrates modified the milestone: July 10 2017 Jul 10, 2017

@zerocrates zerocrates closed this Sep 8, 2017

@margari

This comment has been minimized.

Copy link

margari commented Nov 17, 2017

@Daniel-KM hello, I am trying to check out your installation (http://ifeaistanbul.net/omeka-s/ ), but it seems that is not working at the moment... or maybe it has another url?
I would like to have multilanguage sites and themes for my Omeka. Could you help me please?
Thank you :-)

@hajoki

This comment has been minimized.

Copy link

hajoki commented Nov 17, 2017

Hello @margari, yes sorry the installation has moved to http://archivis.ifea-istanbul.net
This installation uses 3 sites, one site per language, to present the same items and item sets, but also check out the new features of Omeka S (language parameter for a site, etc.) to see what suits you needs best. Feel free to write in Omeka forum to receive help from the community.

@margari

This comment has been minimized.

Copy link

margari commented Nov 17, 2017

Thank you so much!!

@jogogo2

This comment has been minimized.

Copy link

jogogo2 commented Jun 8, 2018

Hi, I want to create a multilingual site with Omeka S (Catalan, Spanish and English), with the ability of switch among languages easily.
@euanfergusson , will you realease your module when ready freely in order to be used by others? (like me), can you explain more in detail how it works?
I really will apreciate your help.
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment