DataMystic

Some filters are described thus:

This routine is ANSI-aware (handles foreign character sets).

To me, such a brief description is rather inadequate. It gives no indication of what happens when
(a) some or all of the Unicode input text is beyond ANSI?
(b) the input text contains hidden Unicode characters?

Example filters: UPPERCASE, lowercase, Title Case, Sentence case, tOGGLE cASE, raNDoM cASe.

Three of those six filters do not have the tick box option for Unicode (UTF-16LE).
Was this omission an oversight?

Moreover, as character case can be locale-sensitive, why is there no mention of the fact in the help?

David

Hi David,

I hope this helps, but I suspect it will lead to more confusion:

UPPERCASE, lowercase :

- To make the conversion, the function uses the current language selected by the user in the system Control Panel. If no language has been selected, TextPipe uses the Windows internal default mapping. The conversion is made based on the code page associated with the process locale.

Title Case, Sentence case, tOGGLE cASE, raNDoM cASe :
- This routine calculates a table of upper and lower case letters on TextPipe startup, and this determination is based on the semantics of the language selected in Control Panel.

This has been added to the help file.

Hi Simon,

I guess it helps others a bit to learn that, but it doesn't advance the capabilities of the TextPipe program.

The bottom line is that all letter case operations depend on the language selected in the Regional and Language Options applet of the Windows Control Panel (or the equivalent applet name in some versions of Windows).

Also, you have still not responded to my observation:

Three of those six filters do not have the tick box option for Unicode (UTF-16LE).
Was this omission an oversight?

David

Hi David - sorry, I missed that.

Yes - we can make sure that all 6 are supported in the next release.

Great!