A single character text can result in a PDF file with 160 lines. Mojave still generates PDF according to the 1999 standard. And why extracted text is all over the place.
For your added security: the first to fix problems when your permissions go awry; the second to practise Unicode obfuscation.
Both apps have been notarized now, for added security protection, particularly when used in Mojave.
Trying to work with Unicode can be frustrating at times. Here’s an excellent free book with valuable practical tips for all users, and much more for linguists too.
Create and resolve Finder aliases from the command line, and convert Unicode strings into any of their normalised forms.
Apfelstrudel, which explores Unicode normalisation and string operations; Dystextia for obfuscating Roman text using spoofing; and Rosettavert for converting between text encodings.
If you’re not sure what a ZWJ is, then now’s the time to catch up. How Unicode emoji have made it impossible to count characters.
Tools for examining Unicode normalisation, converting between text encodings, and for obfuscating text using similar Unicode characters.
Which String.contains() variant should you use, and how can you give access to regex searching? More answers coded in Swift 3.1.
Apple now states that APFS will handle the problems of normalisation of file and folder names. At least in iOS 10.3.3 and macOS 10.12.6, due shortly.