Project

General

Profile

Feature #1907

Feature #1901: modify the conversion process to properly run on Windows

implement configurable control over the line termination characters used for both intermediate files and final output of the conversion process

Added by Greg Shah over 11 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
16.00 h
billable:
No
vendor_id:
GCD
version:

History

#1 Updated by Greg Shah over 11 years ago

See #1565 for some details. Today in Windows, the .java and .cache output files get only a 0x0A (UNIX/Linux line end) instead of 0x0D0A (Windows line end). Some of the intermediate outputs do get the proper 0x0D0A when created on Windows, but all outputs need to be checked.

The p2j.cfg.xml should provide control over the exact line end used, independent of the system on which the conversion process is running. Today, for example, the intermediate outputs get the conversion platform's line end characters. But what if we run conversion on Linux and want Windows line ends because we will be maintaining the code on Windows? The intermediate and final outputs all should have configurable line ends.

By default, output everything with the conversion system's line ends. But then accept overrides and honor them everywhere.

#2 Updated by Greg Shah over 11 years ago

  • Parent task set to #1901

#3 Updated by Greg Shah over 7 years ago

  • Target version deleted (24)

Also available in: Atom PDF