Page 1 of 1

Textpipe log file does not support UTF-8 encoding

Posted: Fri Jun 07, 2019 1:15 am
by DFH
This can be divided into two separate observations:

1. Comment filters containing non-ANSI characters are logged as ????
2. Replace filters containing UTF-8 search text are not rendered as UTF-8.

The first example is

Code: Select all

Fix truncations & expansions of Ушод:
This gets logged as

Code: Select all

Fix truncations & expansions of ????:
The second example is with this replace list.

Code: Select all

Replace [Cонъ] with [Сонъ]
   [X] Match case
   [X] Whole words only
   [ ] Case sensitive replace
   [ ] Prompt on replace
   [ ] Skip prompt if identical
   [ ] First only
   [ ] Extract matches

   [ ] Process longest strings first
   [ ] Simultaneous search
   [ ] Log summary only
   [ ] Only log when a replace occurs

 Further search/replace list phrases (TAB format):
идолосu	идолосю
начальn	начальн
кирьдемсh	кирьдемсъ
Vменей	Именей
The log results are rendered badly as

Code: Select all

Info	2019-06-06 15:15:16	Cyrillic words with Latin letters:
Info	2019-06-06 15:15:16	1 replace(s) performed for exact match [Cонъ]
Info	2019-06-06 15:15:16	1 replace(s) performed for exact match [идолосu]
Info	2019-06-06 15:15:16	1 replace(s) performed for exact match [начальn]
Info	2019-06-06 15:15:16	1 replace(s) performed for exact match [кирьдемсh]
Info	2019-06-06 15:15:16	1 replace(s) performed for exact match [Vменей]
What can be done to improve Textpipe logging of non-Roman characters?

Re: Textpipe log file does not support UTF-8 encoding

Posted: Mon Oct 07, 2019 9:12 pm
by DataMystic Support
This is fixed in TextPipe 10.9

Re: Textpipe log file does not support UTF-8 encoding

Posted: Mon Mar 02, 2020 9:24 pm
by DFH
I've yet to examine a log file after updating to v11.4

David