Bug 494049

Summary: Tellico 4.0: Accented and special characters problem in Tellico report editing
Product: [Applications] tellico Reporter: goupilcom <goupilcom>
Component: generalAssignee: Robby Stephenson <robby>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: 4.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Tellico 4.0: Accented and special characters problem in Tellico report editing

Description goupilcom@gmail.com 2024-10-03 16:31:14 UTC 
Created attachment 174371 [details]
Tellico 4.0: Accented and special characters problem in Tellico report editing

SUMMARY
Accented and special characters problem in Tellico report editing

STEPS TO REPRODUCE
I'm French and create HTML pages from Tellico (for the https://www.lebottindesjeuxlinux.tuxfamily.org/en/online/lights-on/ site) containing an English part and a French part. 

Since version 4.0 (installed yesterday from Linux Manjaro), accented and special characters are displayed correctly in entries (examples: “🕊️🎁 Libre with Free assets” or “(données gratuites) orienté multijoueur”) but not in entry lists (examples “ðï¸ð Libre with Free assets” or "(données gratuites) orienté multijoueur").

SOFTWARE/OS VERSIONS
Linux/Manjaro/Cinnamon/Xorg

ADDITIONAL INFORMATION
These special characters are displayed correctly in the entries, so I think the problem comes specifically from Tellico.
I use the format fr_FR.UTF-8

I've used the “Bibliography” publication template to rule out any problems with my personal publication templates.
Comment 1 Robby Stephenson 2024-10-03 18:32:33 UTC 
I believe this is fixed in 4.0.1. Please let me know if not.

*** This bug has been marked as a duplicate of bug 493180 ***
Comment 2 goupilcom@gmail.com 2024-10-05 16:43:18 UTC 
(In reply to Robby Stephenson from comment #1)
> I believe this is fixed in 4.0.1. Please let me know if not.
> 
> *** This bug has been marked as a duplicate of bug 493180 ***

Yes, the problem has been solved with version 4.0.1.
Thank you very much.