Get help with installation and running here.
Moderators: DataMystic Support , Moderators , DataMystic Support , Moderators , DataMystic Support , Moderators
dfhtextpipe
Posts: 983 Joined: Sun Dec 09, 2007 2:49 am
Location: UK
Post
by dfhtextpipe » Tue Feb 26, 2019 2:49 am
TextPipe replaces each non-ANSI character of the input filename by U+FFFD REPLACEMENT CHARACTER.
This is most undesireable, especially for non-Roman scripts.
But even for accented ASCII letters it does this, so it's a critical limitation on it's capabilities.
Example: Input file:
became output file
Is there even a suggested workaround?
David
David
DataMystic Support
Site Admin
Posts: 2229 Joined: Mon Jun 30, 2003 12:32 pm
Location: Melbourne, Australia
Contact:
Post
by DataMystic Support » Mon May 06, 2019 1:51 pm
Hi David,
Is this with 10.7.2? We have worked to progressively remove any such limitations, so if you can provide an example of where it still lurks, we will take care of it.
Thanks,
Simon
dfhtextpipe
Posts: 983 Joined: Sun Dec 09, 2007 2:49 am
Location: UK
Post
by dfhtextpipe » Tue May 07, 2019 6:15 pm
Given the date I wrote the above, it's almost certainly 10.7.2
David
David
dfhtextpipe
Posts: 983 Joined: Sun Dec 09, 2007 2:49 am
Location: UK
Post
by dfhtextpipe » Fri Jun 07, 2019 1:21 am
There's nothing special about my filter.
It only needs an input filename with (eg) accented letters to test it.
Any filter would do, even a null filter where the only change is to the output file extension.
And I'm sure that you can easily rename any suitable input file so that in Windows the filename contains an accented letter or two.
David
David
dfhtextpipe
Posts: 983 Joined: Sun Dec 09, 2007 2:49 am
Location: UK
Post
by dfhtextpipe » Mon Mar 02, 2020 9:41 pm
Not yet tested the advised improvement.
David
David