View Issue Details

This bug affects 1 person(s).
 8
IDProjectCategoryView StatusLast Update
19891Feature requestsTranslationpublic2025-01-15 13:01
ReporterMazi Assigned Toc_schmitz  
PrioritynoneSeverity@70@ 
Status assignedResolutionopen 
Summary19891: French (Canada) available at translation tool but not able to select as survey language
Description

At https://translate.limesurvey.org/projects/limesurvey-6/ the language "French "Canada) is listed. But tbis language is not available as survey language at the general settings of a survey.

Steps To Reproduce

Steps to reproduce

Search for French (Canada) at the available survey languages.

Expected result

See the language show up there.

Actual result

This language is not available.

TagsNo tags attached.
Bug heat8
Story point estimate
Users affected %

Relationships

related to 09649 new Plugin event : update "default core string" 

Users monitoring this issue

There are no users monitoring this issue.

Activities

DenisChenu

DenisChenu

2024-12-16 09:18

developer   ~81631

I have a contact with a French Canadian company : they tell me it's not needed. Same for French Belgium and French Switzerland.

Mazi

Mazi

2024-12-16 10:14

updater   ~81632

Well, if we have the language available, we should also list it.

DenisChenu

DenisChenu

2024-12-16 11:23

developer   ~81634

Well, if we have the language available, we should also list it.

No !!!
1 translation only ! If it's not needed : do not give work to translator !
https://translate.limesurvey.org/projects/limesurvey-6/fr-ca/default/?filters%5Bstatus%5D=current

If we can not have something like this :

  • String came FR-ca translation if translation exist
  • Else string came from FR translation if exist
  • Else code
Mazi

Mazi

2024-12-16 11:38

updater   ~81635

@DenisChenu, I agree to that this would be a nice solution.
And as long as there is just 1 (!) string translated for French (Canadian) I think we can easily remove the language.

What was the explanation of your customers for stating that this language is not actually needed? Is the default "French" sufficient?

DenisChenu

DenisChenu

2024-12-16 12:02

developer   ~81636

Is the default "French" sufficient?

According to my client some year ago : yes.

If your client need the translation : they know the string to update.

Mazi

Mazi

2024-12-17 15:21

updater   ~81649

@DenisChenu, it turns out that this is not really related to error messages or button labels which are usually taken from the translation files. My customer (big, global company) told me that they especially need to be able to have different question texts for French and French Canadian because terms are different at these languages and they receive specific, different question texts for that language.

So after that feedback my conclusion is that we should add that language to the available languages!
I will also ask them if they can contribute by finishing the translation (actually I think 95% of the texts can be taken from the French translation).

Mazi

Mazi

2025-01-07 11:08

updater   ~81749

@DenisChenu, the user confirmed that they mostly need the French Canadian language for having different question texts. So that is the main purpose of such a fix.
As for the translation: If we could just use the French translation as a base, then the user agreed to provide updated translations for cases at which the phrasing is slightly difficult. -> Would that be possible to add French text as a starting point?

DenisChenu

DenisChenu

2025-01-07 11:54

developer   ~81752

I think it can be best to have a "Specific language" system for some survey.

For this issue/feature : ping @c_schmitz

c_schmitz

c_schmitz

2025-01-08 15:57

administrator   ~81779

There is currently no inheritance system for a case like this.
At some point Glotpress (the translation website we use) was testing this in beta (named 'Locale variants', but then decided to drop it right before release and it was never revived - see https://glotpress.blog/2017/07/12/glotpress-and-locale-variants/

LimeSurvey would need a translation inheritance system, lets call it 'Custom language', where you can basically inherit an existing language and apply a few custom translations on top.
But that is quite some work needed.

DenisChenu

DenisChenu

2025-01-08 16:10

developer   ~81781

LimeSurvey would need a translation inheritance system, lets call it 'Custom language', where you can basically inherit an existing language and apply a few custom translations on top.

I like this idea !

But that is quite some work needed.

Oh yes ! And potential issue !

Mazi

Mazi

2025-01-09 09:26

updater   ~81790

Such an easy to adapt translation system would be really nice. But I also have to admit that it requires quite some effort and only few users will make use of it.
In this case the user requires the additional language not for translating error messages into a rather similar language but to be able to have custom question and answer texts within the survey. For that use case it would be very helpful if the language would get added. And we already have the translation files available. So could this be added to the core if we send a pull request?

DenisChenu

DenisChenu

2025-01-09 09:37

developer   ~81791

I already see this "Feature request" : allow Survey with same language twice on forum. Maybe 2 times.

bismark

bismark

2025-01-15 11:36

reporter   ~81819

https://github.com/LimeSurvey/LimeSurvey/pull/4135

Mazi

Mazi

2025-01-15 12:45

updater   ~81822

@DenisChenu, could you please review this minor feature?
Thanks!

DenisChenu

DenisChenu

2025-01-15 12:49

developer   ~81823

Still unsurfe on decision : we really need Language copy po/mo file without need of update ?

Mazi

Mazi

2025-01-15 13:01

updater   ~81824

@DenisChenu, @c_schmitz: Even if there is no real need to update the translation since "fr" and "fr-ca" are pretty similar, there are users which want to be able to have their own fr-ca welcome or email or question texts. For many other languages and variations we are offering this and it doesn't really cost us a lot adding this language for the mentioned purpose.

Issue History

Date Modified Username Field Change
2024-12-14 16:33 Mazi New Issue
2024-12-16 09:18 DenisChenu Note Added: 81631
2024-12-16 09:18 DenisChenu Bug heat 0 => 2
2024-12-16 10:14 Mazi Note Added: 81632
2024-12-16 10:14 Mazi Bug heat 2 => 4
2024-12-16 11:23 DenisChenu Note Added: 81634
2024-12-16 11:38 Mazi Note Added: 81635
2024-12-16 12:02 DenisChenu Note Added: 81636
2024-12-17 15:21 Mazi Note Added: 81649
2025-01-07 11:08 Mazi Note Added: 81749
2025-01-07 11:54 DenisChenu Note Added: 81752
2025-01-08 15:57 c_schmitz Note Added: 81779
2025-01-08 15:57 c_schmitz Bug heat 4 => 6
2025-01-08 16:10 DenisChenu Note Added: 81781
2025-01-08 17:19 c_schmitz Project Bug reports => Feature requests
2025-01-09 09:26 Mazi Note Added: 81790
2025-01-09 09:37 DenisChenu Note Added: 81791
2025-01-09 09:39 DenisChenu Relationship added related to 09649
2025-01-15 11:36 bismark Note Added: 81819
2025-01-15 11:36 bismark Bug heat 6 => 8
2025-01-15 12:45 Mazi Note Added: 81822
2025-01-15 12:49 DenisChenu Note Added: 81823
2025-01-15 12:49 DenisChenu Assigned To => c_schmitz
2025-01-15 12:49 DenisChenu Status new => feedback
2025-01-15 13:01 Mazi Note Added: 81824
2025-01-15 13:01 Mazi Status feedback => assigned