French localization displays accented characters incorrectly

[b2bidev]

I work for Precisely, and our product B2Bi Sterling Integrator uses SmartClient 12.1.2024. The application supports localization through language-specific properties files, which are used by SmartClient to display the UI in the language selected by the browser.

For the most part, French localization works correctly. However, in one case, accented characters from a specific properties file are not displaying properly. In the attached screenshot, the yellow text renders correctly. This text comes from Filegateway_fr.properties, which is used to create the FG_i18n JavaScript object. That object is then referenced in SmartClient code like this:

//Vlayout containing Events
var arrivedFileEvents_VLayout = isc.VLayout.create({
name: "arrivedFileEvents_VLayout",
width:"45%",
visibility:"hidden",
height:"100%",
members:[
isc.Label.create({
contents:"<b><font color='#000000'>" + FG_i18n.ARRIVED_FILE_EVENTS + "</font></b>",
icon:"[SKIN]/FGimages/FileTxfr_23.png",
iconHeight:23,
iconWidth:35,
backgroundColor:"#EFEFEF",
padding:5,
height:1
}),
arrivedFileEvents_ListGrid
]
});

where :
Filegateway_fr.properties:ARRIVED_FILE_EVENTS=Événements de fichier arrivé

On the other hand, the green text comes from a different properties file, FGEventCodesi18n_fr.properties, which is loaded via the application classpath. That file contains:

119 # START NON-TRANSLATABLE
120 FG_0408.name=ArrivedFileStarted
121 # END NON-TRANSLATABLE
122 FG_0408.displayName=Fichier arrivé démarré OSAMA CHANGE ISO
123 # NLS_MESSAGEFORMAT_ALL
124 FG_0408.text=Le fichier arrivé a démarré.OSAMA CHANGE ISO
125 # NLS_MESSAGEFORMAT_NONE
126 FG_0408.description=Survient lorsqu'un fichier arrive dans File Gateway pour être acheminé

Despite verifying that FGEventCodesi18n_fr.properties is saved as either charset=ISO-8859-15 or charset=UTF-8, the accented characters still appear incorrectly in the UI (e.g., as black diamonds with question marks).

Do you have any ideas on what might be causing this? Could it be related to how the file is loaded or interpreted by SmartClient ?

Thanks,
Osama Qasqas

[Isomorphic]

You are changing the .properties file into a .js file, not SmartClient, so this is not a SmartClient problem.

Specifically, both the original and the .js file need to have the right encoding (generally UTF8) and you need to make sure that the response from your server when it serves the file says UTF8 (in the HTTP headers).

None of these steps are performed by SmartClient.