View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
19283 | Bug reports | Documentation | public | 2023-11-27 09:26 | 2024-11-19 18:14 |
Reporter | Mazi | Assigned To | tibor.pacalat | ||
Priority | none | Severity | partial_block | ||
Status | closed | Resolution | fixed | ||
Product Version | 6.3.x | ||||
Summary | 19283: Manual page about adding custom translations is missing | ||||
Description | At Limesurvey we have DB tables lime_source_message and lime_message. These allow adding your own translation for certain default texts. It is considered a very useful feature because often you want to adjust some of the existing translations for a certain customer only. Unfortunately, there is no documentation at all regarding these tables and how to add your own translation. Please add this so others can benefit from the feature as well. | ||||
Tags | No tags attached. | ||||
Bug heat | 8 | ||||
Complete LimeSurvey version number (& build) | 5.6. | ||||
I will donate to the project if issue is resolved | No | ||||
Browser | |||||
Database type & version | MySQL | ||||
Server OS (if known) | |||||
Webserver software & version (if known) | |||||
PHP Version | 8.1 | ||||
related to | 14782 | closed | DenisChenu | Feature requests | Possibility to override single translations |
related to | 17163 | closed | DenisChenu | Feature requests | Allow translation by DB |
@tibor.pacalat: This feature seems to exist since LS 5.x. Can you discuss within the team how we can make sure we have some documentation for Limesurvey users on how to use this useful feature? |
|
PR with comment : https://github.com/LimeSurvey/LimeSurvey/pull/2213#issuecomment-1016675160 Negotiated on discord. |
|
ping @ollehar and @tibor.pacala t: I'm OK to create tge manual page AND/OR a micro core plugin with 4 inputs
(The except via DB : no way to know current translation, can be added if you want in future) |
|
I would love to see this as a core feature for Limesurvey since this is very helpful for some more special surveys. E.g. some customer want to adjust the registration screen to have "Access key" or "Code" instead of "Token" or add further details about the registration process. Would it be possible to handle translation adjustments not only on global level but also have survey specific adjustments? E.g. globally I replace "Enter your token" with "Enter your code" but for survey A I can have "Enter the access key provided by your teacher"? |
|
It's not included in this feature. It's a new feature. BUT : you can do it easily via SurveyTheme here (and add needed translation in DB) |
|
I think we then need some details for "do it easily via SurveyTheme here (and add needed translation in DB)" at the manual as well because currently I have no idea how this should work. |
|
(Manual page can explain this) |
|
Waiting decision about
|
|
Ok so decisions are:
|
|
Thank you :) |
|
https://manual.limesurvey.org/Custom_translation I think we can add the link at https://manual.limesurvey.org/index.php?title=Not_categorized_and_advanced_features&action=edit and https://manual.limesurvey.org/LimeSurvey_Manual |
|
|
|
Thank you ! |
|
@DenisChenu I added the links as you suggested and made small grammar corrections on that page as well. |
|
Yes, it's my Thank you ;) Do you know why we have «This page contains changes which are not marked for translation.» ? |
|
No idea to be honest, maybe @c_schmitz knows more? |
|
Text changes need top be approved before translation. It is done,. now- |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2023-11-27 09:26 | Mazi | New Issue | |
2023-11-27 09:27 | Mazi | Note Added: 78717 | |
2023-11-27 09:27 | Mazi | Bug heat | 0 => 2 |
2023-11-27 15:44 | DenisChenu | Note Added: 78738 | |
2023-11-27 15:44 | DenisChenu | Bug heat | 2 => 4 |
2023-11-27 15:45 | DenisChenu | Relationship added | related to 14782 |
2023-11-27 15:46 | DenisChenu | Relationship added | related to 17163 |
2023-12-06 10:53 | DenisChenu | Note Added: 78886 | |
2023-12-06 10:57 | Mazi | Note Added: 78887 | |
2023-12-06 11:26 | DenisChenu | Note Added: 78888 | |
2023-12-06 11:39 | Mazi | Note Added: 78889 | |
2023-12-06 11:51 | DenisChenu | Note Added: 78890 | |
2023-12-06 11:52 | DenisChenu | Note Edited: 78890 | |
2023-12-06 11:52 | DenisChenu | Note Edited: 78890 | |
2023-12-14 13:12 | ollehar | Severity | block => partial_block |
2024-04-29 08:20 | DenisChenu | Assigned To | => tibor.pacalat |
2024-04-29 08:20 | DenisChenu | Status | new => feedback |
2024-04-29 08:20 | DenisChenu | Note Added: 80031 | |
2024-04-29 13:59 | tibor.pacalat | Note Added: 80037 | |
2024-04-29 13:59 | tibor.pacalat | Bug heat | 4 => 6 |
2024-04-29 13:59 | tibor.pacalat | Assigned To | tibor.pacalat => DenisChenu |
2024-04-29 14:46 | DenisChenu | Note Added: 80040 | |
2024-05-16 18:12 | DenisChenu | Assigned To | DenisChenu => tibor.pacalat |
2024-05-16 18:12 | DenisChenu | Status | feedback => ready for code review |
2024-05-16 18:12 | DenisChenu | Note Added: 80123 | |
2024-05-16 18:12 | DenisChenu | Note Added: 80124 | |
2024-05-16 18:12 | DenisChenu | File Added: Capture d’écran du 2024-05-16 18-11-21.png | |
2024-05-22 16:12 | tibor.pacalat | Status | ready for code review => resolved |
2024-05-22 16:12 | tibor.pacalat | Resolution | open => fixed |
2024-05-22 16:16 | DenisChenu | Note Added: 80148 | |
2024-05-22 16:23 | tibor.pacalat | Note Added: 80149 | |
2024-05-23 09:26 | DenisChenu | Note Added: 80154 | |
2024-05-23 09:26 | DenisChenu | File Added: Capture d’écran du 2024-05-23 09-25-23.png | |
2024-05-23 10:08 | tibor.pacalat | Note Added: 80155 | |
2024-05-23 10:50 | c_schmitz | Note Added: 80156 | |
2024-05-23 10:50 | c_schmitz | Bug heat | 6 => 8 |
2024-11-19 18:14 | c_schmitz | Status | resolved => closed |