ARTS PDF Split Pro™ FAQ

1. How do I split using control files?
2. I'm using the ARTS PDF Split Pro GUI with Windows NT but can't seem to select a file to split. What is wrong?
3. I'm using the extracttext command on my PDFs, however no text is being extracted.
4. I've drawn a rectangle over my text using ARTS PDF Split Pro Assistant, but the text isn't being recognized by Split Pro. Why is this?
5. When using the "Show Text as ARTS PDF Split Pro sees it" function the text appears as garbage rather than legible words.
6. I am having a problem with this ARTS product and it is not covered in this FAQ. What can I do?

How do I split using control files?

Control Files are a handy way to specify which sections of a pdf need to be split, and what each split's filename is to be. ARTS PDF Split Pro control files use a tab-delimited text file format to dictate where the file should be split, and what the split files should be called. The tab-delimited format can defined by:

[Page range] <tab> [FileName.pdf]

An example of a tab-delimited text file is below:

1-10	FirstSplitFragment.pdf
12,22,32	SecondSplitFragment.pdf
50	ThirdSplitFragment.pdf
55,57-59	FourthSplitFragment.pdf

PAGE RANGE: The 'Page range' section of the control file can be specified by either:

• A single page number, (e.g. 28)
• Single pages separated by a comma, (e.g. 1,4,7)
• A page range, (e.g. 1-10)
• Or a combination the above options, (e.g. 1, 5-9)

Full Path Control files

When splitting by "Control File - Full path", simply include the full file path as well as the filename. For example:

9	C:\SplitProFiles\Test\Fragment2.pdf

This would split Page 9 of the source PDF to the file path C:\SplitProFiles\Test, under the name of Fragment2.pdf.

COMMON MISTAKES WHEN CREATING CONTROL FILES

1. Using spacing made from the spacebar instead of tab spacing. Split Pro will ignore normal spacing, so if you have used spaces to separate the control file instructions they will not be processed.
2. Using commas instead of tabs to delimit the file. Split Pro only examines commas to determine which pages are split. If a comma delimited file (*.csv) is used it will not work.
3. Having more than one command per line. If more than one split command is on the same line, only the first one will be processed.
4. Forgetting to put the '.pdf' in the filename. Split Pro will still create a file, but this file will not have any extension, and a '.pdf' will need to be added before it is viewable in Acrobat.

I'm using the ARTS PDF Split Pro GUI with Windows NT but can't seem to select a file to split. What is wrong?

This is due to an older version of the Windows common control that does not allow individual files to be displayed. The required version of Windows common control came shipped with Internet Explorer 4.01, however as this is no longer available to download, please use the following remedy.

You can run Internet Explorer 6 from the command-line to force the Active Desktop update which includes the newer shell functionality. In the directory IE6Setup.exe is located, run this from the command-line:

IE6Setup.exe /C:"ie6wzd /e:IE4Shell_NTx86 /I:Y"

I'm using the extracttext command on my PDFs, however no text is being extracted

ARTS PDF Split Pro v1.20 contains a bug causing the extracttext commands to fail. If you're using a version before v1.22 of ARTS PDF Split Pro, please ensure you are specifing the file to extract text to using the extracttextfilename command.

Contact our support team to update your copy of ARTS PDF Split Pro to the latest version.

I've drawn a rectangle over text in my PDF using ARTS PDF Split Pro Assistant, but the text isn't being recognized by Split Pro. Why is this?

ARTS PDF Split Pro reads text from the beginning of a text run. You have to ensure your rectangle is covering the beginning of the run of text.

The start of text runs on your PDF can be viewed by selecting 'Show Run Start' from ARTS PDF Split Pro Assistant in the Acrobat Plug-ins menu. More information on text runs can be found in the ARTS PDF Split Pro manual.

When using the "Show Text as ARTS PDF Split Pro sees it" function the text appears as garbage rather than legible words.

It's likely that the font encoding used in the document is not supported by ARTS PDF Split Pro.

1. ARTS PDF Split Pro 2.0 supports four basic methods of text encoding:
   • StandardEncoding.
   • WinAnsiEncoding - encoding defined by Windows systems.
   • MacRomanEncoding - encoding defined by Mac systems.
   • PDFDocEncoding - encoding defined by PDF format.
   Note: A fifth basic encoding named MacExpertEncoding also exists. This encoding is slightly different from MacRomanEncoding. ARTS PDF Split Pro 2.0 does not support MacExpertEncoding, as this is rarely used.
2. ARTS PDF Split Pro 2.0 supports Unicode font encodings. Using Unicode, characters that are not derived from the typical Roman character set are supported (Slovak, Japanese, Chinese, Russia, Arabic and special mathematic characters for example).
3. ARTS PDF Split Pro 2.0 doesn't support encoding types like Identity-H, Identity-V, and more.
4. Custom font encodings are not supported by ARTS PDF Split Pro. PDF Creation applications can define their own font encoding. We do not support these encodings, as we don't have the encoding table for this custom font. In order to rectify the solution, please check the encoding settings used by the PDF creation application and change it to an encoding type supported by ARTS PDF Split Pro, or contact the product vendor for information on how to do this.

I am having a problem with this ARTS PDF product and it is not covered in this FAQ. What can I do?

• Visit our ARTS PDF Forum to talk with ARTS PDF tech support and other ARTS PDF product users. Search the existing discussions and/or post your own questions. Each ARTS PDF product has it own dedicated discussion area.
• Contact our support team. You will receive a reply ASAP.