[Bug 43630] Altium Designer Installer - Richedit control shows rtf code instead of text

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=43630

Jeff D. Hanson <jhansonxi at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jhansonxi at gmail.com

--- Comment #4 from Jeff D. Hanson <jhansonxi at gmail.com> ---
Confirming on Wine 3.19 staging, Xubuntu 16.04 x86-64.

It affects several versions of the installer and the affected language differs.
 Changing to a  faulty language results in coded text, high CPU load, and large
memory usage.

https://s3.amazonaws.com/altium-install/Altium_Designer_14/AltiumDesignerSetup14_3_20.exe
https://s3.amazonaws.com/altium-release-manager/Altium_Designer_15/AltiumDesignerSetup_15_1_16.exe
https://s3.amazonaws.com/altium-release-manager/Altium_Designer_16/AltiumDesignerSetup_16_1_12.exe
https://s3.amazonaws.com/altium-release-manager/Altium_Designer_17/AltiumDesignerSetup_17_1_9.exe
https://s3.amazonaws.com/altium-release-manager/Altium_Designer_18/AltiumDesignerSetup_18_1_9.exe

Affects German and Japanese EULAs on v17.  

Affects English and Japanese EULAs on v14 and v15.

All EULA languages are normal on v16 and v18.

Files are located in user temp directory during installation.  Info from file
command (v17):

EULA_CHINESE.rtf:  Rich Text Format data, version 1, unknown character set
EULA_ENGLISH.rtf:  Rich Text Format data, version 1, unknown character set
EULA_GERMAN.rtf:   Rich Text Format data, version 1, unknown character set
EULA_JAPANESE.rtf: Rich Text Format data, version 1, unknown character set

All v17 files load in native LibreOffice without problems.

Some experimentation using the v15 and v17 German EULA RTF files showed that
the RTF files are what trigger the problem.  If I replace the German file on
the v15 installer with the v17 version then the problem occurs on v15.  If I
replace the German file on v17 with the v15 version then the problem does not
occur on v17.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.