DataMystic

Currently the Case conversion filters are only ANSI aware.

These filters are in need of a radical improvement to provide case conversion for all Unicode bicameral scripts.

A thorough overhaul is long overdue for this early feature of TextPipe.

The filter Remove multiple whitespace also converts tabs to spaces.

When this is all that occurs, the filter log is misleading when it has (eg):
This gives the false impression that nothing has been changed!

David

Hi Simon, I just observed a strange result after converting parts of a text file to sentence case . To illustrate it: 1st Corinthians, an introduction becomes 1St Corinthians, an introduction IMHO, the s in 1st ought not to be capitalised. Please review the definition of sentence case when a sentenc...

Still awaiting your response!!!!!!!!!!!!!!

Hi Simon,

Still awaiting your response!

Is there any further useful information that I could provide?
e.g. From the Windows registry?

Thanks Simon,

David

Hi Simon, Currently, there seems to be no straightforward means to add a suitable header to a single file output (join all input files together). We have two Add header filters: Add file header Add restriction header but neither of these does what's required on its own! The difficulty is accentuated...

Awaiting your response!

I don't know when I last used one, but I tried just now to apply a Context Menu option to a text file, only to discover that the whole TextPipe Windows Shell Extensions menu was no longer listed when I did a right click. Any suggestions as to what might have happened? The whole table is still availa...

As I use PCRE Perl Escape codes in a lot of my replace lists for TextPipe, I think I know what I'm talking about. 8) Also, btw, most ASCII characters never need to be converted to Perl Escape Codes for use in replace lists. Those should also be excluded if you do implement the suggestion as an inter...

Dear Simon, The outputs are not proper Perl Escape codes that would be recognised by a PCRE replace filter. For codepoints beyond \xFF the should be {braces} around each character code! e.g. ðñòóôõö÷øùúûüýþÿ ĀāĂ㥹ĆćĈĉĊċČčĎď 𐀀𐀁𐀂𐀃𐀄𐀅𐀆𐀇𐀈𐀉𐀊𐀋𐀌𐀍𐀎𐀏 should convert to \xF0\xF1\xF2\xF3\xF4\xF5\xF6\xF7\xF8\xF9...

No - that makes no sense to me! Perl Escape Codes for Unicode characters have a variable number of bytes, depending upon how each character is represented in UTF-8 . Squishing everything to 2 bytes would not work for their use in external character replacement list files (such as tab delimited), as ...

Hi Simon, For codepoints 00-FF (in the ANSI range), the leading 00 should be omitted, e.g. \x{00A0} becomes simply \x{A0} because these are single byte characters. Many UTF-8 byte codes are more than 2 bytes! e.g. ﾀ is \xEF\xBE\x80 And beyond the BMP , each Unicode character requires 4 bytes. So yes...

Thanks, Simon.

Happy New Year!

David

Hi Simon, A filter list would be somewhat unwieldy ! It would need to have 143859 entries - one for each named character in Unicode 13.0 . Given that the outputs are eminently calculable, it would be simpler (and surely much less effort) to design two suitable internal filters. And using formulae fo...