Re: [TCLCORE] TIP 716 ready for comments

[<apn...@ya...>]

Harald,

 

It *appears* from the output you are passing UTF-8 data to the DLL which is expecting cp1252 or similar. 

 

For example,

 

% set x 1AÄÖÜäöü

1AÄÖÜäöü

% set utf [encoding convertto utf-8 $x]

1AÃÃÃäöü

% encoding convertfrom cp1252 $utf

1AÄÖÜäöü

 

Which is the output you are seeing. My *guess* (because it works on Tcl8) is you are using one of the Tcl encoding routines which default to [encoding system] (utf-8) and passing that string to the DLL. Note this has not changed in TIP 716 to maintain 9.0 compatibility.

 

Can you elaborate on how you are passing data? I would like to resolve as many of these encoding issues on Windows as we can, whether they relate to the manifest/716 or not, before the next patchlevel.

 

/Ashok

 

 

 

 

-----Original Message-----
From: Harald Oehlmann <har...@el...> 
Sent: Wednesday, April 16, 2025 1:16 AM
To: apn...@ya...; tcl...@li...
Subject: Re: [TCLCORE] TIP 716 ready for comments

 

Am 14.04.2025 um 16:54 schrieb  <mailto:apn...@ya...> apn...@ya...:

> Harald,

> 

> Could you try the tip-716 branch to see if fixes your print dll umlaut 

> issue?

Unfortunately, my dll with A-suffix API prints:

 

1AÄÖÜäöü

 

for 8.6 and

 

1AÄÖÃoeäöü

 

for 9.0 and TIP715 branch

 

8.6 was build with MS.VC 6 32 bit

9.0 was build with VS 2022 32 bit

 

Sorry,

Harald