Feature Wiki
Tabs
Multi-lingual Text Templates for Mails
Page Overview
[Hide]1 Initial Problem
Text templates in the administration can be devised for specific contexts.
These Text Templates are not multi-lingual but they should be.
![](./data/docu/mobs/mm_97959/falsch.png?il_wac_token=ea780419ec08951121dfaf2684abcb4df0b7f873&il_wac_ttl=5&il_wac_ts=1725755432)
2 Conceptual Summary
User creates context and mail in language
- User selects a context and provides Title
- User writes subject and body in one language
- User changes language by view control
User selects and sends Mail from context
- User calls Mail template
- User selects language.
- ILIAS refreshes text with language and placeholder.
- User may edit Mail text and subject.
- If user changes languge selection, all Mail text is refreshed and changes are lost.
- User sends mail in selected language.
- Recipients do NOT get the Mail in their user language but in the language sent.
3 User Interface Modifications
3.1 List of Affected Views
- Administration > Communication > Mail > Text Templates > Add > two new forms
- Composing a mail using a mail template
3.2 User Interface Details
3.2.1 Creating a template for the first time
![](./data/docu/mobs/mm_97960/first.png?il_wac_token=ea780419ec08951121dfaf2684abcb4df0b7f873&il_wac_ttl=5&il_wac_ts=1725755432)
![](./data/docu/mobs/mm_98117/Edit_Text_in_Mail_Template.jpg?il_wac_token=ea780419ec08951121dfaf2684abcb4df0b7f873&il_wac_ttl=5&il_wac_ts=1725755432)
3.2.2 Using the template to send a mail
![](./data/docu/mobs/mm_97964/Send_Mail.png?il_wac_token=ea780419ec08951121dfaf2684abcb4df0b7f873&il_wac_ttl=5&il_wac_ts=1725755432)
3.3 New User Interface Concepts
{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }
3.4 Accessibility Implications
{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }
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
{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }
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: Mix, Eva [emix]
- Maintainer: Jansen, Michael [mjansen]
- 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
Mix, Eva [emix]: This feature request includes the idea to not be able to change the context once the template has been created. If this part of the feature request will be accepted it needs to be decided where the context is shown in existing templates.
Mix, Eva [emix]: It needs to be decided how/where multiligualism is activated. And how does the system behave if a language is selected while composing the mail for which no transtation exists.
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}
Privacy
Information in privacy.md of component: updated on {date} by {user} | no change required
Approval
Approved at {date} by {user}.
Last edited: 10. May 2023, 12:44, Mix, Eva [emix]