New i18n model for Texts

IMAGINARY / imaginary-web

Imaginary website (Drupal 7)

GNU General Public License v2.0

3 stars 0 forks source link

New i18n model for Texts #119

Open elondaits opened 8 years ago

elondaits commented 8 years ago

Texts (BG Materials and Snapshots) should have the following behavior regarding i18n:

Each text node can have several associated PDFs.
- Each PDF corresponds to a different language.
- Available languages include but are not limited to the ones the site is translated in.
- It can have associated source files (another file attach).
The PDF viewer shows the PDF in the language the site is being viewed in, or the default / original file.

(add any extra requirements in the comments below so the new data model contemplates it).

elondaits commented 8 years ago

@ppxasjsm commented in another issue:

At the moment it is not possible to have multiple language PDFs uploaded for the Snapshots. This is problematic since we are now translating more and more of the snapshots and it would be very useful if there were at least an option to have multiple languages available for each snapshot, especially since a basic translation of title and abstract is possible.

elondaits commented 8 years ago

Also see #98 , in which @andreasdanielmatt commented:

I was just about to link to a text (crystal and maths) in the background material section, (http://imaginary.org/de/node/833) from a German web page. Would it be possible to show the German version of the PDF when German is selected? (now always the English one is shown, and the German pdf is small below). This also applies for other languages (maybe one can mark the main pdf for the respective language, default can be English).

ppxasjsm commented 8 years ago

We will be getting a few more translations in the coming months, It would be good if this was up and running soon.

elondaits commented 8 years ago

See if the behavior I listed in the first comment of this page is accurate or you need something else or different.

The key point of the described functionality is that we should be able to load and show translations even for languages that are not those in which the website itself is translated. If the site is being seen in, for example, korean, the korean PDF (if available) should be shown... but a translation in hebrew could be made available for download (or visualization, ideally) as well.