However, WarpIN's Unicode support is totally transparent to the user:
CODEPAGE
setting in CONFIG.SYS, which
is 850 on most systems. This ensures that all file names etc. will always be
processed with the user's default codepage.
However, to make sure that WarpIN's file operations will keep working even if the user chooses to change his default code page (between package installation and de-installation), it is strongly recommended that package creators never use non-ASCII characters (above ASCII 127) in the packages' file names. Otherwise file verification and de-installation of WarpIN might fail if the user chooses to alter the system code page at one point. (But then this is a general problem with OS/2 that WarpIN cannot easily fix.)