Skip to content
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

Improved UI for adding content in (more than one) language. #918

Open
rosiel opened this issue Sep 4, 2018 · 2 comments
Open

Improved UI for adding content in (more than one) language. #918

rosiel opened this issue Sep 4, 2018 · 2 comments
Labels
Subject: Multilingual related to making Islandora multilingual. Consider also using metadata and Drupal tags Subject: User Experience Related to a user’s experience with the software. Type: use case proposes a new feature or function for the software using user-first language.

Comments

@rosiel
Copy link
Member

rosiel commented Sep 4, 2018

Pls tag: "Use Case" and "UI".

Following up on #808, which describes how multilingual content is represented internally and as Linked Data, I'd like to improve the ability for cataloguers/metadata folks to add content in multiple languages.

Example: We have a lot of works in English, but a few which are in other languages. I (metadata person) don't speak those other languages, but want to enter the titles properly including the titles in their original languages. But I don't want to translate the entirety of the metadata, and I don't want to have to read the Drupal UI in that language (which seems to be what happens when you add a translation).

The way that it currently works really feels like doing Web Content Translation - preparing a site to be read in a different language. It does not feel like "doing metadata" - adding strings to fields, with language information where necessary.

(based on discussion with @seth-shaw-unlv )

@seth-shaw-unlv
Copy link
Contributor

Currently Drupal content translation requires a user to enter a separate editor to translate content.

First we create the node:
A test article with a title and body.

Then we select the language we want to add:
Selecting a language to translate. Only English (default) and German are enabled.

Then we provide a translation in that language:
Article edit form for German.

Then we can see that node's translation by adding the language code in the URL (e.g. "mysite.example/de/node/1").
Viewing the article in German.

Ideally we would have a widget that allows adding multiple translations for a given field in a single form:
Form mock-up showing the field widget for "title" with two pairs of fields, each pair consisting of a language drop-down and a text field.

We would also need a formatter that could show all the translations for a field.

@Natkeeran
Copy link
Contributor

@rosiel Interface need not be translated to be able to translate fields. You can customize which fields need to be translated.

Drupal default multilingual feature set and behaviour is well thought out. The out of the box behaviour is useful in most of the common multi language use cases. We have that use case locally at UTSC, and for a community archive that I volunteer with.

I am good with supporting this use case as long as we don't break Drupal's powerful multilingual support structure.

@kstapelfeldt kstapelfeldt added Subject: Multilingual related to making Islandora multilingual. Consider also using metadata and Drupal tags Type: use case proposes a new feature or function for the software using user-first language. Subject: User Experience Related to a user’s experience with the software. and removed multilingual labels Sep 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Subject: Multilingual related to making Islandora multilingual. Consider also using metadata and Drupal tags Subject: User Experience Related to a user’s experience with the software. Type: use case proposes a new feature or function for the software using user-first language.
Projects
Development

No branches or pull requests

4 participants