Path: ...!weretis.net!feeder8.news.weretis.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Ralf Fassel <ralfixx@gmx.de>
Newsgroups: comp.lang.tcl
Subject: Re: ANNOUNCE: Excel file format reader/writer package OOXML 1.9 released
Date: Thu, 05 Dec 2024 15:46:57 +0100
Lines: 14
Message-ID: <ygamsha89we.fsf@akutech.de>
References: <vicj0q$10cg3$2@dont-email.me>
	<23d440f2cbb17d78d4e5446b910ef11d@www.novabbs.com>
	<vis7nh$1idt0$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain
X-Trace: individual.net Jb3QCpd87DK+MBtn6bWgwQvURY36qHaVj196oyvFYKYrvATkM=
Cancel-Lock: sha1:Q9ccuqJtYn6gOlq1EwNkDcmL5/0= sha1:sc9w9pHhzJ28tT2LKCBeEt4Z7ck= sha256:dyNp1BnBJgWItbJ/mBiMMogyafw66vrJg9z/Eow1E40=
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Bytes: 1516

* Harald Oehlmann <wortkarg3@yahoo.com>
| About the "Umlauts". This should be an internal issue. The outputted
| data is utf-8 afaik. But this is critical.
| I have tested Umlauts when reading and that works.
| I had to add an "encoding convertfrom utf-8 $data" to make it work.

Wouldn't that not also depend on how exactly the TCL script is sourced?
I.e. an tcl script containing literal utf-8 data (not the \uxxxx form)
on Windows with the default system encoding (eg cp1252) would require an
explicit -encoding utf8 for the 'source' command to read it properly.
The OP did not specify what OS he was on, and how the tcl script
containing utf-8 data was sourced...

R'