Environment variable @inputPath and accented letters?

[dfhtextpipe]

I found a strange problem with the Output filter when using the following as the Output path:

Code: Select all

@inputPath..\USFM

If part of the input path happens to include any non-ASCII letters (e.g. with an accent, as in the Spanish name Rubén ),
the output path is not properly implemented because these non-ASCII letters get garbled.

TextPipe created such a garbled path for the output files, and even also created an empty folder therein with the same name as the input folder.

This may be a Windows issue, but there's no warning about it in the relevant help page for TextPipe.

David

[DataMystic Support]

Thanks David - this is a TextPipe issue that we have fixed ready for 10.7

[dfhtextpipe]

Hi Simon,

TextPipe 11.6 still has an issue with other non-ASCII characters in the @inputPath.

Input filename KJV.diatheke.plus.psalm.titles.¶.txt
was changed to KJV.diatheke.plus.psalm.titles.�.ligatures.txt
where I had the Output Folder as @inputPath\Derived

Please review the fix and see if it can be further expanded to cope with any Unicode characters valid within the Windows file system.

Please also check that the advised fix in 10.7 wasn't inadvertently reverted or overlooked.

Best regards,

David

[DataMystic Support]

Hi David,

I am not seeing this, can you please provide more details/test files via email?

Input file: C:\Aemail\المؤتمر الدولي العاشر ليونيكود\外销装箱明细3-15.txt
Output folder: @inputpath@\derived
Generated output file: C:\Aemail\المؤتمر الدولي العاشر ليونيكود\derived\外销装箱明细3-15.txt

Incidentally with footer text appended:

--date 20200613072627--
--input file[外销装箱明细3-15.txt]--
--full input file[C:\Aemail\المؤتمر الدولي العاشر ليونيكود\外销装箱明细3-15.txt]--
--input path[C:\Aemail\المؤتمر الدولي العاشر ليونيكود\]--

[dfhtextpipe]

Please try it with also the following:

Change extension to .ligatures@inputExtension

That's the trigger!

It's a feature that I use regularly!

I can readily email you stuff if this doesn't help determine root cause.

David

[DataMystic Support]

Thanks - I can see the issue and we're working on a fix.