New line characters are a bit problematic. This is because some platforms use Carriage Return character (CR, 0D), some platforms Line Feed character (LF, 0A), and some combination of them. The following table contains the possible combinations:
|LF||Unix and Unix-like systems, Linux, AIX, Xenix, Mac OS X, BeOS, Amiga, RISC OS|
|CR||Mac OS through version 9 and Apple II family|
|CR+LF||Microsoft Windows , DOS, CP/M, MP/M|
|LF+CR||Currently no platform uses this combination|
Sisulizer always keep the original new line encoding. This means if the original file uses LF the localized file also uses LF. This works even case by case. If the original data uses in some places LF and in some other places CR the localized file contains the same encoding at the same place as in the original data. The only exception is the situation where the original data does not contain any new lines but the translator has entered a new line. Then the default encoding is used. Use the Encoding sheet of the source dialog to set the default new line. The default value is CR+LF.
Normally you should not enter more new lines as the original data has but Sisulizer does not prevent it because you might need it in some situations. However Sisulizer has a new line validation that is going to warn you if the translation contains different amount of new lines as the original data.
Sisulizer's editing sheet shows new line visually using mirrored P sigh (just like MS Word). This character is replaced with the correct new line encoding when the localized items are created.