Feature Wiki

Information about planned and released features

Tabs

Help on Additional Languages

It was a prerequisite that ILIAS can handle several help packages. This prerequisite was fulfilled with ILIAS 9. 

1 Initial Problem

The help is only presented in German. ILIAS cannot offer the Help File in the language selected by the user if it is other than German. 

2 Conceptual Summary

  • Imported Help Packages have a language property, set upon import.  
  • ILIAS should present Help in the language the user has selected, if there is a help package in that language. 
    • The online Help Package has a master language A and one or more translations B. 
    • ILIAS presents to the help in master language A to all users that set their user language to A
    • ILIAS presents to the help in translation language B to all users that set their user language to B. 
  • ILIAS presents the help in language B to all users that set their user language to C, D. This needs a control to be implemented. 

Note: This feature reuest does not deal with actually translating the file or the process of translation. See Process for Translating the Online Help

3 User Interface Modifications

3.1 List of Affected Views

  • Administration > System Settings and Maintenance > Help System

3.2 User Interface Details

Mock-up

3.3 New User Interface Concepts

No new interface elements will be used. The legacy table will be migrated to a KS ordering table.

3.4 Accessibility Implications

No accessibility issues foreseen using the KS elements. 

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

5 Privacy

No additional personal data will be stored in the service. Data stored in user object will be used.  

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

  • Author of the Request:
  • Tödt, Alexandra [atoedt]
  • Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
  • Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

9 Discussion

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}
  • {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.

Last edited: 23. Jun 2025, 11:23, Tödt, Alexandra [atoedt]